Back to Projects

Dispatch Kickback Tool at Dell

I built a SharePoint tool that kept corrections and feedback with the original repair ticket, so the next reviewer could see what had already been checked.

Dell · SharePoint ·

A repair ticket and a memory module beside an open laptop.

What was the problem?

When a customer needed a laptop or desktop repair, a frontline Tech Support agent created a ticket in ServiceNow, selected the parts and assigned a technician. My team reviewed each ticket in ServiceNow before the technician went out. If a troubleshooting step was missing, we sent the ticket back and explained what the agent needed to check. If a critical part was missing, we added it and told the agent why.

My team sent feedback through Outlook to the agent who raised the ticket and copied the manager. Each email thread covered one ticket, so managers had to piece together separate conversations to see which mistakes kept recurring across the team.

How did we fix it?

I built the Dispatch Kickback Tool in SharePoint. A reviewer on my team copied the ServiceNow ticket number into the tool and selected the Tech Support agent from the company’s Global Address List (GAL). The tool automatically added that agent’s manager and team lead to the feedback.

The reviewer then chose one of two options:

  • Send the ticket back. If a troubleshooting step was missing, we told the agent exactly what to check before sending the ticket back to us.
  • Correct the ticket and send it to the technician. If we could fix the issue ourselves, such as adding a missing part, we recorded what we changed, sent the feedback to the agent and passed the ticket on for repair.

We stored the feedback in Microsoft Access under the original ServiceNow ticket number. If the same case came back to someone else on my team, they could look up that number, read the earlier feedback and check whether the agent had completed the missing step.

How did we use it for training?

We could see which parts agents often missed and which troubleshooting steps caused problems for a particular team. We used real dispatch tickets in training sessions with our customers’ frontline support teams. We showed agents what had been missed, why it mattered for the repair and what to check next time. We also shared short learning flyers on common errors.

What improved?

  • Dispatchers spent 50% less effort recording ticket changes and drafting feedback emails. They also stopped missing one of those steps when they completed the other.
  • With less time spent on each ticket, dispatchers processed 20% more tickets per person per day, on average.
  • Frontline agents used lessons from earlier cases to prepare more complete repair tickets before sending a technician.
View my Dell experience