More in this collection

Mobile plan change orchestration

Coordinate a subscription amendment across customer channels, product data and the systems that apply the change.

The workflow to solve

A plan amendment can affect commercial terms, the effective date and service parameters. If the request is sent independently to several applications, the customer may receive inconsistent answers about when the new plan applies.

A practical software boundary

Begin with the subscribed product and the new offer the customer is allowed to select. Establish the required order steps, the dependencies between them and the point at which a cancellation or reversal needs a different process.

What the design should demonstrate

Use the Order Orchestration Platform discussion to define a traceable journey from the accepted amendment to a confirmed outcome. Customer service should be able to distinguish a scheduled change, an in-progress action and an exception that needs review.

  • Check account authority and offer eligibility.
  • Make effective dates explicit in the order.
  • Coordinate dependent commercial and provisioning actions.
  • Test duplicate requests and a late downstream response.

Questions behind the implementation

When can a plan amendment be cancelled?

The workflow must identify the point at which work can be stopped and the point after which a separate reversal or compensation process is needed. That decision depends on the actions already performed.

Let’s plan your next service journey.

Bring the customer journey, service hand-off or operational workflow you need to improve. We’ll discuss the products and engineering needed to move it forward.

Start a project conversation