UniCourt customer service number — how to find and use support effectively

Overview: UniCourt support channels and what to expect

UniCourt is a court-data and legal-analytics platform used by attorneys, legal tech teams, and investigators. The company prioritizes digital support channels — in-app chat, a contact form on their website, and dedicated account managers for enterprise clients — rather than a public, universally listed support phone line. Because access methods change as products evolve, the most reliable single source for current contact options is the company website at https://unicourt.com and the account dashboard after you log in.

For quick resolution of typical issues (account access, billing, basic data questions), expect initial responses within one business day for standard accounts and within a few hours for paid or enterprise plans. Enterprise customers and API partners commonly receive direct phone and Slack/Teams/Zoom escalation paths and a formal service-level agreement (SLA) that specifies response windows and escalation matrices.

Where to find an official UniCourt customer service number

If UniCourt provides a phone number for your account, it will usually be surfaced in three places: the public Contact/Support page on the website, the footer or help center within the logged-in application, and the welcome/onboarding email you received after subscribing. If you cannot find a phone number on the public site, check the “Help,” “Support,” or “Contact” link in the top navigation after logging in — most SaaS companies show direct-line information only to authenticated users or to enterprise contacts.

If you are an enterprise user, your sales or onboarding representative will supply a direct phone line and escalation contacts (name, extension, and hours). Smaller accounts typically receive phone support only on an as-needed basis and are encouraged to use the in-app ticketing system to preserve ticket history and include attachments such as case screenshots, docket IDs, or API logs.

How to prepare before calling or opening a ticket

Preparation cuts resolution time dramatically. Whether you plan to call, use chat, or submit a ticket, gather the following items so the support agent can reproduce and resolve the issue quickly: your account name and subscription ID, the exact court name(s) and case/docket number(s) you are referencing, timestamps of when the problem occurred, and any error messages or API request/response excerpts. If the problem is billing-related, have invoice numbers and the last four digits of the payment method ready.

Organize technical artifacts: browser version and operating system, the API token and request ID (never paste your full secret; give support a request ID to locate server logs), a short step-by-step description to reproduce the issue, and 1–3 annotated screenshots or a short screen recording (30–90 seconds). For bulk-processing issues, include expected record counts and CSV samples so support can run a controlled test without exposing unnecessary personal data.

Typical response times, SLAs, and escalation steps

While UniCourt’s exact SLA depends on your contract, industry-standard expectations are useful benchmarks: initial acknowledgment within 4–24 hours; triage and assignment within 1 business day; and resolution timelines that vary by issue complexity — from minutes for login resets to days for data-coverage corrections or engineering-level API bugs. Enterprise contracts frequently specify an escalation path with defined time windows (for example: Level 1 support within 4 hours, Level 2 within 8–12 hours, and engineering engagement within 24 hours).

If you need to escalate, follow a documented track: first open or update the existing ticket with the priority flag, then contact your account manager or designated enterprise phone/Slack channel if available, and finally request an internal incident brief or a conference call with engineering if the issue impacts production workflows. Keep ticket numbers and timestamps in each message — this ensures a clear audit trail for billing disputes, data corrections, or compliance reviews.

Common issues and practical fixes to try before contacting support

Many user-reported problems have fast self-serve fixes: password resets, CAPTCHA or 2FA lockouts, browser-cache issues, and permission settings for shared accounts are typically resolved in minutes. For API consumers, check rate-limit headers, verify your API token status in the dashboard, and compare the request timestamp to the server time; mismatched clocks or expired tokens are frequent causes of 401/429 responses.

For data-specific problems (missing dockets, incomplete case history, or sealed-record questions), collect exact identifiers and time windows before contacting support. Large exports and bulk downloads can be slow due to queueing; if you plan a one-time large pull (10,000+ rows), notify support with the intended timeframe — they can sometimes adjust throttles or recommend a snapshot/export method that reduces overall wall-clock time to completion.

Actionable contact checklist

• Before contacting: account name, subscription ID, case/docket numbers, timestamps, and one-sentence problem summary.
• Technical artifacts: browser/OS, API token (use request IDs not full secrets), exact error codes and full response bodies, screenshots or a 30–90s screen capture, and sample CSV if relevant.
• Escalation: ticket number, business impact statement (e.g., “production outage affecting 3 users since 09:12 ET”), requested resolution timeframe, and account manager contact if available.