No public form, ticket tool, or support mailbox is connected in the current prototype.
Support Intake Boundary
WeAcuRe should publish a support route before live checkout, forms, email updates, or member access. The current prototype has no support form, no ticket endpoint, and no public inbox connection.
Current status
First support should cover access, payment, refund, unsubscribe, deletion, and privacy requests.
Support should ask only for the information needed to route the request.
Allowed first fields
- Email address for reply and access matching.
- Request type: access, payment, refund, unsubscribe, deletion, privacy, or general support.
- Order or provider reference only after live checkout exists.
- Short message limited to the support issue.
- Preferred language or market only when needed for routing.
Blocked intake fields
- Do not ask for birth date, birth time, chart output, palace labels, star labels, or private study notes.
- Do not ask for identity documents, payment card data, passwords, recovery codes, cookies, or provider secrets.
- Do not ask users to upload screenshots that include sensitive chart input or account details by default.
- Do not route medical, legal, financial, relationship, or psychological requests into product support.
Before support intake is live
- Choose one support channel and document owner, response scope, retention, and deletion handling.
- Update Contact, Privacy, Terms, Refund, Payment Readiness, and Email Consent Boundary.
- Keep support records separate from campaign events, chart input, payment credentials, and private notes.
- Run static checks before adding a form action, support provider, or email provider.
Related pages
Review Contact, Support Readiness, Payment Readiness, Delivery Readiness, Refund Policy, Email Consent Boundary, Policy Review Readiness, Privacy Boundary, and Terms before enabling support intake.