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

# Connect Treatwell with anny

> Import Treatwell bookings into anny automatically and mirror anny bookings to Treatwell via calendar link.

[Treatwell](https://www.treatwell.de/) is a booking platform for beauty and wellness providers, where end customers book appointments at salons and studios. With the integration, anny keeps bookings from both systems largely in sync: Treatwell bookings come into anny via email forwarding, and anny bookings become visible in Treatwell via a calendar link.

With Treatwell, you can in anny:

* Automatically import Treatwell bookings via email forwarding, including changes and cancellations
* Avoid duplicate entries and account for prepaid payments from Treatwell
* Make anny bookings visible in Treatwell as busy times via a calendar link (ICS)

The integration is especially handy when you use Treatwell and anny in parallel and want to manage your bookings centrally in anny, without maintaining appointments twice.

## Typical use cases

| Use case                      | Description                                                                                                                                                                        |
| :---------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Salon with Treatwell bookings | **Treatwell bookings land in anny automatically.** The booking email is forwarded to the anny inbox, and anny creates or updates the appointment, including cancellations.         |
| Studio with direct bookings   | **anny bookings become visible in Treatwell.** Appointments you create directly in anny, for example by phone or walk-in, appear in Treatwell as busy times via the calendar link. |
| Prepaid appointments          | **Prepayments are carried over.** When Treatwell reports a prepayment, anny accounts for the prepaid information on the booking.                                                   |

## How the Treatwell connection works

The integration uses two separate paths, depending on the sync direction:

* **Treatwell → anny** runs via email forwarding. You forward Treatwell booking emails to a dedicated anny inbox. anny AI reads the content robustly and creates or updates bookings, even if Treatwell changes the email layout.
* **anny → Treatwell** runs via a calendar link. anny provides an ICS calendar feed (ICS is a standardized calendar format) that you import into Treatwell. Treatwell then shows anny bookings as busy times.

Because both directions run over different paths, synchronization is not in real time. Expect a typical delay of about 30 to 60 seconds.

| Data                                 | Direction        | Frequency                                           |
| ------------------------------------ | ---------------- | --------------------------------------------------- |
| New bookings, changes, cancellations | Treatwell → anny | Via email forwarding, about 30 to 60 seconds delay  |
| Bookings as busy times               | anny → Treatwell | Via ICS calendar link, about 30 to 60 seconds delay |

## Connect Treatwell

### Requirements

Before you connect Treatwell, make sure you have the following:

* An active **Treatwell account** with access to the booking confirmation emails
* The ability to set up a **forwarding rule** for Treatwell booking emails in your mailbox
* Access to the anny **admin area**, to set up the integration and retrieve the calendar link

### Set up the connection

<Steps>
  <Step title="Open the Treatwell integration">
    In the admin area, open **Integrations** and select **Treatwell**.
  </Step>

  <Step title="Set up forwarding in your mailbox">
    Under **Mailbox for Treatwell emails**, anny shows you a dedicated **email address** (for example, `tw-…@calendar.anny.co`). Set up a forward in your mailbox that automatically sends Treatwell booking emails to this address. Every forwarded email is read and turned into a booking.
  </Step>

  <Step title="Add more senders (optional)">
    Emails from Treatwell are always accepted. If bookings arrive under a different name, for example from a Treatwell partner or via your own forwarding, enter the address or domain under **More senders** as **Accepted senders** (for example, `@partner.de`).
  </Step>

  <Step title="Map differing names (optional)">
    If a resource or service has a different name in Treatwell than in anny, create a mapping under **Differing names** via **Add**. Without a rule, anny picks the entry whose name matches the email.
  </Step>

  <Step title="Import the calendar link into Treatwell">
    Import the **ICS calendar link** provided by anny into Treatwell, so that anny bookings appear there as busy times.
  </Step>

  <Step title="Activate the integration">
    Activate the integration via the **toggle** in the top right. As long as it is inactive, anny shows the note "The integration is currently not active". Then trigger a test booking in Treatwell and check whether it appears in anny after a short time.
  </Step>
</Steps>

Once the integration is active, forwarded Treatwell bookings are created in anny automatically and anny bookings become visible in Treatwell.

<Tip>
  Treat the forwarding email address like a password: anyone who knows it can write bookings into your calendar. Also make sure the forwarding rule stays permanently active and is not blocked by spam or filter rules.
</Tip>

### Settings & options

| Setting                                      | Description                                                                           |
| -------------------------------------------- | ------------------------------------------------------------------------------------- |
| Email address (Mailbox for Treatwell emails) | Dedicated anny inbox to which you forward Treatwell booking emails                    |
| Accepted senders (More senders)              | Additional addresses or domains whose forwarded emails anny also accepts              |
| Differing names                              | Mapping for when a resource or service has a different name in Treatwell than in anny |
| Activation history                           | History of activations and deactivations of the integration                           |

## Limitations

The Treatwell integration does not support:

* Real-time synchronization: bookings are transmitted with a typical delay of about 30 to 60 seconds
* A direct API connection: Treatwell bookings come in via email, anny bookings go out via calendar link
* Import without active forwarding: without a correctly set up forwarding rule, no Treatwell bookings are imported

## Disconnect

<Warning>
  If you deactivate or delete the integration, no more appointments are synced. Forwarded Treatwell emails are then no longer turned into bookings, and anny bookings are no longer transmitted to Treatwell. Bookings already imported remain in anny.
</Warning>

You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.

## FAQ

<AccordionGroup>
  <Accordion title="How quickly do Treatwell bookings appear in anny?">
    Usually within about 30 to 60 seconds. Synchronization is not in real time, because bookings are transmitted via email forwarding.
  </Accordion>

  <Accordion title="Are cancellations from Treatwell carried over automatically?">
    Yes. When a booking is cancelled in Treatwell, anny updates the related booking accordingly, as long as the cancellation email is forwarded to the anny inbox.
  </Accordion>

  <Accordion title="What happens if the same email arrives multiple times?">
    anny detects duplicates and prevents the same booking from being created more than once, even with re-delivered or forwarded emails.
  </Accordion>

  <Accordion title="Are prepaid payments from Treatwell accounted for?">
    Yes, as long as the prepayment is included in the Treatwell email. anny carries over the prepaid information for the booking.
  </Accordion>

  <Accordion title="Do Treatwell users see my anny bookings?">
    Treatwell shows anny bookings as busy times via the imported calendar link. This keeps availability consistent, without exposing booking details from anny.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Treatwell bookings do not appear in anny">
    Usually the email forwarding is not set up correctly. Check in order: 1. Is the integration active (toggle in the top right)? 2. Is the forwarding rule active? 3. Does the target address match the dedicated anny inbox? 4. Do the emails arrive under a different sender that needs to be added under **More senders**? 5. Are the Treatwell emails landing in spam or a filter?
  </Accordion>

  <Accordion title="anny bookings do not appear in Treatwell">
    Check whether the ICS calendar link was imported correctly into Treatwell. Also keep in mind the typical delay of about 30 to 60 seconds before new anny bookings become visible.
  </Accordion>

  <Accordion title="The booking is assigned to the wrong resource or service">
    Without a mapping rule, anny picks the entry whose name matches the email. If a resource or service has a different name in Treatwell than in anny, create a matching mapping under **Differing names**.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> **Distinction:** Treatwell is a partner/booking channel, NOT a classic calendar integration (like Google/Microsoft) and NOT an API integration. Two separate transport paths: Treatwell → anny via email forwarding to a dedicated anny inbox (`tw-…@calendar.anny.co`); anny → Treatwell via ICS calendar feed that Treatwell imports. Therefore not real time, typical delay about 30 to 60 seconds.
>
> **UI path:** Admin area → **Integrations** → **Treatwell**. Sections in this order: **Mailbox for Treatwell emails** (dedicated email address), **More senders** (field "Accepted senders", address or domain), **Differing names** (resource/service mapping via "Add"), **Activation history**. Activation/deactivation via the **toggle** in the top right, deletion via the **three dots** in the top right.
>
> **No gating:** No plan gating and no separate feature activation other than the activation toggle, so no Info plan note.
>
> **If-then:** Import only works if the integration is active and the forwarding rule points to the correct anny inbox. If the email arrives under a foreign sender, that sender must be stored under "More senders". Prepaid is only carried over if the info is included in the Treatwell email. A cancellation is only carried over if the cancellation email is forwarded. Duplicate protection prevents multiple creation for re-delivered/multiply-forwarded emails.
>
> **Disconnect:** Deactivating or deleting stops all appointment synchronization (no import from Treatwell, no transmission to Treatwell). Bookings already imported remain in anny.
>
> **Robustness:** anny AI parses the emails even when the Treatwell email layout changes.