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.
Last updated
Was this helpful?