Use public documentation for implementation questions, the status page for incidents, and the authenticated support center for workspace-specific issues.
Route visitors by the type of problem so sensitive account data is not submitted to a public form.
Start with the API docs, Quickstart, errors, and webhook guides.
Check the public status page before opening a ticket about a widespread outage.
Sign in to the customer support center to create and track an account-specific ticket.
Use the contact page for volume, pricing, and implementation discussions.
Provide the phoneveriflo job/request ID, approximate timestamp, service name, expected behavior, and a redacted example. Do not paste API secrets, full production datasets, or upstream provider details.
Use the organization’s configured security/privacy escalation process. Do not publish placeholder security email addresses until they are actually monitored.
Link common issues to formatting, file format, rate-limit, webhook, and result-schema guides so users can solve predictable problems quickly.
Sign in and use the authenticated support center so the team can see your workspace context safely.
Use the public status page.
No. Never include a secret API key or full sensitive dataset in a support message.
Use the public contact/sales page.
Use descriptive internal links so users and search engines can understand how these topics connect.
Start with a preflight, review duplicates, cache eligibility, fresh checks, and the frozen maximum quote.