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

# easySales

> Connect easySales so the chatbot and the Email Assistant answer order and parcel questions from it: status, courier and tracking number

If your orders go through [easySales](https://easy-sales.com), that is usually where the most current answer to "where is my order" lives: the order status, the courier, the tracking number and whether the parcel was delivered.

Once easySales is connected, the chatbot and the Email Assistant check it first when a customer asks about an order, and fall back to the order data from your shop platform when easySales has nothing or does not answer within a few seconds.

> [!NOTE]
>
> Sensbot only **reads** from easySales. It never changes an order, a status or a shipment, and the token needs permission to read orders and nothing else.

***

## Before you start

| Requirement | Why |
| - | - |
| A Sensbot account with the chatbot or the Email Assistant | easySales adds order answers to them |
| Access to your easySales account | You create the token there |
| About five minutes | |

> [!NOTE]
>
> Is your shop on a platform without a Sensbot app (for example PrestaShop or a shop built in-house)? Write to [support@sensbot.ai](mailto:support@sensbot.ai) after connecting, and we switch order answers on for your shop.

***

## Step 1 · Create a token in easySales

1. In easySales, open **Account → Settings → API Settings**.
2. Create a **Personal Access Token**, for example named `Sensbot`.
3. Give it permission to **read orders** only. Sensbot never needs to write.
4. Copy the token.

***

## Step 2 · Paste it in Sensbot

1. In the [Sensbot dashboard](https://platform.sensbot.ai), open **Integrations**.
2. Scroll to **Order and shipping systems** and find the **easySales** card.
3. Paste the token into **Personal Access Token**.
4. **Website name in easySales (optional):** if easySales handles more than one webshop for you, enter this shop's name exactly as it appears in easySales, so only its orders are used. With one webshop, leave it empty.
5. Click **Connect**.

Sensbot checks the token before saving it. If easySales does not accept it, the card says so and nothing is saved. Once connected, the card offers **Test connection** to recheck the saved token at any time.

From now on the chatbot and the Email Assistant use easySales for order questions.

***

## What the customer gets

| Question | Answer from easySales |
| - | - |
| "What is the status of my order?" | The order status easySales holds, read when the customer asks |
| "Has my parcel shipped?" | Once it is handed to the courier: the courier, the tracking number and the tracking link |
| "Was it delivered?" | The delivery status the courier reported |

To get order details, the customer gives the order number plus the email address or phone number used on the order. In email, the sender's address counts as the email, and the Email Assistant also finds the sender's orders from the last 30 days.

> [!NOTE]
>
> Product questions are not answered from easySales: they still come from your product feed or your shop platform.

***

## Disconnecting

On the easySales card in **Integrations**, click **Disconnect**. The chatbot and the Email Assistant go back to the order data from your shop platform only. To cut access on easySales' side too, delete the token in **Account → Settings → API Settings**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.