Customer Move Between Sites: Preserving Paid Internet Time

This guide covers Customer move between sites. Start with the checks below. Then compare your result with the example before changing a live service. Moving a subscriber between sites changes network assignment and may change the access method. Review the paid entitlement and target service before treating the move as a new subscription.

Customer move between sites: practical checks

1. Record the current paid-through date and package terms.
2. Check the target site's supported access method and capacity.
3. Test the replacement connection and document any agreed service change.

Customer move between sites: a working example

A tenant moving to another managed building may still have paid time remaining. Preserve the original record while deciding how the new site should deliver the agreed service.

First, write down the starting state and the expected result. Then make one controlled change. Next, compare the result with the example above. Finally, record what changed and who should follow up. Keep private account details out of shared notes.

Where LinkDesk fits

LinkDesk includes customer-service workflows, a customer portal, support tickets and transactional SMS integration. Confirm the available action and staff permissions on your installed version. The proposed operating process should not be confused with a promise of automatic handling.

For the tool or product details behind this guide, see LinkDesk features and current limits. The checklist and example above are WayaDesk’s operating guidance.