Persona: Mark — Mega Church IT Director
starter
Persona: mark-mega-church-it
Touchpoint: /admin/[token], /api/docs
Preconditions
- Visitor is IT director at 2000+ member church
- Evaluating how ChurchWiseAI integrates with existing church stack
- Cares about API reliability, webhook delivery, integration depth
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Check for API documentation | API docs accessible at /api/docs or docs.churchwiseai.com. RESTful endpoints documented with curl/code examples. |
| 2 | Look for integration examples | Examples for Planning Center, RightNow/Breeze, Slack, email provided. Sample webhook payloads visible. |
| 3 | Check webhook delivery reliability | Webhook retry logic documented. Guaranteed delivery claim and SLA if applicable. Webhook testing tools available. |
| 4 | Search for authentication options | API key and OAuth2 options documented. Token management (refresh, revocation) clear. |
| 5 | Look for rate limiting | Rate limit documented (requests/sec, daily quota). Explains how to handle throttling. |
| 6 | Check data export capabilities | API allows bulk export of chatbot messages, contact data, visitor history. Format (JSON, CSV) documented. |
| 7 | Verify webhook signature validation | How to verify webhook authenticity documented. HMAC-SHA256 or similar signing explained. |
| 8 | Look for monitoring/logging | Dashboard shows webhook delivery status. Failed delivery alerts/notifications available. |
| 9 | Check integration support | Support channel (email, Slack) documented. Response time for integration issues stated. |
Known Failure Modes
- No API documentation — Mark can't integrate
- Webhook delivery unreliable — data syncing breaks
- Rate limits too restrictive — integration fails under load
- No data export option — Mark locked into ChurchWiseAI UI
- Webhook failure silent — integration breaks unnoticed
References
- Playwright spec:
e2e/delivers/personas/mark-mega-church-it.spec.ts - Code files:
Notes
Mark manages complex church tech stack (Planning Center, Slack, Breeze, etc). Needs: well-documented APIs, reliable webhooks, integration examples, good error handling/logging. A product without good APIs is a walled garden to Mark. Lifecycle tests don't cover this — they don't need integrations.