Urgent, and from someone you do not know
A call comes in on a Friday afternoon. The caller says they are the office manager at one of your business mobile customers. A director has lost their phone on a train and needs a new SIM today, on the same number, sent to a home address. Your support person wants to help. They also do not recognise the name, and the address is not on the account.
The same week, you get an email asking for PAC codes on three lines, a request to bar international calls on a leaver's number, and a request to move a user to a bigger data plan. Each one goes to your mobile distributor's portal in a different place. One of them, the PAC request, is quietly the first sign that the customer is moving those lines elsewhere.
Each request is quick. What is slow and risky is working out whether the person asking has the right to ask.
Then there is the paperwork after. The lost handset needs recording against the account, the replacement needs posting, and the leaver's phone is still in a drawer at the customer's office. None of that is written down anywhere your team can see next week.
Why mobile requests go wrong
- Authorised contacts are recorded when the account opens and rarely updated.
- Requests are urgent by nature (a lost phone, a leaver), which pushes staff to skip checks.
- SIM swaps and PAC or STAC codes are exactly what a fraudster asking in a customer's name would want.
- Each request type is done in a different part of the distributor's portal, with no shared record.
- Retention signals, such as a PAC request, go unnoticed because they look like admin.
Your team is caught between helping quickly and checking properly, with nothing to make checking quick.
What mistakes cost
| Mistake | Consequence |
|---|---|
| SIM swap for an unauthorised caller | Customer's number in the wrong hands |
| Lost phone not barred promptly | Usage charges the customer disputes |
| PAC request not flagged | Lines leave with no retention attempt |
| Leaver's line left active | Rental and usage on a line nobody uses |
| No record of who asked | Disagreement about who approved what |
A mobile request flow with checks built in
- Each customer has an up to date list of authorised contacts and what each may request. The list is confirmed with the customer periodically, prompted by the system.
- Requests come in through a form, email or a call logged by your team. The system checks the requester against the authorised list.
- For sensitive requests (SIM swaps, PAC or STAC codes, changes of address), the system sends a confirmation to a known contact on a known number or email before work starts. Your own verification rules decide what counts as enough.
- Each request type follows its own checklist: for a lost phone, bar first, then swap; for a leaver, bar or cease, then recover the handset; for a tariff change, check the effect on the contract.
- PAC and STAC requests alert the account manager, with the lines, contract dates and any early termination charges, so a retention call can happen first where appropriate.
- Every request is logged with who asked, who approved, what was done in the distributor portal and when.
The flow does not replace your distributor's own checks. It adds yours, consistently, so the answer does not depend on who picks up the phone.
What the team gets
Support staff can act quickly when the requester checks out, and have a clear reason to pause when they do not. Lost phones are barred first, not after a long conversation. Account managers see PAC requests on the day, with what is at stake. And if a customer ever asks who authorised a change, the answer is on the record.
New starters in your support team pick it up quickly too, because the checklist for each request type tells them what to do in what order. The knowledge that used to live with one experienced person is now in the flow.
Signs you need this
- Authorised contacts on mobile accounts are out of date.
- SIM swaps are approved on the caller's word.
- PAC requests reach account managers late, or not at all.
- Leavers' lines stay active after they go.
- There is no single record of mobile account changes.