SEPTEMBER 2023 RELEASES
September 2023 Releases
Building AI Voice Agent-Ready APIs: Lessons from the Front Lines
As contact centers move beyond simple AI Voice Agent use cases like capturing a callback request or asking a few qualification questions, and start deploying AI Voice Agents to fully own more complex interactions – like coordinating roadside assistance or guiding a customer through a full booking flow – a new challenge is emerging: most APIs were never designed with AI agents in mind.
They were built for deterministic systems: frontends, backends, and workflows that follow strict patterns. But AI Voice Agents aren’t browsers; they’re collaborators that are probabilistic, interpretive, and conversational. They need clear, structured, and contextual access to information and actions, in order to function effectively in real-time conversations. Trying to shoehorn old APIs into LLM-driven workflows can lead to poor agent performance, unnecessary complexity, and brittle integrations. The better your APIs help AI agents reason, explain, and act, the better your customer experience will be.
At Regal, we address this challenge by architecting a middleware abstraction layer between AI agents and customer APIs. This layer translates natural language intents into structured, API-compliant requests, batches API calls when needed for reduced latency, and at times distills verbose raw responses into only what’s relevant for AI agents and enriches raw responses with context-aware summaries, labels, and semantic metadata tailored for conversational interpretation. This lets legacy APIs remain intact while giving AI Voice Agents a clean, usable interface.
Here’s what we’ve learned from building this translation layer to retrofit traditional APIs into AI agent stacks, and how to design future APIs to actually make your AI agents better. To bring our learning to life, we’ll use the example of an AI Voice Agent that helps customers discover, and then book for appointments with, medical providers.
1. Accept and Canonicalize Fuzzy, Human-Centric Inputs
Traditional APIs expect perfectly structured input. But AI Voice Agents deal with vague phrases like "next Friday afternoon" or "Dr. Sanchez" or "my usual location." An AI Voice Agent-ready API handles the normalization, not the agent. On the backend, use libraries like Chrono or Duckling for natural language date parsing, fuzzy location matching based on customer zip code, or named entity resolution to map "Dr. Sanchez" to a provider ID.
Traditional API:
POST /appointments
{
"provider_id": "8932",
"time": "2025-08-02T14:00:00",
"location_id": "brooklyn_1"
}
AI Agent-ready API:
POST /appointments
{
"provider": "Dr. Sanchez",
"time": "next Friday afternoon",
"location": "nearest clinic"
}
Moreover, it’s best practice for your API to echo back the resolved interpretation in the API response, so the agent can confirm naturally: "Great, I’ve scheduled you for 2 PM next Friday. Does that work?”
{
"resolved_time": "2025-08-02T14:00:00",
"raw_input": "next Friday afternoon"
}
2. Return Semantic Metadata, Not Just Raw Codes
AI agents reason better when your API gives them full context – not just what a value is, but what it means and how it should be used in conversation. LLMs don’t operate on raw IDs or numeric codes alone. Imagine how many times a number or letter occurs in its context? Even if the ID is a UUID, it's unreasonable to expect the LLM to parse and match identifiers to semantic representations while staying on task. LLMs make decisions based on relationships, semantics, and intent. Providing clear labels and explanatory metadata allows agents to understand, summarize, and respond accurately without guessing or hallucinating.
Traditional API:
{
"status": "C",
"priority": 2
}
AI Agent-ready API:
{
"status": {
"code": "C",
"label": "Cancelled",
"explanation": "This appointment was cancelled by the provider."
},
"priority": {
"level": 2,
"label": "Urgent",
"description": "Requires attention within 24 hours."
}
}
3. Avoid Overloading Responses with Unnecessary Data
Traditional APIs often return everything a UI might need, such as: long doctor bios, image urls, full calendars, exhaustive list of insurance plans accepted. This makes sense for frontends that humans can scroll and read on their own time, but not in a live AI Voice Agent conversation where agents operate within token limits and care about relevance and latency. Succinct API responses reduce context overload, avoid hallucinations, and help the agent stay focused.
Traditional API:
GET /therapy-providers?specialty=anxiety
{
"providers": [
{
"id": "p_123",
"name": "Dr. Elena Martinez",
"bio": "Elena Martinez, PhD, is a licensed clinical psychologist with over 20 years of experience in CBT, DBT, and trauma-informed care. She earned her doctorate at Stanford University and completed her residency at Mount Sinai. Elena specializes in anxiety, panic disorders, and adolescent therapy...",
"short_bio": "20+ years in CBT, specializes in anxiety and trauma.",
"specialties": ["anxiety", "trauma", "adolescents"],
"insurance_accepted": [
{ "name": "Aetna", "plan_codes": [...] },
{ "name": "Blue Cross", "plan_codes": [...] },
{ "name": "UnitedHealthcare", "plan_codes": [...] },
{ "name": "Cigna", "plan_codes": [...] }
],
"availability": [
{ "date": "2025-07-28", "slots": ["09:00", "14:00", "16:30"] },
{ "date": "2025-07-29", "slots": ["11:00", "13:30", "17:00"] },
// ... more days ...
],
"ratings": 4.9,
"location": "Brooklyn, NY",
"video_sessions": true,
"languages_spoken": ["English", "Spanish"],
"internal_tags": ["tier_1", "promoted"]
},
...
]
}
}
AI Agent-ready API:
GET /therapy-providers/summary?location=Brooklyn&specialty=anxiety&insurance=Cigna&type=virtual
{
"providers": [
{
"name": "Dr. Elena Martinez",
"gender": "Female",
"title": "Licensed Clinical Psychologist",
"summary": "20+ years in CBT, DBT, and trauma-informed care. Specializes in anxiety, panic disorders, and adolescent therapy.",
"ratings": 4.9,
"accepts_customer_insurance": true,
"next_available_slot": "Monday - July 28th, 2025, at 2PM Eastern."
}
]
}
4. Make Errors Recoverable and Helpful
Descriptive error messages with hints of what to do next helps agents retry or redirect naturally.
Traditional API:
400 Bad Request
AI Agent-ready API:
{
"error": "Invalid date format",
"hint": "Try 'next Monday' or '2025-08-01'"
}5. Batch Responses Where Possible
AI agents work better with fewer round trips. Each additional API call introduces latency and raises the risk of failure when the agent is trying to hold a live voice conversation. Unlike traditional systems that can sequence multiple calls without user-facing consequences, agents must maintain conversational coherence and flow. Bundling relevant context into a single endpoint helps the agent reason across multiple dimensions at once, such as user status, plan type, and appointment availability, without needing to stop and fetch information mid-dialogue.
Traditional API:
Requires 4 successive calls:
GET /customer
GET /appointments?customer_id=...
GET /cases?customer_id=...
GET /plan?customer_id=...
AI Agent-ready API:
GET /customer-summary?customer_id=abc123
{
"name": "Alex Smith",
"plan_status": "active",
"next_appointment": "Saturday, August 2nd, 2025 at 3PM Central.",
"number_of_open_cases": 1
}
6. Low Latency APIs
AI Voice Agents operate in real-time, spoken conversations – every pause or delay is felt by the user. While a traditional web UI can tolerate 500ms+ response times, AI agents should not. A slow API response translates directly into awkward silences or interruptions. Critical endpoints should respond in under 200 milliseconds to maintain a natural, fluid exchange. It’s not just about averages, it’s about distribution. If your endpoint’s median latency is 200ms but the 95th percentile hits 5 seconds, that means half your users might be waiting anywhere from 200ms to 5s for a response. That’s a killer for conversational flow. Aim for a p95 latency under 200ms to keep interactions smooth.
7. Provide Conversional Examples in Your API Docs
Providing examples in your API docs or Postman collections helps with prompting, grounding, and debugging. When developers can see how natural-language inputs map to structured payloads, and what responses are expected, they can craft more precise prompts and diagnose issues faster. It also helps align cross-functional teams.
AI Agent-ready API Docs:
- Include realistic request and response bodies
- Show sample natural language prompts that map to the API call
- Document edge cases and expected errors
Building successful AI Voice Agents requires product, engineering, contact center teams and AI agent builders to all be on the same page. Mapping APIs to the call flow may be time-consuming, but it’s essential for creating robust and reliable agent behaviors.
How MCP Changes the Game, But Doesn’t Replace APIs
MCP (Model Context Protocol) is an open standard that defines how AI agents discover and interact with external tools, APIs, and data sources in a consistent, structured way. Think of it as a universal adapter: it tells agents what tools exist, how to use them, and what data or actions each one supports.
As customers build more AI agents, managing tool access and updates becomes a challenge. MCP helps by centralizing all tool schemas and descriptions on a single server. Instead of updating each agent individually when an API changes, you update your MCP server, and all connected agents automatically benefit.
That said, MCP doesn’t replace APIs – it relies on them. Your APIs still do the heavy lifting: business logic, validation, data access, and operations. MCP just standardizes how agents discover and access those APIs. It helps agents.
The Regal Way
The reality today is that most APIs are not designed for AI agents, and it will take years for engineering teams to retrofit them accordingly. That’s one of the reasons why contact center teams partner with Regal to accelerate their AI agent adoption curve. Regal's "Build With" approach doesn't just deliver the tools to build AI agents, but also the expertise. Our AI Forward Deployed Engineers work side-by-side with your team – deeply understanding your business, goals, workflows, and current systems, and providing the bridge to AI agents that don’t just get deployed, but actually wow your customers and achieve business results.
Frequently Asked Questions
What API characteristics best support real-time voice interactions?
Prioritize low and predictable latency, deterministic JSON responses, and compact payloads. Keep operations short-lived, make fields stable and machine-parseable, and pass conversation/customer context explicitly rather than relying on hidden server state.
How can I design endpoints so a language model can select and fill them reliably?
Expose a small set of well-scoped actions with clear, verb-based names and strict JSON schemas. Use required fields, enums, and examples to reduce ambiguity, and return concise, structured results that are easy for tool-calling models to parse.
What’s a safe pattern for operations that have side effects, like bookings or payments, during a call?
Use a two-step pattern: validate/quote first, then confirm/commit after explicit user approval. Include idempotency keys and job IDs, and support status endpoints or webhooks for long-running tasks so the agent can keep the caller informed.
How should errors, timeouts, and rate limits be handled for voice-agent traffic?
Standardize error codes and machine-readable reasons, and mark which errors are safe to retry. Include rate-limit headers, enforce timeouts, and use exponential backoff with jitter; rely on idempotency so retries don’t duplicate side effects.
How do I test and observe agent-to-API behavior to improve reliability over time?
Provide a sandbox with deterministic test data, log request/response pairs with correlation IDs per call and turn, and track p50/p95 latency, error rates, and tool success. Enable transcript-linked traces and replays to diagnose and improve real interactions.
Treat your customers like royalty
Ready to see Regal in action?
Book a personalized demo.
Thank you! Click here if you are not redirected.
Oops! Something went wrong while submitting the form.
Founded in 2020, Regal is an enterprise voice AI agent platform for contact centers. Regal helps businesses build, deploy, and manage autonomous AI agents across sales, support, and operations teams.
Latest Blog Posts
.webp)
.webp)
Outbound Call Center: What It Is, How It Works & Best Practices
The fastest growing High Consideration brands have invested heavily in outbound call centers for sales and marketing. With the right technology, staffing and measurement, you too can build a high performing outbound call center to help hit your growth goals.
Introducing Goal Oriented Agents: Conversational, Dynamic, and Built to Reach Resolution
With Goal Oriented Agents, you can define goal nodes with the information the agent must collect and the prerequisites to get there. A dual-model design keeps the call natural and on track. This makes the agents well suited to complex intake and qualification.
.webp)
Pinpoint Critical Knowledge Base Gaps with Regal Improve
Customer conversations are inherently dynamic, and Regal Improve’s Knowledge Base Coverage tracks changes in retrieval performance over time and at scale. This makes it easy to verify that KB updates increase coverage and if your documentation is keeping up with evolving customer requests.
November 2025 Releases
November's releases make it easier to scale your transfer-heavy call flows, with new tools that align dialer pacing to downstream agent capacity and streamline complex handoffs. You’ll also see improved post-call workflow accuracy, with reliable data extraction and disposition outcomes driven by LLM configurability and earlier validation.
.webp)
Teaching Voice AI to Behave: Prompting Principles Every Parent Already Knows
Building a great AI voice agent isn’t so different from parenting a five-year-old: clarity, examples, and structure make all the difference. This post breaks down proven prompting principles—from positive framing and persona design to conversational guardrails—that help AI agents sound natural, stay on task, and follow directions every time.
Announcing Regal + Rime: Human-Like Voices at Enterprise Scale
Regal is partnering with Rime to deliver ultra-realistic, emotionally nuanced AI voices for enterprise contact centers. Discover new voice options that capture human qualities like pacing, resonance, and subtle expression, and learn how Rime’s technology powers conversations that build trust at scale.
%20(1).webp)
Announcing Regal + Cartesia: Expanding Voice Options for Enterprise AI
Regal is partnering with Cartesia to deliver ultra-low latency, high-fidelity AI voices for enterprise contact centers. Explore new voice options, hear them in action, and learn about Cartesia's industry-leading voice AI offerings.
%20(1).webp)
.webp)
%20(1).webp)
Beyond CCaaS: How to turn your Contact Center into a Revenue Center
Why are so many contact centers stuck being cost centers? Why do they keep looking for cost reductions instead of revenue increases? Bad data and technology decisions are at the core of this issue. We need "marketing automation" (aka unified customer profiles, event-driven systems and a/b testing) like Regal.io in the contact center to empower teams to start looking for incremental revenue instead.
The Next Step Forward in AI will come from Consumer Businesses
Consumer businesses are implementing AI-enabled customer experiences without any change in behavior on the part of consumers, which is leading AI to become common with more speed than past transitions like the internet and the smartphone. And it means that the next step in AI will not come from the LLM providers. The next big step forward in AI rests in the hands of consumer businesses.
Innovating on Patient Care | B2C Sales Podcast Episode 7
Explore Eric Hauser's remarkable career journey from GovTech to healthcare disruption at Cadence, highlighting the transformative power of innovation, collaboration, with a special focus on the pivotal role of Regal in driving patient engagement and outcomes.
How SoFi, Perry Health & Allstate Personalize CX at Scale
Discover how Regal.io's AI-powered personalized outreach solutions are revolutionizing outbound sales and customer experience across industries like healthcare, finance, and insurance in our latest eBook, "Modernizing Outbound Contact Centers: How to Treat Millions of Customers like One in a Million."
.jpeg)
Introducing Collaboration-Native Features to CCaaS
Combining collaboration functionality into CCaaS workflow tools invites more cross-functional users from a company to participate in designing the end-customer experience, leading to better omni-channel orchestration and customer outcomes. Learn more about Regal's collaboration features.
How Regal.io is Turning the $40B CX Industry on Its Head
Jon Heaps, former VP, Channel at Observe.ai, Talkdesk, and inContact interviews Alex Levin, Co-Founder & CEO of Regal.io, about the history of the contact center industry and some of the key challenges teams making outbound calls face as customers demand more online experiences.
New SMS & Branded Caller ID Rules Are Enhancing Customer Experience
Are you using Branded Caller ID for outbound calls or SMS? New SMS and Branded Caller ID regulations rolled out in Q2 2023 that you MUST KNOW ABOUT. The new regulations require that every company register their SMS campaigns and Branded Caller ID campaigns before being allowed to send texts or brand calls.
Announcement: Regal Conversation Intelligence
Regal’s Conversation Intelligence drives higher conversion rates for B2C sales teams. We use both the traditional QA/coaching tools, and brand new conversational triggers that allow you to update customer profiles and send automated follow up messages based on what is said in a conversation.
Caller ID vs. CNAM vs. Branded Caller ID: What’s the Difference?
Caller ID, CNAM, and Branded Caller ID all help identify an incoming call and, therefore, increase call answer rates. Find out how they differ and how outbound phone sales teams can utilize each to reach prospects and customers effectively.
How Regal Helps Consumer Lenders Achieve Growth in Tough Times
Our Co-Founder & CTO, Rebecca Greene, spoke with journalist Tony Zerucha at the recent Fintech Nexus USA 2023 event about how consumer lenders are using personalized phone and SMS sales outreach to obtain growth despite high inflation and rising interest rates.
Meet Regal Call Branding™: Branded Caller ID for 400M+ US Devices
We are excited to announce Regal Call Branding™ including Branded Caller ID. Available on all 400M wireless devices in the US (as well as most of Canada and the UK), Regal Call Branding™ puts you in control of what people see when you call their cell phone – including showing your brand and/or logo.
Q&A with Perry Health’s Scott Chesrown
Get behind-the-scenes insights about Perry Health’s 23% revenue increase with Regal.io. Perry Health’s Scott Chesrown sat down with Regal.io and discussed how they implemented outbound sales technology, integrated new capabilities into their process, and built on their early success.
Drive More Contact Center Revenue With These 6 Holiday Tips
It’s the holiday season and you’d like to hit your December revenue goals. Outbound B2C sales during the holidays can be a major performance driver – if you're prepared and you have the right tools in place. Use these seven tips to get your outbound B2C sales in shape for holiday success.
The Rise of Voice AI Agents: Real-World Deployments Across the Enterprise
In this AI4 fireside chat, Regal.ai COO Sahil Mehta and TaskUs CCO Jarrod Johnson explore how enterprise organizations are deploying voice AI agents across customer experience, support, and sales. They share real-world deployments, discuss quality and ROI trade-offs, and outline best practices for aligning operations and product teams when adopting AI agents at scale.
.png)
.png)
.png)
October 2026 Product Recap
Last month, we shipped releases that improve your contact center operations by extracting business insights with Copilot and reducing wasted agent minutes with our new Voicemail Detection model. The result is more reliable, productive AI agents that can drive revenue for your business.
.png)
How We Built the Voice CX Benchmark
Enterprises need voice agents that hold a natural, human-like conversation while moving each call toward its goal and staying within compliance boundaries. The Voice CX Benchmark scores models on exactly that: how well they progress the call turn by turn, how safely and clearly they communicate, and how quickly they respond.
.png)
Introducing Regal’s Voicemail Detection Model: How We Reduced Voicemails Routed to Agents by 45%
With Regal’s next-generation Voicemail Detection model, you can now classify voicemail, iOS or Google call screeners as separate categories with very high accuracy. This enables screener-specific handling, ultimately reducing missed agent connections.
.png)
September 2026 Product Recap
Last month, we shipped releases that make it easier to build, monitor, and test agents in one interface. Copilot Canvas brings building, editing, and testing into one interface and it can work straight from your files. Multi-state sticky notes let your team document decisions directly on a live agent.
.png)
.png)
August 2026 Product Recap
Last month, we launched features that extend your management of AI agents via MCP and CCaaS platforms. Debug based on agent versions or simulation runs, and manage AI analysis data points via Copilot and Regal MCP. As a Five9 AI Agent Connect partner, Regal now has a dedicated integration API built for Voice AI agents.
.avif)
.webp)
.webp)
.webp)
Dialing Compliance: How We Scaled Outbound Calling Reliably
Behind a fragmented and ever-changing regulatory landscape is a simple goal: protecting people from unwanted or poorly timed outreach and giving them control over how they’re contacted. In practice, that responsibility translates into a set of checks that must be validated.
.webp)
