> ## 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.

# Chat widget

> Website chat that answers from the same knowledge as your phone agent.

The chat widget puts your agent on your website. It answers from the same [knowledge base](/receptionist/knowledge-base) as the phone agent and can qualify and book in the same way — so a visitor who won't call still gets handled.

## Installing it

Generate the embed snippet under **Chat widget** in the dashboard, then paste it into your site.

<Warning>
  Copy the snippet from your dashboard rather than writing one by hand — it carries your workspace identifier and current widget settings.
</Warning>

Where it goes, by platform:

| Platform    | Where to paste                                                     |
| ----------- | ------------------------------------------------------------------ |
| Custom site | Immediately before the closing `</body>` tag in your page template |
| WordPress   | A header-and-footer scripts plugin, into the footer box            |
| Squarespace | Settings → Advanced → Code Injection → Footer                      |
| Wix         | Settings → Custom Code → Add to Body – end                         |
| Webflow     | Project Settings → Custom Code → Footer Code                       |

The snippet loads asynchronously and doesn't block page rendering.

## Voice parity

Chat and voice share configuration. The same services, prices, hours, and FAQs drive both, so a visitor who asks about a call-out fee in chat gets the same number they'd get on the phone. Update the knowledge once and both channels follow.

The differences are practical rather than behavioral:

|         | Voice                                 | Chat                                         |
| ------- | ------------------------------------- | -------------------------------------------- |
| Pace    | Caller sets it, answers must be short | Visitor may take minutes between messages    |
| Detail  | Keep it to a couple of sentences      | Can include links, lists, and longer answers |
| Handoff | Warm transfer to a person             | Escalate to a human or collect a callback    |

## Getting value from it

<Columns cols={2}>
  <Card title="Put it on the pages that matter" icon="file">
    Service pages and pricing pages, not just the homepage. Visitors ask where they're deciding.
  </Card>

  <Card title="Aim at a booking" icon="calendar-check">
    A chat that ends in a scheduled visit is worth many that end in "thanks". Configure it to offer booking, not just answers.
  </Card>
</Columns>

## Reviewing chats

Chat threads appear in the dashboard alongside call logs, with the full exchange and any contact created. Read them the same way you read transcripts — questions the agent handled badly are gaps in your knowledge base. See [QA & learning](/receptionist/qa-and-learning).

## Metering

Chat is billed per conversation from the same pool as [SMS](/channels/sms). See [Plans](/plans).