Plain-English definitions for every acronym, concept, and Meta policy term you actually encounter when buying, running, or migrating a WhatsApp Business API platform. Organised by category, cross-linked to the deep guide for each topic, and kept current with Meta's 2026 policy state.
The core identifiers that define your presence on WhatsApp and who handles your traffic.
Meta's official programmatic interface for sending and receiving WhatsApp messages at business scale. Used by mid-market and enterprise teams; distinct from the free consumer WhatsApp Business App which is a mobile-only tool for small businesses. Access is always mediated through a Business Solution Provider (BSP).
See also: AI WhatsApp Platform guide, BSP, WABA.
A Meta-authorised vendor (for example, Go4whatsup, WATI, Gupshup, Twilio) that hosts your WhatsApp Business API traffic, re-sells Meta's conversation fees, and ships the platform layer — dashboard, inbox, automation — on top of the raw API. You cannot use the WhatsApp Business API directly without a BSP relationship.
See also: BSP transfer, BSP transfer, WABA.
The Meta-level container for your WhatsApp business identity. Lives inside Meta Business Manager, holds your phone numbers (senders), display name, business category, templates, and quality rating. The WABA is yours — not the BSP's — which is why BSP transfer is possible without re-registering.
See also: Display name, Sender, BSP transfer.
A phone number registered to your WABA and used to send WhatsApp Business API messages. Each sender has its own display name, quality rating, and messaging-limit tier. A WABA can hold multiple senders. A sender can only be active with one BSP at a time.
See also: WABA, Messaging limit tier.
The brand name shown to customers in chat alongside your messages. Set on the WABA, reviewed by Meta against their naming policy (must match the legal business name or a closely-matched consumer-recognised brand), and stable across BSP transfers.
See also: Green tick, Meta Business Manager.
Also known as Official Business Account verification. A visible green checkmark next to your business name in customer chats, granted by Meta based on notability evidence — press coverage, search presence, domain authority. Tied to the WABA (not the BSP), so it transfers cleanly when you switch BSPs.
See also: Green-tick filing guide, WABA.
Meta's master console at business.facebook.com where you manage your Facebook Page, Instagram account, ad accounts, and WABAs. Always owned by your business directly — BSPs are granted permissions to act on behalf of your WABA, but they never own it.
See also: WABA, Two-step verification.
What you can actually send, how Meta controls it, and the moving parts of a template approval.
Historically called a Highly Structured Message (HSM). A pre-approved message format — header, body, footer, buttons — that Meta has reviewed and sanctioned for use outside the 24-hour session window. Templates are the only way to initiate a conversation with a customer; free-form replies are only allowed while the session window is open.
See also: Template variable, Session window, Template approval.
Placeholder in a template that's filled in at send time, written as {{1}}, {{2}}, etc. Meta reviews the surrounding template copy, not the variable value — but the variable value must be type-consistent with what was approved. Re-formatting variables (e.g. adding quotes or spaces) is a silent rejection trigger during template re-submission.
See also: Template, Template approval.
Meta's review process for a submitted template. Typical time: 24–48 hours, up to 7 days for borderline promotional content. Each BSP submits independently — template approvals do not transfer between BSPs, which is why every migration includes a template re-submission step.
See also: Template re-submission in migration, Template category.
Meta's classification of what a template is for — one of Marketing, Utility, Authentication, or (historically) Service. Category drives the conversation rate Meta will charge. Category was tightened in 2024–2025 — some templates long-approved as utility are now re-categorised as marketing, with the corresponding rate change.
See also: Meta WhatsApp Pricing guide, Conversation category.
A template or free-form message that includes tappable elements — buttons, list selectors, quick replies, or call-to-action (URL/phone) buttons. Interactive messages convert substantially better than plain text. Go4whatsup's automation layer supports all Meta-sanctioned interactive types.
A one-to-many template send targeting a segment of opted-in contacts. Unlike WhatsApp consumer groups, broadcasts do not create a group chat — each recipient sees a one-to-one conversation. Broadcast send is a common primary use case for buying a WhatsApp Business API platform.
See also: WhatsApp marketing, Opt-in.
A Meta / Instagram ad format that routes a tap straight into your WhatsApp inbox with a pre-filled context variable. Opens a free-service-tier conversation on first tap. Heavily used by D2C, real-estate, education, and clinics because cost-per-qualified-lead is typically 2–4× lower than comparable lead ads.
See also: Conversation category, Session window.
What Meta actually bills for, how conversation units are counted, and where the free tier kicks in.
Meta's unit of billing on the WhatsApp Business API. One conversation covers a rolling 24-hour window of messaging between your business and one customer, regardless of how many individual messages are exchanged. Conversation rate depends on the conversation category and the recipient's country.
See also: Meta WhatsApp Pricing guide, Conversation category.
The category Meta assigns to each billable conversation — Marketing, Utility, Authentication, or Service — which determines the rate. Category is driven by the first template sent in the 24-hour window. Meta charges marketing conversations the highest rate; service (free-tier) conversations are currently free within Meta's monthly allowance.
See also: Meta Pricing guide, Free-service tier.
The rolling 24-hour window that opens the moment a customer sends you an inbound message. While the window is open, your business can reply with free-form messages (no template required). Once it closes, you can only re-initiate with an approved template.
See also: Template, Conversation.
Meta's monthly allowance of free service-category conversations (initiated by the customer) per WABA. The threshold has shifted several times — check the Meta pricing guide for current numbers. Marketing, utility, and authentication conversations are not part of this free tier.
See also: Conversation category, Meta Pricing guide.
A special category of conversation opened when a customer arrives from a Click-to-WhatsApp ad. Currently free within Meta's ad-driven entry-point allowance. Tracked separately from ordinary service conversations for billing purposes.
See also: CTWA, Conversation.
How Meta throttles and polices your account — and how to stay in the green.
The daily cap on business-initiated conversations per sender, enforced by Meta. Tiers typically progress from 1,000 → 10,000 → 100,000 → unlimited as your account demonstrates consistent quality. Tier upgrades are automatic but require sustained good quality rating and consent-compliant sending.
See also: Quality rating, Template quality.
Meta's traffic-light indicator on the sender — High (green), Medium (yellow), or Low (red) — derived primarily from user block / report rates against that sender. A drop to Low can freeze your messaging limit tier. Recovery is achievable but typically takes 2–4 weeks of clean sending.
See also: Messaging limit, Block rate.
A per-template version of the quality rating — High / Medium / Low — driven by user engagement signals (opens, click-throughs, blocks). Low-quality templates can be paused by Meta. Rotate variations and re-submit improved versions to maintain quality at scale.
See also: Template, Quality rating.
The percentage of customers who block your sender after receiving a message from you. The single biggest input into quality rating. Marketing campaigns to cold lists almost always spike block rate — which is why segmented, opt-in-based broadcasts matter more than blast volume.
See also: Quality rating, Opt-in.
Meta's list of product categories prohibited from being sold or promoted on WhatsApp — firearms, tobacco, pharmaceuticals (region-specific), adult services, alcohol (region-specific), and others. Applies at the WABA level; a single violation can trigger a review of your entire account.
See also: Compliance, Business Policy.
The broader policy framework covering business conduct on Meta's platforms — honesty, non-deception, no platform manipulation, no user harassment. Violations are handled with warnings, account restrictions, or permanent bans depending on severity.
See also: Commerce Policy, Compliance page.
What the BSP layer adds on top of Meta's raw API.
A multi-agent conversation interface where a whole team handles inbound WhatsApp on one number. Agents have individual logins; routing rules assign conversations by keyword, working hours, team, or round-robin; supervisors see load and response times. The single most-used feature after broadcasting.
See also: Features, Agent routing.
A visual, no-code workflow that triggers on an inbound signal (keyword, webhook, scheduled time) and runs a sequence of messages, branches, and external API calls. Go4whatsup's automation layer covers keyword triggers, conditional splits, template sends, webhook calls, agent handoff, and AI nodes.
See also: Webhook, AI auto-reply.
A natural-language AI layer that answers inbound messages without agent involvement when the question matches a configured knowledge source or prompt. Go4whatsup's AI auto-reply covers context-aware replies, drafted reply suggestions for agents, campaign copy generation, and language detection.
See also: AI WhatsApp Platform, Drafted reply.
A human-in-the-loop pattern where AI proposes a response inside the agent inbox but does not send until the agent reviews and clicks. Useful for teams that want AI-assisted speed without autonomous AI risk — common in regulated industries.
See also: AI auto-reply, AI platform.
Rules that decide which agent or team receives an inbound conversation. Common dimensions: working hours, keyword match, team tag, round-robin, language detected, customer segment. Part of shared-inbox configuration.
See also: Shared inbox, Flow.
An outbound HTTP call from the BSP platform to your own endpoint (or a partner like Zapier, Make), fired on events — inbound message, template sent, status update, tag added, conversation assigned. Used to sync WhatsApp activity into CRMs, data warehouses, and custom tooling.
See also: API key, Integrations.
The credential your code presents to Go4whatsup's REST API to authorise a call. Scoped to a workspace; rotatable from admin settings. Separate from Meta's Graph API credentials — Meta's tokens live on the BSP side and you do not handle them directly.
See also: Webhook, Two-step verification.
The rules that govern who you can message — and how you prove it.
An explicit, affirmative signal from a customer that they agree to receive WhatsApp messages from your business. Required by Meta policy and by data-protection law (India's DPDPA, UAE's PDPL, GDPR). Opt-in must be captured with a timestamp and a documented source, and stored for the retention period required in your jurisdiction.
See also: Opt-out, DPDPA, Compliance.
A customer's withdrawal of consent to receive further messages. Typically triggered by the word STOP, UNSUBSCRIBE, or the WhatsApp native block action. Must be honoured immediately; continued sending after an opt-out is both a Meta policy violation and a regulatory violation.
See also: Opt-in, Block rate.
The Digital Personal Data Protection Act, 2023 — India's primary data-protection law governing consent, purpose limitation, and data-subject rights. Relevant to WhatsApp marketing because contact phone numbers, opt-in records, and conversation history are all personal data.
See also: Compliance, PDPL.
The UAE's Federal Personal Data Protection Law — the equivalent framework governing consent, data handling, and cross-border transfers in the UAE. Applies to businesses processing UAE-resident personal data regardless of where the business is registered.
See also: DPDPA, Compliance.
The audit trail proving a given customer gave valid opt-in — typically including timestamp, source (website form, in-store signup, SMS short-code, in-conversation agree-to-receive), and the exact wording shown to the customer at the point of consent. Required for regulatory defensibility.
A 6-digit PIN attached to a WhatsApp sender that must be entered to re-register the number on any BSP. Mandatory security measure to prevent unauthorised number hijack. Store the PIN in a password manager — losing it locks you out of the sender and recovery requires a Meta support ticket.
See also: BSP transfer, Meta Business Manager.
Moving between BSPs and the operational parts that go with it.
Meta's official mechanism for moving a WABA from one BSP to another. Initiated in Meta Business Manager; releases from the current BSP within 24–72 hours; re-registers on the destination BSP with a brown-out window typically under 15 minutes. Number, display name, and green tick all persist. Template approvals do not — they must be re-submitted on the new BSP.
See also: Switch from WATI, Switch from Gupshup, Switch from Twilio.
The short period during BSP transfer when the sender is technically re-registering on the new BSP and some inbound messages may not route. Typically under 15 minutes when scheduled in a low-traffic window. Distinct from a total outage — outbound broadcasts are paused, but existing sessions continue.
See also: BSP transfer, Migration playbook.
The process of bringing your customer base into a BSP platform — typically via CSV with phone, name, tags, opt-in status, opt-in source, and language preference. Most modern BSPs also support live CRM sync (HubSpot, Zoho, Odoo, Salesforce) which keeps the contact base in lock-step with the system-of-record.
See also: Integrations, Opt-in.
Low-code automation platforms used to connect a BSP to apps that don't have a native integration. Trigger on a WhatsApp event (inbound, status, tag), run actions in the target app. Works well for long-tail integrations; native connectors are usually a better fit when available.
See also: Webhook, Integrations.
The all-in monthly cost of running WhatsApp as a channel: platform fee + Meta conversation fees + any add-on licenses (AI, agent seats) + engineering overhead to maintain custom code. Comparing BSPs on platform fee alone misses half the picture.
See also: Meta Pricing guide, Compare.
The WhatsApp Business App is a free mobile app intended for small businesses with one operator — no automation, no multi-agent inbox, no broadcasting at scale. The WhatsApp Business API is the programmatic interface for mid-market and enterprise use, always accessed through a BSP, and is what every platform like Go4whatsup, WATI, Gupshup, or Twilio resells on top of.
No. Your WABA (WhatsApp Business Account) is your Meta-level identity — numbers, display name, templates, quality rating — and it belongs to your business. The BSP (Business Solution Provider) is the vendor who hosts your traffic and provides the platform layer on top. The same WABA can move between BSPs through Meta's BSP-transfer flow without losing number, display name, or green-tick status.
A template (sometimes called an HSM) is a pre-approved message format — with fixed copy and variable placeholders — that Meta has reviewed and sanctioned for business-initiated messaging outside the 24-hour session window. You can only initiate new conversations with an approved template. Template approvals are issued per BSP, which is why every BSP migration includes a template re-submission step.
When a customer sends you a WhatsApp message, a rolling 24-hour window opens during which you can reply with any content (free-form text, images, templates, interactive messages) at no per-message charge beyond the conversation fee. Once the window closes, you can only re-initiate with an approved template — which will open a new billable conversation in whichever category the template belongs to.
Meta charges per conversation, not per message — one conversation covers 24 hours of messaging between your business and one customer. The per-conversation rate depends on the conversation's category (marketing, utility, authentication, service) and the recipient's country. A monthly allowance of free service conversations applies. See the Meta WhatsApp Pricing guide for current rates.
Quality rating (High / Medium / Low) is Meta's summary of how recipients react to your sender — primarily block rate, report rate, and failed-delivery rate. A drop to Medium or Low can freeze your messaging-limit tier and prevent upgrades. Recovery is possible but typically takes 2–4 weeks of consistent, consent-compliant sending to segmented lists, rather than broad marketing blasts.
Opt-in is required by both Meta's business policy and regional data-protection law (India's DPDPA, UAE's PDPL, GDPR for EU residents). Sending to contacts without valid opt-in records triggers block-rate spikes that damage quality rating, and exposes the business to regulatory action. Every modern BSP — Go4whatsup included — stores opt-in timestamp, source, and the exact consent wording against each contact.
Number porting is a telecom concept — moving a phone number between mobile carriers. BSP transfer is a WhatsApp-specific concept — moving the WABA assignment of a phone number from one WhatsApp BSP to another. No telecom carrier is involved. The phone number itself doesn't change; only the BSP that handles its WhatsApp Business API traffic changes.
Book a 30-minute demo — we'll walk through how each of these terms maps to your actual WhatsApp setup.
Book A Demo See Pricing