[WhatsApp](/whatsapp-api) # Bird vs Wati for WhatsApp. Bring WhatsApp campaigns and customer conversations together with the data, AI assistance and workflows your business runs in Bird. [Get Started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fwhatsapp%2Fonboarding) [Contact Sales](/demo?product=whatsapp-migrate-wati) ## Set up with your agent [Read the agent setup guide](/docs/ai/set-up-your-agent) Copy this prompt into your coding agent: ```text Bird connects customer communications, data and automation. Help me build with Bird using my coding agent. 1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available. 2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup. 3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step. First task: Inventory my current WhatsApp provider, senders, templates, callbacks, automation and reporting. Read the provider-specific migration guide, discover available Bird MCP or CLI operations and prepare a controlled migration test. Keep the current provider running until I approve the cutover. Use this Bird page as the starting context: https://bird.com/whatsapp-api/compare/bird-vs-wati Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links. ``` [Read customer stories](/customers) [Explore Enterprise](/enterprise) - [Airwallex](/customers/airwallex) - [Glovo](/customers/glovo) - [Zillow](/customers/zillow) - Uber - [Binance](/customers/binance) - Adobe - Meta - PayPal - Pinterest - Square - [Al Jazeera](/customers/aljazeera) - [Aramex](/customers/aramex) - [Bazaar Technologies](/customers/bazaar) - [ComparaOnline](/customers/compara) - [Emma](/customers/emma) ## How each platform fits the work | Capability | Bird | Wati | | --- | --- | --- | | Campaign measurement | Join campaign identity to the actual lead, booking or order. | Use supported template click tracking and evaluate the plan and link-domain setup. | | Service and calls | Keep the customer task, AI assistance and human handoff connected. | Configure call routing and post-call automations for the team. | | Custom integrations | Use published Bird operations and scoped workspace access. | Review the published API and the eligibility of custom calling integrations. | ## Where does Wati fit? Wati is a candidate for teams organizing WhatsApp campaigns, service routing and automation in its workspace. Its documented capabilities include template click tracking, call routing and post-call actions; plan and integration eligibility need to be evaluated for the intended setup. ## Review the documented capabilities - [Wati template click tracking](https://support.wati.io/en/articles/11463471-how-to-enable-click-tracking-for-my-template-messages): Primary product documentation reviewed for this comparison. - [Wati call routing and follow-up](https://support.wati.io/en/articles/16616379-how-to-set-up-whatsapp-call-routing-and-post-call-automations): Primary product documentation reviewed for this comparison. - [Wati custom calling integration](https://support.wati.io/en/articles/15203965-how-to-integrate-whatsapp-calling-with-your-crm-or-internal-portal): Primary product documentation reviewed for this comparison. ## Why choose Bird for WhatsApp? Choose Bird when your WhatsApp experience belongs with the customer data, campaigns, AI assistance and service workflows your team operates in Bird. Evaluate the whole exchange, from the first eligible message to the recorded result. ## A useful campaign Review the audience, approved content, destination and team handling replies. ## A connected service task Use current business information, permitted actions and a clear human handoff. ## A measurable result Join the conversation to the order, booking or case outcome and reconcile its cost. ## Test the campaign and the team response together. Use a campaign that creates a real question for your team. Compare how the audience is selected, how the reply reaches an operator and how the eventual lead or order is recorded. ## Audience and preferences Inventory the tags, consent records and exclusions used by your campaign. Confirm the same inclusion and suppression decisions in Bird. ## Tracked links Record the link domain and destination used in each template. Separate the click observation from the lead or purchase recorded by your business system. ## Team and call routing Rehearse an available assignee, an unavailable contact owner and an unanswered call. Compare the resulting assignment and follow-up your team must handle. ## Custom calling Check access before including a custom voice integration in the evaluation. Wati documents this integration as beta and available on request. Measure whether the customer reaches the right person and the lead or order keeps its identity across campaign, chat and call. [Read the Wati migration guide](/docs/guides/whatsapp/migrate-from-wati) ## Move the workflow along with the number. Inventory campaign audiences, tags, automations, shared-team assignments, click-tracking domains and calling workflows. Preserve lead and order identities when translating those workflows to Bird. ## Prepare the assets Confirm account ownership, sender access and the supported migration path. Keep consent, suppression and customer identities intact. ## Rehearse the cutover Test sends, replies, callbacks and business actions in a controlled evaluation. Agree the monitoring and recovery owner. ## Protect the customer experience Plan active conversations and queued work. A migrated sender does not automatically migrate every application workflow. ## Questions about choosing and switching ### Can we move an existing WhatsApp number to Bird? Review the number, business-account ownership and current provider setup with a specialist. Use the supported migration or eligible coexistence path and test the complete exchange before moving wider traffic. ### Which provider is cheaper? Compare the actual destination and category mix, volume, platform charges, Meta fees, support and integrations. A headline rate does not establish the total cost of your deployment. ### Will templates and automations move automatically? Inventory each asset and confirm the supported transfer or recreation path. Preserve customer preferences and application identifiers; do not assume moving the sender recreates the service workflow. ## Plan the next step - [Move from Wati to Bird](/docs/guides/whatsapp/migrate-from-wati): Prepare the assets, integration, cutover and verification. - [WhatsApp guides and answers](/whatsapp-api/resources): Find the detail behind the evaluation. - [WhatsApp pricing](/whatsapp-api/pricing): Review the published country and category rates. - [Compare WhatsApp platforms](/whatsapp-api/compare): Review the broader provider shortlist. ## Plan your move from Wati. Bring your sender setup, customer workflows and evaluation results. Work through the transition with a WhatsApp specialist. [Read the migration guide](/docs/guides/whatsapp/migrate-from-wati) ## Related resources - [Connecting WhatsApp to Bird: from buying a number to a live channel](/learn/whatsapp/connecting-whatsapp-to-bird) (video) - [Sending WhatsApp messages](/docs/guides/whatsapp/sending-whatsapp) (docs) - [What is the 24-hour customer service window on WhatsApp?](/explained/whatsapp/what-is-the-24-hour-customer-service-window) (answer) - [WhatsApp message builder](/tools/whatsapp-message-builder) (tool) [Get an implementation brief](/learn/workspace?topic=whatsapp)