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

# Getting help

> Where to look first, and how to reach us so we can help quickly.

Most questions are answered faster by looking in the right place than by waiting on a reply. Here's the order worth trying.

## Check these first

<CardGroup cols={2}>
  <Card title="The agent said something wrong" icon="comment-slash" href="/receptionist/call-logs">
    Read the transcript. Wrong facts are almost always a gap in your [knowledge base](/receptionist/knowledge-base) or [business profile](/receptionist/business-profile), not a fault in the agent.
  </Card>

  <Card title="Texts aren't sending" icon="comment-sms" href="/phone/a2p-10dlc">
    Nearly always A2P 10DLC registration still pending or rejected. Voice works before A2P is approved; SMS doesn't.
  </Card>

  <Card title="Bookings aren't reaching my calendar" icon="calendar-xmark" href="/booking/calendars">
    Check the integration's last sync time, and confirm you have exactly one source of availability connected.
  </Card>

  <Card title="An API call is failing" icon="code" href="/api-reference/errors">
    The status code tells you which of the four usual causes it is — auth, permission scope, malformed field, or rate limit.
  </Card>
</CardGroup>

## Contact us

Email [info@recepta.ai](mailto:info@recepta.ai).

To get a useful answer on the first reply rather than the third, include:

<Steps>
  <Step title="Your workspace name">
    We can't look anything up without it.
  </Step>

  <Step title="What you expected, and what happened">
    Both halves. "The agent didn't book" is a symptom; "I asked for Thursday morning and it offered next week" is something we can trace.
  </Step>

  <Step title="A specific example">
    A call ID, a phone number and rough time, a contact, or the exact request and response for an API problem. One concrete case beats a general description.
  </Step>

  <Step title="When it started">
    And whether anything changed around then — a plan change, a new integration, an edit to your agent.
  </Step>
</Steps>

<Warning>
  Never send us an API key, a password, or a customer's card details. If you think a key has been exposed, revoke it from **API keys** first, then tell us. See [Authentication](/api-reference/authentication).
</Warning>

## Something urgent

If calls aren't being answered at all, check first whether your number still forwards to Recepta.ai and whether your subscription is current — a failed payment eventually suspends service. See [Phone numbers](/phone/numbers) and [Billing](/account/billing).

Then email us with **urgent** in the subject and your workspace name.

## Security

Report a suspected vulnerability to [info@recepta.ai](mailto:info@recepta.ai) with reproduction steps. Please don't test against other customers' workspaces or use live customer data. See [Security & privacy](/account/security-and-privacy).