Plivo vs Twilio (2026)

Flows act in other systems through app action nodes with prebuilt actions for Zendesk, HubSpot and Google Workspace, HTTP request nodes for any API, and call forward nodes.

The wider catalog adds Salesforce, Zoho CRM, Shopify, Stripe, Intercom, Jira, Notion, Airtable, Freshdesk, Slack, Google Calendar, Calendly, ServiceNow, GitHub, Google Sheets, MongoDB, BigQuery and PostgreSQL, along with MCP servers, API based tools and Python code nodes. In a single conversation an agent can look up a booking, check availability, book a slot and text a confirmation.

Apps are authenticated once under Settings and then used across agents, and the team handles that authentication and any field mapping itself before the Vibe Agent can use an app in a draft.

Sourceplivo.com/docs/aiagent/getstarted/overviewread 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

Each agent is a flow on a drag and drop canvas. Nodes such as an AI reply, an app action, an HTTP request or a call forward are joined by paths that branch on the customer's input or on system conditions, and variables carry extracted or generated values from step to step. A trigger node starts the flow from a channel or an API call.

The Vibe Agent drafts a flow from a plain English description, first writing a plan that covers the trigger, channel setup, node settings, edge cases and when to close the call, asking clarifying questions and flagging requests it cannot build. By Plivo's own estimate the draft gets a flow about 70 percent of the way, and every generated node is meant to be reviewed by hand. The Playground highlights the active node and the path taken through the flow.

Sourceplivo.com/docs/aiagent/getstarted/overviewread 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

Flows start when a call, a web chat message, an SMS or a WhatsApp message arrives, or when another system sends an authenticated HTTP request with optional input parameters, with basic auth on by default.

One agent can go live on voice through a purchased number, WhatsApp through a business account with template management, web chat and SMS over 10DLC, and conversations run inbound and outbound.

Each number takes one inbound flow while one flow can answer several numbers, outbound calls start from an Initiate call node or an API request, and the flow branches on whether a call was answered, busy, unanswered or rejected.

Sourceplivo.com/docs/aiagent/aistudio/triggerread 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

A knowledge base combines uploaded files of up to 64MB, including spreadsheets, PDFs, Word documents, text, JSON and XML, whole websites of up to 10,000 URLs with limits on depth and paths, and apps such as Notion, Confluence, Freshdesk, Zendesk and Intercom. Website and app sources refresh automatically as often as weekly, one knowledge base can serve several agents, and the agent runs a semantic search at every response step, passing the most relevant chunks to the model and pulling nothing when nothing matches.

Sourceplivo.com/docs/aiagent/aistudio/agentconfiguration/knowledgebaseread 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

Variables hold names, emails, IDs and other values the agent extracts while a flow runs. They are set on the AI conversation node's Extract Variables tab and passed to later steps, and each reply draws on the path the conversation has taken so far. Plivo says context carries over when one customer moves from one channel to another, though where that context is kept, for how long, and whether it reaches a separate conversation days later is left open.

Sourceplivo.com/docs/aiagent/getstarted/overviewread 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

Conversations hand over to human specialists assigned by agent, team or custom rules and routed by skills or queues, with business hours, holidays, agent status, SLAs, retries and workload managed from one dashboard, and calls transfer to a person by number forwarding or authenticated SIP transfer. Transfer to a human is included in the agent price. No step lets a person approve an action or a reply before the agent sends it.

Sourceplivo.com/docs/aiagent/getstarted/overviewread 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

Plivo holds a SOC 2 certification of unstated type, audited each year by an independent firm, is certified compliant with PCI DSS Level 1, has completed a CSA STAR Level 1 self assessment, takes part in the EU and US Data Privacy Framework, and signs a HIPAA business associate agreement on Enterprise.

Each user signs in with unique credentials, a passphrase and a phone verification code sent by SMS or voice call, data is encrypted with TLS 1.2 or higher in transit and 256 bit AES at rest, and backups are encrypted and stored redundantly. Single sign on comes with the Enterprise plan, and Plivo says nothing of roles or permissions inside the studio.

Sourceplivo.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

Six reporting dashboards cover conversations, customer metrics, agent and AI performance, availability and operations. In the Playground, analysis mode shows each node's execution with the prompt used, the tool response, response time and model metrics, and every session carries a run ID for tracing it in the logs. Outside the Playground, node by node detail on live conversations and a log of who changed an agent go unmentioned.

Sourceplivo.com/docs/aiagent/aistudio/playgroundread 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

Plivo advertises data residency in the US, the EU and Asia Pacific, while its platform runs on Amazon Web Services compute and storage spread worldwide. Which region an account lands in, and whether the customer chooses it, is not spelled out. The studio runs as a hosted service only, with no private cloud or on premises edition.

Sourceplivo.comread 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

The studio offers templates alongside plain English building, and Plivo's use cases cover lead capture, customer support, appointment booking, tech support, surveys and multichannel engagement. The Vibe Agent drafts a complete flow from a description, a fast start the team then shapes, as in Plivo's own example of sending a WhatsApp alert whenever a new Zendesk ticket arrives. Plivo sells no named agents a customer simply switches on.

Sourceplivo.com/ai-agentsread 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

Each AI conversation node carries its own model setting, so the builder picks the LLM step by step, with GPT-4.1 as one option and Plivo advising teams to try several models to balance answer quality against latency. The studio's models come from the GPT and Llama families, with voices from Cartesia and ElevenLabs. In the Playground, analysis mode reports metrics for each model run. Developers on Plivo's code path pick their own speech to text, LLM and text to speech providers, such as Deepgram Nova 3 and Cartesia Sonic 2.

Sourcedocs.plivo.com/docs/aiagent/aistudio/nodereference/aiconversationread 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

Any flow can expose an API trigger that outside systems call over HTTP with basic auth and input parameters, starting the agent programmatically, so a CRM or scheduler can have an agent place an outbound call or send a message. Around the studio sit Plivo's voice and messaging APIs, SDKs and a CLI, and audio streaming and SIP trunking interfaces for agents built on other frameworks.

Sourceplivo.com/docs/aiagent/aistudio/triggerread 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

The Playground runs a flow before launch from a simulated inbound hello, with the trigger variables entered by hand. Transcript mode plays the conversation close to the live channel, and analysis mode shows each node's prompt, tool response and timing along with model metrics such as response time and accuracy. Test runs in the Playground are not billed. Simulation testing is included in the agent price, though Plivo does not say what it adds beyond the Playground or whether test cases can be saved and run again.

Sourceplivo.com/docs/aiagent/aistudio/playgroundread 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 act through app actions, HTTP requests, Python code nodes and call forwarding, and the knowledge base crawls websites when content is synced. No hosted browser, remote desktop or screen control is part of the studio, so a system without an API is out of reach unless the team writes code to call it.

Sourceplivo.com/docs/aiagent/getstarted/overviewread 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