Duplicate Subscriber Records: Merge or Correct Carefully

This guide covers Duplicate subscriber records. Start with the checks below. Then compare your result with the example before changing a live service. Duplicate customer entries can split payments, tickets and network identities. Investigate the relationship before removing anything or assuming identical names refer to the same person.

Duplicate subscriber records: practical checks

1. Compare account identifiers, payment references and access usernames.
2. List active entitlements and open support issues on both records.
3. Use a supported correction process that preserves necessary history.

Duplicate subscriber records: a working example

Two accounts named John can represent different households. A genuine duplicate needs a reviewed correction, while similar names alone are insufficient evidence to combine records.

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.