> For the complete documentation index, see [llms.txt](https://docs.apruv.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apruv.io/apruv-field-app-guide/doing-a-service/end-of-service-workflow.md).

# End-of-Service workflow

At the end of each service, follow one of the two options below depending on whether the customer is present.

### Option 1: Customer is present

1. Tap the QR icon on the service
2. Show the QR code to the customer
3. The customer scans the code
4. The customer is directed to a personalized feedback page

### Option 2: Customer is not present

1. Select the completed service
2. Open Customer Overview
3. Add your service notes and media
4. Tap Submit

The system will automatically send a personalized message to the customer. The message appears to originate from you as the assigned technician.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apruv.io/apruv-field-app-guide/doing-a-service/end-of-service-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.