[WhatsApp](/whatsapp-api) # Bird vs 360dialog for WhatsApp. Bring WhatsApp messaging, native experiences and customer workflows into Bird. Give your team a shared place to turn campaign responses and service requests into completed tasks. [Get Started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fwhatsapp%2Fonboarding) [Contact Sales](/demo?product=whatsapp-migrate-360dialog) ## 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-360dialog 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 | 360dialog | | --- | --- | --- | | Operating model | Bring WhatsApp into the customer workflows your team operates in Bird. | Choose the API and partner applications that make up the complete solution. | | Native Flows | Connect a focused native form to the wider customer journey. | Use the documented WhatsApp Flows integration. | | Marketing setup | Align templates, account onboarding, audience eligibility and outcomes. | Review Marketing Messages API onboarding and the connected application’s campaign controls. | ## Where does 360dialog fit? 360dialog is a candidate for teams choosing a WhatsApp API layer and a partner or application stack around it. Its offering emphasizes API access, partner distribution and integration choices, including native Flows and marketing-message onboarding. ## Review the documented capabilities - [360dialog platform](https://360dialog.com/): Primary product documentation reviewed for this comparison. - [360dialog Flows documentation](https://docs.360dialog.com/docs/messaging/flows): Primary product documentation reviewed for this comparison. - [360dialog marketing-message onboarding](https://docs.360dialog.com/docs/waba-messaging/sending-marketing-messages/onboarding-and-sending-messages): 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. ## Map the complete partner setup around the API. A WhatsApp channel can sit beneath a separate inbox, campaign tool or application. Identify the provider of each customer-facing function before deciding what should move into Bird. ## Account and channel Record the WhatsApp Business Account, sender and administrator. Agree the supported transition with the parties that control those assets. ## Partner applications List the inbox, campaign system and automation connected to the channel. Decide which functions remain in place and which your team will operate in Bird. ## Native Flows Inventory published forms, data-exchange endpoints and completion handlers. Test validation, expired requests and the actual booking or order confirmation. ## Marketing delivery Review the account onboarding and message category for your campaign. Compare the same markets and traffic mix, including the platform and Meta charges. The evaluation is complete when the customer can finish the same task and your team can support it without losing the application context held by a partner. [Read the 360dialog migration guide](/docs/guides/whatsapp/migrate-from-360dialog) ## Move the workflow along with the number. Inventory the connected WABA, API credentials, partner applications, webhooks and any coexistence arrangement. Decide which partner functions remain, move into Bird or need a replacement integration. ## 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 360dialog to Bird](/docs/guides/whatsapp/migrate-from-360dialog): 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 360dialog. 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-360dialog) ## 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)