Les nouveautés. Ce qui vous attend.

WhatsApp now supports coexistence: connect your WhatsApp Business App number to Bird and keep using the app on your phone. You can also choose to import contacts and recent chat history during setup.

Connect your WhatsApp Business App.

Bird is now one click away in Claude. Add it from Claude's connector directory, connect your workspace, and ask Claude to handle your email, SMS, WhatsApp and inbox:

• "Set up acme.com as a sending domain and tell me which DNS records to add."
• "How did last week's newsletter do?"
• "Why are emails to Outlook bouncing?"
• "Draft replies to everything unanswered in my support inbox."
• "Create an inbox for yourself on inbox.ai and check what has arrived."

The hosted Bird MCP server at mcp.bird.com now supports MCP Events. A connected client, such as ChatGPT, can subscribe to what happens in your workspace and receive each event as it happens, so your agent can act on new mail without polling for it.

You can subscribe to new mail in a mailbox, inbound SMS, WhatsApp and Apple Messages, and email deliveries. Filters narrow a subscription to one mailbox, conversation, number or broadcast. Each event arrives at the client's callback as a webhook signed with the client's own key. The client renews its subscription, which lasts up to a day at a time.

Every subscription shows in your dashboard's webhook list with its client, event and filters, and you can delete it there.

Read the MCP Events guide.

You can now connect your Bird account to Vercel and let the integration set up your API credentials. It creates a Bird API key and saves it with your workspace's regional API endpoint in your selected Vercel projects, so you don't have to copy either value between dashboards.

During setup, choose your Bird workspace, Vercel projects, and Preview or Production environment. Bird saves BIRD_API_KEY and BIRD_API_BASE_URL as encrypted environment variables. Finish the installation in Vercel, then redeploy your app to use them.

Connect Bird to Vercel.

Verify can now send passcodes from an SMS Sender ID or WhatsApp number in your workspace. Choose a sender for each channel on Configure > Channels, then override it for a destination on the Countries page. Your verification requests do not change.

For SMS, select an existing Sender ID that is registered and permitted for authentication messages in the countries you serve. If your default Sender ID cannot be used in a destination country, Verify sends from Bird Verify there instead. A Sender ID selected for a specific country does not get that sender fallback; if it cannot send, Verify moves to the next channel in the verification plan.

For WhatsApp, select a connected number and an existing approved authentication template from its WhatsApp Business Account. Verify inserts the passcode into that template. You can manage numbers, Sender IDs, and templates from the sender menus in the dashboard.

Senders and branding explains the requirements and fallback behavior. Country configuration shows how to set a destination-specific sender.