What to say when a customer calls asking “so what’s happening with my phone?”

A customer does not call because they are bored. They call because they do not know what is happening with their device and are afraid it has been forgotten. Almost every hard conversation in a repair shop happens because the customer did not learn something in time. So the main rule is simple: the customer should hear bad news from you, and before they ask.

Below are eight situations every shop runs into and what to say in each. The phrases are not a script to read aloud but an example of tone and content.

Before you answer: know what is going on with the device

The worst answer is "let me check", followed by five minutes of silence and then "the technician isn’t here, call back tomorrow". To answer in ten seconds, the front desk needs to see three things: the repair status, the promised deadline and the technician’s latest note — what they did and what they are waiting for. Without that at hand, no amount of good phrasing will help.

And one more thing: if you promised to call back, call back, even with no news. "No news yet, the part is still on its way, I’ll ring you on Thursday" is news too. The customer takes silence as "they’ve forgotten me".

It works best when one person answers the phone — the front desk or the manager, not whoever happens to be nearest. Do not pull a technician away from the soldering iron: they will answer briefly and technically, while the customer needs not a board diagram but a clear answer about what happens next and when.

Every conversation goes on the job

A week later nobody remembers who called, what was promised or what amount the customer agreed to. So after every conversation where something was decided, add one line to the job: "12 Oct, customer called, agreed to replace the charging controller, €85 in total, ready on Friday". Then the next person to pick up the phone continues the conversation instead of starting it over.

In the software, job comments do this: everyone who opens the job sees them, with the date and author. If you keep paper records, write on the back of the job sheet copy. What matters is that the note is where people will look for it, not in one person’s memory.

1. Diagnostics are dragging on

The customer was promised an answer in a day, and three have passed. Do not hide behind general words — say what exactly is going on and when there will be an answer:

"Emma, the fault turned out not to be where we first thought: the power circuit is fine, the problem is deeper, on the board. The technician is checking it so we don’t replace anything unnecessary. I’ll give you the exact price and date by tomorrow lunchtime."

A specific reason and a specific time calm people better than "we haven’t got to it yet".

2. The part has not arrived

The deadline slips through no fault of yours, but that does not make it easier for the customer. Say what happened, what you have done and what they can do:

"The supplier has moved the shipment, the part will be here on Monday. I’ve already checked with another supplier — they don’t have it. If you need the device urgently, you can take it now unrepaired, and when the part arrives we’ll take it back in without queueing."

A choice, even an awkward one, feels like respect to the customer. No choice feels like "nobody asks us".

3. The repair will cost more

The hardest conversation, with the most important rule: do nothing beyond what was agreed without the customer’s consent. First the call, then the work:

"During the repair we found that besides the charging port, the power controller is damaged too — without it the device won’t charge. That’s another €35, €85 in total. Shall we go ahead? If not, we’ll return the device in the condition we received it, and diagnostics are €10 as agreed."

Give the full price, not "a bit more", and always offer the option to decline. Write the answer on the job: who agreed, when and to what amount. That settles the argument if one comes up at collection.

4. The repair is impossible or not worth it

There are no parts, or the repair costs more than a new device. Say so plainly and help the customer decide:

"Honestly, the repair will come to €240, and the same device costs about €280 new right now. I wouldn’t recommend it. We can return the device, and if there is important data on it, we’ll try to save that separately."

A customer who was honestly turned down often comes back with another device. A customer who was talked into an expensive repair does not.

5. The device is ready, but the customer does not come

A finished device sitting for months takes up a shelf and ties up money. Remind the customer calmly, but with a date:

"Hello, this is the repair shop on Station Road. Your laptop has been ready since the 12th. Just a reminder that free storage is 30 days, until 12 November. When would suit you to collect it?"

Storage terms should be on the job sheet the customer signed at intake. Then a reminder is not a complaint, just a fact.

6. The customer is angry

The deadline slipped, the price went up, or the customer is simply tired of waiting. Do not argue with the emotion — acknowledge the problem first, then give specifics:

"I understand, you’ve been waiting a week instead of three days, and that’s frustrating. Here’s where things stand: the part arrived yesterday, and the technician is fitting it today. I’ll call you before seven this evening to tell you it’s ready."

Avoid "it’s not our fault", "these things happen", "we’re very busy". Even if true, the customer hears "we don’t care".

7. The customer asks for a discount

Everyone haggles, and that is normal. The trouble starts when the discount depends on who picked up the phone. Decide in advance who can lower prices and by how much, and say so openly:

"Our labour price is the same for everyone, so I can’t move on that. What I can offer is a cheaper part — not original, but with a three-month warranty. That saves you €25."

Instead of a discount on labour, offer a choice of part or turnaround. The customer gets a solution, and you do not teach everyone to haggle.

8. Back under warranty, but with a different fault

You replaced the charging port, and a month later the screen does not work. To the customer it is "you broke it"; to you it is a different fault. Look first, then talk, and talk in facts:

"We replaced the charging port, and it works — look, the device is charging. The screen is a separate fault; there’s an impact mark in the corner. Our warranty doesn’t cover that, but we’ll look at it free of charge and give you a price."

This is where the job sheet saves you: it records exactly what was repaired and what condition the device was in at intake.

A call or a message

Anything about money and deadlines is better confirmed in writing — by WhatsApp, text or email. A call is quicker, but a week later everyone remembers it differently. A short message such as "As agreed: power controller replacement, €85 in total, ready on Friday" settles the argument before it starts.

What never to say

• "Oh, it’s nothing." You do not know that yet. If the "nothing" turns out to be the board, those are the words the customer will remember.
• "Definitely tomorrow." Give a date with a condition: "tomorrow, if the part fits".
• "The technician did something or other." Either you know what was done, or you say "I’ll check and call you back".
• "It’s your own fault." Not even when there is coffee in the device. State the fact without judgement: "there are traces of liquid on the board, and the warranty does not cover that".

How to get fewer of these calls

The best conversation is the one you never have to have. Most "so what’s happening" calls disappear once the customer knows three things without calling: the deadline, the status and when to collect. The deadline is on the job sheet at intake. The status is in the customer account, where they can see which stage the repair is at. And a ready notice goes by email as soon as the device is done.

In ServiceCenterSoft the ready notice goes out in the customer’s language, and the email log shows whether it was delivered. The customer account shows their repairs, view-only. More on the customer notifications and repair workflow pages, which explain how to spot overdue jobs before the customer does.

In short

• The customer hears bad news from you, before they ask.
• A reason, a specific time and a choice — in every hard conversation.
• Nothing beyond what was agreed without a call and consent recorded on the job.
• Promised to call back — call back, even with no news.
• The customer should know the deadline, status and readiness without having to call.