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

# Chat in FareHarbor

> How FareHarbor booking conversations work in the AI chat widget, WhatsApp, and SMS channels.

<Warning>
  Before using FareHarbor in chat, make sure your [chat agent is set up](/widget/introduction) and [FareHarbor is connected](/integrations/fareharbor/connect).
</Warning>

## How booking conversations work in chat

When a customer starts a booking conversation in any text-based channel — web widget, WhatsApp, or SMS — the AI follows the same structured flow.

```mermaid theme={"dark"}
flowchart LR
    A[Customer message] --> B[AI lists matching tours]
    B --> C[AI checks availability]
    C --> D[AI shares options and pricing]
    D --> E[Customer picks a slot]
    E --> F[AI sends payment link]
```

The AI adapts to the customer's language automatically. A customer writing in Spanish receives tour names, prices, and the payment link message in Spanish.

## What the customer sees

1. **Tour options** — The AI presents available tours with names, short descriptions, and per-ticket prices as formatted text.
2. **Time slots** — After the customer picks a tour, the AI shows open dates and times with remaining capacity.
3. **Pricing confirmation** — The AI validates the selected slot and presents the exact total including taxes.
4. **Payment link** — A clickable URL the customer opens to complete their booking on FareHarbor's hosted checkout. In chat, the link renders inline as a tappable URL.

If the Create Booking action is enabled, the AI may confirm the reservation directly after collecting the customer's name, email, and phone number — without generating a payment link.

## Channel-specific details

<AccordionGroup>
  <Accordion title="Works across all text channels" icon="grid-2">
    The FareHarbor booking tools are available on every text-based channel your AI agent operates on: web chat widget, WhatsApp, and SMS. The booking experience is identical — the only difference is how the payment link renders (tappable URL in all cases).
  </Accordion>

  <Accordion title="Payment links are clickable" icon="link">
    In chat, the AI shares the payment link as a standard URL. Customers tap or click to open FareHarbor's checkout page in their browser. No copy-pasting required.
  </Accordion>

  <Accordion title="Multi-language support" icon="globe">
    The AI detects the customer's language from the conversation and responds in the same language. Tour names and descriptions come from FareHarbor as configured by the operator — the AI translates its own messages (availability summaries, pricing confirmations, the payment link message) but not FareHarbor content.
  </Accordion>

  <Accordion title="Multiple companies" icon="building">
    If your FareHarbor account is affiliated with multiple companies and no default is set, the AI asks the customer which company they want to book with before listing tours. If a default company is configured, the AI uses it without asking.
  </Accordion>

  <Accordion title="Multiple FareHarbor connections" icon="layer-group">
    If your organization has more than one FareHarbor connection (for example, different locations or currency accounts), the AI picks the right connection automatically when the customer's request is specific enough to match one. For general requests, the AI asks the customer which location or brand they are interested in before listing tours. Each connection has its own AI action toggles, so capabilities can differ per location.
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="AI Chat Widget" icon="comments" href="/widget/introduction">
    Set up your chat agent before adding FareHarbor.
  </Card>

  <Card title="Connect FareHarbor" icon="plug" href="/integrations/fareharbor/connect">
    API keys, sandbox mode, and Test & Connect.
  </Card>

  <Card title="Overview" icon="anchor" href="/integrations/fareharbor/overview">
    Capabilities and supported channels.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/integrations/fareharbor/troubleshooting">
    Connection failures, missing availability, SMS issues.
  </Card>
</CardGroup>