Why does a CRM need native WhatsApp?

A CRM is only as good as the conversations it captures. When WhatsApp lives on a rep's phone, the CRM loses:

• History: nobody else can see what was promised to the customer.
• Ownership: when a rep leaves, the conversations leave with them.
• Automation: deal stage changes, reminders and follow-ups can't trigger a WhatsApp message.
• Reporting: response times and message volume are invisible to managers.

Native WhatsApp fixes all four, and it is one of the few CRM features customers will happily pay extra for.

Three ways to add WhatsApp to a CRM

For CRMs that serve small and mid-sized businesses, the third option usually wins: customers keep the number their clients already know, onboarding happens inside your product, and your costs don't grow with message volume.

The data model: what to store in your CRM

Before writing any integration code, decide how WhatsApp maps onto your existing objects. A simple model that works for most CRMs:

Step by step: building WhatsApp into your CRM

// Node.js 18+
const PAT = process.env.WASENDER_PAT;
const API = "https://www.wasenderapi.com/api";

async function connectWorkspace(workspace) {
  const res = await fetch(`${API}/whatsapp-sessions`, {
    method: "POST",
    headers: {
      Authorization: `Bearer ${PAT}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      name: `CRM workspace ${workspace.id}`,
      phone_number: workspace.phone,
      account_protection: true,
      log_messages: true,
      webhook_url: `https://crm.example.com/webhooks/whatsapp/${workspace.id}`,
      webhook_enabled: true,
      webhook_events: ["messages.received", "messages.update", "session.status"],
    }),
  });
  const { data } = await res.json();
  return data.id; // save as workspace.wasender_session_id
}

app.post("/webhooks/whatsapp/:workspaceId", express.json(), async (req, res) => {
  if (req.get("X-Webhook-Signature") !== process.env.WASENDER_WEBHOOK_SECRET) {
    return res.sendStatus(401);
  }
  res.sendStatus(200); // acknowledge fast, then process

  const { event, data } = req.body;
  if (event !== "messages.received") return;

  const msg = data.messages;
  if (msg.key.fromMe) return;

  const workspaceId = req.params.workspaceId;
  const phone = msg.key.cleanedSenderPn;

  const contact =
    (await db.contacts.findByPhone(workspaceId, phone)) ??
    (await db.contacts.create(workspaceId, { phone, source: "WhatsApp" }));

  await db.activities.create({
    workspaceId,
    contactId: contact.id,
    channel: "whatsapp",
    direction: "in",
    text: msg.messageBody,
    externalId: msg.key.id,
  });
});

async function sendFromCrm(workspace, contact, text, userId) {
  const res = await fetch("https://www.wasenderapi.com/api/send-message", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${decrypt(workspace.wasender_api_key)}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({ to: contact.phone, text }),
  });
  if (!res.ok) throw new Error(`WhatsApp send failed: ${res.status}`);

  await db.activities.create({
    workspaceId: workspace.id,
    contactId: contact.id,
    channel: "whatsapp",
    direction: "out",
    text,
    sentBy: userId,
  });
}

CRM features to build on top

Once messages flow both ways, the valuable features are mostly CRM logic you already have:

• Shared inbox: one view of all WhatsApp conversations in the workspace, with assignment to reps.
• Deal stage triggers: send a message automatically when a deal moves to "proposal sent" or "won".
• Reminders: appointment, renewal and payment reminders from your existing scheduler.
• Quick replies: saved snippets reps can insert with one click.
• Documents: send quotes and invoices as files straight from the deal (the send endpoint accepts a document URL).
• Number check: verify a contact is on WhatsApp before a campaign with GET /api/on-whatsapp/{phone}.
• Reporting: first response time and messages per rep, from the activities you are already logging.

How to price WhatsApp inside your CRM

WasenderAPI partners pay a flat $6/month base fee, plus $6.00 per active session per month under 100 sessions and $4.80 per session per month at 100+ sessions. There are no per-message fees. Billing runs on a credit balance, new sessions are prorated, and the unused amount comes back when you delete a session.

For a CRM, one session usually means one connected number per workspace, which makes packaging simple:

• Paid add-on: for example $15 to $29 per workspace per month for WhatsApp.
• Higher tier only: include WhatsApp in your Pro or Business plan to push upgrades.
• Per extra number: charge for additional numbers in teams where each rep has their own line.

As an example, 150 workspaces paying a $19 add-on bring in $2,850 per month, while the WasenderAPI cost is $6 + (150 × $4.80) = $726. Because there are no per-message fees, a workspace that messages heavily costs you the same as a quiet one.

What to tell your CRM customers

In practice, CRM conversations are a good fit for this model because they are mostly one-to-one: replies to leads, follow-ups, reminders and support. Discourage bulk cold messaging in your terms and UI, for example by limiting broadcast sizes or requiring an opt-in field on contacts, and your customers' numbers will stay healthy.

The best CRM WhatsApp features feel like a conversation with a person, not a campaign. Build for that and the channel stays reliable.

Start building your CRM WhatsApp integration

The WasenderAPI Partner Program is invite only and built for CRMs, SaaS platforms, agencies and resellers that manage WhatsApp numbers for their own customers. Tell the team about your CRM, your users and how many numbers you expect to connect.

Apply for Partner Access

Want to prototype first? Create an account and test the API on one number. For the bigger picture, read our guides on the white label WhatsApp API and multi-tenant WhatsApp architecture.

Frequently asked questions