AI voice intake end to end: Three calls, one job to sign-off

FM voice intake and execution from a phone call to a closed job with the helpdesk AI intake agent. Three calls to the helpdesk. One gives the agent everything it needs. One leaves out the site so the agent asks. One falls outside the service scope so it goes to your team. No menus, no forms, no rekeying.

Scenario one. The caller gives the site and the fault in one sentence. 7:12 in the morning. City center mall opens at 10:00. David Harris runs operations for Northwind retail stores here at North Tower and at Airport Retail.

Good morning, facilities helpdesk. How can I help? Hi, the generator alarm is sounding at City Center Mall and we've lost main power to the ground floor.

I'm logging this as urgent. May I have your name, please?

David Harris, Northwind retail.

Thank you, David. I've logged a generator fault at City Center Mall ground floor category electrical priority high. The electrical team has been notified and your reference is work order 27.

Great. Thanks. No buttons, no forms. The agent took the site, the fault, and the urgency from what he said and gave him a reference before he hung up. 0713. Work order 27 is already in Facilio CMMS in the same list as the ones raised by email. Same list, same team, however it arrived.

Every field comes from the call. Raised by is David Harris matched to the Northwind retail contact so the right client and SLA apply. The site is City Center Mall ground floor. The subject is rewritten into a clear description. Category electrical generator priority high because he said the power was lost. He never said electrical and never said a priority.

Created by Helpdesk AI. The created time is when the call began, so the SLA clock starts the moment David rang. The recording and transcript are attached and the electrical team is set, ready for dispatch. Nobody typed a word. Scenario two. The caller leaves out the one detail a work order can't go without.

7:40. David calls about North Tower, but he doesn't say so. Facilities helpdesk. How can I help?

Hi, it's David Harris again. The main distribution board on level 3 keeps tripping. We've reset it twice, but it keeps going off.

No site. The agent doesn't guess, and it creates nothing yet.

Thanks, David. So, I can log this correctly. Could you please tell me which site or building this is at? And is there any burning smell, heat, or sparking at the board?

It's at North Tower, level three. No smell, nothing like that. It just trips.

Thank you. I've logged a tripping main distribution board at North Tower, level 3, priority high. Your reference is work order 28. Please keep the panel closed until the technician arrives. One question asked once. The missing site plus a safety check. A conversation, not a menu, and the same way the agent asks on email.

Work order 28 is in Facilio CMMS above 27 north tower level 3. The description has the two resets and the safety answer and the transcript shows the work order was created only once the site was confirmed. Both work orders run the same path. Here's the generator job.

Back to city center mall 716. Omar Hadad the helpdesk manager clicks assign to engineer electrical team Bruce gold save submitted becomes assigned Bruce gets the job on WhatsApp with the site fault and priority no app to learn he taps accept 721 in progress with the actual start stamped 750 the changeover relay has failed so Bruce pauses the job and the reason is recorded 8:25. One word and the clock is running again. Both land on the work order timeline.

9:05. Power is back. To resolve, Bruce must send an after photo and his remarks. Without both, the job stays open. And resolved isn't closed. It now needs the supervisor's approval. Sarah Mitchell, the helpdesk supervisor, sees the photo, remarks, and pause in one message. One tap and work order 27 is closed.

9:21 David hears back on WhatsApp what was wrong and what was done well before the doors open at 10:00. Nobody had to remember to call him. In Facilio CMMS, the work order keeps the full story. the call and transcript, the photo, both sets of remarks, and the actual times. Work order 28 follows the same path.

Scenario three, out of scope and still not dropped. 10:35. This time it's the airport retail store.

Facilities helpdesk. How can I help?

Hi, David Harris from Northwind Retail. We have a pest control issue at airport retail. There are rodents in the back store room and we need this dealt with immediately.

I understand, David, and I've marked this as urgent. It falls outside our standard service scope, so I've passed it to the helpdesk team to review. You'll hear back shortly. Your reference is H- I06. No work order, it shouldn't raise, and no dropped call. David knows exactly what happens next.

10:36. The request is in the human intervention queue tagged out of scope alongside exceptions that came in by email one queue whatever the channel. It carries everything from the call, the reason it was routed and an urgency flag because David said immediately. No work order yet. That's a decision for a person.

Omar gets the alert on WhatsApp and raises a vendor job with ShieldGuard Pest Control for today. It becomes work order 29. 10:48 13 minutes after he called, David hears back. A specialist is booked for this afternoon. Out of scope, never out of sight.

Three calls, two work orders from plain speech, one exception handed to the right person. Every call answered, every request accounted for.