Customer Content Gaps
Some customer workflows need more product review before the help should describe them in exact detail.
Current Gaps
| Gap | What we explain now | What needs review |
|---|---|---|
| Public domain fallback behavior | Customers may enter through public marketplace links. | Exact fallback and unsupported-link behavior for every domain case. |
| Status labels | Statuses tell you whether a booking or subscription needs attention. | Final customer-facing labels for all payment, cancellation, refund, and renewal states. |
| Cancellation and refund policy detail | Options depend on eligibility, policy, timing, and payment state. | Exact policy copy and examples for each marketplace product type. |
| Auth provider errors | Sign in again, check the link, or contact support. | Provider-specific error messages and recovery steps. |
How To Use This Page
If a guide sends you here, the workflow exists but needs confirmation before we write exact public instructions. That is intentional. We would rather leave a clear gap than give wrong advice.
What Is Safe To Say Now
The first-version help can safely explain:
- where a customer starts
- what each customer page is for
- how to read a booking or subscription detail page
- why cancellation and refund options may depend on policy
- when to contact the operator
The first-version help should not invent:
- exact internal status names that are not confirmed in the customer UI
- refund outcomes
- provider-specific sign-in recovery steps
- hidden route fallback behavior
Review Needed Later
When screenshots are captured, review each customer guide again and check whether the visible labels match the text. If the product UI uses a different word than this help page, update the help page to match the UI.