> 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/intake-forms.md).

# Intake forms

An intake form sets the questions staff answer when they take in a service order of one service type.

{% hint style="info" %}
A service type can have one form for the whole company and one per store. A store's own form wins. Only **Service configuration** can change a company form; a store copies it and edits the copy.
{% endhint %}

An intake form lists the fields asked when a service order of one service type is taken in: their order, which must be filled in, and which follow-up questions appear for which answer. Fields come from the Field library. You find forms under **Settings → Intake forms → Forms**.

Every service order also asks for **Customer**, **Title**, **Description** and **Coverage**. These are on no form and cannot be moved or removed.

***

## Which form applies

Each service type has at most one active form per level: <kbd>Whole company</kbd>, or one store. A store uses its own form for the service type, otherwise the company form, otherwise only the standard questions. An archived form is never used for new service orders.

***

## Forms list

![Settings → Intake forms → Forms, a company form and one store copy for the same service type, store filter set to that store so the 'has its own form' line shows](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FAthWas1043rFhk6A47q8%2Fservice-intake-forms-list.webp?alt=media)

| Field                                   | Meaning                                                                                                                                                                                                                                      |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                                | Opens the form editor.                                                                                                                                                                                                                       |
| **Applies to**                          | <kbd>Whole company</kbd>, or the form's store. With one store chosen in the filter, a company form that store has replaced says "*Store* has its own form".                                                                                  |
| **Fields**                              | How many fields are on the form.                                                                                                                                                                                                             |
| **Store** filter                        | <kbd>All stores</kbd>, <kbd>Company only</kbd>, or one store's forms plus the company forms.                                                                                                                                                 |
| <kbd>Copy to store</kbd>                | On an active company form. See below.                                                                                                                                                                                                        |
| <kbd>Archive</kbd> / <kbd>Restore</kbd> | In the row menu of a form you can edit. Restoring fails if another active form has since taken that service type and level, or if a follow-up rule on it no longer holds; open the form, fix the marked rows, <kbd>Save</kbd>, then restore. |

You see the company forms and the forms of stores you configure. People with **Service configuration** see every store's forms. Forms of inactive stores are not listed.

***

## New form

![the New form dialog with Applies to open, showing Whole company and two stores](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FdXLktRbGilklfyqPWuqv%2Fservice-intake-forms-new-form.webp?alt=media)

| Field            | Meaning                                                                               |
| ---------------- | ------------------------------------------------------------------------------------- |
| **Form name**    | Required.                                                                             |
| **Applies to**   | <kbd>Whole company</kbd> (needs **Service configuration**), or a store you configure. |
| **Service type** | Only types with no active form at that level. Deprecated types are not offered.       |

Service type and store cannot be changed afterwards; archive the form and create a new one instead. The form starts empty and opens in the editor.

***

## Company forms and store copies

Only **Service configuration** can edit a company form. Others see "You can read this form but not change it." A store form can be edited with **Service configuration** or **Service store configuration** at that store.

![the 'Copy form to a store' dialog with Store and Form name filled in](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2Ff6yaQW8PsYW33E9N6FFt%2Fservice-intake-forms-copy-to-store.webp?alt=media)

| Field         | Meaning                                                                                                      |
| ------------- | ------------------------------------------------------------------------------------------------------------ |
| **Store**     | An active store you configure. The copy is used there instead of the company form from the moment it exists. |
| **Form name** | Starts as the company form's name.                                                                           |

The copy takes every field, its order, <kbd>Must be filled in</kbd> and follow-up questions. Later changes to the company form do not reach it.

***

## Form editor

![a form with a yes/no field that has a follow-up question for 'Yes', the Preview beside it](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FEt1kEcwOJ6BUZ5W8PrnA%2Fservice-intake-forms-editor.webp?alt=media)

Nothing is saved until you click <kbd>Save</kbd>.

| Field                         | Meaning                                                                                                                                                                                                               |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <kbd>Add a field</kbd>        | Adds a Field library field at the end. A field can be on a form once; archived fields are not offered. <kbd>New field</kbd> creates one in the library straight away.                                                 |
| <kbd>Must be filled in</kbd>  | The order cannot be created without an answer. Not on **Priority**, which always has a value.                                                                                                                         |
| Arrows or drag                | Set the order staff are asked in.                                                                                                                                                                                     |
| <kbd>Remove from form</kbd>   | The field stays in the library. With follow-up questions, choose <kbd>Remove all</kbd>, or <kbd>Remove only</kbd> to keep them as ordinary questions.                                                                 |
| <kbd>Follow-up question</kbd> | On a **Yes / no**, **Single choice** or **Multiple choice** field that is not sensitive, asked for one answer ("If the answer is…", or "If the answer includes…" for multiple choice). Follow-ups can have their own. |
| **Preview**                   | The form as staff fill it in.                                                                                                                                                                                         |

![the 'Remove … from the form?' dialog for a field with follow-up questions](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FKGLY4QUYexQf3ZYsWj1b%2Fservice-intake-forms-remove-follow-ups.webp?alt=media)

A hidden follow-up question is never required, and when an answer change hides it, its answer is cleared. If a follow-up's rule no longer holds, for example on a form archived while its question was made sensitive, the row is marked and <kbd>Save</kbd> waits until you fix it.

***

## How a service order keeps its form

A service order stays linked to the form it was taken in with. It keeps no copy, so later edits to the form apply to existing orders too. A field you add or make required is demanded of an existing order only when an update clears it or shows it. Archiving the form keeps the link. Each answer keeps the label and type it was given under.

At intake, Flow Service asks the form that applies to the store and service type, in order. Follow-up questions appear as answers are given, required fields must be answered before the order is created, and **Passcode** and other secret fields are masked.

***

## Good to know

* Forms are never deleted, only archived.
* Fields belong to the whole company: a change in the Field library reaches every form using the field.
* <kbd>Copy to store</kbd> works from company forms only. For two stores with the same different questions, copy the company form to each.


---

# 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/intake-forms.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.
