WhatsApp integration guide

WhatsApp CRM integration: Connect messages to your sales workflow

WhatsApp CRM integration connects business conversations to customer records, responsible teammates and sales opportunities. In Qonvera, the connection brings WhatsApp messages into a shared inbox; your team still needs a clear process for ownership, qualification and follow-up.

Use this guide to prepare the business account, connect a number and test an enquiry from receipt to next action. It describes Qonvera’s documented workflow—not a promise of automatic history migration, unrestricted messaging or a ready-made connector to another CRM. Qonvera’s operator publishes this guide.

What does a WhatsApp CRM integration connect?

The messaging connection carries customer enquiries and eligible replies. The CRM gives the team a place to confirm identity, record a sales opportunity and schedule the next action. Receiving a message does not mean a deal has been created or a sale qualified.

Separate the connection from the sales work
Part of the workflowWhat to check
Business number and inboxThe correct WhatsApp connection receives messages in the intended workspace.
Contact and conversationThe team confirms who the customer is and who is handling the chat.
Opportunity and follow-upAn authorized teammate records the potential sale, owner, stage and dated next action.
Understand Qonvera’s WhatsApp CRM capabilities

Before connecting your WhatsApp business number

Qonvera uses the official WhatsApp Business Platform Cloud API through Meta authorization. An Owner or Admin manages the connection in Settings → Channels. Prepare access to an eligible Meta business account and business number, and complete any required number registration.

If the number already runs in the WhatsApp Business App or another provider, confirm the supported migration or coexistence path before changing anything. Do not assume that all previous chats will transfer or that the app can continue using the number in the same way.

  • Choose the workspace that should receive the enquiries.
  • Confirm who is authorized to manage the Meta account and business number.
  • Check your subscription’s workspace, user and connection allowances.
  • Agree who will monitor connection errors and handle incoming enquiries.
Qonvera documentation: channel connection prerequisites Meta documentation: WhatsApp Business Platform and Cloud API

How to connect WhatsApp to Qonvera CRM

Use the channel setup flow rather than sharing account passwords with teammates. Provider screens and eligibility requirements can change; follow the authorization steps shown for your account.

  1. Sign in as an Owner or Admin and select the intended workspace.
  2. Open Settings → Channels, choose WhatsApp and select Connect.
  3. Complete Meta authorization for the correct business account and number, including any required registration steps.
  4. Return to Qonvera and check the channel card for Connected status or a specific error.
  5. Send a customer-initiated test message from a separate test contact. Confirm that it appears in the right inbox, then test a permitted reply and inspect its delivery status.

A Connected status is not evidence that every message will be delivered. Keep the provider account active and review the channel card if permissions are revoked or messages stop arriving.

Follow the documented channel connection steps

Turn an incoming enquiry into an owned next action

Illustrative example: a customer asks for a service quote on WhatsApp. Assign the conversation, confirm the contact and service requirement, and have an authorized teammate create or update the relevant opportunity. Record its owner and current stage, then schedule a specific follow-up.

A useful next action is “Call on Thursday to confirm the proposed service date,” with a responsible person and due time. Check conversation assignment, opportunity ownership and follow-up ownership separately; one does not prove the others are correct.

Managers can edit CRM records. Agents handle inbox and follow-up work within their access, but do not edit core contacts, accounts or opportunities. Owners and Admins manage configuration and team access. Verify the actual permissions before handing work over.

Check workspace roles and permissions Create an owned, dated follow-up Define evidence-based stages for a service-business pipeline

Reply windows and templates still apply

WhatsApp generally permits free-form replies during the 24-hour customer-service window opened by the customer’s latest message. Outside that window, use an eligible approved template. Follow WhatsApp’s consent and opt-out requirements; connecting a number does not give permission to contact everyone in your database.

A Qonvera template draft still needs Meta approval before it can be used as an approved template. Approval does not guarantee eligibility or delivery for every recipient. Check message status rather than treating an accepted send as a delivered message.

Scheduling a follow-up creates work for the team; it does not itself send a WhatsApp message. Any automated action needs separate configuration and permissions, and remains subject to the same provider rules.

Qonvera documentation: reply windows, templates and delivery status WhatsApp Business Messaging Policy Distinguish follow-up reminders from automated messaging

Test the workflow before rolling it out

Use synthetic customer details and a consenting test contact. Check the customer’s device as well as the CRM, and record any limitation before the wider team starts using the number.

WhatsApp CRM integration acceptance checklist
TestEvidence to look for
Incoming enquiryThe test message appears under the correct business number and workspace.
Reply and deliveryAn eligible reply reaches the test contact; its message status is checked separately from connection status.
Team handoverThe receiving teammate can see the permitted context; chat, opportunity and task ownership are checked independently.
Sales recordAn authorized teammate records the correct contact, requirement and opportunity stage without assuming automatic deal creation.
Next actionThe follow-up has an owner and due date, appears in the relevant queue, and is completed only after the action is taken.
Outside-window replyThe team can identify when an eligible approved template is required rather than trying to bypass the restriction.
Review shared-inbox ownership and handovers

What if you already use another CRM?

Connecting WhatsApp to Qonvera is not the same project as synchronizing Qonvera with another CRM. Define which system owns each record, the objects and fields to exchange, sync direction, conflict handling and what should happen after a failed or repeated update.

Qonvera documents licensed API access and outbound webhooks. Credentials, scopes and workspace permissions still apply. Their availability is not proof of a ready-made connector to your chosen CRM; confirm the required implementation before purchasing.

The documented prospect import flow creates or updates contacts and companies, not chats or opportunities. Customer enquiries should use the appropriate intake workflow. Keep credentials and signing secrets out of public pages and customer conversations.

Review API, lead synchronization and webhook scope

Check capacity, provider charges and optional AI

Check current pricing for workspace capacity, users, connections and captured leads. Qonvera subscription fees and external WhatsApp messaging charges are separate considerations. Do not count every message in an existing conversation as a new captured lead; use the published lead-counting definition.

Receptionist responds to incoming enquiries using approved knowledge and hands over when needed. Qualification identifies service interest and scores leads. Sales Assistant summarizes conversations, suggests next steps and answers contextual questions for the team. These agents are optional, separately priced workspace add-ons with configuration and usage allowances; manual inbox work does not require them.

Check current Qonvera pricing, capacity and captured-lead definitions Check licensed integrations, agents and usage allowances Explore Receptionist responses and human handover Explore Qualification service matching and lead scoring Explore Sales Assistant summaries and contextual questions
Common buying questions

Questions to settle before choosing.

Do I need a WhatsApp Business Platform connection?

Qonvera’s documented connection uses the official WhatsApp Business Platform Cloud API through Meta authorization. An Owner or Admin needs access to an eligible business account and number. Confirm the current registration and migration requirements before switching.

Qonvera: Connect messaging channelsMeta: WhatsApp Business Platform

Can I keep using the WhatsApp Business App and import all previous chats?

Do not assume either. Confirm the supported coexistence or migration path for your number and what history is available before changing the existing setup. This guide does not promise a complete historical import.

Qonvera: Connect messaging channels

Does every incoming WhatsApp message create an opportunity?

No. A message is not automatically a qualified sale. Confirm the contact and requirement, then have an authorized teammate create or update the relevant opportunity and next action.

Is AI required to use the WhatsApp inbox?

No. Receptionist, Qualification and Sales Assistant are optional, separately priced workspace add-ons. Your team can handle manual replies and follow-ups without purchasing an AI agent.

Qonvera: Billing and limits

Does API access include a connector to my existing CRM?

Not by itself. Confirm the supported objects, fields, sync direction and implementation for your CRM. Licensed access, credentials and scopes are prerequisites, not a guarantee of a ready-made connector.

Qonvera: API and webhooks
Evaluate your workflow

Bring your enquiry-to-outcome scenario.

Ask us to show what Qonvera supports—and what needs a separate system or setup.