Access before explanations
If a person paid and did not receive the scroll, do not start with philosophy. Restore access or confirm payment status first.
operator room
OmenHall support without panic and smoke
This section gathers internal support playbooks: lost links, refunds, payment issues, privacy, incident log, first 30 days, and ready client replies.
Access
Refund
Privacy
Incident
Do not litigate emotion
A client may be angry not because they are technically right, but because the path broke at a vulnerable moment. Support should lower the heat first.
Less internal magic
Webhook, hash, job id, provider error, and cost cap are for the team. The client usually needs three things: what happened, what you are doing, when access returns.
Every repeated failure becomes a playbook
If the same issue happens twice, it needs a reply template, a check checklist, and an incident log entry.
support playbooks
What to do when real people knock
Lost-link workflowHow to restore scroll access without exposing private data.Refund reviewHow to review refunds without dispute, fear, or chaos.Payment issueDuplicate charges, webhook delay, checkout cancel, and receipt.Privacy deletionDeletion, export, access, and identity confirmation requests.Incident logA single log for bugs, payment failures, emails, and AI errors.First 30 daysWhat to watch daily after launch while the site learns to breathe.Support macrosReady client replies without cold corporate stone.Escalation matrixWhen to reply yourself, stop ads, or escalate to Stripe/Supabase/Vercel.Launch diaryDiary of first signals: complaints, clicks, payments, emails, returns.