# Event Reminder Assistant

> Review a fictional webinar and discuss attendance by voice.

Role-play an event reminder, ask about the schedule and agenda, and revise your attendance intention. This conversation-only demo does not register attendees or send reminders.

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

## Use with Agora CLI

agora init my-agora-event-reminder-assistant-demo --recipe agora-event-reminder-assistant-demo

## Implementation guide

# Agora Event Reminder Assistant Demo

## 1. Overview

Hear a reminder for a fictional webinar, review its schedule and say whether you plan to attend. This first version is conversation-only. No business data lookup, external tools, database, record writes, saved results, or cross-session business history are available. Keep details in the current conversation. Do not claim a real registration, reminder, survey submission, callback, payment or saved result. Do not request secrets or unnecessary personal identifiers.

## 2. Try the Demo

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

- What is the webinar about?
- I am not sure I can attend. Help me review my 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-event-reminder-assistant-demo/blob/main/README.md#what-you-can-do) for the conversation boundary and [verification guidance](https://github.com/AgoraIO-Community/agora-event-reminder-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-event-reminder-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

Hear a reminder for a fictional webinar, review its schedule and say whether you plan to attend. This first version is conversation-only. No business data lookup, external tools, database, record writes, saved results, or cross-session business history are available. Keep details in the current conversation. Do not claim a real registration, reminder, survey submission, callback, payment or saved result. Do not request secrets or unnecessary personal identifiers.

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

## Demonstration event dates

The event schedule is generated when each conversation starts: the following New York calendar day, from 2 to 2:45 PM Eastern. `lib/scenario-knowledge.ts` computes exact dates and U.S. time-zone conversions using the event date’s DST offset. The generated schedule is held fixed within that conversation. A later conversation gets a fresh future date; no real event is rescheduled and no reminder is saved.


## Recipe prompt

Help me create and run the Event Reminder 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-event-reminder-assistant-demo --json

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

Reference source:
https://github.com/AgoraIO-Community/agora-event-reminder-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-event-app --recipe agora-event-reminder-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:
"Walk me through a practice event reminder and attendance confirmation."

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.
