Get to the right answer without searching through dead links.
Use public documentation for implementation questions, the status page for incidents, and the authenticated support center for workspace-specific issues.
Choose the right support path
Route visitors by the type of problem so sensitive account data is not submitted to a public form.
API and integration
Start with the API docs, Quickstart, errors, and webhook guides.
Platform status
Check the public status page before opening a ticket about a widespread outage.
Workspace issue
Sign in to the customer support center to create and track an account-specific ticket.
Sales or pre-purchase
Use the contact page for volume, pricing, and implementation discussions.
What to include in a support ticket
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.
Security and privacy issues
Use the organization’s configured security/privacy escalation process. Do not publish placeholder security email addresses until they are actually monitored.
Self-service before escalation
Link common issues to formatting, file format, rate-limit, webhook, and result-schema guides so users can solve predictable problems quickly.
Questions about support
Where do I report an account-specific problem?
Sign in and use the authenticated support center so the team can see your workspace context safely.
Where do I check for an outage?
Use the public status page.
Should I send my API key in a ticket?
No. Never include a secret API key or full sensitive dataset in a support message.
Where do I ask about enterprise pricing?
Use the public contact/sales page.
Related verification solutions
Explore related verification capabilities, documentation, and pricing.
See the job composition before you commit.
Start with a free preflight scan. Review duplicate counts, syntax formatting, cache eligibility, and the frozen maximum quote in integer micros.