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

# Getting help

> What to check first, and how to reach us when it is not something you can fix.

Most of what looks like a fault is something you can settle in a minute. This page covers those first, then how to reach us.

***

## Check these first

<AccordionGroup>
  <Accordion title="She says she doesn't know something she should know">
    The answer is not in her library, or it is there in words no guest would use.

    Open [Chat History](/ai-manager/analytics/chat-history), find the conversation, and read how the guest actually asked. Then add or reword the document in [Training](/ai-manager/training/overview).
  </Accordion>

  <Accordion title="She gives an out-of-date answer">
    A document still says the old thing. Search your library for it and use **Replace File** rather than uploading a second version — otherwise both answers stay in there.
  </Accordion>

  <Accordion title="Her tone isn't right">
    Edit her identity in [Profile](/ai-manager/receptionist/profile) and publish again. Editing the personality text directly on the Chat or Voice screen is the exception, not the normal route.
  </Accordion>

  <Accordion title="The widget isn't showing on our website">
    Check the code is still on the page, and that your domain is in the allowed list on the [Widget](/ai-manager/widget) screen. A site rebuild sometimes drops the code.
  </Accordion>

  <Accordion title="A guest reached a dead end">
    Check **Connect to Staff** on the [Chat](/ai-manager/receptionist/chat) and [Voice](/ai-manager/receptionist/voice) screens. If no contact is set there, she has nowhere to send a guest who needs a person.
  </Accordion>

  <Accordion title="Something says it needs attention">
    That wording means it was bought but is not working. The card or banner says what is missing. If it does not make sense, that is worth writing to us about.
  </Accordion>
</AccordionGroup>

***

## Writing to us

<Card title="support@hotellinkage.com" icon="envelope" href="mailto:support@hotellinkage.com">
  Tell us your hotel name and what you were doing when it happened.
</Card>

What makes it quick to solve:

* **Which screen** you were on
* **What you expected** and what happened instead
* **When** it happened, roughly — it helps us find the conversation
* **A guest example**, if it was a conversation that went wrong

<Tip>
  **Do not send us a guest's personal details.** The hotel name and roughly when it happened is enough for us to find it.
</Tip>