Answers on WhatsApp numbers, templates, conversations, and billing.

You can send promotional campaigns, order and booking updates, one-time passcodes, and two-way customer support from a single WhatsApp Business number. Combine interactive buttons, product catalogs, AI agents, and live teammate handoffs so customers can finish their task in chat.

When a customer replies to a marketing template or taps a quick-reply button, Bird opens a 24-hour service window and routes the thread to your AI agent or support inbox with the campaign context attached.

The mobile WhatsApp Business app fits small teams handling chats manually on a phone, while the WhatsApp Business Platform adds API automation, multi-agent inboxes, template broadcasts, and CRM integrations. With coexistence on eligible numbers, you can connect the platform without giving up the mobile app.

WhatsApp pricing combines Bird's per-message platform fee with Meta's pass-through rate, which varies by the recipient's country and whether the template is marketing, utility, or authentication. Customer service replies sent inside an open 24-hour window carry no Meta template fee.

Yes. Activate Meta business agent on an eligible number, train it on your help center URLs, documents, and FAQs, and test it with an internal allowlist before opening it to customers. Teammates can step into any thread in Conversations whenever human help is needed.

Sign up directly to connect a number through Embedded Signup, submit templates, and send your first API messages in minutes. Talk to our sales team if you are migrating multiple numbers from another BSP, consolidating regional accounts, or planning high-volume campaigns.

No. A campaign sends an individual one-to-one message to each opted-in customer, and any reply comes back as a private thread with your business. A WhatsApp group puts multiple participants into a shared room where members see one another's messages.

Yes. Promotions, back-in-stock alerts, and cart reminders sent outside an active customer service window require a Meta-approved marketing template and prior customer opt-in.

Yes. Insert customer attributes such as first name, loyalty tier, product image, or dynamic tracking links into your approved template variables, and match the template language to each recipient's locale.

No. A read receipt shows that the recipient opened your message in WhatsApp. To measure conversions, track link clicks, button taps, or customer replies and connect them to completed orders or bookings in your store or CRM.

No. Meta reviews each language translation separately, so one locale can be approved while another is still pending or rejected. Check that the specific language code you pass in your send request has an approved status.

You can configure a fallback language so Bird sends an approved default locale when a customer's preferred translation is unavailable, or set the send to fail so regulated messages are not delivered in the wrong language.

Yes. Connected MCP clients and coding assistants can draft, submit, and inspect WhatsApp templates through Bird's API using your workspace credentials, and each template still goes through Meta's standard category and content review before it can be sent.

No. Meta supports three template categories: marketing for promotions and offers, utility for order confirmations and account alerts triggered by a customer action, and authentication for one-time passcodes.

No. API admission, Meta acceptance, delivery and reads are distinct observations. Confirm the relevant message state and the business outcome separately.

Free-form replies depend on the customer-service window and the supported content type. Outside that window, use an eligible approved template.

The published message API sends individual messages. Pace application fanout using the documented limits; do not assume an email broadcast endpoint also sends WhatsApp.

Use explicit reply identifiers with your stored conversation or task state. A quoted-message reference can help when available, but outgoing metadata is not automatically inherited by the reply.

Yes. You can connect multiple WhatsApp Business Accounts to a single Bird workspace, and each account can manage several phone numbers for different brands, regions, or support teams.

Eligible numbers on the WhatsApp Business app can connect to Bird using Meta's coexistence setup, letting your team keep the mobile app while automating templates, webhooks, and inbox routing through the API.

No. Meta Business Verification confirms your legal company details to access higher daily messaging tiers, while an Official Business Account adds the verified badge next to your display name in WhatsApp for qualifying brands.

Yes. You can migrate an existing WhatsApp Business number from another provider through Embedded Signup while keeping your display name, quality rating, messaging tier, and eligible templates. Our team can help coordinate multi-number cutovers so live traffic moves without downtime.

Yes. When a customer sends a message or replies to a template, a 24-hour customer service window opens. During those 24 hours, you can reply with free-form text, images, documents, and interactive messages without needing a template.

Yes. Include a quick-reply option or keyword rule that routes the conversation to a live queue in Bird, passing the full chat history so a teammate can pick up where your bot or automated flow left off.

No. Sending a read receipt or showing a typing indicator on an incoming customer message is free and does not count as a billable outbound WhatsApp message.

Yes. Emoji reactions arrive as dedicated webhook events linked to the original message ID, so your app can record customer feedback without triggering keyword flows meant for text replies.

Upload websites, help articles, PDFs, and common question-and-answer pairs to Knowledge in Bird. You also add your business profile details and define skills that guide how the agent responds to specific customer requests.

Yes. Use the Test tab in Bird to preview responses against your saved knowledge base without sending live WhatsApp messages. When you are ready for live testing, restrict the audience to an internal allowlist so your team can chat with the agent on WhatsApp before opening it to customers.

Yes. Turn on handoffs so the agent routes complex requests to your team in Conversations. Assigning a teammate pauses automated replies while they help the customer, and reassigning the thread back to the AI agent resumes automated handling.

Meta determines number eligibility by region and account status. To activate the agent for live customer traffic, the WhatsApp Business Account owner accepts Meta's AI terms during setup and adds a valid payment method to the workspace.

The business-group journey requires an eligible sender and applicable Meta group access. Review the connected Official Business Account number and current eligibility.

A campaign generally sends private messages to individual recipients. Use a group when shared participant visibility is intentional and appropriate.

No. Delivery or read updates can apply to individual participants. Keep message counts and participant delivery or read counts separate.

Bird’s outbound message charge and applicable Meta recipient-level fees have different units. Consult the published pricing and billing records for the actual send.

Meta sometimes sends a read receipt before or without a separate delivered callback, depending on the recipient's connection and device state. Bird records the exact read timestamp from Meta so your delivery and engagement reports reflect what actually happened.

Use your Bird billing ledger and invoices for accounting and financial reconciliation. Per-message cost fields in analytics give a fast operational view of spend, while the billing ledger records finalized Bird and Meta charges.

No. A blank cost field means Meta's pricing callback has not arrived yet, whereas a free service reply shows an explicit zero charge. Wait for delivery or read confirmation so the final category rate appears on the message record.

Delivery and read rates show how many customers saw your message, while revenue attribution comes from connecting WhatsApp clicks and replies to checkout, booking, or CRM events in your own systems.

No. An ad brings a customer into a conversation from an advertising placement. A WhatsApp campaign sends eligible messages to an audience that already has the required permission.

Join the conversation and available ad source to a confirmed order or payment event. Define the attribution window and deduplication rules for that integration.

Do not assume that. Preserve referral data when the connected ad integration provides it and follow the published fields of the actual integration.

Use AI when it can answer the expected request and complete a useful next step. Keep a clear human route for complex or ambiguous enquiries.

Outbound messages report when they are accepted by Bird, sent to Meta, delivered to the customer's device, read, failed, or rejected. Inbound customer replies and emoji reactions arrive as separate events so your app can update thread state in real time.

No. Delivery confirms that the message reached the customer's phone, while a read receipt records when the customer opened it. Because customers can disable read receipts in WhatsApp or Meta can send a read update without a prior delivery callback, Bird stores each timestamp independently.

A rejected message is blocked before it leaves Bird, such as when a free-form reply is sent outside the 24-hour service window, and incurs no send charge. A failed status means the message was dispatched toward Meta but could not be delivered, with an error code explaining whether to fix the template, check the recipient number, or retry.

Configure webhooks in Bird to push status updates and incoming replies to your server as they happen, or query the message timeline through the API and dashboard when troubleshooting a specific delivery.

Queue outbound messages in your application and pace requests according to your workspace API rate limit, which scales with your Bird plan. Keep in mind that Meta also enforces per-number throughput limits and 24-hour business-initiated messaging tiers based on your sender quality rating.

No. Outbound campaigns follow your Meta business portfolio's 24-hour messaging tier, your template quality status, and Meta's per-user marketing frequency caps. If Meta pauses a template or throttles a recipient, check the delivery error reason rather than retrying the same send.

Yes. Inside an open 24-hour customer service window, you can send images, videos, audio files, and PDF documents directly in the chat. For business-initiated messages outside the window, attach a media header to an approved template.

Bird applies its per-message platform fee when your outbound message is processed, while Meta's pass-through fee is recorded once Meta confirms delivery or read status for a billable template.

Meta applies authentication-international rates when businesses above certain volume or eligibility thresholds send one-time passcodes to recipients in select countries. Check the pricing calculator for the destination country to compare standard and international authentication rates.

When you send verification codes through a Bird-managed sender, Meta's rate is determined by Bird's business account profile. When you send from your own connected WhatsApp Business Account, Meta bills according to your company's registered country and volume tier.

Track daily and monthly charges in the Bird dashboard under Usage and Spend, or review the billing ledger for finalized invoice line items broken down by Bird platform fees and Meta pass-through costs.

Each webhook request from Bird is signed with your endpoint's signing secret. Verify the signature against the raw request body before processing the event, and rotate signing secrets in the dashboard whenever credentials change.

Workspace access keys are scoped to the specific permissions you grant, such as sending messages, reading conversations, or managing templates. Create separate keys for each integration so your production app, analytics pipeline, and admin tooling hold just the permissions they require.

Choose your Bird workspace region to control where message logs and conversation records are hosted, and review which webhooks, CRMs, and internal tools receive decrypted message payloads after Meta delivers them to Bird.

Scope the agent's tools and knowledge sources to verified customer records, avoid placing sensitive account details in shared WhatsApp groups or unauthenticated links, and route sensitive account changes to a human teammate.

Yes. You can send initial test messages using Bird's pre-approved templates and shared test senders as soon as you create a workspace. When you are ready to display your own brand name, create custom templates, and receive customer replies, connect your own WhatsApp Business number through Embedded Signup.

Verify the full customer loop: send an approved template, reply from a real phone to open the 24-hour service window, exchange free-form messages or media, and test how your app or team handles a handoff to a human agent.

Yes. When a customer messages your business, Bird tracks the 24-hour service window so you can reply with free-form text and media. Once the 24-hour window closes, Bird blocks free-form sends automatically so you know to send an approved template instead.

When you connect your own WhatsApp Business number, customer replies route directly to your workspace inbox and webhooks. Shared test senders are designed for outbound verification and do not route private customer replies back to your workspace.