Service call requests

The pain

A service request is a revenue event that looks like an email. It arrives with the equipment half-identified, the site named the way the customer says it rather than the way your ERP spells it, and no serial number at all. Someone reads it, works out which customer and which asset it refers to, chases what is missing, and types it into the system dispatchers work from.

That reading and retyping is where service margin goes. Requests sit unread in a shared mailbox while the customer assumes work is scheduled. Two people open the same request twice. A request that should have been a warranty claim gets opened as a billable job, or the reverse. And because the queue only reflects what someone got around to typing, the backlog nobody has entered yet is invisible to the people planning capacity.

The cost is not the typing. It is response time on a customer who is already having a bad day, and a dispatch board that does not match reality.

How it works

• Capture from every channel: requests are picked up from shared service mailboxes, portal submissions, and notes written up from phone calls, into one queue.
• Resolve the entities: customer, site, and equipment are matched against your master data, so "the chiller at the Fresno plant" resolves to an asset record rather than to a guess.
• Chase what is missing: incomplete requests are followed up in the original thread until they are complete enough to dispatch, instead of landing half-formed on the board.
• Open the record: a complete, routable service record is created in your ERP or field-service system, linked to the original request. Judgement calls pause for a person: warranty versus billable, priority, a customer on credit hold.

What you get

• Requests acknowledged and opened the day they arrive, not when someone reaches the mailbox.
• A dispatch queue that reflects everything that has come in, so capacity planning works from real demand.
• Fewer duplicate and miscategorised jobs, and fewer of the credits that follow them.
• Full traceability from the customer's original message to the service record.