# Hotel Reception Assistant

> Compare rooms and plan a simulated hotel stay by voice.

Explore a fictional Boston hotel, compare rooms and review demo prices before confirming a simulated stay. The conversation does not create a real reservation or save booking records.

- Author: Agora
- Updated: 2026-11-12
- Guide language: unspecified
- Guide status: available
- Difficulty: Intermediate
- Categories: voice-ai
- Platforms: TypeScript
- Use cases: Hospitality, Voice AI
- Capabilities: Conversational AI, Voice Agent, Agora RTC, Next.js
- [Recipe page](https://recipes.agora.io/recipes/agora-hotel-reception-assistant-demo)
- [Implementation repository](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo)
- [Source recipe](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/RECIPE.md)
- [Raw source Markdown](https://raw.githubusercontent.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/main/RECIPE.md)
- [All recipes](https://recipes.agora.io/llms.txt)

## Use with Agora CLI

agora init my-agora-hotel-reception-assistant-demo --recipe agora-hotel-reception-assistant-demo

## Implementation guide

# Agora Hotel Reception Assistant Demo

## 1. Overview

Compare rooms, dates and demo prices at a fictional Boston hotel, then confirm a simulated stay. This first version is conversation-only with explicitly fictional simulation. No business data lookup, external tools, database, record writes, saved results, or cross-session business history are available. You may guide the configured simulated booking or trial enrollment and, only after explicit confirmation of the complete selection, say it is confirmed for this demo conversation. A simulated confirmation is an unsaved verbal recap, not a real reservation, inventory lock, submitted request, payment or external action. Do not invent an order number, confirmation code, email, callback or persistent record. Keep choices and corrections only in the current conversation. Never imply another session or a real business can retrieve this recap. Do not request passwords, verification codes, payment details or unnecessary personal identifiers.

## 2. Try the Demo

Run the app using [local setup](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/README.md#run-it). Choose `Talk to hotel reception`, allow microphone access and try:

- What time is check-in and breakfast?
- I am planning a family stay. Help me think through the room options.

Ask for a verbal recap before ending. Only the current page retains the transcript and session diagnostics; no business record is created.

## 3. Architecture & Tech Stack

The browser uses Agora RTC for audio and RTM for transcript and Agent events. Next.js only signs credentials and starts/stops the managed Agent. No business session, data API, local file store or persistent application database is required. Native Node.js, Docker and a Next.js-compatible serverless deployment use the same conversation flow. Actual hosted voice acceptance remains a separate check.

Next.js 16, React 19, TypeScript, agora-agents, Agora RTC/RTM and the adopted agent-ui components provide the existing voice lifecycle.

## 4. Prerequisites & Configuration

Use Node.js 22+, pnpm 9.15.9 and an Agora project with RTC, Signaling and Conversational AI. Configure `env.local.example` in `.env.local`.

| Variable | Required | Exposure |
| --- | --- | --- |
| `NEXT_PUBLIC_AGORA_APP_ID` | Yes | Public; build and runtime |
| `NEXT_AGORA_APP_CERTIFICATE` | Yes | Server runtime only |

The default managed pipeline needs no vendor key. Business-tool origins and business-storage variables are not used.

## 5. Quick Start

~~~bash
pnpm install --frozen-lockfile
pnpm run doctor
pnpm run dev
~~~

Create .env.local from env.local.example only when absent, fill the two required values, and open http://localhost:3000. Keep existing credentials when reusing a checkout.

## 6. How It Works

The start action requests a combined RTC/RTM token and starts the managed Agent with only requester_id and channel_name. The assistant follows lib/agent-config.ts. No business session is created before voice startup, and legacy tool environment variables cannot enable business operations.

See [current capabilities](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/README.md#what-you-can-do) for the conversation boundary and [verification guidance](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/AGENTS.md#verification-and-maintenance) for checks.

Each session ends automatically after 10 minutes; choose Start again to continue.

## 7. Customize for Your Business

Edit lib/agent-config.ts for the role, workflow, greeting and static public reference material. Edit lib/presentation.ts for the scenario entry and visible identity. Keep lib/runtime-profile.ts aligned with the invite route. Adding business integrations is outside this first version.

## 8. Deployment & Validation

Follow [deployment instructions](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/README.md#deployment). Run pnpm run verify; run pnpm run verify:docker separately when checking the container. Supply the public App ID at build and runtime and keep the App Certificate server-only.

Mocked startup and build checks do not establish real speech quality or hosted connectivity. Verify actual two-way speech, transcript, interruptions, error handling and clean stop with real project credentials.

## Usage FAQ

Choose FAQ in the header to read scenario-specific usage answers in a right-side drawer. It is available before starting a conversation and does not start a session.


## Phase-one conversation update — 2026-11-08

Compare rooms, dates and demo prices at a fictional Boston hotel, then confirm a simulated stay. This first version is conversation-only with explicitly fictional simulation. No business data lookup, external tools, database, record writes, saved results, or cross-session business history are available. You may guide the configured simulated booking or trial enrollment and, only after explicit confirmation of the complete selection, say it is confirmed for this demo conversation. A simulated confirmation is an unsaved verbal recap, not a real reservation, inventory lock, submitted request, payment or external action. Do not invent an order number, confirmation code, email, callback or persistent record. Keep choices and corrections only in the current conversation. Never imply another session or a real business can retrieve this recap. Do not request passwords, verification codes, payment details or unnecessary personal identifiers.

See [current capabilities](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/README.md#what-you-can-do), the [conversation contract](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/ARCHITECTURE.md#conversation-behavior) and [verification guidance](https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/blob/main/AGENTS.md#verification-and-maintenance). Tools remain disabled, and no persistent business operations are provided.


## Recipe prompt

Help me create and run the Hotel Reception Assistant using Agora CLI.

Check that Agora CLI is installed and ready. If installation or an upgrade is needed, ask before proceeding. Guide me through browser login when required.

Get the recipe details:
agora recipes show agora-hotel-reception-assistant-demo --json

Read its implementation guide:
https://raw.githubusercontent.com/AgoraIO-Community/agora-hotel-reception-assistant-demo/main/RECIPE.md

Reference source:
https://github.com/AgoraIO-Community/agora-hotel-reception-assistant-demo

Before initialization, confirm which Agora project to use. Ask before creating a new Agora project.

Initialize the app in a new or empty directory. Replace <confirmed-project-id> with the actual ID of the project confirmed above before running:
agora init my-hotel-app --recipe agora-hotel-reception-assistant-demo --project <confirmed-project-id> --json

Let the CLI configure the credentials. Never print the App Certificate in chat or expose it in browser code.

Follow the returned nextSteps to install dependencies and start the app. Help diagnose and resolve any errors.

Provide the local URL and guide me through microphone access. Help me test this request:
"What time is check-in, and what facilities does the hotel offer?"

Report what was verified and what still needs testing. Follow the capabilities and limits in the implementation guide; do not claim external actions were completed without verification.
