AIToday
Large Language ModelsAI Business & IndustryAmazon AI BlogPublished: Jul 17, 2026, 01:00 JST

AWS builds AI phone host for restaurants using Bedrock and Nova 2 Sonic

AWS builds AI phone host for restaurants using Bedrock and Nova 2 Sonic

3 Key Points

  1. What happened

    AWS published a technical guide showing how to build a voice AI system that answers restaurant phone calls, takes orders, and books tables. The system uses Amazon Bedrock AgentCore to run the conversation logic, Amazon Nova 2 Sonic for speech processing, and connects to a restaurant backend through the Model Context Protocol. The full stack deploys via AWS CDK and bridges phone calls through a SIP gateway on Amazon ECS Fargate.

  2. Why it matters

    Restaurants miss an average of 150 phone calls per location every month, with about 60 percent of those being customers trying to place an order or book a table—calls that often come during dinner service when staff are busiest. This AI host can answer those calls without pulling workers off the floor, solving a problem that website or app ordering alone cannot address.

  3. What to watch

    The solution warms the agent session while the phone is still ringing to avoid dead air, and uses a microVM-per-call isolation model in AgentCore Runtime. A sample repository and deployment script are available on GitHub, with prerequisites including access to Amazon Nova 2 Sonic in Amazon Bedrock, Amazon Chime SDK PSTN Audio, and AgentCore Runtime availability.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The problem this solution addresses is concrete and widespread: restaurants lose business because they miss inbound calls during peak service hours, when answering the phone becomes logistically impossible. The article notes that approximately 60 percent of the 150 calls per location monthly are order or reservation requests—precisely the calls that represent lost revenue. Adding a website or mobile app helps customers who prefer to order online but does nothing for callers who prefer the phone, creating a gap that no single digital channel has closed.

The technical architecture reflects a deliberate design principle: separating the phone layer (SIP gateway, media handling), the agent layer (conversation logic and speech processing), and the restaurant backend (menus, orders, locations). This separation means the ordering logic is decoupled from the telephony channel, allowing the same agent and backend to serve multiple interfaces (phone, app, kiosk) without duplication. The use of the Model Context Protocol as an open standard between the agent and backend further enables the restaurant to change backend systems without redeploying the agent itself.

The system also solves a user-experience problem that is often overlooked: cold start latency. By warming the agent's microVM session while the phone is still ringing, the solution ensures the caller hears a greeting immediately, avoiding the awkward silence that would damage trust in an automated system. This detail reveals an understanding that voice ordering systems are sensitive to timing in ways web-based systems are not.

FAQ
What does the restaurant need to have in place to deploy this system?
An AWS account with Amazon Bedrock model access for Amazon Nova 2 Sonic, Amazon Chime SDK PSTN Audio access, Node.js 24.x or later, AWS CLI 2.x, git, and an AWS CDK bootstrap in the target account and region. The agent container itself is built with Python, but Python does not need to be on your machine since the build runs inside AWS CodeBuild.
How does the system avoid delays when a customer calls?
The system warms the agent session while the phone is still ringing, so the caller never hears dead air. When a call arrives, a Lambda function creates a session identifier and opens a connection to AgentCore Runtime to prepare the microVM before media streaming begins.
What happens if the restaurant wants to add a new ordering channel like a mobile app?
The backend logic stays independent from the phone channel. A new channel like a mobile app or kiosk can connect to the same agent and backend without rewriting the backend, because the agent communicates with the backend through the Model Context Protocol, an open standard for connecting agents to external tools.
Amazon AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAmazon-backed Anthropic seeks billions in new credit lines