Support
Support pages collect the recurring questions, symptom-first troubleshooting trees, and recovery recipes that don't naturally belong in the user guide or platform sections.
When to use which section
| You are… | Start with |
|---|---|
| a tenant user | Troubleshooting → For users — test calls, microphone, audio quality, missing conversations. |
| a team admin | Troubleshooting → For team admins — flows not publishing, tools failing, API keys, invites, billing. |
| a platform admin (tenant) | Troubleshooting → For team admins plus the User guide → For platform admins section. |
| a platform operator | Troubleshooting → For operators and the per-service runbooks under Platform → Operations. Use Recovery recipes when something is broken in production. |
If you just want a quick answer to a common question, check the FAQ first.
How this section is organised
- FAQ — short answers to the questions we hear most often, grouped by audience.
- Troubleshooting — symptom → likely cause → check trees, scoped to a single audience per page.
- Recovery recipes — operator-focused playbooks for restoring a broken environment (rotate secrets, redeploy a service, regain superuser access, restore Postgres).
- Getting help — what to attach when you file a support request so the back-and-forth is short.
What's not here
- Local development for the Delphi platform itself is not documented on this site. Platform source is not public; only the client SDK is.
- Per-service deep dives stay in Platform → Operations — Support links out to them rather than duplicating.
- Step-by-step product walkthroughs stay in the User guide. Support assumes you've already found the feature and something is wrong with it.