> 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/manager-self-service/manage-inventory/returning-or-swapping-services.md).
# Returning or Swapping Services
Devices break, get lost, or simply stop being needed. In many companies, those situations quickly become messy: emails, messages, spreadsheets, unclear responsibilities, and a general sense that no one really knows what happened to the equipment. In equipme, you handle returns and replacements directly from the service item so these everyday issues stay organized and visible.
If a device should be returned or replaced you open the employee profile and go to the **Services** section. Select the relevant service and open **Actions** to start the return process. The form asks for a brief explanation such as defective lost or another reason. This small step ensures that the removal of a device is transparent and not forgotten over time.
### Managing urgency without informal pressure
Some situations break daily work while others are inconvenient but tolerable. A missing laptop tends to stop someone from working while a faulty adapter rarely does. In the request you can indicate how urgent the situation is so the provider understands whether immediate attention is needed. Clarity at this point prevents frustration and repeated reminders.
### Sending a replacement to the correct location
If a replacement device is needed you select the delivery address in the same process. You can use the default company address or choose another location when someone works remotely or temporarily elsewhere. equipme includes this information directly in the request so deliveries do not rely on side conversations or personal memory.
### Approvals as a safeguard not a slowdown
After submitting the request it moves to **Approvals** where it needs to be confirmed before it becomes active. This makes sure that changes to hardware inventory are intentional and documented. It prevents expensive devices from disappearing quietly and gives everyone involved a single moment of acknowledgement before money is spent or equipment is moved.
Returns and replacements become predictable instead of chaotic. Devices do not vanish without context. Employees receive working equipment faster. Administrators know what changed and when it changed. The process becomes a normal part of lifecycle management rather than a small crisis that someone has to solve in a rush.
---
# 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/manager-self-service/manage-inventory/returning-or-swapping-services.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.