Roll out employee connectivity

Prepare the employee markets, device mix, approved plan policy, billing structure and the HR or IT workflow that initiates assignments.

Start with a small group whose devices and destinations you can verify. Confirm which continuing plans or travel packages are available for that group before promising a company-wide entitlement.

1. Define the entitlement

Choose the continuing mobile plan or travel allowance for the employee’s role. Record who pays, who can approve additional purchases and how a personal or company-owned number is treated.

Agree on these responsibilities before assigning the first service:

Keep the employee assignment and the underlying service reference together. A change in the HR system should initiate a review or supported service action; it should not be treated as evidence that network service has already changed.

2. Assign the service

Create a subscriber from the employee’s contact, then assign the profile through Assign person on the eSIM or the assignment API. Creating a subscriber prevents deletion of its contact, including after the service ends; subscriber associations cannot currently be removed. Follow the purchase or subscription to fulfillment and retain its references in your employee record.

3. Deliver setup

Send the authorized employee a private installation journey. Follow installation separately from provisioning, and provide a path to help with device compatibility or the setup step reached.

4. Operate the assignment

Review usage observations and unresolved cases with their timestamps. Connect charges to the employee, team or cost center in the company’s billing structure.

5. Complete offboarding

Stop future renewal for any recurring subscription and confirm the effective date. If you intend to retire the profile, release it separately after reviewing the remaining data that will be forfeited. The eSIM API does not provide number transfers or subscriber reassignment. Removing an employee’s application access does not itself end network service.

Troubleshooting

If an employee cannot access installation, verify the assignment and identity before resending private credentials. If a departing employee still owns a number they need, resolve the agreed transfer path before terminating service.

Verify the first assignment

Check that the approved employee receives the correct offer, can install it on the intended device and can use the advertised service. Confirm that support can find the assignment without asking the employee to share a QR code or activation credential.

Trace a charge back to its employee and billing owner. Test a role change or departure against the agreed policy: revoke company access, stop future renewal, and verify any requested profile release. Keep any unresolved billing or number-transfer task visible after the employee’s account is closed.

Use the operations guide to prepare support and the number-porting guide when a rollout involves moving existing numbers.

Next steps

• Assign subscribers through the API.
• Prepare installation.
• Resolve service issues.