> 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/getting-started/software-clients/assistant/service-orders.md).

# Service orders

Take in repairs, warranty claims and other work for a customer, such as a watch service or a ring resizing. A service case keeps the customer, the item, what is to be done, who pays, photos and every message together, from the counter to the workshop and back to the customer. The service types, jobs, forms and statuses are the ones your company has set up in Flow Admin.

You see **Services** when your company uses service and you have access to service orders.

## Find a case

Go to **More** and tap **Services**, or tap the **Services** tile on the Home tab. **More** also shows how many cases are open and ready for pickup.

The list shows the cases your store owns, newest first, with the status in your company's colour, the customer, the item and when the case should be ready. A case with **Highest priority** (red) or **High priority** (amber) says so. Tap a chip to show only **Open**, **Ready for pickup**, **Waiting for customer** or **Past estimate** cases. The number on each chip is how many there are.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FnYRwq3d0wQ64KMPl1t6d%2Fservices-01_service_list-a62171c6.png?alt=media" alt="Services with the open cases, the chips with counts and the bell" width="300"><figcaption><p>Services</p></figcaption></figure>

### Message from the workshop

When the workshop has written a message for the staff in Flow Service, it shows at the top of **Services** under **Message from the workshop**. You see the whole text, line breaks included. It cannot be closed, and when there is no message there is no empty space for it either. It is only on the list, not on the case page.

A message for your store alone shows below it, under **Message for** and the store's name. Either one shows on its own when only it is written.

Without network, or when Flow does not answer, the last message you got stays, with **Last fetched** and the time (and the day, when it is not today), and **Updates when the network is back.** A device that has never received a message shows nothing.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F1yCYqQCYzcKRwoOZffRY%2Fservices-23_staff_banner-d61151cc.png?alt=media" alt="Services with the message from the workshop above the search field" width="300"><figcaption><p>The workshop's message</p></figcaption></figure>

Tap the search field to open **Find service order**. Search by service number, phone, name or serial number. The search covers every store: cases another store owns are listed under **In other stores**. You can open them, but changes are made where the case is.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2Flv2fSsBSupaUAeUTyPhm%2Fservices-09_find_service-510cf48a.png?alt=media" alt="Find service order with one case in this store and one in Acme Jewellers Bergen" width="300"><figcaption><p>Find service order</p></figcaption></figure>

The fastest way is to scan:

* Scan the barcode on the intake slip anywhere on the screen, and the case opens.
* Scan the serial number or IMEI of the item. One open case opens straight away. If several cases have the same number, **Find service order** lists them.

## Register a case

Tap **New service order**, or **Register a service order on the item** in the product's **⋯** menu. Everything is on one page, in up to six steps. The stepper at the top shows what is done, and the bar at the bottom says what is still **Missing**. A step that is done folds to one line: tap **Change** to open it again.

1. **Customer**: find the customer by phone, name or membership card, or create a new one.
2. **Type**: choose the service type. Each type shows how many working days it usually takes, and **Estimated ready** suggests the date. Tap it to choose another day: the calendar strikes through the days the store is closed and its holidays (**Closed**). You can still pick one. Tick the **Job types** if you know the work (they are optional): tap **Checklist** to see the points the workshop checks before the item is handed back. Then choose the **Coverage**, every time, since nothing is chosen in advance: **Customer pays** (with an estimate and **Max without asking**, both optional), **Consumer claim**, **Warranty claim** or **Insurance claim** (with the insurance company, claim number and deductible).
3. **Unit**: this step is there only when the form of the chosen type asks for a product. The stepper says **required** or **optional**, as the form decides, and only waits for the unit when it is required. The customer's latest purchases are listed sale by sale. Tap **Select** on the item. Or scan the serial number, the receipt or the product's barcode. A serial number finds the sale in every store and links the case to it. If you type a different serial number than the one on the sale, the case is registered without the link to that sale, and the field says so. If the item is already in for service, you see **This unit is already in** right away, with **Open** and the case number. A unit you have already chosen is never lost when you change the type: if the new type does not ask for one, it stays in view with **This service type does not ask for a unit. The one you chose comes along with the service.** Tap the cross to remove it.
4. **Form**: the questions your store asks for this type, such as the serial number, what came with the item, or a passcode. Serial numbers and IMEI can be scanned. A passcode or other code is typed hidden, the keyboard does not correct, suggest or remember it, and it is stored encrypted.
5. **What is wrong**: the **Description**, a **Title** for the list (suggested for you), and up to six photos. Each photo is **Internal** or **Shown to customer**.
6. **Terms**: the customer accepts the terms **Accepted in the store**, signs with **Sign on this screen**, or gets a link with **Send link by SMS**. When your store requires the terms, **Later** registers the case now: the terms must be accepted before work starts.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FmAQlLLH8L8jjPN3YpsyF%2Fservices-02_new_service-f8315214.png?alt=media" alt="New service order: the job types with their checklists and the coverage" width="300"><figcaption><p>The type, the job types and the coverage</p></figcaption></figure>

Tap **Register service order**. The case is never registered twice, also on a poor network: if no answer comes, **Try again** checks whether the case was made before it sends again.

{% hint style="info" %}
Take pictures of scratches and damage when you take the item in. Then everyone can see what it looked like when the customer handed it over.
{% endhint %}

## The case is registered

**Service order registered** shows what happened:

* the intake slip is printed on this device's printer. Attach it to the unit. Tap **Print again** if needed.
* the terms the customer accepted
* the SMS to the customer, with a link to the case
* when the case should be ready
* the photos. They upload in the background, also if you close the screen. Without network they wait on the device (**Waiting for network**) and go as soon as the network is back.

Tap **Open the service order**, **Register new for customer** for another item, or **Done**.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2Fg1Nozlw2AVkOar2e9BOB%2Fservices-04_service_registered-9f5fb233.png?alt=media" alt="Service order registered: slip printed, terms accepted, SMS to the customer and the ready date" width="300"><figcaption><p>The case is registered</p></figcaption></figure>

## The case page

Open a case to see:

* the status in your company's colour, the priority, what the customer sees, the assignee and the estimated ready date (**past estimate** when the date has passed)
* the unit with its serial number and the product the case is made for. Tap **Change** (or **Choose product**) to scan or search for another product. If the case is linked to the sale the unit was bought on, the app asks first, because another product takes the case off that sale
* the **Codes** the customer has given (see below)
* the **Quote**, once a price is given (see below)
* the **Job types**. Tap **Change** to add or remove job types after intake
* the **Checklist** for the job types, ticked off while you work (see below)
* the photos. Tap a photo to switch between **Internal** and **Shown to customer**, or tap **Take photo** to add one
* the customer, what is wrong, **Coverage** (who pays), the **Assignee**, where the item is kept, the estimate, **Max without asking** and the answers from the form
* the **Diagnosis** and the **Resolution** (see below)
* **Parts and work**: the lines on the case and the total (see below)
* **Sales**: the sales made for the case (see below)
* **Log**: every status change, note, message and checklist, with who can read it (**Internal**, **Document** or **Customer**). What the customer wrote stands out in purple. A message to the customer shows how far it got on each channel: **SMS · Sent**, **E-mail · Failed** (with what the provider said), **Not sent** or **Delivery uncertain**. Under a note, diagnosis or resolution the customer can read, tap **Make internal** to hide it from the customer. The text stays, and the entry is marked **Edited**.

<div><figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FXwapxQDl3mRiQUvjH17X%2Fservices-05_service_order-2e6c1201.png?alt=media" alt="Service order #40021: status, unit, job types and photos" width="300"><figcaption><p>The case</p></figcaption></figure> <figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FUnKe5Udq7V9KI4R0GExm%2Fservices-19_history-ef8482e3.png?alt=media" alt="Log: a message to the customer, the customer&#x27;s reply, the diagnosis and the status changes" width="300"><figcaption><p>Log</p></figcaption></figure></div>

### Add a code

The **Codes** card lists the codes the customer has given by their name and when they were added, such as **Device code** and **Added 2 Oct 11:30 by Emma S.** Use it for a code the customer remembers after the case was taken in, such as an e-mail password or the code to the device.

Tap **Add code**. Choose one of the three names (**Email password**, **Device code** or **Account password**) or write your own under **What is it?**, then type **The code**. It is typed hidden: tap the eye to check it. Tap **Save code**.

The code is stored encrypted in Flow, and it is never kept on the device: no draft, nothing left when the sheet closes, and the keyboard does not correct, suggest or learn it. Without network **Save code** is locked and says why. If Flow does not answer, the code may be saved: tap **Save code** again, and it is saved only once. If Flow refuses, you see its reason and what you typed stays.

### Show a code

To unlock the device and test it, tap the code's row (**Show**). The code is shown in the row until you tap **Hide**, for a minute at most, and never after you leave the case or the app. When your company asks for a PIN for service, you type your own PIN first; a wrong PIN, or too many tries in a row, is said in the sheet. The case's log notes who saw the code.

You can add a code on an open case at the store that has it, and at the store that took it in. Not at other stores, and not when the case is finished: closing a case deletes its codes for good.

### Who is responsible, and where the item is kept

The facts show **Coverage**, who pays for the work as the intake chose it. It is read only here.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FtGiI5RPv4npP4JEtDbvM%2Fservices-29_facts-79a18d49.png?alt=media" alt="The facts: coverage, assignee and where the item is kept, each with Change" width="300"><figcaption><p>Coverage, assignee and place</p></figcaption></figure>

On an open case at the store that has it, tap **Change** beside **Assignee**. The sheet lists the people who can be given the case at this store (with a search field when there are many), with **No assignee** first: the store's service staff are told instead. Tap a name to save it. If Flow refuses, the sheet stays open and the banner says why. The hand-over shows in the **Log**. Choosing the same person again changes nothing and tells nobody.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FQrDW7TwcFnk5HGClAmXL%2Fservices-30_assignee-68082117.png?alt=media" alt="Assignee with No assignee first and the people at the store" width="300"><figcaption><p>Change the assignee</p></figcaption></figure>

The place the item is kept, such as **Shelf B3**, stands in the facts under the name your intake form gives it (otherwise **Location**). Tap **Change**, or **Add** while none is written, type the place and save. An empty text removes it. On a closed case, and at other stores, you can only read it.

### Diagnosis and resolution

**Diagnosis** and **Resolution** sit under the facts, as in Flow Service. Each shows the newest text for staff (**Internal**) and the newest for the customer (**Customer**), or **Nothing written yet**. Tap **+ Write**, type the text and choose who sees it: **Internal** (staff only, the default) or **Customer** (in the portal and on the documents, but never sent as a message). The new text replaces the one shown. The old one stays in the log. You write them at the store that has the case, also after it is closed. Elsewhere you can only read them.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FFH9Xt0qi86EFY67qFdrw%2Fservices-22_diagnosis_resolution-a333805d.png?alt=media" alt="Diagnosis with an internal text and a text for the customer, and the resolution" width="300"><figcaption><p>Diagnosis and resolution</p></figcaption></figure>

### Parts and work

**Parts and work** lists what the case charges for, with the total. On an open case at the store that has it, tap **Add part**. The sheet stays open while you put parts on:

* Scan the part (the scanner, or the camera on a phone), or search and tap the product. The part goes straight onto the case with quantity 1. The same part again is one more.
* Only what Flow demands is asked: the variant of a configurable product (the same picker as on a sale), a serial number (scanned or typed, always one piece) and a reference, when the product asks for one. There is no price or discount to choose: Flow sets them, and the lines and the total are Flow's own figures. A small line above **Done** says **Warehouse: default**: Flow picks the warehouse the part comes out of, as it always did. Tap **Change warehouse** to take the part from another warehouse; the list shows your store's service warehouse first, then the other warehouses your store delivers from, then **Other warehouse locations**. Your choice holds for as long as the sheet is open, and each line then says **From** and the warehouse.
* If Flow refuses a part, for example because it has no price, its reason shows in the sheet and nothing is left on the case. If there is no warehouse Flow can take the part from, the warehouse list opens by itself with Flow's own words on top and how many of the part each warehouse has. Choose one and the same part is sent again.

Tap **Done** when you are finished.

When a job type suggests parts, they are listed under the job types on the case, as **Suggested for** and the job type, with each part's name, the job type's note and the store's price. Tap **Add** to put the part on with the same rules as a scanned one: a variant, serial number or reference is asked first. A part the case already has says **Added**; add more of it with **Add part**. The suggestions show only where parts can be added.

<div><figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FMdktbJbj6U38XiYUiuSr%2Fservices-24_parts-1a1429af.png?alt=media" alt="Parts and work with four lines, three of them locked, and the total" width="300"><figcaption><p>Parts and work</p></figcaption></figure> <figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FANWTZqlVPmftcYUTtzvF%2Fservices-25_add_part-24453a4d.png?alt=media" alt="Add part with the mainspring just added" width="300"><figcaption><p>Add a part</p></figcaption></figure></div>

Each line has **+**, **−** and **Remove**. After **Remove** you have a few seconds to tap **Undo**. A line that is already on a sale shows a lock (**On a sale. Cannot be changed.**), and a line with a serial number has no **+** or **−**.

Without network, a part you have found is kept on the device and shows **Waiting for network**, with **The price is set when it is sent**. The total shows **…** until Flow has it. The part is sent by itself, once, when the network is back, also after you have restarted the app. Changing a quantity and removing a part need the network and say so. A scan cannot be looked up without network and says so too. A part Flow refuses after it had waited stays on the case with Flow's message until you remove it.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FEEsF1x1IdtqPDQjVwyi9%2Fservices-26_part_waiting-2ab1fbb0.png?alt=media" alt="A crown gasket set waiting for the network, with no price and the total not known yet" width="300"><figcaption><p>A part waits for the network</p></figcaption></figure>

On a closed case, and at other stores, the lines are read only.

### Sales on the case

**Sales** lists the sales made for the case, each with its number, the date, the amount and whether it is **Paid**, **Partly paid**, **Not paid** or **Cancelled**. A paid sale opens as a sale. A sale that is not paid opens in the payment flow, as **Take payment** does (it keeps the hand-over link when the case is ready for pickup), and the case is read again when you come back. A cancelled sale only shows what it was.

If lines are billed on a sale this store cannot list, for example one made at the store that had the case before, the card says **The case is billed on a sale this store cannot see. Check that it is paid.** If the sales cannot be read, you see Flow's reason and **Try again**.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FjY3diJiMGpKtzBENpnpy%2Fservices-31_sales-5c51b9e1.png?alt=media" alt="Sales with one paid and one unpaid sale" width="300"><figcaption><p>The sales for the case</p></figcaption></figure>

### Tick off the checklist while you work

The **Checklist** card lists the points of the job types. Tap ✓ or ✗ on a point as you do the work: the answer is saved at once, and the checklist before the next status starts from your answers. If the case has not been started, the first tap asks **Start the work?** and moves the case to a status that is under work. From **Ready for pickup** and at other stores, the checklist is read only.

### Change the status

Tap **Change** on the status card, or **Change status** at the bottom. The statuses are grouped by stage (**Not started**, **In progress**, **Ready for pickup** …), each stage with what it means, and every status with its colour. Add a note if you like: only staff see it. Tap **Save status**.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F39hdtFe0g9j2cR5oipCn%2Fservices-06_add_note-7ca807fd.png?alt=media" alt="Change status with Waiting for parts chosen and a note" width="300"><figcaption><p>Change the status</p></figcaption></figure>

Before a case is set to ready for pickup or handed over, the app asks for the **Checklist before** that status. Mark each point **Passed** or **Not passed**, and tap **Save and continue**. Points that do not pass stay in the log. **Skip** asks for a reason.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FVAw2rzthL1mVW9m9lAV0%2Fservices-11_checklist-6de7af78.png?alt=media" alt="Checklist before Ready for pickup with three points passed" width="300"><figcaption><p>The checklist before the status</p></figcaption></figure>

If the customer has not accepted the terms yet and your company requires it, the app asks for them first (see **Accept the terms**).

If your store has asked to confirm before a case is closed, setting a status that finishes the case, or cancels it, asks **Set the status to …?** first. Closing a case deletes its codes for good.

### Send a quote

Tap **⋯** › **Send quote** to offer the customer a price. Type the price (the estimate and **Max without asking** stand under the field), and tick **SMS** or **E-mail**: the customer gets a link to the portal, where they accept or decline. SMS is ticked when the customer has a mobile number. With nothing ticked, **Save price** only saves it, for a price agreed over the counter. If the message cannot be sent, nothing is saved: the sheet says why and offers **Save without sending**.

Once a price is given, a **Quote** card shows the amount and where it stands: **Waiting for the customer**, **Accepted** or **Declined**, and where the answer came from (**In the portal**, **In the store**, **On the phone** or **In writing**). While it waits, tap **Record answer** if the customer answered in person. **New price** sends a new quote.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FhC2JNs0mmvbGIJHKQawo%2Fservices-20_quote_card-37dfddbc.png?alt=media" alt="The Quote card: 1 650 kr, waiting for the customer, with Record answer and New price" width="300"><figcaption><p>The quote waits for the customer</p></figcaption></figure>

### Accept the terms

When the customer has not accepted the terms yet, **Terms · Not accepted yet** in the facts and **Record acceptance** in **⋯** open the terms the case was taken in under. Choose **Accepted in the store**, **Sign on this screen** or **Send link**. Once accepted, the action is gone and the log says so.

### Note or message

* **Note** writes a note on the case. Choose where it shows: **Internal** (only staff, the default), **Document** (printed on the service summary and the damage report, never in the portal) or **Customer** (shown in the customer portal and on the documents). A note is never sent: to reach the customer, tap **To the customer instead**. The switch to notify the assignee (or the store's service staff) is on by default: they get a notice in Flow.
* **Message to the customer** (in **⋯**) sends an SMS and/or an e-mail, depending on what the customer has. The message is also shown in the customer portal. Replies come in the customer portal, not by SMS, and show up on the case and under the bell.

<div><figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F5OWv10o62yf9rHsAFXdb%2Fservices-12_comment-1ca4c408.png?alt=media" alt="A note with where it shows, and the assignee notified" width="300"><figcaption><p>A note</p></figcaption></figure> <figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FwUXnI3EfXNkDYSaM7dRN%2Fservices-13_message-67dbd492.png?alt=media" alt="Message to the customer by SMS, with the note that replies come in the customer portal" width="300"><figcaption><p>A message to the customer</p></figcaption></figure></div>

When the case is ready for pickup, **Message to the customer** can send your store's own "ready for pickup" message.

### More actions

Tap **⋯** at the top for:

* **Take payment**: the customer can pay now, also before the case is ready (see below)
* **Record acceptance**, while the customer has not accepted the terms
* **Message to the customer**
* **Send new portal link**: the customer gets a new link to their case on SMS and/or e-mail, and the old link stops working at once
* **Change customer**: put the case on another customer. The link to the case is renewed right away, so the old link stops working. Then the app offers to send the new link to the customer. Sales already made for the case keep their customer.
* **Print the slip again**
* **Send document by e-mail**: the service confirmation, the service summary or the damage report as a PDF. The customer's address is filled in; type another one to send it to an insurer or a manufacturer (the e-mail then has no link to the case). A damage report can carry up to 12 of the photos the customer can see
* **Add photo**
* **Send quote**: offer the customer a price (see above)
* **Quote: record the customer's answer**, while a quote waits for an answer

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FsPmZxuPYT0nF8uOz8WAI%2Fservices-14_more_actions-c368d8d6.png?alt=media" alt="More actions: take payment, message, new portal link, change customer, print the slip, e-mail a document and add photo" width="300"><figcaption><p>More actions</p></figcaption></figure>

## Take payment and hand over

When the case is ready for pickup and there is something to pay, the main button is **Take payment**. Tap it to see the lines that are not paid yet, then **Make the sale and take payment**. One sale is made for the case, and it opens in the normal payment flow (see [Sales](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/sales.md)). The sale is never made twice, also on a poor network.

<div><figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FYx0atbuvw0ULbMj8H0Hh%2Fservices-15_ready_for_pickup-1f989c54.png?alt=media" alt="The case is ready for pickup, with Take payment at the bottom" width="300"><figcaption><p>Ready for pickup</p></figcaption></figure> <figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2Fa8rDoJFarkjscjoS8Mc7%2Fservices-16_take_payment-ddc41c4f.png?alt=media" alt="Take payment for #40021 with the work and the part" width="300"><figcaption><p>Take payment</p></figcaption></figure></div>

After the payment, the app offers **Hand over and close the case**. Tap **Not now, the customer collects later** if the customer comes back for it. The offer is still there after a restart.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FwLlOR32kdZOppxi4KnAd%2Fservices-17_hand_over-5245aab0.png?alt=media" alt="Paid: hand over and close the case, or not now" width="300"><figcaption><p>Hand over after the payment</p></figcaption></figure>

* A case that was paid earlier shows **Paid** and **Hand over**.
* A case with nothing to pay, such as a warranty case, goes straight to **Hand over**.
* Something not paid never stops a hand-over: the money may be settled elsewhere. Before a case is closed, **Check the money on this case before handing it over.** lists what is not billed or not paid yet, and **Take payment** still works on a closed case.

{% hint style="info" %}
The customer can pay before the case is ready: tap **⋯** › **Take payment**. Lines added later get a sale of their own.
{% endhint %}

## A case at another store

A case can be taken in at one store and repaired at a workshop in another. Then the case page says **The case is at** the other store. You can read the case, write a note and, at the store that took it in, add a code. Only the store that has the case changes the status, the parts or the assignee, or takes payment.

* With service access in that store, tap **Move the case here**.
* Otherwise, tap **Ask the workshop to move it**. The workshop gets a note and a notice.

When the case is ready at the workshop, asking to move it here is the main button.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FNI2IqZaxp3CsPgntdNVB%2Fservices-18_other_store-4625ea6b.png?alt=media" alt="The case is at Acme Jewellers Bergen, with Ask the workshop to move it" width="300"><figcaption><p>A case at another store</p></figcaption></figure>

## Notifications

The bell at the top of **Services** shows your own notifications: the customer replied, a case was moved here, a quote was answered, a case is past its estimate, and more. The number on the bell is how many are unread. You also see it on **Services** under **More** and on the Home tab.

Tap a notification to open the case and mark it as read. **Mark all as read** clears them.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FwTOEWzF0ijmMTcOs8Kg0%2Fservices-10_notifications-7e0f2af8.png?alt=media" alt="Notifications: the customer replied, moved here, quote answered and past estimate" width="300"><figcaption><p>Notifications</p></figcaption></figure>

## Serial numbers

Expensive items such as watches often have a serial number. When you sell a product that needs one, Assistant asks for it: scan the barcode marked S/N on the box, or type it in, and tap **Confirm**. If the item is not handed over now, tap **Deliver later**: the serial number is then given when the item is handed over.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FnA8CmeTVfZgqSE7JD0JL%2Fservices-07_serial_number-3ff25364.png?alt=media" alt="Serial number for the watch, scanned on the sale" width="300"><figcaption><p>The serial number on the sale</p></figcaption></figure>

If a line still has no serial number when you tap **Pay**, Assistant lists the lines that are missing one. Tap a line to scan it, or tap **Hand over later and pay now**.

The serial number is kept on the order line, so you can find the exact item when the customer comes back with it.

## Service cases on the order and the customer

In the order details, **Services** lists the cases connected to the sale, with the number, the status and the title. It also shows cases another store or the workshop has, and whether the sale sold the item or paid for the case. Tap one to open it.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FofoDBlvINQd657L7mIL0%2Fservices-08_order_with_services-47533cda.png?alt=media" alt="Order details with the service cases and the serial number on the lines" width="300"><figcaption><p>The service cases on the order</p></figcaption></figure>

On a sale made from a case, the line for the work lists the products behind it, for example **2 × Crown gasket**, with **S/N** and the serial number under a part that has one, and what the case charges for each on the right. They stand under the line on the open sale, on the order and on the receipt (see [Sales](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/sales.md) and [Orders and receipts](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/orders-and-receipts.md)). The figures are Flow's: nothing is added up in the app.

On the customer card, the **Services** tab lists the customer's cases in every store, open and finished (see [Customers](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/customers.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/getting-started/software-clients/assistant/service-orders.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.
