Questions about WA Console?

WA Console is a platform for managing and integrating WhatsApp Business API infrastructure from one place — WhatsApp Business Accounts, phone numbers, message templates, messaging activity, webhook events and API access.

Businesses operating their own WhatsApp, SaaS companies embedding WhatsApp in a product, agencies running WhatsApp for several clients, and developers integrating WhatsApp into an existing backend.

No. WA Console works on top of WhatsApp Business API. Your WhatsApp Business Account stays with Meta; WA Console is the management and integration layer around it.

No. WA Console is WhatsApp Business API infrastructure and management. It does not provide a CRM, chatbot builder, campaign manager, broadcast tool or automation engine.

Create your WA Console account, connect your WhatsApp Business Account through Meta’s Embedded Signup, and WA Console syncs the account’s phone numbers and templates. From there you can send messages and see activity in the console.

Yes. WA Console manages an account you own. Meta sets the eligibility, business verification and phone number requirements for WhatsApp Business API, and those apply before an account can be connected.

Yes. Connecting an account uses Meta’s Embedded Signup, which authenticates through Meta and returns authorisation for the WhatsApp Business Account you select.

Yes. Embedded Signup connects an account you already have — you select it during the flow, and its phone numbers and templates are synced afterwards.

It depends on your Meta configuration rather than on WA Console. If your business is already verified and your phone number is ready, connecting is quick; if verification or a new number is involved, Meta’s process sets the timeline.

WABA stands for WhatsApp Business Account. It is Meta’s account structure that holds your WhatsApp Business API resources — phone numbers and message templates in particular.

The account’s connection and metadata, its phone numbers, its templates and their status, messages sent through it, and the webhook events Meta reports for it.

Yes, on Growth and above. One organisation can hold several accounts, and each is billed at your plan’s per-WABA price. There is no "unlimited" tier — you pay per account you manage.

No. The account remains your business’s, held with Meta. WA Console holds the authorisation you grant during Embedded Signup so it can manage the account on your behalf, and you can disconnect it.

Plans start at ₹499 per WABA per month. Growth is ₹999 and Business is ₹1,999, each per WABA per month, and Agency pricing is quoted.

Per WABA. The subscription is billed for each WhatsApp Business Account, and each account includes one phone number. Additional phone numbers are ₹199 per number per month.

No. Your WA Console subscription is the platform fee. Meta bills its WhatsApp messaging charges separately, based on your usage and Meta’s applicable pricing at the time. WA Console does not resell or mark up Meta’s charges.

Meta provides the WhatsApp Cloud API. WA Console is what sits around it: account and number management, template status, a webhook receiver with signature verification, stored event history, message status with Meta’s failure reasons, and scoped API keys — the parts you would otherwise build and run yourself.

Yes. Subscriptions are held per WhatsApp Business Account, so you can change what an account is on as your requirements change.

Yes, per account. Cancelling stops the next renewal rather than cutting access immediately — the month you have already paid for runs to its end, and the account stays usable until then.

Refund terms are not something we want to state loosely on a marketing page. Please contact us and we will confirm the current policy for your situation in writing.

Your plan includes one phone number per WABA, and you can add more at ₹199 per number per month. Beyond that, how many numbers an account can hold is governed by Meta’s limits for your WhatsApp Business Account, not by WA Console.

Yes. Numbers on your WhatsApp Business Account are synced from Meta and registered through the console. Additional numbers beyond the one included are ₹199 per number per month.

No. A phone number is registered to a single WhatsApp Business Account at a time — that is Meta’s rule for WhatsApp Business API, not a WA Console restriction.

Moving a number between WhatsApp Business Accounts is a Meta operation, performed in Meta’s tools. WA Console does not move numbers for you; once Meta has moved it, syncing the account picks up the change.

Templates are message formats Meta approves in advance, used for the kinds of business messaging WhatsApp requires them for — order updates and similar notifications.

No. Approval is Meta’s decision. WA Console syncs your templates and surfaces the status Meta reports — approved, pending, rejected — so you can see where each one stands without checking elsewhere.

Yes. Templates are listed with their current status, and a template status change from Meta arrives as a webhook event and is recorded.

Yes, through the API. One endpoint covers text, image, video, audio, document, template, interactive, location, reaction and contact messages.

Yes. Meta reports sent, delivered, read and failed for each message, and those land in WA Console as events tied to the message they belong to.

The failure is recorded against the message with Meta’s own code, title and explanation — for example that more than 24 hours have passed since the customer last replied — rather than a generic error.

No. WA Console charges a subscription per WhatsApp Business Account. Per-message charges come from Meta and are billed separately by Meta.

Yes. Your backend can send messages, list them, fetch one, and read message analytics over plain HTTP.

With two headers on every request — x-access-key and x-secret-key — from a key pair created in the console. It is not a bearer token. Each key is scoped to one WhatsApp Business Account and can only act on that account.

No. There is no official SDK. Integrations are plain HTTP requests, which work from any language without adopting a dependency.

Yes. Your backend calls the API with a key scoped to the relevant account, which is how a SaaS gives its own customers WhatsApp capabilities without owning the infrastructure.

Meta delivers WhatsApp events to WA Console, which verifies Meta’s signature, acknowledges immediately and processes them in the background. Your application reads those stored events per account. WA Console does not currently forward events on to your own endpoint.

Stored events are classified as inbound_message, status_update (sent, delivered, read, failed), template_status, and account_update. Each carries the account, the recipient, the delivery status and Meta’s message id where relevant.

Not today. WA Console is the receiver Meta posts to, and your application reads the stored events. If outbound delivery to your endpoint matters for your integration, tell us — it helps us prioritise.

Every payload must carry a valid X-Hub-Signature-256 HMAC from Meta. Anything without one is rejected, so what appears in your event list is what Meta actually sent.

Server-side only. The secret key should live in your environment configuration or a secret manager — never in browser code, a mobile app, or a committed file.

Yes. Keys are listed in the console and can be deleted, which stops them authenticating. Create a replacement key first if the integration needs to keep running.

Yes. Messages you send, inbound messages and webhook event payloads are stored, which is what makes message history, delivery status and the event list work. There is no automatic deletion schedule today, so if you have a retention requirement, raise it with us and we will confirm what is possible.

Hosting region is not something we want to state imprecisely. Contact us and we will confirm the current arrangement for your account in writing.

Yes. Either keep every client account in one organisation, or give each client its own organisation and switch between them. Each client’s account, numbers, templates and events stay separate either way.

Yes. Every API key is scoped to exactly one WhatsApp Business Account, so a key issued for one client cannot act on another client’s account.

No. There is no white-label dashboard, agency branding, reseller tier or client-facing subaccount today. WA Console is the platform your team uses; your clients are not billed through it and do not see an agency-branded product.

Not per client. Members belong to an organisation and carry a role there, so access is organisation-wide. If a client needs harder separation, give that client its own organisation.

Work through it in this order: you are signed in to the Meta account that administers the business; the business is verified with Meta; the WhatsApp Business Account is visible to you during Embedded Signup; the phone number has completed Meta’s verification; then retry the connection. Most failures here are Meta-side prerequisites rather than WA Console.

Numbers come from Meta, so the number must exist on the connected account first. Re-sync the account to pull the current list, and check the number has finished registration on Meta’s side.

Check in this order: the phone number’s status; the template’s status, if you are sending a template; the request itself, since validation failures name the exact field; and then the failure recorded against the message, which carries Meta’s own code and explanation.

Events are read for a specific account, so confirm you are querying the right one. Meta must also have the webhook configured against your account for events to arrive at all, and only payloads with a valid signature are accepted.