Work arrives in whatever form the customer felt like sending it. Your business runs on one system that expects it in exactly one form. Somebody stands in that gap all day.
The job today
Count the ways a new job can reach you. The phone during business hours. The phone after hours, which is voicemail, which is somebody's morning. The website form, which emails somebody. The lead platforms, which email somebody else. A customer who emails a PDF purchase order because that is how their AP department works. A customer who logs into their own portal and expects you to go get it. A text to the owner's cell phone. A photo of a ticket a tech filled out by hand because the app was slow that day.
Each of those is handled by a person who reads it, works out what it is, decides who it belongs to, and types it into the system. The typing is not the expensive part. The expensive part is that each channel has a different person watching it, a different response time, and a different chance of being missed entirely — and nobody can see the whole picture at once.
Then there is the second job, which nobody names: working out whether this is new, or whether it is the same customer who called yesterday about the same thing. Get that wrong and you have two records, two people working it, and a customer who has now explained their problem twice.
What the agent does
It watches every channel, all of them, all the time.
Something arrives. It reads it — the transcript of the voicemail, the body of the email, the fields of the form, the text inside the PDF, the handwriting in the photo. It works out what kind of thing this is and pulls out what the system needs: who, what, where, when, how urgent, what they actually asked for.
Then it checks whether it already knows this person. Existing customer, open job, previous call this week — it attaches to what exists rather than creating a duplicate, which is the failure that quietly costs the most.
It creates the record in your system with the original attached, so whoever picks it up can see the actual email or hear the actual call rather than trusting a summary. It routes it to the right person or the right queue with the context already gathered. And where something is genuinely urgent — the words that mean urgent in your business, not in general — it says so loudly rather than filing it politely.
What it cannot read confidently, it does not guess at. Those go to a person, marked as needing eyes, with the reason it was unsure.
What changes
Response time stops depending on which channel someone used. The after-hours voicemail and the Tuesday-morning phone call get the same treatment, because a system is doing the reading. For a lot of businesses this is the single largest change: the customer who called at seven at night is contacted first thing rather than at eleven, and in trades and professional services that is frequently the whole difference in who wins the job.
The retyping stops. Which matters less for the labor than for the errors — a transposed digit in a phone number costs a job, and it always came from somebody retyping.
And you get one view of everything that came in. Right now, if you asked how many new inquiries you received last month, you would have to add up four systems and guess. Afterwards, it is one number that includes the voicemails.
What it connects to
Every channel you actually use. The mailbox or mailboxes, the web forms, the phone system for voicemail and its transcripts, the lead platforms, the portals your bigger customers make you log into. The portals are the awkward ones — most have no proper connection available, so it is a login and a scrape rather than an integration, which works but needs watching when the vendor redesigns their site.
Your system of record. The CRM, the field service platform, the practice management system, the job system — whatever holds the customer and the work. It needs to both read it, to recognize existing customers, and write to it.
A confidence line and a review queue. This is the decision that determines whether the whole thing is trusted. Anything the agent is not sure it read correctly goes to a person rather than into the system. Set that line too loose and someone finds a garbled record and stops believing any of them; set it too tight and you have rebuilt the manual queue. It starts conservative and gets loosened once you have watched what it actually gets wrong.
And a rule for the ambiguous ones. Some messages are not a new job and not an existing one — they are a complaint, or a supplier, or somebody selling you something. It needs somewhere to put those that is not your dispatch board.