Plivo Blog | News, Industry Trends and Analysis, and Best Practices by the Plivo Team

Compare 10 AI voice agents for real estate in 2026. Evaluate response time, CRM integration, multi-channel support, and scalability to find the right solution.

AI voice agents in real estate are all about response time, coverage and quick follow-through. If your system can't answer calls immediately, qualify intent, book tours and update your CRM without manual cleanup, it's not helping you win more deals; it's adding another layer for you to manage.

This guide isn't for browsing tools. It's for operators deciding whether to commit to AI voice agents in 2026 and ship something that actually helps you scale. We compare 10 platforms based on how they perform after signup, how fast you can go live, what breaks under real lead volume, and what it takes to keep them working week after week.

Top 10 AI Voice Agents for Real Estate (2026)

The goal here is simple: Helping you choose an option that you can launch confidently, not replace after the first integration headache.

1. Plivo

When aiming to build and scale AI voice agents for real estate, you care about two things: reaching prospects first and converting more inquiries into confirmed showings. Plivo excels here since it gives you production-ready AI voice agents that place instant callbacks, answer listing questions from your data, and book tours directly on your agents' calendars. They operate reliably across phone, SMS, WhatsApp and chat without stitching together telephony, AI models and messaging vendors.

Plivo is the AI agent builder platform for voice-first, omnichannel experiences—built on a carrier-grade telephony network trusted by Uber, Meta, Zomato, and thousands of businesses worldwide. Business teams can launch agents without writing code using Vibe agent. Engineering teams can orchestrate custom voice agents in code with full control. The foundation is Plivo's global communications infrastructure spanning 190+ countries: 15+ years of proven reliable infrastructure, low latency, and the call quality enterprises demand.

Core Capabilities:

Inbound & Outbound AI Voice Agents: Handle live calls end-to-end, qualify intent, route intelligently and escalate to human agents when needed.
Multi-Channel Agent Coverage: Run the same AI agent across phone, SMS, WhatsApp and chat with shared context across channels.
No-Code AI Agent Builder (Vibe): Build and deploy voice agents using plain-English instructions, no prompt engineering or coding required.
Build your way: Business teams launch with no-code tools; engineering teams build custom voice agents with full-code control. You're never forced into a single way of working.
Vertically Integrated Telephony (CPaaS): Voice runs on Plivo's own global telephony infrastructure, avoiding third-party carrier dependencies.
Low-Latency Voice AI Stack: Integrated TTS, STT and LLM orchestration enables sub-500ms response latency, critical for natural voice conversations.
Enterprise-Grade Reliability: Built on Plivo's proven CPaaS platform with 99.99% uptime, 15+ years of reliable infrastructure, and global carrier connectivity across 190+ countries.
CRM & Workflow Integrations: Pull customer context in real time and write call outcomes back to CRMs and support tools automatically. Connect Follow Up Boss, kvCORE, BoomTown, Salesforce, HubSpot, Google Calendar, Outlook, and your MLS/IDX feed.
You own the stack: You get to choose your speech-to-text (STT), text-to-speech (TTS), and LLM while keeping prompts and data portable and avoiding lock-in.

Best fit if you:

Need real-time voice agents that can operate continuously at scale.
Want to avoid stitching telephony, AI and messaging vendors together.
Plan to deploy across multiple channels, not voice alone.
Have defined workflows for lead qualification, routing or follow-ups.

Not a fit if you:

Only need a lightweight voice demo, basic IVR or short-term experiment.
Want a fully turnkey, real estate-specific tool with no configuration or workflow control.
Don't plan to integrate voice agents into your CRM, data stack or operations.

2. Luron AI

Luron AI is best suited for teams that need 24/7 AI voice agents that never miss calls and qualify leads automatically. It supports multilingual conversations and keeps pacing tight across accents and speaking styles. The system handles inbound and outbound voice conversations in dozens of languages and automates bookings and follow-ups without human staffing.

Core Capabilities:

Instant call answer & qualification: AI answers every call, gathers intent, and qualifies leads without hold times.
Multilingual support: Handles AI conversations in 45+ languages to cover diverse lead sources.
Inbound & outbound support: Manages both types of calls and can also run outbound follow-ups.
SMS, chat & email automation: Extends voice agents to text and messaging channels for a unified engagement approach.
CRM & integration options: Connects to existing phone systems via SIP trunking and can integrate with CRMs and ticket systems.

Best fit if you:

Want 24/7 lead capture and qualification without adding staff.
Need multilingual voice conversations for global or diverse markets.
Expect to automate bookings, follow-ups and reminders on voice and messaging channels.
Have a CRM or existing phone system you must integrate with.

Not a fit if you:

Only need a simple inbound answering or IVR replacement without automation.
Want a solution focused on voice only, with limited channel reach.
Prefer fixed, transparent pricing tiers publicly listed.

3. Callers AI

Callers AI is a platform for automating customer conversations with human-like voice agents that handle both inbound & outbound calls and messaging channels, powered by your brand's data and tone. It's focused on scaling high-volume voice interactions while maintaining contextual continuity across channels in a single branded voice experience.

Core Capabilities:

Omni-channel AI interactions: Voice agents run across phone, SMS, WhatsApp and chat from a central AI brain.
Human-like voice calls: Agents answer and place calls in a natural conversational style.
Lead workflows & use cases: Supports lead qualification, cold call automation, appointment confirmation, retention flows and more.
24/7 availability & language breadth: Designed to handle calls and messaging around the clock, in multiple languages.
Context remembering: Conversations carry context across voice and messaging so follow-ups feel continuous.
Integrations & automation: Connects to CRMs and tools (300+ integrations) so call outcomes can update your systems.

Best fit if you:

Want both inbound and outbound AI calling with consistent, natural-tone responses across channels.
Need an AI system that can qualify leads, confirm appointments and manage follow-ups automatically.
Are scaling high call volumes 24/7.
Prefer a central "brain" that keeps context across channels and workflows.

Not a fit if you:

Only want a basic voice or outbound dialer with limited cross-channel logic.
Need a tool focused exclusively on simple IVR or basic routing without AI conversation layers.
Prefer a product you can set up and forget in minutes without upfront configuration or workflow definition.

4. SquadStack AI

SquadStack AI is best suited for teams that want AI-assisted sales and voice engagement workflows supported by configurable human-in-the-loop automation. It blends automated outreach and qualification with options to escalate to human agents where needed, helpful for revenue teams that are focused on pipeline speed.

Core Capabilities:

Automated Lead Engagement: AI enabled workflows proactively contact prospects and qualify them using data-driven sequencing.
Voice & Messaging Channels: Supports outbound dialing, ringless voicemail, SMS and multi-touch sequences.
Human-in-the-Loop Escalation: Configurable handoffs to live agents when conversations need human judgment.
Sales Workflow Automation: Built-in logic for lead routing, prioritization and follow-ups across channels.
CRM Integration + Data Sync: Sync outcomes and engagement data back to CRMs like Salesforce, HubSpot, etc.

Best fit if you:

Want inbound and outbound automated voice interactions with natural conversation flows and multilingual capability.
Need AI that handles lead qualification, follow-ups and reminders as part of sales or customer engagement sequences.
Are automating sales outreach and conversational workflows alongside voice calls.

Not a fit if you:

Need an AI platform focused on low-latency, bespoke voice agent infrastructure tied tightly to your own telephony stack.
Are building a multi-channel bot with CRM/telephony hooks and developer control from the ground up at scale.

5. Telgent

Telgent leans into MLS and portal context. It is best for businesses that want always-on voice AI calling with automated scheduling, intelligent call handling and quick setup. Its platform emphasizes immediate activation, seamless integration with existing phone systems and natural AI responses that handle calls, schedule meetings and engage customers day and night.

Core Capabilities:

24/7 AI voice calling agents: Always-on call automation that answers and routes customer calls at any hour.
Lead engagement & scheduling: Automatically books appointments, meetings and showings based on natural language conversations.
Inbound call handling: AI answers incoming inquiries, qualifies intent and routes prospects with minimal human intervention.
Automated inquiry responses: Provides instant answers to property questions and responds to rental or sales leads.
Integration with real estate systems: Works with Zillow, Realtor.com, MLS platforms, Follow Up Boss, kvCORE, BoomTown, Salesforce and HubSpot for CRM continuity.

Best fit if you:

Need round-the-clock call handling that captures leads and books appointments without missing inquiries.
Want your voice AI to integrate with core real estate tools and CRM systems so client details are synced automatically.
Are focused on lead conversion and showing scheduling as part of your customer engagement workflows.

Not a fit if you:

Only require basic outbound calling with simple scripts rather than inbound + scheduling automation.
Expect a no-config, plug-and-play voice bot that requires zero setup or customization.
Want a platform that handles only one channel (voice only) without extending into SMS/WhatsApp/chat automation.

6. AIOnCalls

AIOnCalls is positioned as a virtual receptionist that never misses calls or opportunities. Best for teams that want an always-on voice AI assistant that handles inbound and outbound calls around the clock, engages callers in natural language, qualifies leads, books appointments and updates CRM data.

Core Capabilities:

24/7 Inbound & Outbound Voice Handling: AI answers and places calls around the clock across all hours and holidays.
Lead Qualification & Follow-Up Automation: Qualifies callers in real time and automates follow-ups via voice, SMS and email.
Appointment Scheduling & Calendar Invites: Books appointments and sends confirmations during calls.
CRM & Workflow Integrations: Integrates with CRMs like Zoho, HubSpot, GoHighLevel, Google Calendar for real-time lead syncing and activity logging.
Multilingual Conversations: Supports multiple languages and can handle simultaneous call sessions.
Live Agent Escalation: Transfers complex calls to human agents when needed.
Real-Time Analytics & Transcriptions: Provides live call monitoring, transcripts, sentiment analysis and dashboards.

Best fit if you:

Need an AI voice agent that never misses inbound calls and engages leads immediately, 24/7.
Want automated lead qualification, booking and follow-ups in voice, SMS, and email without human staffing.
Are integrating call outcomes and engagement data into CRM or calendar workflows.
Operate in industries where speed-to-lead matters and missed calls are costly.

Not a fit if you:

Only need simple IVR or on-premise call routing without conversational automation.
Prefer a pure telephony or developer API platform without built-in AI conversational layers.
Are looking for a voice agent with deep, specialized industry templates.

7. Brilo AI

Brilo AI is a business-focused AI phone and voice call agent platform that enables teams to automate real-time voice interactions across industries like real estate. It promises fast setup, natural human-like voice responses, 24/7 coverage, integration with business tools and built-in analytics, all without needing a technical team to get started.

Core Capabilities:

24/7 AI voice call agents: Always-on AI phone agents handle inbound calls and customer engagements at any hour.
Human-like voice interactions: Conversational voice responses built to sound natural and engaging.
Appointment booking & scheduling: Voice agents can book appointments with synced calendars and handle reminders.
CRM and business integrations: Integrates with a broad range of business apps (6,000+ app connections claimed) to sync customer context and outcomes.
Real-time analytics & insights: Live call transcripts, sentiment analysis, intent tracking and topic detection support actionable insights post-call.
Lead qualification automation: Agents engage prospects, capture intent and route high-value leads in real time.

Best fit if you:

Need 24/7 automated voice engagement that never misses inbound or high-volume calls for lead capture, scheduling or support.
Need a platform that books appointments, manages follow-ups and drives customer engagement without manual management.
Plan to integrate the voice agent with CRM, calendar tools and analytics pipelines to maintain context across systems.

Not a fit if you:

Simply need a basic phone tree, IVR or traditional call routing system.
Are focused solely on developer-centric API telephony without AI built in.
Require industry-specific compliance guarantees (HIPAA, PCI, etc.) documented publicly.

8. VocalDesk

VocalDesk is an AI-enabled voice and contact automation platform that helps teams automate calling, lead follow-up, support interactions and scheduling. Its focus is on automated voice conversations and multi-channel engagement with CRM integration and configurable workflows that replace manual outreach tasks.

Core Capabilities:

Automated Voice Conversations: Handles inbound and outbound calls using AI to engage, qualify, and route callers.
AI-Driven Lead Qualification: Automated conversation flows that marks lead intent and priority.
Appointment Booking & Reminders: Schedules meetings and sends reminders as part of automated flows.
Multichannel Messaging: Engages customers across voice, text and messaging platforms.
CRM & Workflow Sync: Connects with CRM systems and business tools to log interactions and maintain records.

Best fit if you:

Want to automate call handling and lead follow-up without manual dialing.
Need a solution that combines voice and messaging outreach with CRM context.
Are focused on lead qualification and scheduling as part of broader sales engagement.

Not a fit if you:

Only need basic call routing or IVR without AI handling.
Require explicit developer control over telephony APIs.
Rely on hard metrics like latency, concurrency limits or multi-region telephony SLAs.

9. Calldock

Calldock is an AI voice agent platform intended for instant lead engagement, automatic qualification and scheduling. Its system calls leads within seconds of form submission, conducts natural conversations and integrates with calendars and workflows to automate follow-ups and booking.

Core Capabilities:

Instant lead callbacks: Calls website leads within ~60 seconds of a submission, boosting early engagement.
Calendar booking: Agents can book appointments directly to your calendar during live calls.
Multi-channel follow-up: Agents send SMS and email follow-ups as part of the call workflow.
Seamless handoff & callbacks: You can trigger human handoffs in natural language and schedule intelligent callbacks.
API, webhooks, & integration ecosystem: Support for APIs and pre-call webhooks lets you fetch context before calls and connect with Gmail, Google Calendar, Slack, Zapier and thousands more.
Developer playground & documentation: Provides API documentation and code examples for triggered calls and automated workflows.

Best fit if you:

Want immediate lead engagement that happens in seconds.
Need voice agents that qualify, book and follow up automatically across voice, SMS and email.
Plan to integrate voice engagements with calendar and business workflows.
Need a voice agent that works with easy templates for common industries with minimal setup.
Want a low-code or no-code setup that goes live with simple configuration.

Not a fit if you:

Need proper inbound/outbound calling with API integration.
Require deep telephony infrastructure control or enterprise telephony SLAs.
Are building highly custom dialogue systems that need proprietary LLM tuning beyond the existing templates.

10. Ylopo

Ylopo is a digital marketing and lead gen platform built for the real estate industry. It combines lead capture, nurturing, AI voice calling, AI texting, branded websites and marketing automation into one system that integrates with CRMs and helps real estate teams generate and convert leads.

Core Capabilities:

AI Voice Follow-Up: Automatically calls new and existing leads to qualify interest and connect them to agents.
AI Text Conversations: Runs two-way SMS conversations to nurture leads until they're ready to talk.
AI² Voice + Text System: Combines calling and texting into one coordinated follow-up engine.
Automated Appointment Transfers: Delivers live transfers or booked appointments when leads are qualified.
Lead Generation & Nurture: Includes PPC ads, remarketing and IDX websites to capture and feed leads into AI follow-up.
CRM & Website Integration: Syncs AI conversations and lead activity with CRMs and branded real estate websites.

Best fit if you:

Want lead capture with nurturing as a unified system rather than isolated voice interaction tools.
Are a realtor or team that wants AI to automatically engage leads by text and phone, not just manage manual contacts.
Need branded websites with IDX search and integrated lead capture feeding into automated follow-up.
Plan to keep leads engaged over longer time horizons (e.g., 90-day voice follow-up).
Value combined marketing + AI follow-up rather than a single channel (voice only).

Not a fit if you:

Are looking for pure AI voice agent infrastructure like a telephony-first CPaaS platform.
Need tools focused on enterprise-grade telephony performance, low-latency voice systems or custom telephony workflows.

What Matters Most in AI Voice Agents (Beyond the Basics)

1. Telephony Ownership vs. Vendor Stitching

Many AI voice tools rely on third-party telephony stitched together with AI layers. This often introduces latency, call drops and limited routing control at scale.

What to prioritize:

Built-in telephony with direct carrier connectivity
End-to-end control over call routing and quality
Fewer external dependencies

Plivo runs on its own global CPaaS and carrier-grade telephony stack, removing third-party voice dependencies.

2. Real-Time Performance (Latency & Uptime)

Voice conversations break down quickly when responses lag or calls fail. Sub-second latency and high uptime aren't "nice to have"—they're mandatory.

What to validate:

Sub-500ms voice response latency
99.99% uptime or better
Real-time STT, TTS, and LLM orchestration

Plivo's vertically integrated Voice AI stack is designed for low-latency, real-time conversations on proven infrastructure.

3. Multi-Channel Context, Not Disconnected Bots

Leads move between calls, SMS, WhatsApp and chat. Treating each channel as a separate bot creates broken experiences and duplicate work.

What to look for:

Shared context across voice and messaging
Unified conversation history
Seamless handoffs between channels

Plivo supports multi-channel agents that share context across phone, SMS, WhatsApp and chat from a single system.

4. Integration Depth (CRM, Calendars, Workflows)

Voice agents don't operate in isolation. Without deep integrations, they become another silo your team has to manage.

Prioritize platforms that:

Read from and write to CRMs in real time
Trigger workflows during live calls
Integrate cleanly with calendars and support tools

Plivo integrates directly with CRMs and business systems, allowing agents to act on live data and update records automatically.

5. Built for Scale, Not Just Launch

Many tools work well for pilots but struggle under sustained call volume or multi-region deployment.

Ask:

Can this run continuously without degradation?
Are pricing and performance predictable as usage grows?
Will this still work when channels or regions expand?

Plivo's AI agents are built on infrastructure that already powers enterprise-grade voice and messaging at global scale.

FAQs

What's the fastest way to go live without breaking existing operations?

Start with a single, contained flow like after-hours inbound calls or instant lead callbacks. Connect your phone numbers, CRM and calendar, define escalation rules and launch! You can expand coverage once live data validates the flow.

How do I ensure voice quality doesn't feel robotic or laggy?

Voice quality depends on latency and telephony control. Platforms with integrated telephony and real-time STT/TTS orchestration keep responses sub-second, which is critical for natural conversations that callers don't hang up on.

How does the agent stay accurate and compliant with real estate data?

The agent should pull from a restricted, curated knowledge source (MLS, IDX, listings) and operate within defined guardrails. When questions exceed scope like pricing nuance, legal terms, fair-housing-sensitive topics, it escalates to a human automatically.

What happens when call volume spikes or multiple leads call at once?

Calls don't fail—they should queue. High-intent conversations can be routed to live agents, while others are qualified, scheduled or followed up asynchronously. Every outcome is logged so nothing gets lost.

How does this fit into my CRM and follow-up workflows?

The agent reads live CRM data during calls and writes outcomes back automatically in the form of notes, disposition, next steps and booked appointments. Your team picks up conversations with full context instead of starting from scratch.

Try Plivo Free

Curious how an AI voice platform performs in your workflows, not just in theory? Plivo offers a free trial account with credits so you can experiment with voice, SMS, WhatsApp and chat services before committing. When you sign up, you get trial credits, can add a phone number and start testing features like real-time voice interactions and multi-channel engagement using APIs or visual tools like PHLO. This lets you validate performance, integrations, and call flows with your actual data—all without upfront cost.

Plivo's trial lets you test core capabilities immediately, making it easy to see how quickly you can build, launch, and refine agents that handle calls, qualify leads and update systems in real time.

Get started with your free trial now and begin building your first agent today.

Jan 20, 2026

5 mins

Best AI Voice Agents for Customer Support and Service (2026): What to Deploy Now

Compare 10 AI voice agent platforms for customer support. Get a practical 30-day pilot framework, implementation workflow, and outcome-driven selection guide.

1) Plivo — The fastest path to production-grade AI voice agents for customer support

A recent Gartner survey found that most customer service leaders plan to explore or pilot conversational GenAI in 2025—making a clear, near-term mandate to deliver something that works on the phone channel, not just in chat. That's your cue to build a reliable voice front door with an AI agent builder platform designed for voice-first, omnichannel experiences.

Why Plivo is #1

Plivo is the AI agent builder platform that lets you build your way. Whether you're a business leader who needs to launch fast or an engineering team building custom workflows, Plivo meets you where you are. Start with no-code tools that let non-technical teams deploy agents in hours. Go deeper with low-code orchestration for more control. Or build from scratch with full-code frameworks that integrate into your existing stack. You're never forced into a single way of working.

What it does for you

Plivo's Voice AI stack is modular by design. Want speed? Use the fully integrated platform—STT, LLM, TTS, and telephony—pre-configured and ready to go. Want control? Orchestrate your agents using code with Plivo's Agentic STT models and Telephony, alongside your preferred LLM providers. Want just the connectivity layer? Use audio streaming or SIP trunking and bring everything else yourself. You decide where Plivo ends and your stack begins.

Underlying it all is a reliable, carrier-grade telephony platform that scales for enterprises—global PSTN/SIP connectivity, number provisioning and porting, call routing with failover, recording with consent, and clean human handoff with full context into your CRM or help desk.

Segment-by-segment fit

If you're SMB, launch fast with no-code tools that let you deploy agents in hours, plus a simple dashboard and connectors for Shopify and Calendly. If you're mid-market, use low-code orchestration for more control, with a modular stack that lets you use what you need—swap in your preferred LLM, STT, or TTS. If you're enterprise, build with full-code frameworks that integrate into your existing stack, plus a modular Voice AI stack to pick-and-choose what you need, governance features (RBAC, audit transcripts, data residency), and contact center integration for high availability and reporting.

Start with Voice, go everywhere

Voice is the hardest channel to get right—and it's where Plivo leads. But the same flexible building experience extends to WhatsApp, SMS, RCS, and Chat. Build once, deploy across channels, and meet customers wherever they are.

Suitable for

Fintech customer service: consent-first flows, secure keypad capture, dispute status, and callbacks.
Healthcare scheduling: multilingual intake, appointment changes, escalations with a summarized handoff.
Retail and logistics: order status, returns, delivery windows, and SMS/WhatsApp follow-ups.

No more choosing between a locked-in platform that's easy but limiting, or a DIY approach that's flexible but painful. Plivo gives you both—simplicity when you want it, depth when you need it.

Explore the Voice API, check pricing, review compliance, handle numbers & porting, browse case studies, or jump into the quickstart.

2) Google Dialogflow CX — Complex, branching flows without spaghetti

Key features

Dialogflow CX uses a flow-and-page model to capture state and branching, so you can manage multi-step intents like returns, warranty claims, and multi-factor verification without dozens of brittle intents. It supports voice and text and includes versioning, experiments, and test tools. For telephony, you can use partner gateways or SIP; for global reach, put Plivo at the edge and connect to CX.

Why it matters

Complicated support journeys need explicit state. CX gives you that structure. If your "Where's my order?" workflow forks based on identity checks, fulfillment method, and policy windows, you can keep logic readable and testable. CX also plays well with multilingual experiences and mixed initiative, so callers can change course mid-conversation.

Implementation steps

Start with a single high-volume journey and draw it as a CX flow. Add a fallback page with a short menu for noisy lines. Ground the bot in your knowledge base and order system, then add handoff rules. Put Plivo in front for numbers, routing, and recording consent, and pass summaries back to your ticketing system.

Suitable for

Teams with multiple brands or product lines, where branching grows quickly and consistency matters across regions.

3) Amazon Lex + Amazon Connect — AWS-first voice automation that ops can own

Key features

Lex handles the speech and NLU for voice and text. Connect adds the contact-center fabric: routing, IVR, call recording, and agent desktop. It's a natural fit if your data and apps live in AWS and security prefers IAM-managed access. For global numbers or bring-your-own carrier control, front with Plivo and route into Connect.

Why it matters

Staying inside AWS accelerates procurement, security reviews, and monitoring. You can call Lambdas for tool use, search knowledge with Kendra, and use Connect metrics and contact flows your ops team already knows. That shortens time to value and concentrates governance in one place.

Implementation steps

Define one call flow in Connect (ID&V → status lookup → handoff). Build Lex intents from your top FAQs. Add Plivo for number management, routing, and failover. Send summaries back to your CRM or help desk. Keep a barge-in plan for noisy environments and a keypad fallback for payment flows.

Suitable for

IT-led programs where AWS standardization, auditability, and a single pane of glass for monitoring are priorities.

4) IBM Watson Assistant — Governance-first deployments in regulated industries

Key features

Watson Assistant supports omnichannel conversations with documented security and governance options, including deployment paths designed for regulated workloads. If your risk office leads the decision, IBM provides clear guidance on audit logging, data handling, and architectural choices. Add Plivo to handle PSTN/SIP, call consent prompts, and compliant recording policies.

Why it matters

Financial services and healthcare teams often need auditability from day one. When you need clear data-handling boundaries and deployment models that align with internal controls, IBM's documentation and support track help you pass reviews without months of back-and-forth.

Implementation steps

Map your data-classification rules to Watson's deployment options. Keep contact recordings and transcriptions in your approved storage. Use Plivo's routing and consent prompts to standardize intake across regions. Summarize calls into your case system for full traceability.

Suitable for

Organizations with heavy compliance needs, strict data residency, or formal audit trails for every customer interaction.

5) Cognigy.AI — IVR modernization with fine-grained voice control

Key features

Cognigy combines a visual designer with a voice gateway that supports streaming ASR, interruptibility, and transfer control. It integrates with multiple speech providers and enterprise systems like SAP and Salesforce. This lets you tune barge-in sensitivity, error handling, and handoff cues rather than living with a one-size-fits-all IVR.

Why it matters

If callers still hear a menu tree, you're wasting time and goodwill. Cognigy helps you replace rigid menus with natural conversations and graceful escalation. You keep the levers you need—timing, sensitivity, fallback prompts—so the agent feels human, not scripted.

Implementation steps

Start with the two intents that create the most queue time. Set barge-in thresholds conservatively and widen them after you test in live traffic. Put Plivo at the edge to manage numbers, recording policies, and failover. Send summaries with disposition tags to your CRM.

Suitable for

Enterprises with legacy IVRs, high call volumes, and a clear need to reduce effort without ripping out the contact-center core.

6) Salesforce Agentforce — CRM-native service automation where your team works

Key features

Agentforce brings AI agents into the Salesforce console and data model. Your service team stays in the view they know, while the agent handles common intents, drafts summaries, and routes cases. Add Plivo for calling so every phone interaction lands in Salesforce with the right context.

Why it matters

When everything you need to resolve an issue already lives in Salesforce, keeping the agent there shortens integration time and improves analytics. Supervisors can coach on the same dashboard and review case summaries, while admins maintain clear governance over data and automations.

Implementation steps

Pick one queue with repetitive calls. Tie identity checks to account data and warranties. Keep a "press 0 for a human" fallback and make sure the agent passes a clean summary with next steps. Use Plivo for the phone edge so call recordings and consent are consistent across regions.

Suitable for

Service teams that treat Salesforce as the system of record and want automation to feel native—not bolted on.

7) Zoom Virtual Agent for Phone — A 24/7 receptionist and concierge

Key features

Zoom's Virtual Agent for Phone handles greetings, routing, and the most common requests. You train it from existing docs and site content, then turn it on for after-hours or full-time reception. It's built for quick wins like appointment scheduling, store hours, and simple status checks with transfers when needed.

Why it matters

If reception lines clog your switchboard, a front-door voice agent can deflect simple questions without new headcount. As you add skills, you can expand from triage to completing tasks. For broader reach, connect Plivo to add global numbers and transactional notifications via SMS or WhatsApp.

Implementation steps

Start with greeting, business hours, and routing. Add appointment booking next. Keep live-agent transfers one click away. If you outgrow the PBX perimeter, bring Plivo in to manage numbers and cross-channel follow-ups.

Suitable for

Single-number switchboards, high-volume reception desks, and teams that need a quick, always-on front door.

8) Sierra — Enterprise "autonomous" agents with category momentum

Key features

Sierra focuses on enterprise-grade AI agents for customer service with an emphasis on agentic workflows. The leadership and market traction give executives confidence to back bigger bets. If you're evaluating multi-channel automation with rigorous SLAs, Sierra is a credible short-list option. Plug it into Plivo for reliable telephony, recording consent, and global routing.

Why it matters

Momentum reduces perceived risk. When you need cross-functional buy-in, a vendor that's already in enterprise production helps. You still need the phone edge right: numbers, routing, and failover that won't buckle under peaks.

Implementation steps

Define two end-to-end journeys (e.g., ID&V + order update; returns approval). Keep human handoff one step away and capture every call summary in your case system. Instrument containment and transfers, then iterate weekly.

Suitable for

Large teams planning multi-channel agents and looking for vendor accountability with clear deliverables and timelines.

9) Tidio (Lyro) — SMB eCommerce chat that pairs well with voice

Key features

Tidio blends live chat, an AI agent, and eCommerce integrations. It's a practical way to resolve repetitive questions, free up your team, and capture intent while buyers are on your site. Add Plivo for a simple order-status line and SMS/WhatsApp updates so customers get answers by phone as well as chat.

Why it matters

eCommerce teams need fast coverage more than complex architectures. You can start with FAQs, then add checkout and account questions. When phone calls spike—promos, holidays—route a basic voice flow through Plivo and keep your agent consistent across channels.

Implementation steps

Load your top FAQs and shipping policies, add a returns flow, and set clear handoff rules. For voice, route a single Plivo number to a lightweight agent that authenticates by order ID and ZIP code, then offers a callback option during peaks.

Suitable for

Lean teams that want to reduce repetitive chat volume now and add phone coverage without standing up a full contact center.

10) Robylon — Multi-channel AI agents focused on support teams

Key features

Robylon specializes in AI-driven customer support across voice, chat, email, and messaging. It integrates with help desks like Zendesk and Freshdesk, supports multiple languages, and offers analytics dashboards designed for service leaders. It's a pragmatic fit if your help desk is the hub of your operation.

Why it matters

You want human-like conversations that escalate cleanly. Robylon's positioning around support workflows means your ticketing, SLAs, and dispositions stay intact. For reliable calling, use Plivo for numbers, routing, and recording consent so your phone channel matches the quality of your chat channel.

Implementation steps

Start with account updates and appointment scheduling. Ground the agent in your help-desk knowledge base and macros. Track resolution time and transfer reasons; refine weekly.

Suitable for

Mid-market support teams who want a focused system that plugs into existing help-desk processes and expands to voice without heavy lifting.

How to run a safe, high-signal pilot in 30 days

Define success first

Pick three metrics: containment, transfer rate, and average resolution time. Write a one-line target for each and a go/no-go threshold. Everyone should know what "good" looks like before you take your first call.

Start with narrow, high-volume intents

"Where's my order?", appointment changes, returns, account updates. These are predictable, frequent, and measurable. Script your handoff sentence so agents never start from zero.

Build the right guardrails

Add a consent prompt, a keypad fallback for sensitive inputs, and a short backup menu for noisy environments. Keep the escalations simple: one route for billing, one for everything else.

Ground every answer

Connect the agent to your CRM/help desk and knowledge base. If the answer doesn't exist in your source of truth, escalate. Summarize every call into the ticket with disposition and next steps.

Iterate weekly

Review 20 call transcripts together. Fix the top three friction points. Update prompts and knowledge. Ship changes. Repeat.

FAQ

What's the fastest way to launch a voice agent without changing my stack?

Keep your telephony and routing on Plivo, connect your preferred conversation engine, and ground it in your CRM/help desk and knowledge base. Start with one number, one intent, and a simple fallback.

How should I measure success in the first 30 days?

Track containment, transfer rate, and resolution time. Listen for barge-in moments and interruptions—they reveal prompt and timing issues that you can fix quickly.

How do I implement consent, recording, and PCI/PHI safely?

Play a clear consent prompt before any recording. Use keypad input for payments or sensitive data. Store recordings and transcripts in approved systems and keep audit logs.

When is Dialogflow CX better than Lex, IBM, or Cognigy?

Choose CX for complex branching flows and multilingual journeys; Lex when your team standardizes on AWS; IBM when governance and deployment control are paramount; Cognigy when you're modernizing IVR with fine-grained voice settings.

How do I handle accents, noise, and barge-in in production?

Use a robust ASR, tune your barge-in sensitivity, and keep a keypad fallback. Test in noisy environments and shorten prompts. Summaries help human agents pick up without asking callers to repeat themselves.

Conclusion: Build the voice edge once, then scale what works

A measured result to anchor ROI. McKinsey reported that, at one company with thousands of agents, applying generative AI raised issue resolution and lowered handling time—small percentage gains that compound into real savings at scale. That's the kind of lift your leadership expects—and the reason to start with a focused pilot that moves one metric.

Bring your "brain" of choice, but keep the phone edge on Plivo so every call connects, every consent is captured, and every handoff carries context. Define three KPIs, pick one journey, and go live with a human fallback. Review transcripts weekly, then scale to the next two intents.

Ready to hear what real-time voice feels like? Build your agent or talk to an expert today.

Jun 19, 2025

5 mins

RCS Marketing 101: Your Complete Guide

Discover how RCS marketing delivers rich, branded messages that drive engagement for your business.

SMS marketing works, but let’s be honest: it feels a bit outdated compared to modern apps.

But what if you could send rich, interactive messages with branded content, images, buttons, and carousels straight to your customers’ native messaging apps?

Rich communication services (RCS) makes that possible.

If you’re ready to explore how RCS marketing can transform your engagement strategy, this guide will walk you through everything you need to know. Let’s get started.

What is RCS marketing?

RCS marketing uses rich communication services to send interactive, branded messages through a customer’s default messaging app. It’s a modern upgrade to SMS that lets businesses share images, buttons, carousels, and more — all without needing third-party apps.

A user on Reddit summed up this perfectly:

Screenshot of a Reddit comment explaining what RCS is — *RCS explained by a Reddit user*

RCS lets you send messages that are visually branded with logos and colors while remaining interactive. This turns static updates into an app-like experience inside a message.

This shift is part of a broader industry move, led by Google and backed by major mobile carriers, to upgrade messaging infrastructure and make RCS the default standard on Android devices.

As support continues to grow, businesses are adopting RCS as part of their customer engagement strategy. Platforms like Plivo make that adoption easier with a reliable, enterprise-grade gateway to deliver rich, reliable RCS campaigns at scale.

RCS vs. SMS marketing: A quick comparison

Marketers today are looking for ways to deliver more interactive and visual communication, and RCS is clearly leading the way.

While SMS still works well for simple alerts, it lacks the creativity and engagement that RCS marketing offers.

Let’s take a quick look at RCS vs. SMS marketing.

Key feature	SMS marketing	RCS marketing
Message length	Limited to 160 characters; with longer messages split	Up to 8,000 characters in a single message
Multimedia	Supports only plain text and links; needs MMS for multimedia	Natively supports high-resolution photos, videos, audio, and GIFs
Security and verification	No built-in sender verification	Includes verified sender profiles with business name, logo, and custom colors
Read receipts	No standardized way to know if a message was delivered or read	Provides delivery and read receipts for real-time engagement tracking
Typing indicators	Doesn't show when the other party is typing	Displays typing indicators, creating a more conversational feel
Interactive buttons	Not supported; calls to action (CTAs) are limited to plain text links	Allows interactive buttons with predefined replies and actions
User experience	Static, text-heavy, and transactional	Dynamic, visually rich, and conversational — feels more like a mobile app
Analytics and reporting	Basic delivery tracking (if supported by carrier)	Advanced analytics: opens, clicks, conversions, and user behavior tracking

4 key benefits of RCS marketing

RCS marketing makes messaging feel more natural for both you and your customers. And since you can see what’s working and what’s not, it’s easier to pivot your strategy and get better results.

Here are its four key benefits.

1. Improved user interaction

One of the biggest advantages of RCS marketing is how seamless it makes the experience for your customers. Instead of typing out replies or clicking a link to open a website, users can just tap a button right inside the message.

Want them to book a demo, check order status, or browse products? It’s all possible with just a tap.

Fewer steps mean less effort, and that leads to more people following through. In fact, individuals spend up to 37 seconds engaging with RCS messages, which is a lot longer than most other types of mobile messaging.

Image showing the engagement results of RCS messaging — *People engage more with RCS than any other platform*

That extra time and interaction can make all the difference when you’re trying to convert interest into action.

2. Consistent brand experience

RCS marketing doesn’t just tell people who you are — it shows them.

Verified business profiles help people know they’re getting messages from the real brand. Every message shows your brand’s logo, name, colors, and a checkmark. These small details make it clear that the message is coming from a genuine source.

Image showing that MAYI - HOMES sends a verified RCS message with branding — *Verified RCS message from MAYI - HOMES*

This consistency matters because 88% of people are more likely to buy from a brand they trust.

3. In-depth analytics

With RCS marketing, you can track open rates, button clicks, and how people interact with each part of your message.

You get clear visibility into what’s working and where users are dropping off.

This makes it much easier to measure the return on investment (ROI) and fine-tune your campaigns. The more you understand how people engage, the better you can shape your messaging for results.

4. Higher conversion potential

RCS marketing makes it easier for customers to take action — whether that’s browsing products, booking a service, or making a purchase — all within the message itself.

With fewer clicks and no need to switch apps, the path to conversion feels effortless. And when it’s that easy, more people follow through.

For example, EaseMyTrip used RCS to run a post-COVID travel survey. They added quick-tap answer options and followed up with a thank-you coupon. The campaign saw a 4x higher click-through rate than email, 10x more survey completions, and a 2.7% increase in conversion rate.

5 major use cases of RCS marketing

Here are five major use cases showing how brands are using RCS marketing effectively.

1. Product promotions

RCS makes product promotions feel more like browsing a store than reading a message. Brands can send image carousels that customers can swipe through to explore new arrivals, check product details, and see what’s available without leaving their messaging app.

Verified RCS message highlights a 25% off promotion on all items — Verified RCS message from Daily-donuts

Example: A fashion retailer promoting its spring collection could send an RCS message featuring a carousel of outfits with styled images, prices, and buttons like “View Lookbook” or “Shop Now.”

Tapping a button could open a mini product page inside the chat, letting customers browse and buy without switching apps.

2. Abandoned cart reminders

The average cart abandonment rate is over 70%, which means most shoppers never make it to the finish line. RCS marketing can help bring them back by making the reminder more engaging and easier to act on.

You can send a message that shows exactly what they left behind, along with a clear button to complete the purchase. It’s visual, straightforward, and the entire experience stays within their messaging app.

Example: A home electronics store could follow up with customers who left a pair of wireless earbuds in their cart. The RCS message might include a product photo, the price, and a “Buy Now” button that takes them straight to checkout.

3. Appointment confirmations and reminders

A PhD thesis from Manchester Metropolitan University found that forgetfulness is the most common reason people skip their appointments.

RCS makes it easier for both businesses and customers to stay on the same page. You can send a message that shows the appointment details along with a simple calendar view. Add buttons to confirm, reschedule, or cancel — all within the chat.

Image depicting an interactive RCS booking confirmation message — Booking confirmation via RCS with quick action buttons

Example: A dental clinic could use RCS to remind patients of upcoming cleanings. The message might show the date, time, and location of the appointment, plus a “Confirm” button and options to “Reschedule” or “Cancel.”

Patients can respond instantly, helping the clinic manage its schedule more efficiently.

4. Customer surveys and feedback

Getting feedback is important, but most customers lack the time or patience to complete lengthy forms. RCS marketing makes it easier by allowing brands to ask short, targeted questions and receive quick responses.

Plus, the rich features of RCS let you include images, ratings, or multiple-choice options, making feedback feel more like a conversation.

Example: A restaurant could send an RCS message after a meal asking customers to rate their experience with simple buttons like “Excellent,” “Good,” or “Needs Improvement.”

The message might also include a photo of the dish they ordered and a quick question like, “What did you like most?” This quick interaction makes it easy for customers to respond and gives the restaurant valuable insights.

5. Customer support follow-ups

After a support request is resolved, following up shows customers you care and helps close the loop on their experience. But if the follow-up message gets buried in an email inbox or goes unnoticed, that opportunity to connect is lost.

With RCS marketing, you can send a quick message to check if everything’s working fine. You can include helpful buttons like “Change Password,” “Manage Account,” or “Talk to Support.”

Support bot provides instant replies and follow-ups for customer queries — AI-powered support for account management

RCS marketing myths and realities

Despite RCS marketing’s growing adoption and proven results, some common misconceptions still hold businesses back from trying it. Let’s look at a few of the biggest myths and what’s actually true.

Myth 1: RCS marketing is too expensive

At first glance, RCS business messaging can seem like a pricey upgrade. Rich visuals, tap-to-action buttons, and branded layouts look premium, so it’s easy to assume they come with a hefty cost.

But cost alone doesn’t tell the full story.

What you get in return matters more. RCS drives significantly stronger engagement with higher click-through rates, increased interactions, and better overall outcomes.

Take Club Comex, the loyalty program of North American paint brand Comex. They sent two rich and interactive RCS campaigns to their members and saw a 10x higher click-through rate, which helped increase revenue by 115%.

That’s the value side of the equation. Better targeting and richer content mean more people click, engage, and convert.

Myth 2: RCS marketing doesn’t reach enough users to be worth it

This concern made sense in the early days of RCS, when adoption was still catching up. But the landscape looks very different now.

In June 2024, the 12-month growth of RCS users reached 36.3%, showing faster uptake than other messaging channels. More Android devices support RCS by default, and it’s being rolled out across more networks globally. Even Apple has announced support, which means RCS is on track to reach a massive number of smartphone users worldwide.

With that kind of growth and widespread support, the hesitation around RCS is starting to fade. Brands can confidently invest in RCS marketing knowing it will connect with more customers than ever before.

Myth 3: RCS gets treated like spam and ends up ignored just like emails

Unlike email, RCS messages appear directly in the user’s primary messaging app alongside personal conversations. They include rich media and interactive elements, making them more engaging and less likely to be ignored.

This creates a more natural, conversational experience that drives higher open and response rates than traditional marketing channels.

Why choose Plivo for your RCS marketing needs

With RCS, you can turn simple messages into rich, branded conversations that feel more like chatting than broadcasting.

Plivo gives you the tools to make that shift without the hassle. From verified messaging to smart automation, everything works together to help you connect better and respond faster.

When combined with AI Agents and a unified customer data platform, RCS becomes more than just messaging. You can deliver personalized experiences at scale, automate everyday interactions, and keep conversations flowing without lifting a finger.

Here’s what you get with Plivo’s RCS API:

Real-time personalization: AI Agents tailor conversations using customer profiles and behavior triggers to improve engagement and conversions.
Multi-channel fallback: If RCS isn’t supported, messages automatically switch to SMS to ensure delivery and maintain consistent communication.
Conversational automation: AI Agents handle FAQs, process orders, schedule deliveries, and route complex queries within RCS.
All-in-one messaging platform: Manage RCS, SMS, WhatsApp, Voice, and more from a single dashboard.
Reliable performance: 99.99% uptime and global infrastructure keep your campaigns running smoothly.

With Plivo’s no-code tools, you can quickly launch AI-powered RCS messaging across channels and deliver a consistent customer experience from day one.

See how you can launch your first RCS marketing campaign with Plivo by requesting a demo today!

‍

Subscribe to Our Newsletter

Plivo’s cloud communications platform is backed by a robust, reliable, fault-tolerant.

Thank you for subscribing. Read some of our amazing customer stories.

Oops! Something went wrong while submitting the form.

Feb 8, 2022

5 mins

New Starter Registration Makes 10DLC Messaging More Affordable

New Starter brands and campaigns let individuals and small businesses enjoy the benefits of 10DLC text messaging at a low cost.

10DLC

**** As of October 19, 2022, Plivo has paused Starter registrations. Please refer to our blog post Updated A2P 10DLC Registration Guidelines in the US for our current 10DLC registration recommendations. ****

Businesses of all sizes can benefit by using text messaging to communicate with their customers and prospects. Texting is inexpensive, it scales easily, and it has global reach, but its main advantage is that people prefer to be contacted by text message. They’d rather receive a text than a phone call or email.

Plivo’s SMS API lets businesses add texting to their applications. You may have heard that there’s a new number type in the US, 10-digit long code (10DLC), that has become the best way to send A2P text messages. Businesses can now register their long codes and get the benefits of better deliverability and potentially higher throughput. However, the registration costs for 10DLC numbers may be a little high for some individuals and small businesses, so we’re introducing a new Starter 10DLC registration plan.

10DLC registration for individuals and small businesses

When you visit the 10DLC registration page of the Plivo console, you’ll now see two options: Standard and Starter. A Standard account lets you register your brand and campaigns and get everything you know and love about Plivo.

Starter is a new option designed for individuals and small businesses that lack a tax identification number or EIN. Its key advantage is its low cost: Starters don’t have to pay a registration fee, just a monthly fee of less than a dollar for a messaging campaign.

The price is right, but Starter brands are more limited than Standard. Starters can register only a single campaign, and associate a maximum of five phone numbers with it. Messaging throughput, which can be as high as 4,500 transactions per minute for a Standard brand, is limited to 75 transactions per minute. But that’s more than enough for a small medical practice that sends out appointment reminders, or any other business that sends out only a few dozen messages a day.

The 10DLC page in our Support portal has more details about Starter brands and all things 10DLC.

SMS services for everyone and anyone

Starter brands and 10DLC phone numbers put text messaging within reach of any organization, from the neighborhood flea market vendor to Fortune 100 businesses.

If you’ve been interested in Plivo but hesitant to make a commitment because you were afraid of receiving a high bill, don’t wait any longer. If you’re a small-businessperson who loved Plivo but had to switch for cost reasons, we’d like to have you back. Sign up for a trial account and use the free credits we provide new customers with to rent a phone number and register your brand, then use Plivo’s SMS API to integrate your applications with our cloud communications platform.

Feb 3, 2022

5 mins

How to Build a Conference Application the No-Code Way Using PHLO

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

PHLO

Voice API

How To

Conference

You can create and deploy a workflow to implement conference calling with a few clicks on the PHLO canvas.

Prerequisites

To get started, you need a Plivo account — sign up with your work email address if you don’t have one already. To receive incoming calls, you must have a voice-enabled Plivo phone number. You can rent numbers from the Numbers page of the Plivo console, or by using the Numbers API.

Create the PHLO

To create a PHLO, visit the PHLO page of the Plivo console. If this is your first PHLO, the PHLO page will be empty.

Click CREATE NEW PHLO.
In the Choose your use case pop-up, click Build my own. The PHLO canvas will appear with the Start node.Note: The Start node is the starting point of any PHLO. It lets you trigger a PHLO to start upon one of three actions: incoming SMS message, incoming call, or API request.
From the list of components on the left side, drag and drop the Conference Bridge component onto the canvas. When a component is placed on the canvas it becomes a node.
Draw a line to connect the Start node‘s Incoming Call trigger state to the Conference Bridge node.

In the Configuration tab at the right of the canvas, enter a Conference ID for your conference. You can also add an announcement message to greet callers, and configure the hold music.
Once you’ve configured the node, click Validate to save the configuration.

Give the PHLO a name by clicking in the upper left, then click Save.

Your complete PHLO should look like this.

Assign the PHLO to a Plivo number

Once you’ve created and configured your PHLO, assign it to a Plivo number.

On the Numbers page of the console, under Your Numbers, click the phone number you want to use for the PHLO.
In the Number Configuration box, select PHLO from the Application Type drop-down.
From the PHLO Name drop-down, select the PHLO you want to use with the phone number, then click Update Number.

Test

You can now call to your Plivo phone number and see how callers are added to a conference call.

For more information about creating a PHLO application, see the PHLO Getting Started guide. For information on components and their variables, see the PHLO Components Library.

Haven’t tried Plivo yet? Getting started is easy and only takes minutes. Sign up today.

Feb 1, 2022

5 mins

How to Build an SMS Alerts Application the Low-Code Way Using PHLO

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

PHLO

How To

Alerts

Use Cases

Alerts can help people receive crucial updates in a timely manner, allowing them to make timely decisions. You can create SMS alerts easily by using our PHLO visual workflow builder.

Prerequisites

To get started, you need a Plivo account — sign up with your work email address if you don’t have one already. If you’re using a Plivo Trial account, you can send SMS messages only to phone numbers that have been verified with Plivo. You can verify (sandbox) a number by going to the console’s Phone Numbers > Sandbox Numbers page.

Create the PHLO

To create a PHLO, visit the PHLO page of the Plivo console. If this is your first PHLO, the PHLO page will be empty.

Click Create New PHLO.
In the Choose your use case pop-up, click Build my own. The PHLO canvas will appear with the Start node.Note: The Start node is the starting point of any PHLO. It lets you trigger a PHLO to start upon one of three actions: incoming SMS message, incoming call, or API request.
From the list of components on the left-hand side, drag and drop the Send Message component onto the canvas. When a component is placed on the canvas it becomes a node.
Draw a line to connect the Start node’s API Request trigger state to the Send Message node.

In the Configuration pane at the right of the canvas, configure the Send Message node with a sender ID in the From field. Enter the destination number you wish to send a message to in the To field. Put your message in the Text field.Note: You can define a static payload by specifying values when you create the PHLO, or define a dynamic payload by passing values through Liquid templating parameters when you trigger the PHLO from your application.
Once you’ve configured the node, click Validate to save the configuration.

After you complete the configuration, give the PHLO a name by clicking in the upper left, then click Save.

Your complete PHLO should look like this.

Your PHLO is now ready to test.

Trigger the PHLO

You integrate a PHLO into your application workflow by making an API request to trigger the PHLO with the required payload — the set of parameters you pass to the PHLO. You can define a static payload by specifying values when you create the PHLO, or define a dynamic payload by passing values through parameters when you trigger the PHLO from your application.

In either case, you need your Auth ID and Auth Token, which you can get from the overview page of the Plivo console.

You also need the PHLO ID, which you can copy from the PHLO list page.

With a static payload

When you configure values when creating the PHLO, they act as a static payload.

Code

Create a file and paste the below code.

1
2
3
4
5
6
7
import plivo

phlo_id = "<phlo_id>"
phlo_client = plivo.phlo.RestClient("<auth_id>", "<auth_token>")
phlo = phlo_client.phlo.get(phlo_id)
response = phlo.run()
print(response)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
require 'rubygems'
require 'plivo'

include Plivo

AUTH_ID = '<auth_id>'
AUTH_TOKEN = '<auth_token>'

client = Phlo.new(AUTH_ID, AUTH_TOKEN)

# if credentials are stored in the PLIVO_AUTH_ID and the PLIVO_AUTH_TOKEN environment variables
# then initialize client as:
# client = Phlo.new

begin
  phlo = client.phlo.get('<phlo_id>')
  response = phlo.run()
  puts response
rescue PlivoRESTError => e
  puts 'Exception: ' + e.message
end

1
2
3
4
5
6
7
8
9
10
11
12
var plivo = require('plivo');
var PhloClient = plivo.PhloClient;

var phloId = '<phlo_id>';
var phloClient = phlo = null;

phloClient = new PhloClient('<auth_id>', '<auth_token>');
phloClient.phlo(phloId).run().then(function(result) {
    console.log('Phlo run result', result);
}).catch(function(err) {
    console.error('Phlo run failed', err);
});

1
2
3
4
5
6
7
8
9
10
11
12
13
<?php
require 'vendor/autoload.php';
use Plivo\Resources\PHLO\PhloRestClient;
use Plivo\Exceptions\PlivoRestException;
$client = new PhloRestClient("<auth_id>", "<auth_token>");

$phlo = $client->phlo->get("<phlo_id>");
try {
    $response = $phlo->run();
    print_r($response);
} catch (PlivoRestException $ex) {
    print_r($ex);
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
import com.plivo.api.Plivo;
import com.plivo.api.PlivoClient;
import com.plivo.api.exceptions.PlivoRestException;
import com.plivo.api.models.phlo.Phlo;
import java.io.IOException;

public class Example
{
    private static final String authId = "<auth_id>";
    private static final String authToken = "<auth_token>";
    private static PlivoClient client = new PlivoClient(authId, authToken);
    public static void main(String[] args) throws IOException, PlivoRestException
    {
        String phloId = "<phlo_id>";
        Plivo.init(authId, authToken);
        Phlo phlo = Phlo.getter(phloId).client(client).get();
        PhloUpdateResponse response = Phlo.updater(phloId).payload().run();
    }
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
package main

import (
	"fmt"
	"plivo-go"
)

// Initialize the following params with corresponding values to trigger resources
const authId = "<auth_id>"
const authToken = "<auth_token>"
const phloId = "<phlo_id>"

func main() {
	testPhloRunWithoutParams()
}

func testPhloRunWithoutParams() {
	phloClient, err := plivo.NewPhloClient(authId, authToken, &plivo.ClientOptions{})
	if err != nil {
		fmt.Print("Error", err.Error())
		return
	}
	phloGet, err := phloClient.Phlos.Get(phloId)
	if err != nil {
		fmt.Print("Error", err.Error())
		return
	}
	response, err := phloGet.Run(nil)
	if err != nil {
		fmt.Print("Error", err.Error())
		return
	}
	fmt.Printf("Response: %#v\n", response)
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
using System;
using Plivo;

namespace test_PHLO
{
    class Program
    {
        public static void Main(string[] args)
        {
            var phloClient = new PhloApi("<auth_id>", "<auth_token>"); 
            var phloID = "<phlo_id>";
            var phlo = phloClient.Phlo.Get(phloID);   
            Console.WriteLine(phlo.Run());
        }
    }
}

1
2
3
4
curl --request POST \
  --user AUTH_ID:AUTH_TOKEN \
  --url 'https://phlorunner.plivo.com/v1/account/{auth_id}/phlo/{phlo_id}' \
  --header 'Content-Type: application/json'

Replace the auth placeholders with your authentication credentials from the Plivo console. Replace the phlo_id placeholder with your PHLO ID from the Plivo console.

With a dynamic payload

To use dynamic values for the parameters, use Liquid templating parameters when you create the PHLO and pass the values from your code when you trigger it.

Code

Create a file and paste the below code.

1
2
3
4
5
6
7
8
9
10
import plivo

auth_id = '<auth_id>'
auth_token = '<auth_token>'
phlo_id = '<phlo_id>'
payload = {"From" : "<caller_id>","To" : "<destination_number>"}
phlo_client = plivo.phlo.RestClient(auth_id=auth_id, auth_token=auth_token)
phlo = phlo_client.phlo.get(phlo_id)
response = phlo.run(**payload)
print (response)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
require 'rubygems'
require 'plivo'

include Plivo

AUTH_ID = '<auth_id>'
AUTH_TOKEN = '<auth_token>'

client = Phlo.new(AUTH_ID, AUTH_TOKEN)

# if credentials are stored in the PLIVO_AUTH_ID and the PLIVO_AUTH_TOKEN environment variables
# then initialize client as:
# client = Phlo.new

begin
  phlo = client.phlo.get('<phlo_id>')
  #parameters set in PHLO - params
  params = {
     From: '<caller_id>',
     To: '<destination_number>',
  }
  response = phlo.run(params)
  puts response
rescue PlivoRESTError => e
  puts 'Exception: ' + e.message
end

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
var plivo = require('plivo');
var PhloClient = plivo.PhloClient;

var authId = '<auth_id>';
var authToken = '<auth_token>';
var phloId = '<phlo_id>';
var phloClient = phlo = null;

var payload = {
    From: '<caller_id>',
    To: '<destination_number>',
}
phloClient = new PhloClient(authId, authToken);
phloClient.phlo(phloId).run(payload).then(function (result) {
    console.log('Phlo run result', result);
}).catch(function (err) {
    console.error('Phlo run failed', err);
});

1
2
3
4
5
6
7
8
9
10
11
12
13
<?php
require 'vendor/autoload.php';
use Plivo\Resources\PHLO\PhloRestClient;
use Plivo\Exceptions\PlivoRestException;
$client = new PhloRestClient("<auth_id>", "<auth_token>");

$phlo = $client->phlo->get("<phlo_id>");
try {
    $response = $phlo->run(["From" => "<caller_id>", "To" => "<destination_number>"]);
    print_r($response);
} catch (PlivoRestException $ex) {
    print_r($ex);
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
import com.plivo.api.Plivo;
import com.plivo.api.PlivoClient;
import com.plivo.api.exceptions.PlivoRestException;
import com.plivo.api.models.phlo.Phlo;
import java.io.IOException;

public class Example
{
    private static final String authId = "<auth_id>";
    private static final String authToken = "<auth_token>";
    private static PlivoClient client = new PlivoClient(authId, authToken);
    public static void main(String[] args) throws IOException, PlivoRestException
    {
        String phloId = "<phlo_id>";
        Plivo.init(authId, authToken);
        Phlo phlo = Phlo.getter(phloId).client(client).get();
        Map<String, Object> payload = new HashMap<>();
        payload.put("From", "<caller_id>");
        payload.put("To", "<destination_number>");
        PhloUpdateResponse response = Phlo.updater(phloId).payload(payload).run();
    }
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
package main

import (
	"fmt"
	"plivo-go"
)

// Initialize these parameters with corresponding values to trigger resources
const authId = "<auth_id>"
const authToken = "<auth_token>"
const phloId = "<phlo_id>"

func main() {
	testPhloRunWithParams()
}

func testPhloRunWithParams() {
	phloClient, err := plivo.NewPhloClient(authId, authToken, &plivo.ClientOptions{})
	if err != nil {
		fmt.Print("Error", err.Error())
		return
	}
	phloGet, err := phloClient.Phlos.Get(phloId)
	if err != nil {
		fmt.Print("Error", err.Error())
		return
	}
	//pass corresponding from and to values
	type params map[string]interface{}
	response, err := phloGet.Run(params{
		"From": "<caller_id>",
		"To":   "<destination_number>",
	})

	if err != nil {
		println(err)
	}
	fmt.Printf("Response: %#v\n", response)
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
using System;
using System.Collections.Generic;
using Plivo;

namespace test_PHLO
{
    class Program
    {
        public static void Main(string[] args)
        {
            var phloClient = new PhloApi("<auth_id>", "<auth_token>");
            var phloID = "<phlo_id>";
            var phlo = phloClient.Phlo.Get(phloID); 
            var data = new Dictionary<string, object>
            {
                { "From", "<caller_id>" },
                { "To", "<destination_number>" }

            };  
            Console.WriteLine(phlo.Run(data));
        }
    }
}

1
2
3
4
5
curl --request POST \
  --user AUTH_ID:AUTH_TOKEN \
  --url 'https://phlorunner.plivo.com/v1/account/{auth_id}/phlo/{phlo_id}' \
  --header 'Content-Type: application/json' \
  --data '{"from": "<caller_id>","to": "<destination_number>"}'

Replace the auth placeholders with your authentication credentials from the Plivo console. Replace the phlo_id placeholder with your PHLO ID from the Plivo console. Replace the phone number placeholders with actual phone numbers in E.164 format (for example, +12025551234).

Test

Save the file and run it.

Haven’t tried Plivo yet? Getting started is easy and only takes minutes. Sign up today.

Jan 27, 2022

5 mins

How to Migrate Your Go SMS Application from Twilio to Plivo

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

Migration

Go SDK

SMS API

How To

Migrating your Go SMS application from Twilio to Plivo is a seamless and painless process. The two companies’ API structures, implementation mechanisms, XML structure, SMS message processing, and voice call processing are similar. We wrote this technical comparison so that you can scope between Twilio and Plivo APIs for a seamless migration.

Understanding the differences between Twilio and Plivo development

Most of the APIs and features that are available on Twilio are also available on Plivo and the implementation mechanism is easier as the steps involved are almost identical. This table gives a side-side comparison of the two companies’ features and APIs. An added advantage with Plivo is that not only can you code using the old familiar API/XML method, you can also implement your use cases using PHLO (Plivo High Level Objects), a visual workflow builder that lets you create workflows by dragging and dropping components onto a canvas — no coding required.

Features and APIs	Twilio	Plivo	Similarities	Implementation Interface
SMS API: Send SMS/MMS messages	✅	✅	Request and response variables’ structure	API PHLO
Managed number pool for US/CA Messaging	Copilot	Powerpack	Feature parity	API Console
Geo Permissions	✅	✅	Feature parity	Console
SMS Sender ID registration	✅	✅	Feature parity	Console
Number Lookup API	✅	✅	API Parity	API
Phone number management	✅	✅	Feature parity	API Console
Validating Requests	✅	✅	Feature parity	API XML
Subaccounts	✅	✅	Feature parity	API
HTTP callbacks	✅	✅	Feature parity	API XML PHLO

Plivo offers one unique advantage: Not only can you code using APIs and XML, you can also implement your use cases using PHLO (Plivo High Level Objects), a visual workflow builder that lets you create workflows by dragging and dropping components onto a canvas — no coding required.

Plivo account creation

Start by signing up for a free trial account that you can use to experiment with and learn about our services. The free trial account comes with free credits, and you can add more as you go along. You can also add a phone number to your account to start testing the full range of our voice and SMS features. A page in our support portal walks you through the signup process.

You can also port your numbers from Twilio to Plivo, as we explain in this guide.

Migrating your Go SMS application

You can migrate your existing application from Twilio to Plivo by refactoring the code, or you can try our intuitive visual workflow builder PHLO. To continue working with the APIs, use one of the quickstart guides to set up a development environment for your preferred language. Plivo offers server SDKs in seven languages: Python, Node.js, .NET, Java, Python, Ruby, and Go. For another alternative that lets you evaluate Plivo’s SMS APIs and their request and response structure, use our Postman collections.

How to send an SMS message

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Go application to send an SMS message by changing just a few lines of code.

Twilio Plivo

package main

import (
	"encoding/json"
	"fmt"
	"github.com/twilio/twilio-go"
	openapi "github.com/twilio/twilio-go/rest/api/v2010"
	"os"
)

func main() {
    from := 
os.Getenv("TWILIO_FROM_PHONE_NUMBER")
    to := 
os.Getenv("TWILIO_TO_PHONE_NUMBER")
    subaccountSid 
:= os.Getenv("TWILIO_SUBACCOUNT_SID")

    client :=
 twilio.NewRestClientWithParams(twilio.RestClientParams{
        AccountSid: subaccountSid,
    })
    
    params := &openapi.CreateMessageParams{}
    params.SetTo(to)
    params.SetFrom(from)
    params.SetBody("Hello there")
    
    resp, err := client.ApiV2010.CreateMessage(params)
    if err != nil {
        fmt.Println(err.Error())
    } else {
        response, _ := json.Marshal(*resp)
        fmt.Println("Response: " + string(response))
    }
}

package main

import (
    "fmt"

    "github.com/plivo/plivo-go/v7"
)

func main() {
    client, err: = plivo.NewClient
    ("<auth_id>",
    "<auth_token>", & plivo.ClientOptions {})
    if err != nil {
        fmt.Print("Error", err.Error())
        return
    }
    response, err: = client.Messages.Create(
        plivo.MessageCreateParams {
            Src: "+14151113333",
            Dst: "+14151112222",
            Text: "Hello, this is a sample text",
            URL: "https://foo.com/sms_status/",
        },
    )
    if err != nil {
        fmt.Print("Error", err.Error())
        return
    }
    fmt.Printf("Response: %#v\n", response)
}

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an SMS message, your PHLO would be this:

How to receive and reply to SMS

You can migrate an application for receiving and replying to an incoming SMS from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

package main

import (
    "net/http"
    "encoding/xml"
)

type TwiML struct {
    XMLName xml.Name `xml:"Response"`

    Message string `xml:",omitempty"`
}

func main() {
    http.HandleFunc("/twiml", twiml)
    http.ListenAndServe(":3000", nil)
}

func twiml(w http.ResponseWriter, r * 
http.Request) {
    twiml: = TwiML {
        Message: "Ahoy! Thanks so much for
        your message.'"
    }
    x,
    err: = xml.Marshal(twiml)
    if err != nil {
        http.Error(w, err.Error(), 
        http.StatusInternalServerError)
        return
    }

    w.Header().Set("Content-Type",
    "application/xml")
    w.Write(x)
}

package main

import (
    "net/http"
    "plivo-go/xml"
)

func handler(w http.ResponseWriter, r * 
http.Request) {
    fromnumber: = r.FormValue("From")
    tonumber: = r.FormValue("To")
    text: = r.FormValue("Text")
    print("Message Received - ", fromnumber, " ", tonumber, " ", text)

    response: = xml.ResponseElement {
        Contents: [] interface {} {
            new(xml.MessageElement).
            SetDst(tonumber).
            SetSrc(fromnumber).
            SetContents("Thank you, we received
            your request"),
        },
    }
    w.Write([] byte(response.String()))
}

func main() {
    http.HandleFunc("/reply_sms/", handler)
    http.ListenAndServe(":8080", nil)
}

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your SMS applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

How to send an MMS message

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Go application to send an MMS message by changing just a few lines of code.

Twilio Plivo

package main

import (
    "fmt"
    twilio "github.com/kevinburke/twilio-go"
    "net/url"
)

func main() {
    client: = twilio.NewClient("TWILIO_AUTH_SID", "TWILIO_AUTH_TOKEN", nil)
    gif,
    _: = url.Parse("https://media.giphy.com/media/uGGT9wVlxPAuk/giphy.gif")
    mms,
    _: = client.Messages.SendMessage("FROM_NUMBER", "TO_NUMBER", "", [] * url.URL {
        gif
    })
    fmt.Println("You just sent a gif with Twilio using Go!! " + string(mms.Status) + " - " + string(mms.Sid))
}

package main

import (
    "fmt"
    plivo "github.com/plivo/plivo-go/v7"
)

func main() {

        client, err: = plivo.NewClient("<auth_id>", "<auth_token>", & plivo.ClientOptions {})
        if err != nil {
            panic(err)
        }
        createResp, err: = client.Messages.Create(plivo.MessageCreateParams {
            Src: "+14151113333",
            Dst: "+14151112222",
            Text: "Hello, from Go!",
            Type: "mms",
            MediaUrls: [] string {
                "https://media.giphy.com/media/26gscSULUcfKU7dHq/source.gif"
            },
            MediaIds: [] string {
                "801c2056-33ab-499c-80ef-58b574a462a2"
            },
        })
        if err != nil {
            panic(err)
        }

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an MMS message, your PHLO would be this:

More use cases

You can migrate your applications serving other use cases too.

Simple and reliable

And that’s all there is to migrate your Go SMS app from Twilio to Plivo. Our simple APIs work in tandem with our Premium Communications Network to guarantee the highest possible delivery rates and the shortest possible delivery times for your SMS messages. See for yourself — sign up for a free trial account.

Jan 25, 2022

5 mins

How to Migrate Your Go Voice Application from Twilio to Plivo

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

Migration

Go SDK

Voice API

How To

Migrating from Twilio to Plivo is a seamless and painless process. The two companies’ API structures, implementation mechanisms, XML structure, SMS message processing, and voice call processing are similar. We wrote this technical comparison between Twilio and Plivo APIs so that you can scope the code changes for a seamless migration.

Understanding the differences between Twilio and Plivo development

Features and APIs	Twilio	Plivo	Similarities	Implementation Interface
Voice API: Make phone calls	✅	✅	Request and response variables’ structure	API PHLO
Programmatically manage call flows	Twiml	Plivo XML	XML element and its attributes structure	XML PHLO
Geo Permissions	✅	✅	Feature parity	Console
Number Lookup API	✅	✅	API Parity	API
Phone number management	✅	✅	Feature parity	API Console
Call Insights	✅	✅	Feature parity	Console
Validating Requests	✅	✅	Feature parity	API XML
Subaccounts	✅	✅	Feature parity	API
Speech recognition	✅	✅	Feature parity	XML
SSML (Speech Synthesis Markup Language)	✅	✅	Feature parity	XML PHLO
Browser and Mobile SDKs	✅	✅	Feature parity	Browser Android iOS
Transcription	✅	✅	Feature parity	API XML PHLO
Custom SIP Headers	✅	✅	Feature parity	API XML PHLO Browser SDK Mobile SDKs
HTTP callbacks	✅	✅	Feature parity	API XML PHLO

Plivo account creation

You can also port your numbers from Twilio to Plivo, as we explain in this guide.

Migrating your voice application

As mentioned earlier, you can migrate your existing application from Twilio to Plivo by refactoring the code, or you can try our intuitive visual workflow builder PHLO. If you prefer the API approach, you can follow one of the voice quickstart guides based on your preferred language and web framework. Plivo offers server SDKs in seven languages: Python, Node.js, .NET, Java, Python, Ruby, and Go. For another alternative that lets you evaluate Plivo’s SMS APIs and their request and response structure, use our Postman collections.

How to make an outbound call

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Go application to make an outbound call by changing just a few lines of code.

Twilio Plivo

package main

import (
    "fmt"
    "github.com/twilio/twilio-go"
    openapi "github.com/twilio/twilio-
    go/rest/api/v2010"
    "os"
)

func main() {
    from: =
    os.Getenv("TWILIO_FROM_PHONE_NUMBER")
    to: =
    os.Getenv("TWILIO_TO_PHONE_NUMBER")

        client: = twilio.NewRestClient()
    
        params: = & openapi.CreateCallParams {}
    params.SetTo(to)
    params.SetFrom(from)
    params.SetUrl("http://twimlets.com/holdmusic?
    Bucket=com.twilio.music.ambient")
    
    resp,
    err: = client.ApiV2010.CreateCall(params)
    if err != nil {
        fmt.Println(err.Error())
    } else {
        fmt.Println("Call Status: " + * resp.Status)
        fmt.Println("Call Sid: " + * resp.Sid)
        fmt.Println("Call Direction: " +
        * resp.Direction)
    }
}

package main

import (
    "fmt"
    "github.com/plivo/plivo-go/v7"
)

func main() {
    client, err: = plivo.NewClient("<auth_id>",
    "<auth_token>", & plivo.ClientOptions {})
    if err != nil {
        fmt.Print("Error", err.Error())
        return
    }
    response, err: = client.Calls.Create(
        plivo.CallCreateParams {
            From: "+14151234567",
            To: "+15671234567",
            AnswerURL:
"https://s3.amazonaws.com/static.plivo.com/answer.xml",
            AnswerMethod: "GET",
        },
    )
    if err != nil {
        fmt.Print("Error", err.Error())
        return
    }
    fmt.Printf("Response: %#v\n", response)
}

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to make an outbound call, your PHLO would be this:

How to receive an incoming call

You can migrate an application for receiving and handling an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

package main

import (
  "net/http"
  "encoding/xml"
)

type TwiML struct {
  XMLName xml.Name `xml:"Response"`

  Say    string `xml:",omitempty"`
}

func main() {
  http.HandleFunc("/twiml", twiml)
  http.ListenAndServe(":3000", nil)
}

func twiml(w http.ResponseWriter, r *
http.Request) {
  twiml := TwiML{Say: "Hello World!"}
  x, err := xml.Marshal(twiml)
  if err != nil {
    http.Error(w, err.Error(), http.StatusInternalServerError)
    return
  }

  w.Header().Set("Content-Type", "application/xml")
  w.Write(x)
}

package main

import (
	"fmt"
	"net/http"
	"github.com/plivo/plivo-go/v7"
)

func handler(w http.ResponseWriter, r *
http.Request) {

	response := xml.ResponseElement{
		Contents: []interface{} {
			new(xml.SpeakElement).
			AddSpeak("Hello, you just
      received your first call"),
		},
	}
	fmt.Printf(response.String())
}

func main() {
	http.HandleFunc("/receive_call/", handler)
	http.ListenAndServe(":8080", nil)
}

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

How to forward an incoming call

You can migrate an application for forwarding an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

package main

import (
    "net/http"
    "encoding/xml"
)

type TwiML struct {
    XMLName xml.Name `xml:"Response"`

    Dial string `xml:",omitempty"`
}

func main() {
    http.HandleFunc("/twiml", twiml)
    http.ListenAndServe(":3000", nil)
}

func twiml(w http.ResponseWriter, r * 
http.Request) {
    twiml: = TwiML {
        Dial: "415-123-4567"
    }
    x,
    err: = xml.Marshal(twiml)
    if err != nil {
        http.Error(w, err.Error(), 
        http.StatusInternalServerError)
        return
    }

    w.Header().Set("Content-Type",
    "application/xml")
    w.Write(x)
}

package main

import (
    "net/http"
    "plivo-go/xml"
)

func handler(w http.ResponseWriter, r *
http.Request) {
    response: = xml.ResponseElement {
        Contents: [] interface {} {
            new(xml.DialElement).
            SetContents(
                [] interface {} {
                    new(xml.NumberElement).
                    SetContents
                    ("<destination_number>"),
                },
            ),
        },
    }
    w.Write([] byte(response.String()))
}

func main() {
    http.HandleFunc("/forward_call/", handler)
    http.ListenAndServe(":8080", nil)
}

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

More use cases

You can migrate your applications serving other use cases too.

Simple and reliable

And that’s all there is to migrate your Go voice application from Twilio to Plivo. Our simple APIs work in tandem with our Premium Communications Network. See for yourself — sign up for a free trial account.

Jan 24, 2022

5 mins

How to Build a Text Autoresponder the No-Code Way Using PHLO

How to create a text autoresponder without writing a single line of code to respond to incoming messages on your business numbers.

PHLO

SMS API

How To

Use Cases

This guide shows how to write an autoresponder for SMS text messages. Autoresponders can streamline marketing campaigns and subscription signups and reduce the amount of work humans have to do. You can create a text autoresponder either by using our PHLO visual workflow builder or our SMS API. Follow the instructions in one of the tabs below.

You can create and deploy a PHLO to implement an SMS autoresponder with a few clicks on the PHLO canvas.

How it works

Prerequisite

Create the PHLO

To create a PHLO, visit the PHLO page of the Plivo console. If this is your first PHLO, the PHLO page will be empty.

Click Create New PHLO.
In the Choose your use case pop-up, click Build my own. The PHLO canvas will appear with the Start node.Note: The Start node is the starting point of any PHLO. It lets you trigger a PHLO to start upon one of three actions: incoming SMS message, incoming call, or API request.
If you plan to use a dynamic payload — passing values through parameters when you trigger the PHLO from your application — click on the Start node to open the Configuration pane. Under API Request, enter key names for the variables you want to use in your payload — for example, a list of numbers to send an SMS message to.
Once you’ve configured the node, click Validate to save the configuration.
From the list of components on the left-hand side, drag and drop the Send Message component onto the canvas. When a component is placed on the canvas it becomes a node.
Draw a line to connect the Start node’s Incoming Message trigger state to the Send Message node.
In the Configuration pane at the right of the canvas, configure the Send Message node with a sender ID in the From field. Enter the destination number you wish to send a message to in the To field. Put your message in the Text field.Note: You can define a static payload by specifying values when you create the PHLO, or define a dynamic payload by passing values through Liquid templating parameters when you trigger the PHLO from your application.

Once you’ve configured the node, click Validate to save the configuration.
After you complete the configuration, give the PHLO a name by clicking in the upper left, then click Save.

Assign the PHLO to a Plivo number

Once you’ve created and configured your PHLO, assign it to a Plivo number.

On the Numbers page of the console, under Your Numbers, click the phone number you want to use for the PHLO.
In the Number Configuration box, select PHLO from the Application Type drop-down.
From the PHLO Name drop-down, select the PHLO you want to use with the phone number, then click Update Number.

How to Build a Text Autoresponder Using PHLO | Plivo

Test

You can now send a message to your Plivo phone number and see how the autoresponder works.

For more information about creating a PHLO application, see the PHLO Getting Started guide. For information on components and their variables, see the PHLO Components Library.

Jan 14, 2022

5 mins

What is MMS Messaging?

Detailed guide to MMS messaging at Plivo including the difference between SMS and MMS and how to get started.

MMS API

What is MMS Messaging?

When you go out in public these days, few people are interacting with each other — typically, they’re all on their phones. But they aren’t talking — they’re sending GIFs, emojis, and short video clips. This visual content allows consumers to interact with each other and the messaging service that lets you incorporate images, audio, and video into text messages is MMS.

What does MMS mean?

MMS — Multimedia Messaging Service — allows your phone to send emojis, pictures, videos, GIFs, audio recordings, and other non-text content. MMS can be more personalized than a plain text message. While you can send an emoji in an SMS message, you can send a GIF in MMS to amplify the tone of your message.

MMS vs. SMS: Which is better for your use case?

An MMS with graphical elements can be visually engaging for message recipients. Corporate marketing departments have trouble getting potential customers to pay attention to their messages. The visual element that MMS provides can solve that problem. According to Salesmate, “Pop an emoji or emoticon in your subject lines, and your open rates could soar. 56% of brands that use emoticons in that way have higher open rates. It’s something your business can’t afford to neglect.”

MMS has unique strengths for several industries. Consider retail for instance — retailers can use MMS to send coupons with embedded QR codes, or receive product registrations that include images of barcodes or QR codes. We wrote a blog post about how retailers can take full advantage of MMS. Recommended uses include coupons and promotions, personal shopping, product registrations, and branded content. Even if you’re not a retailer, it has ideas you might be able to apply to your business.

You can use MMS for any of the same use cases as SMS. Check out our guide on getting started with SMS marketing for more information.

As MMS is such a personal form of communication, we advise businesses to be thoughtful about when and how they use it. A messaging strategy loses its power when you inundate consumers with irrelevant messages or send messages too often or at inconvenient times, such as when they’re settling into bed for the night.

Plivo’s MMS API

Make sure to work with a high-quality MMS API provider that can provide the features, network, and infrastructure needed to help make your strategy successful. Our guide to choosing an SMS API provider details what you should look for from your SMS/MMS provider. Ultimately you’re looking for an API solution that makes it easy for developers to programmatically send and receive messages, that also leverages the cloud for scalability, and that runs on a global communications network to intelligently and cost-effectively route messages.

The Plivo MMS API lets you send and receive pictures and videos across phone numbers in the US and Canada. Several key features let you easily engage your customers visually.

You can send and receive MMS messages across the US and Canada via multiple sender types, including long code and toll-free numbers.
Choose between a variety of multimedia formats, such as image files (JPEG, GIF), emojis, audio (MP3), and video (MP4), for a rich multimedia experience.
The API intelligently resizes your images to ensure the best delivery across different carrier networks.
Plivo provides multimedia storage for both inbound and outbound MMS messages for easy access and reuse.
The API can convert multimedia messages into SMS when you’re sending messages to MMS-incompatible phone numbers.
Message queuing retries concurrent messaging requests to comply with carrier regulations and offers increased deliverability.

MMS on Powerpack

Plivo’s Powerpack provides a set of features that make message communication at scale more effective and reliable, ensuring that your SMS and MMS messages get delivered at whatever scale you’re sending them, to any country. Powerpack automates all of the complex logic that you would otherwise have to code manually. It’s designed to meet large-scale message throughput and volume requirements. By automatically distributing your overall messaging traffic across a pool of source numbers, Powerpack guarantees that you stay compliant with throughput limits and that your MMS messages get delivered.

Get started with MMS at Plivo

Not sure how to use Plivo for MMS? We’ve written Getting Started guides to sending MMS and receiving MMS for developers who use Node.js, Ruby, Python, PHP, .NET (C#), Java, and Go. And if those aren’t enough, we’ve got answers to several MMS questions in our support portal.

Our competitive pricing starts at $0.0080 for inbound and $0.0160 for outbound MMS messages. Pricing is pay-as-you-go, but discounts may apply to messages sent at higher volumes; you can contact our sales team for higher volume enrollment. Additional carrier surcharge fees may apply to all inbound and outbound MMS usage rates.

Jan 13, 2022

5 mins

How to Migrate Your Ruby Voice Application from Twilio to Plivo

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

Migration

Ruby SDK

Voice API

How To

Understanding the differences between Twilio and Plivo development

Features and APIs	Twilio	Plivo	Similarities	Implementation Interface
Voice API: Make phone calls	✅	✅	Request and response variables’ structure	API PHLO
Programmatically manage call flows	Twiml	Plivo XML	XML element and its attributes structure	XML PHLO
Geo Permissions	✅	✅	Feature parity	Console
Number Lookup API	✅	✅	API Parity	API
Phone number management	✅	✅	Feature parity	API Console
Call Insights	✅	✅	Feature parity	Console
Validating Requests	✅	✅	Feature parity	API XML
Subaccounts	✅	✅	Feature parity	API
Speech recognition	✅	✅	Feature parity	XML
SSML (Speech Synthesis Markup Language)	✅	✅	Feature parity	XML PHLO
Browser and Mobile SDKs	✅	✅	Feature parity	Browser Android iOS
Transcription	✅	✅	Feature parity	API XML PHLO
Custom SIP Headers	✅	✅	Feature parity	API XML PHLO Browser SDK Mobile SDKs
HTTP callbacks	✅	✅	Feature parity	API XML PHLO

Plivo account creation

You can also port your numbers from Twilio to Plivo, as we explain in this guide.

Migrating your voice application

How to make an outbound call

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Ruby application to make an outbound call by changing just a few lines of code.

Twilio Plivo

require 'rubygems'
require 'twilio-ruby'

account_sid = ENV['TWILIO_ACCOUNT_SID']
auth_token = ENV['TWILIO_AUTH_TOKEN']
@client = Twilio::REST::Client.new(account_sid
, auth_token)

call = @client.calls.create(
            url: 
'http://demo.twilio.com/docs/classic.mp3',
            to: '+14155551212',
            from: '+14155551212'
)
puts call.sid

require 'rubygems'
require 'plivo'

include Plivo
include Plivo::Exceptions

auth_id = ENV['PLIVO_AUTH_ID']
auth_token = ENV['PLIVO_AUTH_TOKEN']

api = RestClient.new(auth_id,auth_token)

begin
  response = api.calls.create(
    '+14151234567',
    ['+15671234567'],
    'https://s3.amazonaws.com/static.plivo.com/answer.xml'
  )
  puts response
rescue PlivoRESTError => e
  puts 'Exception: ' + e.message
end

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to make an outbound call, your PHLO would be this:

How to receive an incoming call

You can migrate an application for receiving and handling an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

require 'sinatra'
require 'twilio-ruby'

post '/twiml' do
  # Start our TwiML response
  Twilio::TwiML::VoiceResponse.new do |r|
    # Use <Say> to give the caller some
    instructions
    r.say(message: 'hello world!', voice: 'alice')
  end.to_s
end

include Plivo
include Plivo::XML
include Plivo::Exceptions

class PlivoController < ApplicationController
 def inbound
    response = Response.new
    speak_body = 'Hello, you just received your
    first call'
    response.addSpeak(speak_body)

    xml = Plivo::PlivoXML.new(response)
    render xml: xml.to_xml
 end
end

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

How to forward an incoming call

You can migrate an application for forwarding an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

require 'sinatra'
require 'twilio-ruby'

post '/twiml' do

   response = Twilio::TwiML::VoiceResponse.
   new
   response.dial(number: '415-123-4567')
   response.say(message: 'Goodbye')
   puts response
   end.to_s
end

def forward
   response = Response.new
   dial = response.addDial()
   dest_number = "<destination_number>"
   dial.addNumber(dest_number)

   xml = PlivoXML.new(response)
   puts xml.to_xml
   render xml: xml.to_xml
 end

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

More use cases

You can migrate your applications serving other use cases too.

Simple and reliable

And that’s all there is to migrate your Ruby Voice app from Twilio to Plivo. Our simple APIs work in tandem with our Premium Communications Network. See for yourself — sign up for a free trial account.

Jan 10, 2022

5 mins

How to Migrate Your Ruby SMS Application from Twilio to Plivo

Plivo's SMS API and Voice API enables businesses to communicate with their customers at global scale. Sign up for free now.

Migration

Ruby SDK

SMS API

How To

Migrating your Ruby SMS app from Twilio to Plivo is a seamless and painless process. The two companies’ API structures, implementation mechanisms, XML structure, SMS message processing, and voice call processing are similar. We wrote this technical comparison so that you can scope between Twilio and Plivo APIs for a seamless migration.

Understanding the differences between Twilio and Plivo development

Features and APIs	Twilio	Plivo	Similarities	Implementation Interface
SMS API: Send SMS/MMS messages	✅	✅	Request and response variables’ structure	API PHLO
Managed number pool for US/CA Messaging	Copilot	Powerpack	Feature parity	API Console
Geo Permissions	✅	✅	Feature parity	Console
SMS Sender ID registration	✅	✅	Feature parity	Console
Number Lookup API	✅	✅	API Parity	API
Phone number management	✅	✅	Feature parity	API Console
Validating Requests	✅	✅	Feature parity	API XML
Subaccounts	✅	✅	Feature parity	API
HTTP callbacks	✅	✅	Feature parity	API XML PHLO

Plivo account creation

You can also port your numbers from Twilio to Plivo, as we explain in this guide.

Migrating your Ruby SMS application

How to send an SMS message

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Ruby application to send an SMS message by changing just a few lines of code.

Twilio Plivo

require 'twilio-ruby'

account_sid = '<account_sid>'
auth_token = '<auth_token>'
client = Twilio::REST::Client.new(account_sid,
auth_token)

from = '+15551234567' # Your Twilio number
to = '+15555555555' # Your mobile phone
number

client.messages.create(
	from: from,
	to: to,
	body: "Hey friend!"
)

require 'plivo'
include Plivo

api = 
RestClient.new('<auth_id>','<auth_token>')
response = api.messages.create(
	src:'+14152345678',
	dst:"'+14151112222',
	text:'Hello, from Ruby!'
)
puts response

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an SMS message, your PHLO would be this:

How to receive and reply to SMS

You can migrate an application for receiving and replying to an incoming SMS from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

require 'twilio-ruby'
require 'sinatra'

post '/sms-quickstart' do
  twiml = Twilio::TwiML::MessagingResponse
  .new do |r|
    r.message(body: 'Ahoy! Thanks so much for
    your message.')
  end

  twiml.to_s
end

# using Rails
def replysms
	from_number = params[:From]
	to_number = params[:To]
	text = params[:Text]
	response = Response.new
	params = {
		src: to_number,
		dst: from_number,
	}
	message_body = 'Thank you, we
  received your request'
	response.addMessage(message_body
  , params)
	xml = PlivoXML.new(response)
	puts xml.to_xml
	render xml: xml.to_xml
end

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

For more information about migrating your SMS applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

How to send an MMS message

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple Ruby application to send an MMS message by changing just a few lines of code.

Twilio Plivo

require 'rubygems'
require 'twilio-ruby'

account_sid = '<account_sid>'
auth_token = '<auth_token>'
@client = Twilio::REST::Client.new(
account_sid, auth_token)

message = @client.messages
  .create(
     body: 'This is the ship that made the Kessel Run in fourteen parsecs?',
     from: '+15017122661',
     media_url: 
['https://c1.staticflickr.com/3/2899/14341091933_1e92e62d12_b.jpg'],
     to: '+15558675310'
   )

puts message.sid

require 'rubygems'
require 'plivo'

include Plivo

api = RestClient.new('<auth_id>','<auth_token>')
  response = api.messages.create(
    src:'+14152345678',
    dst:'+14151112222',
    text:'Hello, from Ruby!',
    media_urls:[
    "https://media.giphy.com/media/26gscSULUcfKU7dHq/source.gif"],
    type: 'mms'
  )
puts response

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an MMS message, your PHLO would be this:

More use cases

You can migrate your applications serving other use cases too.

Simple and reliable

And that’s all there is to migrate your Ruby SMS app from Twilio to Plivo. Our simple APIs work in tandem with our Premium Communications Network to guarantee the highest possible delivery rates and the shortest possible delivery times for your SMS messages. See for yourself — sign up for a free trial account.

It’s easy to get started. Sign up for free.

Create your account and receive trial credits or get in touch with us.

Get Volume Pricing

Request Trial

AI Voice Agents - The Complete Guide to Voice Chat (2025)

What is an AI voice agent?

Types of AI voice agents

Rule-based AI voice agent

AI-assisted voice agent

Conversational AI voice agent

Voice-activated voice agent

How does an AI voice agent improve customer engagement?

Use case: Get a quick update on order status, 24/7

Benefits:

Use case: Improve language learning for students

Benefits:

Use case: Improve patient outcomes in healthcare

Benefits:

Use case: Streamline routine financial services

Benefits:

Use case: Get personal shopping assistance

Benefits:

Features of an AI voice agent

Natural language understanding (NLU)

Personalization capabilities

Multi-language support

Integration with other platforms and services

Benefits of voice agents

Enhanced user experience

Better cost efficiency

Accessibility for users with disabilities

Data collection and analysis for improved services

24/7 availability

Future of AI voice technology

Key upcoming trends:

Launch an AI voice agent with Plivo

AI Voice Agents for Real Estate (2026): 10 Tools Compared, Real Limitations and What Actually Scales

Top 10 AI Voice Agents for Real Estate (2026)

1. Plivo

2. Luron AI

3. Callers AI

4. SquadStack AI

5. Telgent

6. AIOnCalls

7. Brilo AI

8. VocalDesk

9. Calldock

10. Ylopo

What Matters Most in AI Voice Agents (Beyond the Basics)

1. Telephony Ownership vs. Vendor Stitching

2. Real-Time Performance (Latency & Uptime)

3. Multi-Channel Context, Not Disconnected Bots

4. Integration Depth (CRM, Calendars, Workflows)

5. Built for Scale, Not Just Launch

FAQs

What's the fastest way to go live without breaking existing operations?

How do I ensure voice quality doesn't feel robotic or laggy?

How does the agent stay accurate and compliant with real estate data?

What happens when call volume spikes or multiple leads call at once?

How does this fit into my CRM and follow-up workflows?

Try Plivo Free

Best AI Voice Agents for Customer Support and Service (2026): What to Deploy Now

1) Plivo — The fastest path to production-grade AI voice agents for customer support

Why Plivo is #1

What it does for you

Segment-by-segment fit

Start with Voice, go everywhere

Suitable for

2) Google Dialogflow CX — Complex, branching flows without spaghetti

Key features

Why it matters

Implementation steps

Suitable for

3) Amazon Lex + Amazon Connect — AWS-first voice automation that ops can own

Key features

Why it matters

Implementation steps

Suitable for

4) IBM Watson Assistant — Governance-first deployments in regulated industries

Key features

Why it matters

Implementation steps

Suitable for

5) Cognigy.AI — IVR modernization with fine-grained voice control