Skip to main content

User Journey: Denomination-Specific Content Quality

non-critical   Property: ChurchWiseAI   Category: UX / Flow Tier: starter-chat Persona: pastor-evaluator Touchpoint: /ai-for/[denomination]

Preconditions

  • Pastor finds ChurchWiseAI via Google search for their denomination
  • Landing page at /ai-for/[denomination] exists (Baptist, Catholic, Pentecostal, etc.)

Steps

#ActionExpected Result
1Navigate to /ai-for/baptist landing pagePage loads with Baptist-specific heading. Content uses Baptist language (scripture, faith, believer, gospel, congregation). No Catholic sacramental terms appear.
2Navigate to /ai-for/catholic landing pagePage loads with Catholic-specific heading. Content uses Catholic language (mass, sacrament, tradition, liturgy, parish). No Protestant altar-call language appears.
3Verify denomination pages have working CTAsCall-to-action links present to pricing or onboard. At least one 'Get Started' button visible.
4Navigate to invalid denomination slug (e.g. /ai-for/this-does-not-exist)Returns 404 error. Page does not crash with 500.
5Visit /ai-for index pageIndex shows links to available denomination pages. At least 3 denominations listed.
6Verify CTA language matches denominationBaptist page CTA says 'for Baptist churches'. Catholic page CTA says 'for Catholic parishes'. Denomination-specific copy is present.

Known Failure Modes

  • Baptist page shows Catholic language — confuses pastor
  • Invalid denomination crashes with 500 — poor user experience
  • Index page missing denomination links — pastors can't find their tradition
  • Generic copy on all pages — loses denomination personalization advantage

References

Notes

Tests that denomination landing pages deliver authentic, denomination-specific content rather than generic copy. Critical for relevance in niche vertical markets. Pastor should feel understood and see their language/theology reflected back. Validates the landing page strategy: every pastor sees their tradition represented.