Whose Problem Is It, Really?
The starting session for teams that treat a complaint as an interruption. It works the thinking behind service, before scripts, before etiquette, before anyone is handed a phrase bank.
Where the Mindset Shows Itself
You can hear it in one sentence: that is not my department. Technically true, and the customer has just learned that your business is a set of departments rather than a company. The gap shows up in the accounts team sitting on an invoice query, the dispatch note nobody chases, the promise sales made that operations never saw. This is the foundation session, the one that comes before phrasing and etiquette, and it is built for whole teams rather than the front line alone.
What the Session Covers
Reading a Request From the Other Side
Restating a customer's complaint from where the customer is standing, which is usually a different problem from the one your system has recorded.
Not My Department, and What Follows It
Where a handover between your own teams becomes a dead end for the customer, and what an employee can do about it without stepping outside their role.
Complaints as Information
Treating a complaint as the cheapest feedback your business will ever get, rather than as an accusation to be managed and closed quickly.
The Journey Behind the Counter
Mapping what actually happens to a customer's order or query inside your business, including the steps the front line has never seen.
Where the Back Office Touches the Customer
Accounts, dispatch, stores and admin rarely speak to a customer and routinely decide their experience. Making that link visible to the people in those seats.
The Standard Nobody Wrote Down
A fast-growing team carries several private definitions of good service. Surfacing them, and agreeing the one your business will stand behind.
Consistency Between Two Desks
Why two employees give the same customer two answers in the same week, and what has to be shared for that to stop.
What Changes Across the Business
Fewer Dead-End Handovers
Employees learn to close the loop or hand it over properly, instead of giving a customer another number to try.
One Answer Per Question
Teams find where their answers diverge and agree what the business actually says about the questions that come up most.
Support Functions See the Customer
Accounts and dispatch learn which of their routine delays turns into a phone call somebody else has to take.
A Shared Vocabulary Before the Skills Training
Later modules on complaints, etiquette or recovery land better on a team that has already agreed what good service means here.
How GullyHR Runs It
Whole-Team Cohorts
We deliberately mix front line and back office in the room, because most service failures in a small business happen in the handover between them.
Your Journey, Mapped in the Session
Participants map your real order-to-resolution flow rather than a textbook customer journey, and mark the points where it breaks.
No Lectures About How You Work
Plenty of Indian SMBs run genuinely good service on WhatsApp, a register and a phone. We build on what already works instead of prescribing a system you did not ask for.
Honest About What Training Cannot Move
Where the session surfaces a structural problem, a step with no owner or a policy nobody can defend, it goes into the report to you.
Start With the Thinking, Not the Script.
Tell us where the handovers break and who ought to be in the room, and we will scope the session around that.
Frequently Asked Questions
Anyone whose work reaches a customer, including people who never speak to one. Accounts, dispatch, stores, admin and HR all shape the experience. Mixed cohorts work better here than single-department ones.
Scoped at the needs discussion. It is often run as the opening session before the complaint-handling and etiquette modules, in which case the sequence is planned together rather than each part quoted separately.
It changes what they are equipped to notice and act on. Whether the habit holds depends on what supervisors reinforce afterwards and whether the business backs the standard when it costs something. We brief supervisors for exactly that reason, and we do not promise behaviour we cannot control.
Yes. Complaint logs, review comments and call samples all work, with customer details removed before use. Feedback from your own customers carries more weight in the room than any case study we could write.