How we support our partners — the process behind every request, how fast we aim to respond, and the hours we're here.
We treat every request as a tracked case and stay on it until it's resolved. Here's how our support works, in plain English — the process behind every request, the hours we're available, and the targets we hold ourselves to.
Every request becomes a tracked support ticket — nothing lives only in someone's inbox. Our support team is your first point of contact, and from there we route and escalate each case to the right team based on what it needs, keeping ownership until it's fully resolved.
Open a request by email, the contact form, or live chat. You'll get a confirmation that we have it.
We open a tracked ticket, set its priority, and confirm anything we need from you to move fast.
The case goes to the team that owns it — technical, billing, or onboarding — and is escalated as needed.
We fix it, explain what happened in plain language, and close the loop with you.
Audit1 sits between insurance carriers, agencies, and the businesses they insure. Knowing who to contact first gets your answer faster:
We partner directly with carriers and agencies. If you're an insured or employer, the fastest path is through your carrier or agency — and we work right behind them to get it solved.
Our support team is available during these hours, U.S. Eastern Time (ET):
| Monday – Friday | 9:00 AM – 5:00 PM ET |
| Saturday | 9:00 AM – 12:00 PM ET |
| Sunday | Closed |
We aim to acknowledge and resolve issues within the targets below. They're deliberately conservative — in practice we usually move faster.
| Priority | Examples | Initial response | Target workaround | Target resolution |
|---|---|---|---|---|
| P1 · Critical | Platform outage, payroll processing unavailable, or premium-calculation failures affecting multiple customers. | 30–60 minutes | 2–4 hours | 8–16 hours |
| P2 · High | A single carrier or agency unable to process policies, integration failures, or major functionality unavailable. | 2 business hours | 8 business hours | 2 business days |
| P3 · Medium | Reporting issues, isolated calculation errors with a workaround, or a non-critical feature malfunction. | 8 business hours | 2 business days | 4–10 business days |
| P4 · Low | Cosmetic issues, documentation requests, feature enhancements, or usability improvements. | 2 business days | — | Scheduled for a future release |
A few notes on the targets above: response times apply during our published support hours. Resolution times are targets and can vary with issue complexity, third-party dependencies, or customer-specific setups. Critical incidents receive immediate engineering attention and remain our top operational priority until mitigated.
Pick whatever's easiest — every channel opens a tracked ticket, so nothing gets lost:
Have a question or need a hand?
Contact Us