Support should be visible before a user gets stuck. In this template, support is part of the public trust surface and part of the signed-in product flow.
Public support surfaces
- Header navigation should expose a support entry
- Footer should expose a contact email
- Docs should explain refunds and help expectations in plain language
Signed-in support surfaces
/dashboard/ticketsfor product and account help/dashboard/ordersfor purchase history and refund requests/dashboard/subscriptionfor plan status before contacting support
Refund guidance
Refund handling should be predictable:
- explain when users should request refunds
- point them to the correct ticket flow
- keep plan and order information easy to inspect before they contact you
What to customize before launch
contactEmailinzship.app.json- support copy in pricing, docs, and dashboard pages
- internal process for ticket response times and refund review