User Journey: Admin Daily Dashboard Use
starter-chat
Persona: pastor-admin
Touchpoint: /admin/[token]
Preconditions
- Pastor has active subscription and logs in daily
- Church has been using chatbot/voice for 1+ weeks
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Log in to admin dashboard | Dashboard loads quickly (<2s). Greeting shows pastor name. Date/time visible. |
| 2 | Check message count today | Widget shows 'X messages today' with upward trend vs yesterday. Visual indicator of engagement. |
| 3 | View visitor contacts (recent) | Recent visitor/prayer request cards visible. Can quickly see who contacted church. |
| 4 | Check chatbot analytics | Charts show: messages per hour, top questions, sentiment. Actionable insights at a glance. |
| 5 | Review any prayer requests | Prayer requests flagged visibly. Can assign to prayer team or respond. |
| 6 | Check if any escalations pending | Critical/escalated messages highlighted. Human handoff needed shows with pastor/staff name. |
| 7 | Make quick adjustment (e.g. enable/disable chatbot) | Toggle visible and responsive. Change takes effect immediately. |
| 8 | Check notification badge | Unread messages/items count shown in dashboard nav. Easy to see what needs attention. |
| 9 | View help/documentation | FAQ or help link accessible from dashboard. Quick answers without leaving dashboard. |
Known Failure Modes
- Dashboard slow to load — pastor gives up
- No daily summary — admin can't tell if chatbot is working
- Escalations not highlighted — critical messages missed
- Analytics missing — admin flying blind
References
- Playwright spec:
e2e/journeys/admin-daily-dashboard.spec.ts - Code files:
Notes
Tests daily admin experience. Pastors check dashboard once a day during office hours. Need: quick summary of activity, recent contacts, escalations, ability to respond/adjust. Dashboard is the nerve center of the church's AI operations. Speed and clarity critical.