A backup internet plan you can actually use during a client call

1. Choose an alternative connection

If your main connection is fibre, a phone hotspot or a dedicated mobile router can be a practical backup to investigate. If your main connection already uses mobile data, test a different underlying network where possible. A second brand does not always mean separate infrastructure, and different providers can still share points of failure.

Start with the equipment you own. Check whether your phone and plan support tethering, then connect your laptop and do a normal piece of work. A dedicated mobile router may make sense later if a phone hotspot proves awkward, unreliable or hard to keep charged.

Use a coverage map, such as MTN's South African coverage checker, as an initial screening tool. Then test the service at your actual address. Indoor reception, congestion and the position of the device can matter to your experience.

Ask your employer or client whether there are connection, VPN or device requirements before committing to a plan. A connection that opens a web page may still be unsuitable for their workflow.

2. Test the work, not only the speed

Try a short rehearsal during the hours you expect to work. Connect to the backup, open the required applications, join a call with a friend, share your screen, and upload a representative file containing only practice data. Check both what you see and what the other person hears.

A speed test is one observation. Also record whether audio breaks up, whether screen sharing remains usable, and whether the connection drops. Repeat the exercise on more than one day before relying on the result.

If you use the supported Teams desktop app, Microsoft's test-call instructions explain how to check your microphone, speaker and camera. Follow that with an actual call on the backup connection to test the wider setup.

Keep a small log:

3. Budget for data and power together

Measure mobile data before and after a representative work session. Use that observation to estimate what your own backup work block might consume, then allow extra capacity. Video settings, uploads and background activity vary, so a universal “one hour equals this many gigabytes” promise is not a good basis for your plan.

Check bundle expiry, permitted usage and the cost of running out. Keep a note of how to top up from your phone. If activating a new SIM requires registration, complete the provider's process before an emergency.

Review background downloads and synchronisation on the laptop, using controls your organisation permits. Do not disable security software or required protection to save data. A large optional update can wait for the main connection; essential work and required security controls take priority.

A phone hotspot also needs a charged phone. If the interruption is electrical, your primary router and ONT may need backup power too. Use the backup-power buying guide to plan the devices together.

4. Write a five-line switching plan

Your plan should be short enough to follow when you are distracted:

1. Save the task and note what was in progress.
2. Switch the laptop to the tested backup connection.
3. Rejoin the call or confirm that the required work tools connect.
4. Send an update through the communication channel agreed with the client.
5. If backup also fails, use your agreed alternative and give a time for the next update.

Set a strong hotspot password and keep the details somewhere you can access without your main connection. Practise the sequence. Some calls will need you to rejoin after a network change; find that out during the rehearsal.

Choose a fallback location only after checking that it is available, that you can reach it, and that working there meets the client's privacy and security requirements. A public space may be unsuitable for confidential calls.

5. Prepare a useful client update

A helpful update explains the effect on the work and your next step. Save an adaptable message, for example:

My primary connection has dropped. I am switching to my backup and will update you by 14:15 SAST. The draft is saved; the upload is the only outstanding step. If I cannot reconnect, I will send a revised delivery time in that update.

Only say the draft is saved if it is. Replace the time and task with the real situation, and use the time zone your client expects. Give a specific next update rather than a recovery promise you cannot verify.

Afterward, spend five minutes reviewing the interruption. Did the backup connect? Was there enough data? Could you find the right contact channel? Adjust one weak point while the experience is fresh. Reliability grows from a plan you keep practising.