> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/service/get-started.md).

# Get started

Take a tenant from no Flow Service to its first registered service order.

Set up Flow Service in this order: switch it on in Flow Admin, give people access, then make the settings a service order needs.

{% stepper %}
{% step %}

#### Activate the Service extension

In Flow Admin, open **Settings → Extensions** and the Service extension's card. Turn on **Active** and click **Save**.
{% endstep %}

{% step %}

#### Give people a role

In **Users → Roles**, add **Service**, **Service store configuration** or **Service configuration** to roles. Give each user a role on their **Roles and access** tab.
{% endstep %}

{% step %}

#### Open Flow Service

Click **Flow Service** in Flow Admin's sidebar and sign in with the same user. Choose a store if asked.
{% endstep %}

{% step %}

#### Check statuses and the start status

In **Settings → Statuses**, give every state you use a status. In **Settings → General**, choose the **Start status for new service orders**.

![Flow Service, Settings → Statuses with statuses grouped by state](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FSEi23SooSLJejrEfSvoN%2Fservice-statuses-list.webp?alt=media)
{% endstep %}

{% step %}

#### Create a service type

In **Settings → Service types**, click **New service type**. Give it a name, an icon and an **Expected turnaround**.
{% endstep %}

{% step %}

#### Choose which statuses message the customer

In **Settings → Statuses**, open a status. Under **Messages for** that status, choose a text for SMS or E-mail. Start with the start status.
{% endstep %}

{% step %}

#### Register the first service order

In **Service orders**, click **New service order**, choose the service type, fill in the order and click **Register**.
{% endstep %}
{% endstepper %}

***

## What happens when you activate the extension?

Saving the extension as active also creates, where the tenant has none:

* the number series for service numbers
* two products per VAT code that service sales are booked on. See [Service sales products](https://docs.flowretail.com/docs/service/service-sales-products.md)
* ready message texts for every message, in every language, which you then adjust under **Settings → Message texts**

You need the **Extension Management** permission in Flow Admin. If there is no Service extension card under **Extensions**, contact Flow to add it. The card's **Service portal address** is set up by Flow; leave it as it is.

***

## What should I know about the setup steps?

* **Roles.** Give **Service configuration** under **Whole Company**. Someone who sets up and also works on cases needs **Service** too. See [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md).
* **Signing in.** Flow Service opens your default store, your only store, or **Choose a store**.
* **Statuses.** A new tenant starts with one status in each state. Without a start status, registering is refused unless exactly one active status is in <kbd>Not started</kbd>. The start status can only be one in <kbd>Awaiting product</kbd> or <kbd>Not started</kbd>. See [Statuses](https://docs.flowretail.com/docs/service/statuses.md) and General settings.
* **Service types.** A service order is always registered under one. Each new type gets an empty intake form, so registering works before you build forms. See [Service types](https://docs.flowretail.com/docs/service/service-types.md).
* **Messages.** No message goes out automatically until a status has one. The start status's message carries the customer's portal link. See [Message texts](https://docs.flowretail.com/docs/service/message-texts.md).
* **SMS.** A store sends SMS only when the SMS extension is active for the tenant and the store, with a sender name. A message that cannot be sent shows as failed in the service order's message log.

***

## What comes next?

Set these up when you need them:

* **Intake forms** and the **Field library**: questions asked at registration, company-wide or per store. See [Intake forms](https://docs.flowretail.com/docs/service/intake-forms.md) and Field library.
* **Job types**: checklists and suggested parts for kinds of work. See [Job types](https://docs.flowretail.com/docs/service/job-types.md).
* **Stores**: each store's parts warehouse, turnaround and warnings. See [Stores](https://docs.flowretail.com/docs/service/stores.md).
* **Terms**: the terms customers accept. See [Terms and conditions](https://docs.flowretail.com/docs/service/terms-and-conditions.md).
* **Insurance companies**, **Holidays** and **Staff notice**. See [Insurance companies](https://docs.flowretail.com/docs/service/insurance-companies.md), Holidays and Staff notice.
* **A shared counter screen**: turn on **Require a PIN code from staff** in **Settings → General**, and give staff a PIN in Flow Admin. See [Shared screens](https://docs.flowretail.com/docs/service/shared-screens.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/service/get-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
