A lab takes its orders through its own website. A customer reported being unable to finish an order on their phone: no error popped up, the submit button simply did nothing. Testing it confirmed the problem: the exact same order, placed from a computer, went through fine, with its confirmation and attached document. Placed from a phone, it never went through at all, and the screen never said why.
If your business takes orders, bookings, or requests through your website, this is the kind of failure that's hardest to catch, precisely because it never announces itself.
What was actually happening?
It wasn't one cause, it was two at once, and both shared the same trait: neither one showed up on screen.
The first: a non-numeric character had slipped into a field that only accepts numbers. The system rejected it internally, but never communicated that outward. Whoever was filling in the order had no signal that anything was wrong.
The second: the order included a photo attachment, several megabytes in size, uploading over mobile data, slower than an office wifi connection. The screen showed no progress bar and no indication the upload was even running. Whoever was waiting had no way to tell whether the upload was simply slow or whether, in fact, nothing was happening at all.
Both causes together produced the same result from the outside: a still screen, no message, no progress bar, and no order on the other end.
Why had nobody noticed before?
Because a form that fails with a warning is annoying, but a form that fails silently is worse: nobody reports it as quickly. The person tries once, maybe twice, and then stops trying. They don't write in to complain about an error, because they never saw one. They just leave.
From the business's side, that's indistinguishable from a customer who simply chose not to buy. There's no alert, no red line on any dashboard, nothing that says "something got lost here." The order disappears without a trace, and the business never finds out it was one click away from happening.
It was fixed on two fronts: the photo is now automatically resized the moment it's uploaded from a phone, before the system tries to send it, and the screen now shows the upload progressing while it takes its time, so whoever is waiting knows something is happening.
How do you check this on your own website?
You don't need to know how to code to run this test. You need a phone, mobile data (not your office wifi, which is much faster and hides the problem), and ten minutes.
- Go through your own order, booking, or request process yourself, from your phone, using mobile data instead of wifi.
- If any step asks you to attach a photo or document, use a real photo straight from your phone, without resizing it first, and watch what happens while it uploads.
- Type something nobody should type into a field: a letter where only numbers are expected, an extra space, an odd character. Not to break anything, just to see what the screen says when you do.
- At each step, ask yourself: if something went wrong right here, would I find out, right now, just by looking at the screen? Or would everything simply sit still?
If the answer at any point is that you wouldn't find out, you have exactly the same blind spot the lab had. It may already be costing you orders, and you won't know it until someone tells you over the phone, like what happened here, or until nobody ever tells you at all.
The rule that matters here, beyond this one case
A form that "does nothing" when it fails is worse than one that shows an error, because a visible error at least leaves a complaint behind. Silence leaves nothing: no alert, no call, no line in any report. Just an order that never arrived.
This isn't only a lab problem. The same thing happens on a website taking restaurant reservations, on an enrollment form for a school, on a page asking for a photo to process a return. Anywhere someone has to fill something in from their phone, on a worse connection than the one you use to test it from your desk, a similar gap is waiting to show up on the day you can least afford it.
The test you can run today is simple: put yourself in the shoes of your customer with the worst signal, on their busiest day, and go through the whole process from there. What you see, or don't see, will tell you whether your website is losing something you don't even know exists.
This kind of review, checking how your website or software actually behaves before a customer finds the failure instead of you, is part of how we work in our services. And if what you need is to bring the data from every program your business uses into one place, so you stop hearing about problems through a phone call and start seeing them coming, you can see how we did it for a group of pharmacies in this real case.
If you'd like us to check what really happens when a customer tries to buy from you on their phone, get in touch and we'll look at it together.
