WhatsApp Business FAQs

Connect campaigns, useful notifications and service conversations to your business systems. Use the channel’s supported native experiences, AI assistance and human support to help customers complete a task.

A campaign can start a useful conversation. Route the customer’s reply to the right AI assistant or team, keep the original offer and account context available, and help complete the purchase, booking or service request.

The app and Business Platform serve different operating needs. Review automation, team access, integrations and the eligible coexistence or migration path for your number.

Review Bird’s sending charges and applicable Meta fees using the published country and category rates. Include the operating and integration requirements of your use case.

Connect the chosen assistant to approved knowledge, authorized actions and a clear human handoff. Bird AI, Meta Business Agent and MCP developer access are distinct arrangements.

Create a workspace to explore a sender, template or integration. Speak to a specialist for provider migration, multiple brands or markets, calling and a coordinated customer journey.

No. Campaign recipients receive individual messages. A WhatsApp group is a shared conversation whose participants can see the room and other participants’ messages.

Business-initiated marketing uses an approved marketing template and the required customer permission. Approval, audience eligibility and market availability are separate checks.

Use the approved template’s parameters and a supported language. Review missing customer values before sending, and keep the destination consistent with the message.

A read is a messaging observation. Record purchases, bookings or qualified leads in the system that owns the outcome and join them to the campaign separately.

No. Review the approval and applied category for the language selected by the send. Other languages can have different verdicts.

Your language policy determines the result. A required recipient language must be supplied; permitted fallback can resolve through an approved base language or configured default. Use fail when sending an alternative is inappropriate.

MCP is a way for an authorized tool or agent to manage Bird resources. Template creation still follows the same ownership, review and Meta approval requirements.

No. WhatsApp uses distinct categories including marketing, utility and authentication. Choose the category that matches the message’s actual purpose.

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. A workspace can contain several WhatsApp Business Accounts, and each can contain several phone numbers. A connected account has a specific organization, workspace and regional owner.

Review whether your number and account qualify for the supported coexistence path. Do not assume every app number must be deleted or that every account is eligible.

No. These are distinct Meta processes with different purposes and eligibility. Completing one does not automatically grant the other.

Use a specialist-led plan for existing accounts, multiple numbers or a coordinated cutover. Review access, templates, routing, reporting and rollback before changing customer traffic.

Eligible incoming customer messages establish the service window used for free-form replies. Follow the documented window calculation and use an approved template when required.

Build a clear escalation path with a receiving team, context and an understandable next step. Human assistance should remain accessible when automation cannot resolve the request.

Bird’s read acknowledgement updates a received message and is not a billable outbound message. Typing and read state have distinct behavior.

Bird exposes WhatsApp reaction events. Handle the reaction in the context of the referenced message rather than treating it as a new textual answer to every workflow.

No. Meta Business Agent is Meta’s runtime connected to an eligible business number. Bird AI assistance is a distinct operating model; evaluate the knowledge, actions and handoff of the chosen setup.

MCP lets an authorized agent or tool work with Bird resources. That developer integration does not by itself create a customer-facing assistant or define its behavior.

Connect an authorized action to the system that owns the order or booking. Apply identity checks and customer confirmation where needed, then communicate the recorded result.

Review task completion, accurate answers, failed actions and the quality of handoff. Include difficult and ambiguous requests in the evaluation.

No. A WhatsApp Flow is a native structured experience inside the chat. A Bird journey coordinates a wider process and can connect the form result to other actions or channels.

Use current availability and submit the selected slot to your booking system. Show a confirmed appointment only after that system accepts it.

Explain the change, preserve the relevant answers and offer a valid alternative or a human handoff.

Use a form when a structured set of choices makes the task easier. Keep simple questions and nuanced service requests conversational.

Payment options vary by market, provider and business eligibility. Design the appropriate supported experience and keep a useful hosted-checkout path where needed.

No. A click indicates interest. Record the order or successful payment in the system responsible for the transaction.

Use approved product knowledge and current availability. Keep recommendations relevant and allow a person to take over when the customer needs specialist advice.

Your commerce and payment systems remain responsible for those actions. The conversation should reflect their confirmed result.

No. WhatsApp Business Calling uses WhatsApp’s calling experience and eligibility rules. Telephone voice uses a different route and contract. WhatsApp calls must not be bridged to the public telephone network.

Do not treat messaging permission as universal calling permission. Follow the applicable business-calling consent and eligibility requirements.

Connect the supported voice runtime with approved knowledge, authorized actions and a human transfer path. Evaluate the actual calling setup and market before launch.

Offer a clear next step, such as a message, callback request or support route. Keep the task context and respect the customer’s communication preferences.

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.

Provider observations can arrive in different shapes or orders. Preserve the separate read timestamp and documented message-state behavior rather than inventing a missing delivery event.

Use the billing ledger as the financial authority. Message cost fields are useful projections and can be incomplete while processing catches up.

No. Unknown or unresolved cost is distinct from an explicit zero. Reconcile the applicable charges before drawing a conclusion.

No. Join the conversation or campaign to a confirmed business event using an appropriate identity and attribution model.

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.

Follow accepted, sent, delivered, read, failed and rejected observations for outbound messages, and received events for inbound messages. Reactions have their own event and change log.

No. Read is a separate observation and timestamp. An individual message can have a read observation without a delivered event; preserve the documented state instead of inventing that event.

Rejected means Bird stopped the message before dispatch without charging it. Failed can describe a processing or provider delivery failure; inspect the recorded cause before deciding whether another attempt is appropriate.

Subscribe to the relevant webhook types or read a message’s event timeline through the published API. Keep unfamiliar event types for investigation and verify webhook authenticity before acting on them.

Use the documented API rate-limit response and a bounded queue. Review the sender’s Meta throughput and the portfolio’s messaging allowance separately from the Bird API limit.

No. A campaign must respect the current sender, portfolio, template and recipient rules. Treat a provider restriction according to its actual cause instead of repeatedly resending the same message.

Use the supported free-form content types inside the service window, or the appropriate approved template format. Review the published media shape and the selected template’s parameters.

Bird charges its outbound component during processing. The applicable Meta component can be recorded from delivered or read callbacks. Use billing records for reconciliation and keep unresolved cost distinct from zero.

Meta applies a distinct rate under its country, business-location, eligibility and start-time rules. Review the current authentication-international guidance and the published rate for the destination.

Managed authentication senders use Bird’s account context. Your own connected account has its own business-location and eligibility context; compare the published rate for the actual route and category.

Use the dashboard’s Usage and Spend views and the billing ledger. Message cost fields help investigate individual sends but can be incomplete while charge projections catch up.

Follow the published webhook signature-verification procedure with the endpoint’s secret. Verify the original payload before acting on it, and use the documented rotation process when changing the secret.

A key can perform the operations granted by its scopes and workspace context. Give each integration the access it needs and review the separate permissions required for sender and account management.

Review the configured Bird region, WhatsApp provider processing and the business systems receiving messages. Evaluate the complete customer-data journey rather than treating channel encryption as a guarantee about every downstream system.

Use verified identity, authorized retrieval and scoped actions. Keep sensitive data out of unnecessary prompts, public URLs and shared groups, and preserve a human path for exceptional requests.

Bird-managed senders and the managed template catalog support an initial eligible send. Connect your own business number for your business identity, inbound conversations and workspace-authored templates.

Test an eligible send, the actual reply, the application action and its confirmed outcome. Include a closed service window, an unexpected response and a request for human help.

Yes. A free-form request into a closed window can be refused before admission. If the window expires before dispatch, the admitted message can fail with the recorded service-window error.

Incoming customer messages reach the connected number’s workspace. Shared Bird-managed senders do not provide a private inbound conversation for every workspace using them.