General support
Website questions, care-plan requests, launch details, or where to find something.
Start requestSupport center
One front door for website buildout and care questions.
Support stays organized around the work: website updates, form checks, onboarding, billing, access, care-plan requests, and urgent launch issues.
Request types
Send the issue to the right lane.
A clear support path keeps website requests from living in scattered texts, inboxes, and memory. Each request should have a type, priority, and useful context.
Onboarding
Website assets, domain/hosting, safe access, launch checklist, forms, and calendar setup.
Open onboardingBilling and account
Invoices, monthly care, business details, and account contact changes.
Ask billingWebsite or form issue
Form did not route, a page looks wrong, hosting needs review, or a website edit needs attention.
Report issueClient visibility
Support should be easy to inspect too.
The client-facing support lane needs current state, owner, next step, and whether something needs attention.
Form path connected. Waiting on one sample submission before launch QA.
Need destination inbox, expected owner, and launch expectation before scope is confirmed.
Need approved review copy and placement before the page update goes live.
Submit details
Start with context, not a scavenger hunt.
This form tries the support queue first. If the backend bridge is not available, it falls back to a prepared email so the request still moves.
Client portal
Want a simple place to see website requests?
The client preview shows how website requests, onboarding, launch status, and care notes can live together.