Say you’re at a service desk, trying to explain a noise your car only makes sometimes. You’re remembering when it started, wondering what it might cost, and hoping the person across the counter understands what you mean.
Somewhere in that exchange, they tap a button on a tablet.
You probably don’t know what that tap did. They might have opened your appointment, added a note, or started recording your voice. From your side of the desk, those actions can look exactly the same.
That’s what bothered me about the recording flow I was exploring. A decision that matters to the customer could become a small piece of routine work for the person using the screen.
What the customer came in for
The person at the service desk needs to take responsibility for a visit. That tells everyone who is looking after the customer. Recording the conversation has a different consequence: something said across a counter becomes something that can be played back later.
I want the screen to keep those decisions separate. Taking on a visit should leave the microphone off. When the advisor is ready to record, they should make that choice deliberately.
That also gives the advisor a clearer job. They can get the visit open, check the details, and speak with the customer before dealing with the recording. They shouldn’t have to remember whether accepting the appointment also switched something on.
The pause I would keep
In the two versions I compared, accepting a visit already left recording off. The difference came at the next step. One started the recording straight away. The other asked the advisor to confirm first. Both were working examples using a simulated timer.
I’d keep the confirmation. I want that moment to say whose visit is open and what is about to happen. I want canceling to leave the microphone off, with no doubt about it.
I wouldn’t add a question before every ordinary task. Most of those would soon become another thing to tap past. Here, the pause belongs at the point where the consequence changes.
And once recording starts, the screen has to keep saying so. The advisor should be able to answer “Is this on?” with a glance, even after turning their attention back to the customer.
A question the screen can’t answer
There was a loose end in the design. It still told the advisor to confirm the customer’s permission, but the control for doing that had been removed.
That gap matters more than how polished the recording button looks. The advisor confirming an action on a tablet doesn’t establish that the customer agreed to it. There still has to be a conversation across the desk.
I haven’t tested whether these steps are clear enough for advisors. I’d start by asking someone to accept a visit, begin recording, and then cancel. At each point, I’d ask what they thought the microphone was doing.
I’d also want to know how they would explain the recording to a customer. If the screen gets through its steps while that person is still wondering what they agreed to, there’s work left to do.