> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/admin/inventory/confirmation-of-receipt.md).
# Confirmation of receipt
{% hint style="info" %}
Walkthrough goes here.
{% endhint %}
Delivery completed means your side considers the job done. It does not mean the device reached the person. Confirmation of receipt closes that gap by asking the employee to confirm it themselves.
The request appears in their self service dashboard, and you can switch on an email so it does not sit there unnoticed. Outstanding confirmations are also collected on the dashboard, so you can follow up instead of asking around.
This matters most where you cannot hand something over in person: another site, a home office, a courier delivery. In those cases the confirmation is the only evidence you have.
If your process needs a signature rather than a click, you can generate a handover document for the selected services instead.
### Read more
{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/eKfDhV8Mdzo5JBOFhCdU" %}
[Transfer and Return Documents](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees/transfer-and-return-documents)
{% endcontent-ref %}
### Next
Sometimes a device has to go back or be exchanged. That is [Returning or swapping Services](/classes/admin/inventory/returning-or-swapping-services.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://hub.equipme.io/classes/admin/inventory/confirmation-of-receipt.md?ask=&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.
