> 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/assigning-successor-services.md). # Assigning successor services {% hint style="info" %} Walkthrough goes here. {% endhint %} A successor is for the case where a service does not simply stop. The contract runs out, the device is due for replacement, and something has to take its place. equipme can remind you before that point, typically thirty days ahead, and the employee can pick their next device themselves. The old service ends, the new one is ordered, and the two stay connected instead of appearing as unrelated events. You can do this for several services at once. equipme only offers the options that actually work for the whole selection and tells you why a service is excluded, which saves you finding out after the fact. Assigning a successor prepares the change. It still goes through approval like anything else, and only then continues into fulfilment. During the handover both can be booked for a short time, the old device until it comes back, the new one from the moment it is ordered. That is expected, not a mistake in your inventory. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/Ghn8nWASNAh9BKNYmCz3" %} [Assigning Successor Services to Multiple Devices](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/understanding-the-inventory/assigning-successor-services-to-multiple-devices) {% endcontent-ref %} ### Next Returned and spare devices need somewhere to live. That is [Warehouse](/classes/admin/warehouse.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/assigning-successor-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.