PJM Studios / Client Success Stories / Helpdesk System

A helpdesk for a company too small to have one.

A forms-based helpdesk that routes incoming requests to the right department automatically and keeps requesters informed, replacing an inbox one person could no longer keep up with.

ClientConfidentialFive-person organization: Marketing, Ops, Sales, Dev
PillarAutomateLead & Response Automation, Business Automation
Built withCustom codeRouting logic over Google Sheets and the site form
StatusIn serviceMetrics feeding monthly board reporting
0 manual triageRequests forwarded by hand, per week
4Departments routed automatically
MonthlyHelpdesk KPIs in board reporting
ImmediateAcknowledgement with a ticket ID

Challenge

At a five-person organization spanning Marketing, Ops, Sales and Dev, every incoming question, request and piece of information from clients landed in the same place: the Ops inbox.

There was no routing, no status tracking, and no way to know whether something had been picked up or was still sitting unanswered. The volume became too much for one person to triage on top of her actual job, and requests that belonged with Sales or Dev regularly sat with Ops far longer than they should have.

Context

The organization did not need a helpdesk platform licence or a new CRM. Both would have been more software than the problem justified, and both would have needed someone to administer them.

What it needed was a way to take requests that were already arriving through the website and get them to the right person automatically, with visibility for the team and for the person who submitted the request.

Strategy

The approach was to intercept requests at the point of entry, the Contact Us page, rather than downstream in an inbox. If the system could work out where a request belonged the moment it arrived, the manual triage step disappears entirely, and the requester gets an immediate acknowledgement instead of silence.

Status tracking went in from the start rather than being added later. The original problem was not only misrouted requests. It was having no visibility into whether anything was being worked on at all.

Execution

A form on the Contact Us page replaced the general inbox as the entry point. When someone submits it:

What happens on submission

  1. They pick from a list of issue and topic options relevant to their request.
  2. The system reads the submission, combining the selected category with keyword matching against the request itself, and determines which department it belongs to: Marketing, Ops, Sales or Dev.
  3. The requester immediately receives a confirmation email carrying a ticket ID and a status of open.
  4. The request is routed to the right team member, who responds through the system rather than from their own inbox.
  5. That response updates the ticket status and is relayed back to the original requester, so nobody is left wondering whether anyone saw their message.

Helpdesk volume, response times and topic mix are tracked and rolled into the organization’s monthly board reporting, giving leadership ongoing visibility into a workflow that was previously invisible.

Built with

Custom routing logicGoogle SheetsWebsite contact formAutomated email

Results

What actually changed

Result

No before-and-after study

There is no formal time study on this one, and it is presented honestly as such.

Result

Triage stopped being a person

An Ops team member who was struggling to keep up now works from a system that routes requests for her and keeps requesters informed automatically.

Result

The invisible became measurable

Volume, response time and topic mix became numbers, and those numbers now appear in the monthly board report.

Result

Room to grow into

The bottleneck would only have got worse as the organization grew. It no longer exists.

What it taught me

Not every automation produces a clean percentage improvement, and it is better to say so plainly than to invent one. The value here was structural: turning an ad hoc, one-person inbox into a system with routing logic, status tracking and reporting. For a small team the win is not always faster. Sometimes it is sustainable.

Related

Lead and response automation →Business automation →