80 lines
2.7 KiB
Markdown
80 lines
2.7 KiB
Markdown
# Demo Showcase Runbook
|
|
|
|
Use this flow before showing the MVP to management.
|
|
|
|
## One-command prep
|
|
|
|
```powershell
|
|
powershell -ExecutionPolicy Bypass -File scripts\prepare_demo.ps1
|
|
```
|
|
|
|
What it does:
|
|
|
|
- starts the full local stack in the background
|
|
- clears local demo data before start
|
|
- runs the smoke check against `http://localhost:8080`
|
|
- seeds demo data for customers, interactions, integrations, KB, supervisor, KPI, and one sample recording
|
|
|
|
## What to open
|
|
|
|
- Operator UI: `http://localhost:8080/operator`
|
|
- Supervisor UI: `http://localhost:8080/supervisor`
|
|
- Admin UI: `http://localhost:8080/admin`
|
|
- Logs: `.local_stack\logs`
|
|
- Demo summary: `.local_stack\demo-seed-summary.json`
|
|
- Login: `admin / admin123`
|
|
|
|
## Demo sequence
|
|
|
|
1. Log in as `admin / admin123`.
|
|
2. Open the interactions list and show:
|
|
- one voice interaction already assigned, escalated, and closed
|
|
- one active follow-up interaction
|
|
3. Show that assign / escalate uses default values (`operator_a`, `line2`) without browser prompts.
|
|
4. Trigger the voice channel, Telegram, Webchat, and Email checks.
|
|
5. Search KB for `demo-showcase`.
|
|
6. Refresh the supervisor block and read the summary cards.
|
|
7. Refresh KPI and read the summary cards.
|
|
- the JSON payload also includes extended metrics and a `by_channel` breakdown
|
|
8. Open `/supervisor`, load `Recordings`, and show playback/download of the seeded sample.
|
|
9. Open `/admin`, load the seeded IVR flow, show the completed IVR session, and preview route override with `ivr_session_id`.
|
|
|
|
## Optional Telegram chat follow-up
|
|
|
|
If the Telegram bot env is configured:
|
|
|
|
1. Open `/operator`.
|
|
2. Go to the `Telegram` page in the sidebar.
|
|
3. Send one test message to the configured bot from a real Telegram client.
|
|
4. Show that:
|
|
- a persistent thread appears for that `chat_id`
|
|
- the linked interaction uses `channel="telegram"`
|
|
- the operator can claim the thread and reply from the same page
|
|
|
|
## Optional live voice follow-up
|
|
|
|
If the Asterisk lab bridge is enabled on a dedicated Linux VM:
|
|
|
|
1. Open `/operator`.
|
|
2. Choose the QA media path:
|
|
- browser softphone via `Browser Softphone`
|
|
- or external fallback via `MicroSIP/Zoiper`
|
|
3. Place one lab call from softphone `1001` to `7000`.
|
|
4. If using browser media, connect the browser softphone first and answer in Chrome/Edge.
|
|
5. Use the current voice baseline from `docs/runbooks/voice-baseline.md`.
|
|
|
|
## Optional separate shells
|
|
|
|
After the main management flow, you can open:
|
|
|
|
- `/supervisor` to show dedicated realtime and queue controls
|
|
- `/admin` to show separate user and queue management
|
|
|
|
## Stop after the demo
|
|
|
|
```powershell
|
|
powershell -ExecutionPolicy Bypass -File scripts\stop_all_local.ps1
|
|
```
|
|
|
|
For a short speaking script during the meeting, use `docs/runbooks/management-demo-brief.md`.
|