Training Jordanian Employees to Manage Internal Service Requests

On Sunday morning, an HR officer at a company headquarters in Amman opens 23 requests. A salary certificate is needed for a bank appointment tomorrow. A new employee starts today with no system access. A meeting room’s air conditioning has failed. A manager wants a headcount report ‘urgently’, and two requests belong to IT. She works in arrival order, and the new employee waits until noon.

Nothing in her inbox was unusual. What was missing was a shared way to decide which request comes first, when to escalate, and how to pass a request to the right department without losing it. Most employee training on service focuses on external customers. Requests from colleagues get far less attention, though support teams such as HR, IT and facilities spend much of their day on them.

This article is for HR teams and business leaders in Jordanian companies whose employees handle internal requests. It sets out employee training on three linked skills: priority sorting, escalation, and handover between departments, built around a timed priority-sorting exercise. All scenarios are hypothetical.

Why Internal Requests Need Their Own Employee Training

Internal customers cannot go to another supplier, so poor handling rarely shows up as a lost sale. It shows up as a new employee without a laptop, a payroll correction that misses the cut-off, or a manager calling three people to find who owns a task. Three habits cause most of it, and employee training can target each one:

• First come, first served: requests are handled in arrival order, whatever their impact.

• The loudest wins: ‘urgent’ in a subject line or a senior name in copy moves a request up the queue.

• Bouncing: a request sent to the wrong team is forwarded without context, or returned to the requester with ‘not our department’.

Employee training that only explains the procedure does not change these habits. Staff needs to practice deciding, under time pressure, with requests that look like the ones in their own inbox.

A Simple Priority Rule: Impact and Time

Before any employee training, agree a priority rule with the heads of the support departments. Keep it to two questions:

• Impact: how much work stops, and for how many people? A team unable to work outranks one person’s inconvenience; anything affecting customers, payroll, or a legal deadline ranks high.

• Time: when does the impact start? A request needed for tomorrow’s appointment outranks one needed next month, whatever the subject line says.

Combine the answers into three levels with agreed response targets, for example, two hours, one working day, and three working days. The targets are a business decision tied to what the company most needs to protect; our guide to linking learning and development to Jordanian business priorities discusses that conversation. Write the rule on one page and use it in every session of the employee training, with one question for any requester who says ‘urgent’: what happens if this is done tomorrow instead of today?

A Priority-Sorting Exercise for Employee Training

The core of this employee training is an in-basket exercise. The format is well established in assessment: the US Office of Personnel Management describes a typical in-basket test as designed to simulate administrative tasks, with participants asked to read and react to a pile of memos, messages, reports and articles. OPM describes it as a selection method; here it is adapted as practice, with feedback instead of a hiring score.

Build the in-basket for the employee training from your own requests, with names and personal details removed:

• Fifteen to twenty requests from different channels: email, a phone note, a messaging-group screenshot, a form.

• A realistic mix: a few genuine priority 1 requests, several marked ‘urgent’ that are not, two or three that belong to another department, and one that needs a decision above the participant’s authority.

• A time limit, such as 25 minutes, so that participants must sort before they can do everything.

For each request, participants record a priority level and one action: do now, schedule, escalate, or hand over. They also write one reply to a requester who must wait. The debrief is where most of the employee training happens: compare sorts across the group, and treat requests ranked very differently as a sign of an unclear rule rather than a weak employee.

The Reply to a Colleague Who Must Wait

Sorting is only half the task; the colleague whose request waits still needs an answer. A good waiting reply confirms receipt, gives the priority in plain words, says when the request will be handled, and names a contact if circumstances change. ‘Received; this is scheduled for Tuesday morning; if your deadline moves earlier, call me on extension 214’ prevents three follow-up messages. Practice this reply in every round of employee training, because it is what the requester actually sees.

Escalation: When and How

Escalation is part of handling a request, not a failure to handle it. Employee training should make the triggers explicit:

• The response target will be missed, and the requester or the work will be harmed.

• The request needs a decision beyond the employee’s authority, such as an exception to policy or an unbudgeted cost.

• Two managers ask for conflicting things with the same deadline.

• The same request has come back for the third time.

Then use the employee training to practice a short escalation message with five parts: what the request is, the impact, the deadline, what has been done and the decision needed. A message like this can be answered in minutes. Copying every senior name onto an email is not escalation; it spreads responsibility until nobody holds it. In the exercise, the request above the participant’s authority tests exactly this message.

Handing Over Between Departments Without Bouncing

Misrouted requests are a frequent reason colleagues lose patience with support teams. Agree on one rule and build it into the employee training: whoever receives a request owns it until another department confirms it has taken it over. In practice, a good handover has three steps:

• Pass it with context: the original request, what has been checked, and why it belongs elsewhere.

• Get confirmation: the receiving department acknowledges it and names an owner.

• Close the loop: the requester is told who now owns the request and when to expect an answer.

Include two or three misrouted requests in every round of employee training so participants practice the full handover, not just forwarding. A clear point where ownership changes is also the core of a three-way handover template between sales, operations and finance, applied there to customer deals.

Checking Real Requests After Employee Training

Run a fresh in-basket at the end of the employee training session and discuss each participant’s differences from the agreed answer. Then look at real work. Each month, a supervisor reviews a sample of closed requests and asks four questions: was the priority right, was the target met, was the request bounced, and did any escalation contain the five parts? Reviewing real outputs this way is the logic behind using work samples to assess learning in Jordanian companies, and it shows employee skills far better than a satisfaction survey can.

Patterns from the review feed the next round of employee training: if facilities requests are often under-prioritized, add more of them to the in-basket; if handovers stall at one department, invite that department to the next session.

A Hypothetical Example: Employee Training for a Shared Services Team in Amman

This example is hypothetical and shows only how the elements fit together.

A pharmaceutical manufacturer with offices in Amman and a plant in the Sahab industrial area runs shared HR, IT, and facilities teams. Plant supervisors complain that requests disappear between departments, while support staff say everything arrives marked urgent. The HR director and the IT manager agree on a priority rule with three levels and then run employee training for twelve support staff from the three teams.

The in-basket for the employee training holds eighteen anonymized requests from the previous month, including a production line stopped by a failed scanner login, a salary certificate needed for a bank appointment, an ‘urgent’ request for new office chairs and a leave correction sent to IT by mistake. Most participants rank the stopped line first but disagree sharply on the salary certificate, so the department heads add ‘external appointment with a fixed date’ to the rule’s time question before the next round of employee training.

After the employee training, supervisors review twenty closed requests each month using the four questions, and each new in-basket adds the requests that caused most disagreement in the last review.

Summary

Internal requests fail in predictable ways: arrival order instead of priority, the loudest voice instead of the greatest impact, and requests that bounce between departments. Employee training for support staff should target those habits directly with a shared priority rule, explicit escalation triggers, and a handover that keeps ownership clear.

A timed in-basket built from your own requests lets employees practice all three in one session, and a monthly review of real requests keeps the practice honest. Kept this specific, employee training gives Jordanian support teams a common way to decide what comes first and who owns what.

Click here. If you would like employee training built around the internal requests your own teams receive, you can discuss your corporate training requirements with the SkillUp MENA team.