Operations checklist

Keep every active connectivity service ready for its next change

A delivered service needs a reliable operational, commercial, support, and billing record throughout its life. This checklist helps teams preserve that context from activation through change, renewal, migration, and closure.

Published by Trunkstar · Reviewed August 27, 2026

Explore service lifecycle management Discuss your service workflow

Activation handover

Create a complete service record when delivery finishes

Customer, site, product, supplier, and service identifiers
Order, supplier reference, and activation evidence
Contract term, start date, renewal date, and notice period
Customer price, supplier cost, currency, and billing frequency
Technical, access, support, and escalation information
Named operational and commercial owners

Operational ownership

Keep support tickets and tasks attached to the service context

A support conversation is easier to understand when it retains the customer, site, supplier, product, contract, and service identifiers it concerns. Link tickets to the relevant object instead of relying on a subject line to recreate context.

Assign follow-up tasks to individuals or teams and preserve due dates, decisions, and completion evidence alongside the service event.

Change control

Use a consistent workflow for upgrades, downgrades, and renewals

Record the requested outcome and effective date
Check current term, notice, and buyout conditions
Confirm supplier availability and revised commercial inputs
Approve customer pricing and contractual changes
Coordinate order or delivery work where required
Update recurring and one-time billing at the agreed event

Migration and cancellation

Coordinate the old and new state before closing a service

A migration should connect the replacement service with the service it supersedes, including target activation, dependency, overlap, billing, and closure decisions. A cancellation should verify notice, supplier obligations, buyout, final billing, credits, and customer confirmation.

Do not remove the historical record when the live status closes. The original quote, order, supplier decision, support history, commercial changes, and billing context remain useful evidence.

Review cycle

Use upcoming commercial events to trigger work early

Review renewal and notice dates, unresolved tickets, open tasks, commercial exceptions, supplier changes, and billing mismatches before they become urgent. Assign the next action and keep it with the service record.

A consistent review cycle turns the service inventory into an operational workflow rather than a static list of circuits.

Frequently asked questions

Clear answers for connectivity teams

What should a connectivity service record contain?

It should connect customer, site, product, supplier, order, contract, technical, support, commercial, billing, and ownership information with stable service identifiers.

Can support tickets be linked directly to a service?

Yes. Trunkstar support tickets can be linked to any lifecycle object, including a customer, project, quote, order, or active service.

Which service changes should use a controlled workflow?

Upgrades, downgrades, renewals, migrations, and cancellations should preserve operational, supplier, contractual, billing, approval, and ownership context.

What should be checked before cancelling a service?

Check notice and term obligations, supplier commitments, buyout, dependencies, final charges or credits, customer confirmation, and the evidence required to close the service.

Keep exploring