> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot Voice AI

> Fix the two most common Voice AI failures: a number that rings with dead air and isn't answered, and calls that don't create a PSA ticket. Includes the required settings and a step-by-step checklist.

<Note>
  See the latest **Voice AI** updates in the [changelog](/changelog/q3-2026).
</Note>

Two Voice AI problems account for most support requests: a number that **rings but is never answered**, and calls that connect but **don't create a PSA ticket**. Both are almost always a configuration or PSA-data issue you can fix yourself. Work through the relevant section below before contacting Thread Support.

## The number rings with dead air and isn't answered

When a call rings endlessly with no answer and **no call record is created**, the agent could not start. The usual cause is missing defaults.

**Check first — required agent settings:**

* **Default company and default contact must both be set** in the agent's general settings. If either is missing, the agent cannot proceed, the line rings with no answer, and no call record appears. The Voice admin shows a warning when these are missing. Setting both fixes it — missing defaults have caused multi-day silent outages that look like an outage but are a config gap.
* **The agent must be Active.** Set the agent to Active before testing so behavior is reliable.

<Warning>
  A missing default company or default contact produces silent failure — the caller hears dead air and nothing is logged. Always confirm both are set after any change to the agent or your PSA.
</Warning>

## Calls connect but no PSA ticket is created

If the agent answers and handles the call but no ticket appears in your PSA, check these in order — the first match is usually the cause:

<Steps>
  <Step title="PSA and board configuration">
    Confirm the agent's default status and default team are set, that the target company is allowed to create Service Tickets, and that any "disallow tickets" setting for the company or board is turned off.
  </Step>

  <Step title="PSA credentials">
    Stale or invalid PSA credentials cause authentication failures (401 errors) when Thread tries to write the ticket. Re-authenticate the PSA integration in Settings → Integrations.
  </Step>

  <Step title="Validation errors">
    A malformed or missing required field blocks ticket creation — most commonly a **default contact that was deleted in the PSA**. Reselect a valid default contact and re-sync.
  </Step>

  <Step title="PSA rate limiting">
    A burst of activity can hit your PSA's rate limit (429 errors), which drops the write. This usually clears on its own; if it recurs, review other automations writing to the PSA at the same time.
  </Step>

  <Step title="Thread runtime errors">
    If none of the above applies, collect the **call link**, the expected **ticket link**, and any banner shown in the Voice admin, then contact Thread Support with those details.
  </Step>
</Steps>

<Tip>
  After correcting any PSA data (contacts, companies, credentials), re-sync in Settings → Integrations so Voice AI has the latest information.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Voice AI contact mapping" icon="address-book" href="/ai-agents/contact-mapping">
    Troubleshoot caller identification and contact-mapping failures.
  </Card>

  <Card title="Voice AI FAQ" icon="circle-question" href="/ai-agents/voice-ai-faq">
    Common Voice AI questions and answers.
  </Card>
</CardGroup>


## Related topics

- [Voice AI FAQ](/ai-agents/voice-ai-faq.md)
- [Voice AI Contact Mapping](/ai-agents/contact-mapping.md)
- [Voice AI SIP Trunks & Caller ID](/ai-agents/voice-ai-sip-trunks-and-caller-id.md)