Bird vs Twilio (2026)

An agent signs in to Bird through browser OAuth and then acts with a scoped, revocable grant. Through the hosted MCP server it sends email, SMS, WhatsApp messages and one time passcodes, orders phone numbers, adds sending domains and senders, and manages templates, contacts, audiences and preferences.

Grants cover only the overlap of what the client asked for, what the user approved and what the user holds, and owner and platform admin scopes can never be delegated. In the other direction, webhook destination connectors hand each inbound message to a Claude Managed Agents session or a Grok routine. Connections to the customer's own business systems are the customer's agent's to make.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Agent Connect gives an agent a tool system built on standard function calling. A developer defines a name, description and JSON schema, and the SDK formats the tool for whichever LLM provider runs the agent. Custom tools are written with a decorator in Python or defineTool in TypeScript and can read the session, the customer profile and the channel.

Three tools come built in, knowledge search over Enterprise Knowledge, memory retrieval and escalation to a Studio flow that can route into Flex. Because each tool is the customer's own code, the agent can act in any system the customer can reach, and Twilio's own messaging, voice, email and Verify APIs sit alongside as further actions.

Sourcetwilio.com/docs/conversations/agent-connect/core-conceptsread 2026-10-11

Events move to the agent and its output moves back out through Bird. Each inbound WhatsApp, SMS, Apple Messages or mailbox message is delivered as event JSON, failed deliveries are retried, and a webhook can be paused or deleted.

The sequence of steps an agent takes, its tools and its decisions run in the customer's agent platform, and for voice the customer's application owns speech, reasoning and business tools while Bird carries the call.

There is no workflow builder or multistep runtime for agents inside Bird, so a reminder sequence or an escalation path is something the customer's agent or its own scheduler runs.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Conversation Orchestrator joins voice calls, SMS and WhatsApp messages into one threaded conversation tied to a customer profile, with a lifecycle that moves each conversation from open to inactive to closed on timeouts the customer sets. Studio, Twilio's visual flow builder, runs multistep communication workflows and receives the agent's handoff payload, and Flex routes the conversation to a person with the history attached. The reasoning inside the agent stays in the customer's own code, while the movement of a conversation between channels, the agent, flows and people runs on Twilio.

Sourcetwilio.com/docs/airead 2026-10-11

Inbound WhatsApp, SMS, Apple Messages and agent mailbox email each fire an event, whatsapp.received, sms.received, amb.received and email_mailbox.message_received, that a webhook delivers to the agent and that starts a new agent run. MCP Events let an MCP client subscribe to events such as new mail and receive each as a signed webhook. Voice calls reach a customer built voice application over SIP, and agent mailboxes give an agent an address of its own.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Inbound voice calls, SMS, WhatsApp, RCS and web chat all reach the agent through one shared callback, so a single handler serves every channel. Webhooks and WebSocket connections carry the events, and Conversation Relay streams a live phone call to the agent with speech recognition and synthesis handled by Twilio. Outbound sends and calls start from the REST APIs, and Studio flows start on incoming calls, messages or API requests, which covers inbound, event driven and programmatic starts across the channels a contact center uses.

Sourcetwilio.com/docs/conversations/agent-connect/core-conceptsread 2026-10-11

No knowledge base for an agent to search sits inside Bird. Its skills are instruction packs for the agent itself, one routing requests to the right CLI command group and one auditing a sending domain's authentication and mail records, and the knowledge base Bird runs is customer help for account setup, deliverability and billing. Grounding an agent in a company's own documents happens in whatever agent platform the customer runs. Templates, contacts and audiences in Bird hold messaging data, which an agent can read through the MCP server but which is not indexed for retrieval.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Enterprise Knowledge stores a company's policies, documents and reference material as knowledge bases that agents and human agents search for grounded answers. It is billed as a persistent store, $0.018 per GB hour of storage and $0.005 per retrieval, and Agent Connect exposes it as a knowledge search tool the agent calls when a customer asks a question, returning matching passages for the reply. Customer profiles live separately in Conversation Memory.

Sourcetwilio.com/en-us/products/conversational-ai/pricingread 2026-10-11

Every routed message starts a new session or run, and the agent receives the event payload for that message alone, so any history across messages lives in the customer's agent platform. Message records, contacts and audiences persist in the organization's region as the messaging data model, and an agent can look a contact up through the MCP server. Nothing in Bird stores what an agent learned about a person or hands it back on the next message.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Conversation Memory keeps one profile per customer inside a memory store. Each profile holds conversational memory, the observations and summaries extracted automatically after each conversation closes, and factual memory, the traits and identifiers that describe the customer. New observations are added, merged with an existing one when they add detail, replace it when they contradict it, or are discarded when they lack support, so the profile stays current.

A Recall API returns the most relevant observations, summaries and recent messages by semantic and lexical search, and Agent Connect calls it on every messaging turn. Up to five stores separate data such as sandbox and production, each profile holds up to 500 observations and 500 summaries, and observations can be switched off per configuration. Memories carry no fixed retention period and persist until they are reconciled, edited or removed.

Sourcetwilio.com/docs/conversations/memory/conversation-memory-conceptsread 2026-10-11

A person approves each agent's access on a consent screen that flags the client name as unverified, can revoke the grant at once under connected apps, and can pause a webhook to stop deliveries.

The outbound call tool prepares a call that a person reviews and places from the browser, template versions reach recipients only once submitted, and destructive tools carry annotations so the agent host can ask before running them.

Sends of email, SMS and WhatsApp go out when the agent calls the tool, with no Bird approval step in between, and handing a conversation to a person is left to the customer's own systems.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

The built in escalation tool hands a conversation to a Studio flow and on to a Flex agent with full context, on voice after the agent's last reply plays and on digital channels by posting straight to the flow. When and why to escalate is the customer's code to decide, and Agent Connect makes no decisions about what the agent does.

Conversation Memory applies a prompt exclusion meant to screen out GDPR special category data. Agent Identity adds scoped, revocable tokens and human approval over SMS or RCS before a high risk action, but it is in private release, so approval before each action is not yet open to every customer.

Sourcetwilio.com/docs/conversations/agent-connect/core-conceptsread 2026-10-11

Teams are organized into workspaces with member roles, API keys are scoped per channel with none, read or write access to email, SMS and WhatsApp, and agent access runs on OAuth grants limited to what the user holds and approved. Bird holds ISO/IEC 27001:2022, SOC 2 Type 2 and SOC 3 reports and HIPAA compliance, and its trust center supplies an ISO certificate bundle, statement of applicability and penetration test letters on request. Bird does not mention single sign on for its dashboard.

Sourcebird.com/securityread 2026-10-11

Twilio Console sign in works through a corporate identity provider over SAML 2.0, with SP and IdP initiated login and multiple SSO profiles, on Twilio Editions that include single sign on. Which accounts a user can open and which role they hold are set in the Console and Admin Center, and Flex maps identity provider roles to its own.

Twilio holds ISO/IEC 27001 certification and is audited externally on a regular cycle, with security and privacy reports available on request through security.twilio.com. Agent Connect and Conversation Memory are not HIPAA eligible or PCI compliant, so regulated workflows sit outside them.

Sourcetwilio.com/docs/iam/single-sign-onread 2026-10-11

Audit logs record changes such as API key updates and member invitations, each webhook attempt shows the agent platform's response status and body or a failure reason, and call records and voice events track phone calls, with every message kept as a record in its region. That shows what reached the agent and what Bird sent. The agent's own reasoning and tool sequence are logged in the platform that runs it.

Sourcebird.com/securityread 2026-10-11

Conversation Orchestrator stores every message and transcribed call as a threaded conversation linked to a profile, Conversation Memory shows the observations and summaries it extracted, and Conversation Intelligence analyzes each conversation for sentiment, summaries and custom criteria. Agent Connect logs a warning when it falls back from the Memory API. Together that shows what was said and what the system learned. The tool calls and reasoning live in the customer's agent, so a step by step trace of a run comes from the customer's own logging.

Sourcetwilio.com/docs/conversations/memoryread 2026-10-11

Each organization picks the us1 or eu1 region at signup, starting from a guess based on location, and the choice is fixed afterward. The workspace, API keys, messages, recipient data and event logs stay in that region and are never copied across, with only sign in and account administration held globally. Keys carry their region in the prefix, and a request to the wrong region is refused with a 421 error.

Sourcebird.com/docs/api/regionsread 2026-10-11

The agent and its model run wherever the customer hosts them, since Agent Connect is an SDK inside the customer's own application. Twilio's isolated regions are US1 in the eastern United States, IE1 in Dublin and AU1 in Sydney, and a customer chooses one to keep a workload's data there.

Voice, SIP trunking and messaging run in Dublin, and voice in Sydney, while Conversation Memory, Orchestrator, Enterprise Knowledge and Conversation Relay are offered in the US region only, so the agent layer runs in the US. While regions roll out, Twilio does not guarantee that all data stays in the selected region.

Sourcetwilio.com/docs/global-infrastructure/regional-product-and-feature-availabilityread 2026-10-11

Agent skills and plugins come for Claude Code, Codex, Cursor, OpenCode and Antigravity, including a CLI router skill and an email audit skill, plus AI builder guides and a setup prompt to paste into an existing agent. These equip an agent the customer already runs. Bird offers no ready made agents for support or sales.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

Agent Connect starts from a quickstart and integration guides for AWS Bedrock and Microsoft Foundry, Conversation Intelligence ships Twilio authored language operators alongside custom ones, and Twilio Skills and the Code Exchange give developers guided patterns and sample apps. Each of these is a starting point the customer builds on. Twilio does not offer finished agents for support, sales or scheduling that a customer switches on.

Sourcetwilio.com/docs/conversations/agent-connectread 2026-10-11

No model runs inside Bird. The customer's agent platform, whether Claude, Codex, Cursor, Grok or its own voice application, reaches Bird through the CLI, MCP or webhooks, and which model that agent uses is decided entirely outside Bird. The webhook connectors are set up for Claude Managed Agents and Grok, and any other platform receives the same event JSON through a plain webhook.

Sourcebird.com/docs/ai/set-up-your-agentread 2026-10-11

The customer picks the model. Agent Connect does not run inference. The customer supplies the LLM application and controls how it responds, with integration guides for AWS Bedrock and Microsoft Foundry and support for OpenAI or any other provider. Tools are formatted for whichever provider the customer uses, so switching models is a change in the customer's own code. Twilio's own generative features, such as observation extraction in Conversation Memory, run on models Twilio chooses.

Sourcetwilio.com/docs/conversations/agent-connectread 2026-10-11

Every public endpoint sits in an API reference generated from an OpenAPI spec, with SDKs for TypeScript, Python and Go and a bird CLI for the shell. The MCP server comes in three forms, a hosted endpoint with the full tool catalog, a dynamic endpoint exposing only search and execute for clients with tool limits, and a local server inside the CLI. All three sign in through OAuth with dynamic client registration and PKCE, and their tools create and change Bird's own objects, such as messages, numbers, domains, senders, templates and contacts.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

Every product has a public REST API and helper libraries, including a Conversation Memory API with profile, trait, observation, summary, import and Recall endpoints. Agent Connect itself is an SDK for Python and TypeScript with a FastAPI server for webhooks and WebSockets. An MCP server gives coding agents semantic search across more than 1,500 endpoints in over 30 products, and Twilio Skills package product guidance for AI coding tools.

Sourcetwilio.com/docs/airead 2026-10-11

Each webhook attempt can be inspected with the agent platform's response status and body or the reason a delivery failed, which traces why an agent did not run. Template versions stay away from recipients until they are submitted, so an agent's draft can go out as a test message and be checked on a real phone first. Testing what the agent itself says or does belongs to the agent platform the customer uses.

Sourcebird.com/docs/ai/route-messages-to-an-agentread 2026-10-11

Conversation Intelligence runs language operators over voice and messaging conversations, Twilio authored ones for sentiment and summaries and custom ones written as natural language prompts, which a team can point at its AI agent's conversations to flag compliance misses or missed upsells. That reviews live traffic after the fact. The Agent Connect quickstart builds and tests an application locally, and there is no suite of saved test cases with pass or fail results to run against a new version of an agent before it goes live.

Sourcetwilio.com/en-us/products/conversational-ai/pricingread 2026-10-11

Agents use Bird through API calls, CLI commands and MCP tools for messaging, numbers and domains. No hosted browser, remote desktop or screen control is part of the platform. Even the outbound call tool stops short of acting on its own, preparing a call that a person reviews and places from the browser.

Sourcebird.com/docs/ai/mcp-serverread 2026-10-11

The agent layer connects an agent to communication channels, customer memory and knowledge through APIs and tools the customer writes. No hosted browser, remote desktop or interface control is part of it. An agent that has to work inside a web page or a desktop application brings that capability as a custom tool in the customer's own code, outside anything Twilio runs.

Sourcetwilio.com/docs/airead 2026-10-11