A calling pilot should prove that the right agent can handle a permitted WhatsApp call, update the correct customer record and stop unnecessary follow-ups. Indian teams should test one customer journey before expanding. This checklist covers ownership, production-readiness tests and measurement, rather than repeating the full Calling API feature guide.

Updated 15 September 2026. For current eligibility, permission, pricing and platform limitations, use our WhatsApp Business Calling API guide. This page is the implementation-readiness companion for marketing, sales and support managers.

Choose a pilot problem, not a calling target

For an Indian business with 10K+ contacts and a 50 to 500 employee team, turning the entire database into a call queue is the wrong starting point. Pick one workflow where a customer needs a human answer, the team can staff the handoff and the result can be checked.

• Delivery clarification: resolve an address or delivery-slot question against the current order.
• Sales configuration: answer a prospect’s specific product question before issuing a quotation.
• Support escalation: help a customer whose ticket cannot be resolved in a short message.

These are proposed pilot scenarios, not CampaignHQ case studies. Record the current process before testing a new one: where the request arrives, who follows up, how it is resolved and when another channel is more appropriate.

If the basic account is not ready, start with the WhatsApp Business API setup guide for India and verify the requirements against the official WhatsApp Business Platform documentation. Do not treat an existing messaging connection as a calling readiness certificate.

Name the owners before connecting the systems

• Business owner: selects the customer problem, defines success and decides whether the pilot continues.
• Platform owner: checks the actual business number, production eligibility, billing and permission settings.
• CRM/integration owner: maps identities and events, handles duplicates, and owns failed updates.
• Service lead: defines coverage hours, agent training, language routing and missed-call handling.
• Privacy/security owner: approves access controls and any recording, retention or data-transfer arrangements.

One person can hold several roles. None should be left to an unnamed vendor team. Ask the supplier to list what it configures, what your team must build, what is separately charged and who responds after launch.

Write a short acceptance brief

Give the implementation owner a concrete test case: “A customer asks for help with an order. The right agent sees the order and message history, checks calling permission, completes the call and writes the outcome to the same ticket. Once the issue is resolved, neither email nor WhatsApp sends another recovery reminder.”

Specify the source of truth for each field. The CRM can own contact identity and lead stage; the order system can own delivery status; the calling integration must use the actual Meta permission state. Do not let a manually edited “consent: yes” field replace that state.

List the precise connector path: native connector, custom API integration or middleware. Include the events supported in each direction, the matching key and the person who handles a failed update. Keep credentials in the approved secret store, not in the test brief.

Run these production-readiness tests

1. Eligibility: prove calling is enabled on the intended production number. Record its country code and the supported agent interface. A sandbox demonstration is not enough because Meta relaxes testing restrictions.
2. Customer permission: approve, decline and revoke permission using a test customer account. Check that the agent cannot dial when the current state disallows it. Test expiry where applicable and ensure a lead score or form submission cannot bypass permission.
3. Message-window handling: test the free-form permission request inside an open customer service window and the approved-template route where needed. If template approval is the blocker, use how long WhatsApp template approval takes in India.
4. Inbound and missed calls: test a staffed call, an unavailable agent and an outside-hours call. Confirm what the customer sees and who owns the resulting task. Do not promise a callback without a valid permission path.
5. Audio and devices: test both participants hearing each other on representative networks and supported mobile clients. Include blocked microphones and a dropped connection. Agent-browser support is a separate question from customer WhatsApp Web support.
6. CRM integrity: test an existing contact, an unmatched identity, a duplicate event and an out-of-order call event. One call should not create several leads or overwrite a final disposition with stale status.
7. Stop rules: resolve the ticket or order before a queued call starts. Confirm the call task and unnecessary follow-ups stop. Repeat with an opt-out, complaint and agent rejection.
8. Recovery: simulate an unavailable CRM or webhook endpoint. Check the error queue, retry behaviour and alert owner. Never retry a customer call blindly just because a CRM write failed.

Use Meta’s permission documentation for the actual permission state and allowed actions. Its Calling API FAQ warns that webhook delivery may be duplicated or out of order. Save evidence of each test, not just a supplier’s checkbox.

Keep permission, contact preference and recording separate

Click-to-chat WhatsApp links can start a conversation. They do not automatically give the business permission to place an outbound call. Likewise, a customer asking for an email quotation has not necessarily asked for a call.

Store the customer’s preferred time and language alongside the technical calling permission. Even when a call is technically allowed, the operational choice may be to wait or reply asynchronously. Review the WhatsApp Business Messaging Policy and your own privacy obligations.

If recording is proposed, ask which system records, how participants are informed, who can listen, where recordings are retained and how deletion requests are handled. Meta now has optional recording documentation, but that does not establish that your vendor exposes it or that your legal review is complete.

Measure resolution, not just dialling activity

Choose a primary outcome tied to the pilot: resolved support cases, confirmed appointments or corrected delivery exceptions. Define the denominator before launch, such as all eligible cases assigned to the pilot, so the report does not count only answered calls.

• Permission funnel: eligible cases, permission requested, approved, declined and expired.
• Handling quality: connected and missed calls, unavailable agents, failed CRM writes and unresolved cases.
• Customer outcome: cases resolved, time to resolution, complaints and requests not to be called again.
• Cross-channel follow-up: whether email or WhatsApp completed the next step, and whether suppression prevented duplicate reminders.

Keep “call connected” separate from “issue resolved” and “lead qualified.” A small pilot can reveal defects without proving conversion lift. Compare like-for-like cases and retain the baseline. For a D2C journey, the broader Email + WhatsApp for Shopify D2C brands playbook can help define the channel roles.

Agree on a go/no-go decision

Expand only after the permission, audio, identity, stop-rule and failure-recovery tests pass, agents can handle the assigned workload, and no material privacy or support question remains open. If these fail, keep the journey in messaging or use another explicitly agreed contact method while the defect is fixed. Do not replace permission checks with manual instructions to “be careful.”

Ask for written implementation and support scope. WATI’s calling integration documentation, for example, describes beta/on-request availability and need-based Business Plan implementation support. Those conditions illustrate why an API feature and a service commitment are different purchases.

CampaignHQ assessment: bring the workflow, verify the scope

CampaignHQ is a Meta Tech Partner focused on email + WhatsApp retention automation, with AWS as supporting infrastructure. Its public voice-calling page describes calling alongside the team inbox. Before treating that as a fit for your rollout, request a demonstration on your number and a written answer on plan eligibility, CRM integration, implementation ownership and ongoing support.

If the decision is broader than a calling pilot, compare the best WhatsApp marketing platforms in India. Keep general platform selection there, and keep Meta calling rules in the Calling API reference guide.

Frequently asked questions

Should we pilot every sales and support journey at once?

No. Begin with one clearly owned customer problem. You need to identify failures and outcomes before expanding to teams with different triggers or coverage hours.

Is a successful sandbox call enough to launch?

No. Test the actual production eligibility, account limits, agent interface and CRM path. Sandbox calling restrictions are relaxed.

Does an inbound chat mean an agent may call back?

No. Check the official calling-permission state. A message, ad click or website form is not a substitute for permission to initiate a WhatsApp call.

Who should own failed CRM updates?

Name an integration owner before launch. That person or contracted team must monitor failures, resolve identity mismatches and safely replay data updates without automatically repeating customer calls.

What should we ask CampaignHQ to demonstrate?

Ask for the exact path from customer permission to agent call, CRM outcome and stopped follow-up. Confirm what is available for your number and plan, what needs integration work and who supports it.

Written by CampaignHQ Team