CX Outlet logo CX OutletCustomer experience, made practical for small businesses
Customer Service

How to Hand Over a Customer Issue at Shift Change

I keep complaint logs for a living, and the single most boring pattern in them is this: a customer explains a problem at ten past four, the person they explained it to goes home at five, and the next call about it starts from zero.

Two shop staff standing at a counter at closing time reading a handwritten handover card together

I keep complaint logs for a living, and the single most boring pattern in them is this: a customer explains a problem at ten past four, the person they explained it to goes home at five, and the next call about it starts from zero. The customer is not angry about the original fault any more. They are angry that they had to tell the story twice.

In the last set of logs I went through for a two site bike shop, 31 of 104 repeat contacts over three months traced back to a shift boundary. Nobody had been rude or lazy. The issue simply had no owner between five and nine the next morning, and an issue with no owner behaves exactly like an issue nobody is working on.

What actually gets lost at the boundary

It is rarely the facts. Most small businesses write the facts down somewhere, in a ticket, a notebook or a chat channel. What goes missing is three other things, and they go missing in a predictable order.

First, the promise. Somebody told the customer that a call would come back today. That sentence usually lives nowhere except in the memory of the person who said it. Second, the tone. The note says the customer wants a refund; it does not say the customer was close to tears about a wedding gift. Third, the next physical action. A ticket that reads "awaiting supplier" does not tell the morning shift who is meant to chase the supplier or when.

So a handover that only passes facts is not really a handover. It is a filing exercise that happens to occur at five o'clock.

The six fields that make a handover note usable

I have tried long templates and nobody fills them in. Six fields is the most I have seen survive a busy Saturday. The shop I mentioned above printed these on a card taped beside the till.

FieldWhy it is thereExample entry
Customer and reachSo nobody has to search for the numberMarta R, mobile ending 4471, prefers calls after 2pm
What they asked for, in their wordsStops the issue being quietly reclassified"I want the same model, not a repair"
What we promised and by whenThis is the field that prevents repeat callsCallback before 6pm today, said by Dev
Next action and ownerAn action without a name does not happenAna to email supplier for stock date, Monday 9am
Mood, one lineLets the next person pitch the call rightPatient but has called twice, gift for Saturday
What has already been offeredStops the second person undercutting the firstFree collection offered, no discount mentioned

The last field matters more than it looks. The fastest way to turn a solvable complaint into a grievance is for the morning person to offer less than the evening person did. I have watched that happen twice in one week at a dry cleaner, and both customers stopped coming.

Say it out loud, then write it down

Here is the part that most advice gets backwards. Nearly every guide on this says to get everything into the system so that the record is the handover. In my experience the written record is necessary and not sufficient, and treating it as sufficient is why handovers keep failing in shops that have perfectly good software.

A note gets read when someone goes looking for it. At nine in the morning with a queue forming, nobody goes looking. What makes a handover stick is a spoken sentence with a name in it, said while both people are standing there. Sixty seconds, three items, out loud.

"Two open things. Marta R is expecting a call from us before six, and I have not made it, so that is yours. The Kowalski repair is waiting on a part, nothing needed until Thursday."

That is it. The note holds the detail; the spoken line transfers ownership. When a shop of four people added that ritual at the end of each shift, repeat contacts in their log fell from 31 in a quarter to nine in the next one. I would not swear the handover was the only change, because they also started logging complaints more consistently, but the direction was unmistakable.

If the handover happens by message instead of in person, make the message end with a question. Something as plain as "can you take Marta's callback before six" forces a reply, and a reply is proof of transfer. A broadcast into a channel is not a transfer, it is an announcement.

Promising a time, and keeping it when the shift ends

People worry about promising a callback time when they will not be there to make the call. The instinct is to stay vague, so you say someone will be in touch as soon as possible. That phrase is the single most common line in the complaint logs I read, and it is almost always the line the customer quotes back when they escalate.

Say the name and the window instead. "I finish at five, so Dev will call you between five and six." Three things happen. The customer stops wondering. Dev inherits a specific obligation rather than a vague one. And if it slips, the customer has a name to ask for, which keeps the second call short instead of starting over. The mechanics of that second call are worth reading on their own in when a customer calls back about the same problem.

One caveat. Never hand a name to a customer without handing the issue to that person first. Telling Marta that Dev will call, and then not telling Dev, is worse than saying nothing.

The end of day sweep that catches strays

Handovers cover what somebody remembered. The sweep catches what they did not.

Ten minutes before closing, one person scans the day for anything still open: unanswered voicemails, a message left on read, a bag behind the counter with no note on it, a chat window closed without a resolution. Anything open gets a line on the handover card or, if it cannot wait, a call made before the door is locked.

At a hardware shop I worked with, the sweep caught an average of 1.4 items a day that nobody would otherwise have mentioned, and the most common one was a customer who had been put on hold and then dropped. That particular failure has its own fix, covered in how to put a customer on hold without annoying them, but the sweep is what stops it turning into a silent weekend.

Start the sweep this week with a single sheet of paper and the six fields. Do it for ten working days, then read the sheets back as a batch. The patterns in your own handwriting will tell you which part of the day leaks customers, and that is a more useful answer than any template I could give you. More on the service side of this sits in the service section.

FAQ

Who should own an issue overnight, the first person or the manager?

The person on the next shift who can actually act on it. Parking everything with the manager looks tidy and creates a bottleneck by Tuesday. The manager's job is to check the card was cleared, not to be the default owner of every open item.

Does a handover note need to be in the ticketing system?

Eventually, yes, because that is where patterns show up later. For the handover itself, a card by the till that both people can see beats software neither of them opens mid shift. Transfer it into the system during the sweep.

What if the customer calls back before the new shift has read the note?

Say that you have the details in front of you, then read the customer's own words back from the note before asking anything new. Repeating their phrasing is what tells them the story did not have to be told twice, and it buys you the twenty seconds you need to catch up.

How do you handle a handover between two different sites?

Treat it as a phone call, not a forwarded note. Two minutes of voice between the two people, with one named owner agreed at the end. Written only, across sites, is where I see the longest delays in any log I read.

TA
Tanvir Ahmed

Tanvir writes about using feedback and handling complaints, turning difficult moments into stronger customer relationships.

More posts by Tanvir

More in Customer Service

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto