Article · 8 July 2026
An AI copilot in a service firm — on the team’s side, not the customer’s
Why a public chatbot damages SLAs, and a dispatcher copilot saves them. RAG, contract citations, and the “I don’t know” rule.
A public chatbot in a service firm likes to promise things that are not in the contract. The customer will remember. So will counsel. That is why the first AI deployment in field service, outsourcing or facilities should sit with the team: dispatcher, account, back office.
What a copilot can do immediately
Ticket classification. A drafted reply with an SLA citation. Similar-job suggestions. A call-out checklist. Translating customer jargon into a CMMS fault code.
What it should not do: send the email, move a crew slot, negotiate a penalty clause.
RAG without a citation is a chat
Index contracts, addenda, call-out rates, SOPs. Every answer either has a source or goes to a senior. “I don’t know” is a valid output. A hallucinated clause 7.2 is not.
Deployment is permissions
Who sees which contract. Who accepts a draft. What you log. That is not a compliance add-on — it is the product. Without it you will not get into larger accounts.
Start with one ticket type and one team. Custodianship: a monthly reject review. That is where you see whether the copilot is learning, or just writing nicely.
