Support and operations model
How Lovely Home Hub is operated when the platform is sold to households — not a customer-facing page. Use this with the Customer hub playbook and Platform admin.
Roles
| Role | Typical person | Access | Responsibilities |
|---|---|---|---|
| Platform operator | You / small ops team | Cloudflare Access (platform admin, ops handbook, marketing if gated), GitHub, Stripe Dashboard | Provision hubs, billing overrides, Terraform, CI, incident response |
| Support | Future hire or contractor | Platform admin (limited), ops handbook, Stripe (read/refund as policy allows) | Account lookup, resend emails, guide customer through owner UI, escalate infra |
| Customer (owner) | Paying household | Their hub hostname + Account | Onboarding wizard, billing portal, backup/restore, house guide content |
| Guest / sitter | Invited by owner | Hub Access (email OTP) or demo password on demo only | Read house guide, controls as configured — no platform admin |
Operators are managed under Platform settings → Site access → Platform operators on the platform admin. Support staff should not be added there unless they need full platform admin and infrastructure access.
What customers can self-serve
Documented on the marketing site Help and inside the hub Settings:
- Change billing via Stripe Customer Portal (linked from Account)
- Download full site backup and factory reset (hub Settings)
- Edit house guide, bins, contacts, Wi‑Fi in the owner UI
- Cancel subscription (Stripe) → automated billing deprovision pipeline (see Platform billing)
Support should default to sending owners to in-app flows before running platform workflows.
What operators run (GitHub Actions)
| Scenario | Workflow / doc |
|---|---|
| New paid signup (happy path) | Hosted provision via hub-jobs → public orchestrator; registry via Platform site registry — Hub provision public setup |
| Wizard create/edit/delete site | Platform site manage → PR → merge |
| Site removed from registry (auto) | Platform site deprovision on push to main |
| Infra left after registry gone | Manual Platform site deprovision with use_github_hosted — Platform provision |
| Stripe cancel / delete | Platform site billing deprovision |
| Redeploy worker only | Platform site deploy |
| Platform admin / marketing infra | Platform admin Terraform |
| Stuck signup / abuse | Signup abuse protection, platform admin health |
Always check platform admin → Sites for registry_last_error, provision_last_error, and billing state before re-running destructive workflows.
Support escalation ladder
- Owner UI — backup, reset, billing portal, setup wizard re-run.
- Platform admin — site row, resend email, read-only health, marketing copy (not infra).
- GitHub Actions — retry provision/deprovision, manual dispatch with explicit
site_id(document run URL in ticket). - Terraform / Cloudflare dashboard — DNS, Access policy, rate limits; prefer scripted changes via PR + apply workflow.
- Data recovery — Site backup & archive; R2 archive from billing deprovision before teardown.
Communication norms
- Customer-facing tone lives on lovely-home.co.uk and in transactional email templates (Resend).
- Internal runbooks use direct language and link to workflows by file name in this repo.
- After an incident, update the relevant
docs/*.mdpage and merge tomainso this handbook stays truthful.
Lovely Finance (later)
Finance will get its own ops section when the product is packaged for sale. Expect a smaller surface: one app, fewer moving parts than multi-tenant hubs. This handbook will gain a Finance nav group; until then, treat Finance as out of scope here.
Related
- Customer hub playbook — practice run and first real customer
- Platform billing — webhooks and deprovision chain
- Grafana dashboards — Social Insights, Stripe Billing, AI usage
- CI runner strategy — why jobs queue on
lovely-home - Demo hub — public demo; not a customer template