Infobip vs Twilio (2026)

In the Tools section a customer adds three kinds of tool to each agent, a Component, an MCP server or an Exchange application, which let the agent call APIs, execute backend logic, retrieve external data and trigger automated workflows. Components encapsulate reusable logic and can orchestrate multiple API calls or backend processes for complex integrations.

MCP servers are configured with a name, endpoint URL, HTTP headers for authentication tokens, and an Allowed functions field naming which actions the server may take when called, so each connection is authenticated and scoped. Exchange applications are selected from a published integrations catalog. Underneath sits the messaging estate the agent acts through, more than fifteen natively integrated channels each with its own API, plus the modular CPaaS X stack.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

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

An AI agent can be set up as an orchestrator that coordinates other agents. The customer adds subagents from a list, and the orchestrator delegates tasks to specialized agents, combines their responses and controls conversation routing, with the agents table showing how many subagents each orchestrator has connected. Each agent's Description field is what other agents read to decide when to call it.

Beneath that, Automation Studio builds journey flows and chatbots that route on rules, triggers and Customer Profiles data, and the Agent connector element drops an AI agent into a chatbot so deterministic flows and autonomous agents combine in one path. Agents themselves execute multi-step tasks, calling tools in sequence to reach a goal.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

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

Agents work across WhatsApp, SMS, RCS, MMS, email, voice, live chat, video, in-app messaging, mobile push, Viber, Messenger, Instagram, Telegram, Apple Messages for Business, Kakao, Line and Zalo, each with its own API page, all flowing through the same system.

Work starts in three ways, inbound when a customer reaches out on any supported channel, event-driven when Automation Studio journey flows are triggered by customer behavior or profile changes, and scheduled when journeys start on dates.

Voice is built in, with a Transfer call to AI agent element placing an agent inside an IVR flow, and Broadcast handles outbound at volume.

Sourceinfobip.com/docs/automation-studioread 2026-09-05

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

Knowledge agents are specialized agents for retrieving information from documents, URLs and files, built for FAQ-style interactions, and they sit alongside a Knowledge Base shared component available across AgentOS. Quality center has a dedicated Knowledge agents section that validates responses against expected answers and tracks quality over time, against a persistent body of content the customer curates. General-purpose AI agents reach the same material through tools and components. The Customer Profiles data platform is a separate database of customer profiles and events.

Sourceinfobip.com/docs/ai-agents/knowledge-agents/overviewread 2026-09-05

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

Customer Profiles is AgentOS's customer data platform, holding person and company profiles, attributes, segments and behavioral events, with interaction history available to AI agents so they can personalize responses and make context-aware decisions across sessions.

Agents also carry session state within a conversation, and past sessions can be viewed through Session history.

Customer Profiles is a store the customer loads and queries, not state the agent forms and retains, and Infobip has no agent memory product, no scope, lifetime or deletion control for retained agent state, and no memory entry in the AgentOS product set.

Sourceinfobip.com/docs/customer-profilesread 2026-09-05

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

Guardrails are a field in the agent's Advanced settings with their own configuration page, where the customer selects content filters that detect and block harmful content in agent conversations, controlling what the agent can and cannot discuss. Release control sits with the customer too, since a configured agent stays a draft until a named version is created and explicitly activated for production, with earlier versions available to roll back to.

Each MCP server carries an Allowed functions list naming what it may do when called. When automation reaches its limit the conversation transfers to Inbox with the complete history, so the customer does not have to start over with the human agent, who works with an Inbox copilot. Infobip does not describe an approval step before an individual agent action goes out.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-guardrailsread 2026-09-05

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

Infobip is audited regularly against ISO/IEC 27001, 27017, 27018 and 22301 and the ISAE 3000 standard, assessed annually, with certificates available for download at infobip.com/certificates and a full or summary copy of current reports provided on written request. It also holds a HIPAA attestation under SSAE 18, and its sub-processor list, data transfer agreement, data retention notice and privacy notice are all public at named URLs.

Single sign on works through any SAML 2.0 identity provider with SP-initiated flow, with identity-provider groups mapped to custom roles and re-synchronized on every login, and role-based access control with predefined and custom roles governs per-feature permissions. Admins can set two-factor authentication to be remembered or required at each login, and password validity and maximum login attempt policies, IP safelisting and separate API access permissions complete the controls. Infobip's identity, authentication and fraud prevention products are things it sells to its customers, not controls over the customer's own tenant.

Sourceinfobip.com/docs/essentials/manage-my-account/account-settingsread 2026-09-05

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

Insights and Analytics, one of the five AgentOS products, monitors AI agent performance, tool usage and session tracking through dedicated dashboards, with every interaction across all five products feeding it and the output covering performance metrics, root causes and AI-driven recommendations. Tool usage and session tracking record what an individual agent did, not only an aggregate.

From inside an agent, Go to Session history opens previous sessions with their analytics, and View as code renders the running configuration. Changes are tracked separately, since agents autosave up to ten draft versions, named versions are created and activated deliberately, and version history records what was live when. Infobip does not describe an immutable audit log with actor and timestamp for configuration changes.

Sourceinfobip.com/docs/insights-and-analyticsread 2026-09-05

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

AI agents are available only in five data centers, Europe (EU1), Sweden (SE1), Germany (FR4), India (MUNM) and United States (NY2), so an account sits in a named region across three continents and the customer can tell which.

Infobip publishes its full legal tier openly, a sub-processor list, a data transfer agreement, a data retention notice and a privacy notice, each at its own public URL, plus an infrastructure overview and network connectivity options.

Infobip offers no self service or other way for the customer to choose or move their region, placement appears to be set at account provisioning, and there is no on premise, private cloud or single tenant deployment.

Sourceinfobip.com/docs/ai-agents/ai-agents/overviewread 2026-09-05

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 instructions can be filled from predefined templates, Appointment booking agent, Order status assistant and Sales representative, and Automation Studio has its own predefined and custom templates to speed up journey and chatbot creation.

Agents move as units, since an existing agent can be duplicated, exported to a .export file and imported into another workspace. Components are reusable logic blocks selected from a list and shared across agents. AgentOS itself ships as five named products a customer switches on. The template set is small, and there is no browsable marketplace of ready made agents.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

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

Under Advanced settings when configuring an AI agent, the Model field lets the customer select the LLM that best matches its requirements for reasoning capability, latency and cost, so each agent can run on a different model. It sits alongside Guardrails and structured output in the same settings panel, and the Instructions field acts as the system prompt for the underlying language model. Third party agents reaching Infobip through MCP are a matter of interoperability, not model choice.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

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

Infobip publishes an API reference, SDKs, release notes, an integrations catalog and a public roadmap, all reachable without a login, plus Postman collections, a GitHub organization and a developer Discord. Every channel is exposed as its own REST API, and the modular CPaaS X stack is sold specifically for platforms building on top.

On the agent side, MCP servers let an Infobip agent call outside systems with scoped allowed functions, and an agent's configuration can be viewed as code, exported to a portable file and imported elsewhere, with structured output constrained by a customer-defined JSON schema. Components let a developer encapsulate backend logic the agent then calls, and Exchange applications add partner integrations.

Sourceinfobip.com/docs/apiread 2026-09-05

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

AgentOS ships Quality center, a set of tools to monitor, evaluate and improve agent response quality, where the customer creates test groups, defines test cases, runs tests and reviews results to confirm agents behave as expected.

For Knowledge agents it validates responses against expected answers and tracks quality over time, producing a scored comparison. Separately, the build flow has a step before publishing, Test an AI agent, that validates agent responses and behavior, and agent versioning lets a team activate a specific version and roll back a bad one. The tests run against the customer's own agent.

Sourceinfobip.com/docs/ai-agents/quality-center/overviewread 2026-09-05

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

An Infobip agent reaches other systems through three tool types, all programmatic, Components running backend logic, MCP servers called at an endpoint URL with scoped allowed functions, and Exchange applications from the integrations catalog, and its output side is the messaging estate of more than fifteen channels, each with its own API. AgentOS offers no browser control, hosted session, virtual desktop or interface automation, and nothing in the agent configuration offers a browser, a screen or a pointer.

Sourceinfobip.com/docs/ai-agents/ai-agents/configure-ai-agentread 2026-09-05

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