> For the complete documentation index, see [llms.txt](https://nomadia-docs.gitbook.io/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nomadia-docs.gitbook.io/products/customer-communication/end-of-visit.md).

# End of Visit

## 1. Introduction

The **End of Visit** communication setting allows you to automate follow-up messages sent to your customer.

**What is the End of Visit?** It is the process that occurs **once the delivery has been completed**. Upon completion, the customer automatically receives an email with an attached PDF file.

**The PDF Proof of Delivery (PoD)** This attached PDF serves as the official proof of delivery. It confirms essential details for the customer, including:

* The customer’s name
* The customer’s address
* Signatures collected during the visit

## 2. Initial Configuration

Before sending your first message, you must enable the basic communication channels.

1. **Access the End of Visit Settings:**
   * Click the **End of Visit** option to access the configuration screen.

![](/files/FvI2SdtLSuwkhDIpKujf)

2. **Enable Outgoing Channels:**
   * Enable the **outgoing emails** option

![](/files/MTqMhdcZIyJI3evxkSpj)

3. **Set the Email Subject**

![](/files/JYncOfQmOp3lAutQH03R)

4. Activate the toggle to send the PoD as a PDF file

![](/files/9ucBmJjvOp4gDiHUd0mw)

5. Click the **Save** button to apply changes to the modified template.

## 3. Feature Explanations with Benefits

This feature offers flexibility and clear documentation delivery.

| Feature                      | Description                                                                                                                           |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **ETA Link**                 | A link containing the estimated time of arrival (ETA) is automatically created and sent once the delivery completes.                  |
| **Email Subject Editing**    | You can enter and customize the **email subject** so customers immediately know the purpose of the message.                           |
| **Message Body Editing**     | You can freely **edit the message** that will be sent to your customers, allowing for personalized language and important details     |
| **Personalization Tags ($)** | Entering the **dollar symbol** ($) reveals options that you can insert and edit directly into the body of the email, saving you time. |
| **Preview Window**           | Before saving, you can see the **preview** of the exact message that will be sent, ensuring it looks professional and accurate.       |
| **Live Location Tracking**   | The link allows the customer to track the live location of the delivery (or deliverer).                                               |
| **Outgoing Email**           | Option to enable sending the ETA link via email.                                                                                      |
| **Outgoing SMS**             | Option to enable sending the ETA link via text message.                                                                               |

## 4. Customizing and Reviewing the Subject

Follow these steps to customize the message body and confirm the final appearance of the email.

1. **Select the Communication Mode:**
   * Change the communication **mode** to **standard** or **advanced** based on your required level of detail.

![](/files/YB3OKxp2RJmCAeQgELTg)

2. **View the Current Message:**
   * Look at the section that shows the **message to be sent to the customer**.
3. **Edit the Message Body (Optional):**
   * If you need to adjust the content, you can **edit this body of the email**.

![](/files/8vDlwILidhk4B0hfKAHr)

4. **Preview the Final Email:**

   * Review the **Subject:** Check the **preview** area to see exactly how the final email will look to the customer. This is your chance to review the message before saving

   * **Insert Personalized Information (Optional)** To include dynamic information (like a customer's name or specific appointment details), enter the **dollar symbol** ($). This will show options you can use to edit the body of the email.

   > 💡 **Tip:** Using personalization tags makes the message feel more direct and professional.

![](/files/rDSuTw16lL19XbYQYRfJ)

5. **Save the Configuration:**
   * Once you are satisfied with the settings and the preview, click on **Save**.

![](/files/ATknZrago83B8xDu7fj1)

6. The customer will receive the following email

<figure><img src="/files/6KS055pqP3bQqfnyzAxi" alt=""><figcaption></figcaption></figure>

***

## 5. Productivity Tips

Use these tips to maximize the effectiveness and clarity of your customer communications.

* **💡 Pre-Check the PoD Content:** Remember that the PDF attachment is crucial. You can remind yourself that the customer will verify their name, address, and signatures within the attachment.
* **💡 Use the Preview Often:** Before saving any changes, use the preview feature to double-check formatting and ensure the message body reads correctly. The preview shows exactly what the customer will see.
* **💡 Verify Attachment Inclusion:** Always ensure that you have enabled the option to **Insert the PDF report of the intervention as attachment**. This guarantees the necessary proof of delivery is included.


---

# 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, and the optional `goal` query parameter:

```
GET https://nomadia-docs.gitbook.io/products/customer-communication/end-of-visit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
