The Team Waiting on You Is a Customer Too
Sales waits on accounts, the plant waits on stores, everyone waits on HR. This session applies a service standard to the requests your people make of each other.
Where Internal Requests Die
Nothing in a business fails as quietly as a request between two departments. A reimbursement sits with accounts. A material indent waits at stores. An offer letter stalls with HR, and the hiring manager finds out when the candidate declines. Nobody is being obstructive; the request simply had no owner, no acknowledgement and no date on it. This session treats those requests the way a good service desk treats a customer, using the same method your customer-facing teams learn.
What the Session Covers
Acknowledgement Is Not the Answer, But It Is Owed
A prompt acknowledgement with a realistic date removes most of the chasing that clogs internal groups and inboxes.
Yes, No, and Not This Week
Declining or deferring a colleague's request with a reason and an alternative, rather than going quiet and hoping it is forgotten.
Dates People Can Plan Around
Committing to a date you can meet, and telling the other team early when it slips instead of on the day it was due.
The Handover That Loses Things
Where work changes hands, sales to operations, operations to accounts, HR to payroll, and what a complete handover has to carry with it.
The Escalation That Is Not an Attack
Raising a stalled request to a manager without it reading as a complaint about a colleague, and without copying half the company on the mail.
Requests in the WhatsApp Group
Most internal service in an SMB happens in group chats. What belongs there, what needs a mail or a ticket, and how a request stops getting buried under the next message.
Follow-Through to Closure
Owning an outcome rather than an action. The request is done when the other team can proceed, not when your part left your desk.
What Changes Between Teams
Less Chasing
People stop spending the first hour of the day following up on requests that were never acknowledged in the first place.
Fewer Escalations to the Owner
Two departments settle a stalled request between themselves instead of putting the promoter in the middle of it.
Handovers Arrive Complete
Fewer restarts caused by a transfer that was missing the reference, the approval or the context behind the request.
A No People Can Work With
Teams give a clear refusal with a reason and an alternative, which is more useful to the other side than a silence that reads as a maybe.
How GullyHR Runs It
We Map Your Actual Internal Flows
Participants map the requests that pass between their departments and mark where they stall, so the session works on your bottlenecks rather than illustrative ones.
Mixed-Department Rooms
The two teams who disagree about a handover practise it together, in front of each other. That conversation does not happen on its own at a desk.
Service Method, Internal Setting
We use the same acknowledge, investigate, resolve, close structure your customer-facing teams learn, so the business runs one method instead of two.
Behaviour and Structure Kept Separate
Some internal friction is manners. Some is a missing owner, or an approval routed through one person who travels. We report which is which rather than training a structural fault.
Fix the Handover, Not Only the Manners.
Tell us which requests keep stalling between your teams, and we will build the session on those.
Frequently Asked Questions
The departments that hand work to each other, typically HR, accounts, stores, operations, sales and admin. Sending one team alone limits what the session can do, because internal service is a two-sided habit.
Scoped per engagement. How many departments you include, and whether you want a follow-up session on the flows you agreed, both affect it. We plan it at the needs discussion rather than quoting a fixed format.
Both. On site works better where two departments need to be in the same room; online suits teams split across branches or shifts, with breakout practice.
Only the part caused by how people handle each other's requests. If every approval sits with one person, or a team is short-staffed, or a system forces rework, that is structural and training will not move it. We name it in the report rather than pretend the session solved it.