Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration

Connect WhatsApp Business to Apragya: Templates, Campaigns and Support Chats on the Record

For sales and support teams whose customers prefer WhatsApp: send approved messages from the CRM, and handle incoming chats as tickets, all on the customer's record.

A counsellor handing a speech bubble card to a student at a reception desk

To connect WhatsApp Business to Apragya, you add your Meta WhatsApp Cloud API details, the access token, phone number ID and app secret, in the integrations settings, and register Apragya's webhook in Meta. CRM can then send approved templates, and incoming messages reach CRM or support.

In most Indian businesses, customer WhatsApp lives on staff phones. Conversations disappear when people change jobs, and nobody can see what was promised.

This page covers the setup, how templates and consent work, an illustrative example from a coaching institute, and the rules Meta applies to every business number.

An example: a Lucknow coaching institute

Take an illustrative institute that follows up enquiries on WhatsApp and handles fee and schedule questions the same way. Counsellors used their own phones.

Going live on the Cloud API

  • Business numberRegistered on the WhatsApp Business Platform.Done
  • Webhook verifiedMeta's handshake completed, signatures checked.Done
  • Follow-up templateSubmitted and approved by Meta.Ready
  • Consent recordsOnly opted-in contacts selected.Checked
  • Support channelIncoming chats open tickets.Done
  • Fee reminder templateWaiting for Meta's approval.Pending
A template can be sent only after Meta approves it, so the reminder waited.

Enquiry follow-ups now go out from the institute's number with approved wording, and replies land on the lead. Fee questions arrive as tickets, and students who reply STOP are left out of later sends.

Sealed envelopes in a row and one set aside with a padlock
The student who replied STOP stays set aside from every later send.

What phone-based WhatsApp costs

Chats on personal phones

Customer history leaves with the employee.

No consent record

Nobody knows who agreed to receive messages.

Slow support

Complaints wait until someone checks a handset.

Inconsistent wording

Every salesperson writes their own version.

Opt-outs ignored

A customer who said STOP keeps getting messages.

No view of results

Nobody can tell which messages worked.

How the WhatsApp Business API integration works

Step 1 of 5

Add Cloud API details

Access token, phone number ID and app secret from your Meta app.

  1. Add Cloud API details: Access token, phone number ID and app secret from your Meta app.
  2. Register the webhook: Apragya answers Meta's verification and checks every signature.
  3. Submit templates: Write with friendly placeholders; Apragya submits and tracks approval.
  4. Send from CRM: Single messages, sequences and campaigns to opted-in contacts.
  5. Handle support chats: Incoming messages open tickets or join the open one.

WhatsApp Cloud API CRM, or staff phones?

The WhatsApp Business app on a phone is fine for a one-person shop. Once several people talk to customers, the Cloud API with a shared record keeps history, consent and wording under control.

Staff phones, against Apragya with the Cloud API

FeatureStaff phonesApragya with Cloud API
HistoryOn handsetsOn the lead and ticket
ConsentNot recordedChecked before campaigns
Opt-outsRemembered, maybeSTOP replies suppressed
WordingEach person's ownApproved templates
Campaign costUnknownEstimate shown before sending

Checked against public information on 16 September 2026.

What sets WhatsApp support tickets and CRM messaging apart

One record

Messages sit with the lead, deal or ticket.

Consent gate

Campaigns reach only contacts with active consent.

24-hour rule respected

Outside Meta's service window, only approved templates go out.

Paced campaigns

Sends are paced to your messaging tier.

Agents on chats

An agent can classify incoming chats for routing.

Audit log

Integration changes are recorded.

Messages land in CRM activities and tickets. For WhatsApp through Twilio instead, see connecting Twilio.

Getting started

  1. Set up a Meta app and a business phone number on the WhatsApp Business Platform.
  2. Add the access token, phone number ID and app secret in Apragya.
  3. Register the webhook in Meta and complete the verification.
  4. Submit one template and wait for approval.
  5. Send it to a few opted-in contacts, then add a support channel.

Record consent before the first campaign. It is the rule that protects your number.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

Connecting WhatsApp Business, answered

Can we keep using the WhatsApp Business app on a phone?
A number registered on the Cloud API is managed through the API. Check Meta's current rules before moving a number.
Why was our message rejected?
Outside the 24-hour window after a customer's last message, Meta allows only approved templates.
Who pays for the messages?
Meta charges your WhatsApp Business account. Apragya shows an estimate before a campaign is sent.
What happens when a customer replies STOP?
The number is added to the suppression list and left out of later campaigns and sequences.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Send your first approved template

Add your Cloud API details, verify the webhook, and message one opted-in lead.