Working With Patchy Connectivity

Software is designed on fast connections in offices and used in car parks, basements, lifts and buildings with thick walls. For the teams described in field teams, site visits and the mobile inbox, that gap is not an edge case — it is Tuesday. Our guide to running the whole CRM from your phone finishes with the practicalities of working where the signal is not reliable.

Know what happens to a message you send

The single most important behaviour is what the app does when you press send with no connection. There are two possibilities and they are very different: the message is queued and delivered when signal returns, or it fails and is lost along with whatever you typed.

Test this deliberately — put the phone in flight mode, send something, and see what happens. Everyone assumes queuing; not every app does it, and finding out the hard way means a customer who was never told their appointment moved.

Ticks are not decoration

In poor coverage the delivery indicator is the difference between knowing and hoping. A single tick means it left your phone; a double tick means it reached the recipient. Teach the team to look at it before walking away from a conversation.

The habit worth building: when you send something that matters — a rescheduling, a price, an arrival time — glance at the tick before you put the phone away. Ten seconds there prevents the conversation that starts "I never got that".

“

Send it, then look at the tick. In bad coverage that glance is the whole difference between told and assumed.

— be digital ai team

Read before you go in

The reliable habit for buildings with no signal is to load what you need beforehand. Open the customer's conversation and the job details in the car park, where there is coverage, rather than in the basement where there is not.

The same applies in reverse: write your notes and take your photos on site, and expect them to send when you come out. What you must not do is assume you can look something up while standing in front of the customer — that is the moment the connection is worst and the cost of not knowing is highest.

Habits for bad coverage

• Text rather than voice notes when signal is weak; a forty-second recording needs far more bandwidth than a sentence.
• Compress or delay large photos. Four full-resolution images on a weak connection will sit in the queue for a long time.
• Prefer short, complete messages over a stream of fragments, since each one is a separate delivery that can fail.
• Do the important message first, while whatever signal exists is still there.

None of these are software features. They are working habits, and they are worth saying out loud to a field team rather than assuming everyone works this way.

What to check before you rely on it

Three questions settle whether a mobile client is usable in your conditions. Does it queue outbound messages reliably? Does it show clearly when it is offline, rather than appearing to work? And does it keep recently viewed conversations readable without a connection, with the context described in what actually works better on mobile?

The second matters more than people expect. An app that silently behaves as though everything is fine while nothing is sending is worse than one that says plainly it has no connection — because the person carries on working and finds out an hour later that none of it happened.

Automations are unaffected

One useful reassurance: workflows run on a server, not on anyone's phone. A reminder scheduled for tomorrow morning goes out whether or not the person who set it up has signal, and a follow-up sequence continues through a week of bad coverage.

That is a strong argument for automating the messages that must not be missed rather than relying on someone remembering to send them from a van. The routine confirmations and reminders described in automating appointment booking on WhatsApp are exactly the traffic you want off human hands in a field business.

Design the process around it

Where connectivity is genuinely poor for a whole team — rural service areas, underground work, large industrial sites — build it into the process rather than fighting it. Confirm the day's jobs in the morning while everyone has signal, set customer expectations that updates come at intervals rather than instantly, and let automations rather than people carry the routine messages, since a scheduled reminder does not care that the technician is in a cellar.