> 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/administrative-functions/manage-inventory/assigning-successor-services.md).

# Assigning successor services

Successor services are used when an existing service does not simply end, but continues in a different form. This can be the case when a device is replaced, returned, or when a service setup changes and a follow-up step is required.

From an admin perspective, successor services help keep things connected. Instead of stopping one service and manually starting another, you define what should happen next and let the process continue in a controlled way.

Successor services are always assigned to existing services. You are not creating something new from scratch, but deciding how an active service should move forward. This keeps changes traceable and avoids breaks in the service lifecycle.

In many cases, the same situation applies to more than one service. When that happens, successor services can be assigned to several services at once. equipme supports this by showing only the options that actually work for the selected services. If something is not possible, the reason is shown clearly, so you always understand why a service is included or excluded.

The assignment itself prepares the change, but it does not execute it immediately. Just like other changes, successor services follow the standard approval flow. Once approved, the successor is applied and continues through the usual fulfillment and delivery processes.

This approach keeps service transitions predictable, even when multiple devices, locations, or regions are involved.

If you want to see the exact steps for assigning successor services, the detailed guide in the documentation below walks through the process in depth. This course focuses on how to think about successor services from an administrative point of view.

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/Ghn8nWASNAh9BKNYmCz3" %}
[Assigning Successor Services to Multiple Devices](/equipme/assets/understanding-the-inventory/assigning-successor-services-to-multiple-devices.md)
{% endcontent-ref %}


---

# 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://hub.equipme.io/classes/administrative-functions/manage-inventory/assigning-successor-services.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.