What a forward deployed engineer automates, department by department
A practical catalogue of the work Voho's forward deployed engineers go in and automate with AI: contact centre, service desk, finance, HR, procurement, operations and reporting. What is automated, what stays with a person, and how to choose where to start.
"Where should we use AI?" is the question every leadership team asks, and the honest answer is: wherever work arrives as a request, a document or a record, follows rules most of the time, and is already written down somewhere. That describes a surprising share of what an organisation does.
This is the catalogue our forward deployed engineers work from when they go into an organisation. It is not a list of things to automate all at once. It is where to look first, and what to leave alone.
The rule behind every item
- Automate what is high-volume, rule-bound and already recorded.
- Keep a person on anything that needs judgement, carries real liability, or is rare.
- Every automated action waits for the approval your process already requires.
- Every step is logged, so it can be checked and reversed.
Contact centre
| Automate | Keep with a person |
|---|---|
| Answering and resolving routine calls in the caller's dialect | Complaints that need discretion or compensation |
| Verifying the caller and reading back account, booking or case status | Anything the caller asks to escalate |
| Raising tickets, bookings and callbacks in the real system | Vulnerable callers and sensitive cases |
| Outbound reminders, confirmations and follow-ups | Negotiation |
| Transcripts, call summaries and quality scoring on every call | Coaching conversations with agents |
IT and facilities service desk
| Automate | Keep with a person |
|---|---|
| Taking requests by phone, chat or email and raising complete tickets | Major incidents |
| Classification, priority and routing to the right resolver group | Changes to production systems |
| Password resets and access requests, within policy | Exceptions to access policy |
| Status updates to the requester without anyone chasing | Root-cause analysis |
| Facilities work requests into Maximo or Archibus | Contractor disputes |
Finance
| Automate | Keep with a person |
|---|---|
| Reading invoices and matching them to purchase orders and receipts | Approving payments above your threshold |
| Flagging duplicates, mismatches and missing documents | Supplier disputes |
| Answering supplier payment-status queries | Write-offs and credit decisions |
| Drafting month-end reconciliations with the sources attached | Signing off the close |
HR
| Automate | Keep with a person |
|---|---|
| Answering policy questions from the approved handbook, in Arabic and English | Grievances and disciplinary matters |
| Raising leave, letter and certificate requests | Hiring decisions |
| First-round screening questions for high-volume roles | Anything touching pay or contract terms |
| Onboarding checklists across IT, facilities and payroll | Performance conversations |
Procurement
| Automate | Keep with a person |
|---|---|
| Reading quotations and building a like-for-like comparison | Award decisions |
| Checking supplier documents for completeness and expiry | Negotiation |
| Drafting purchase requests from approved templates | Single-source justifications |
Operations, field and plant
| Automate | Keep with a person |
|---|---|
| Drafting maintenance notifications and work orders from alarms and inspections | Anything that writes to a control or safety system — never automated |
| Shift handovers written from the alarm and event log | Deciding to shut down or start up |
| Answering questions from manuals, procedures and P&IDs, with citations | Management of change approval |
| Ranking bad actors from failure history | Turnaround scope sign-off |
Management reporting
| Automate | Keep with a person |
|---|---|
| Assembling recurring reports from the systems that hold the numbers | The interpretation and the recommendation |
| Explaining variances with links to the underlying records | Decisions the report informs |
| Answering ad-hoc questions about the data, with the query shown | Anything going to a regulator unreviewed |
How an FDE chooses where to start
Not by asking which department wants AI. By looking at volume, rules and records. The first week is spent reading the tickets, listening to the calls and walking the systems. The output is a short ranked list: the two or three workflows with the most volume, the clearest rules and the data already in place, plus an honest note on what to leave alone. The first automation goes live on one of those, measured on real work, and each one after it reuses the connectors, permissions and evaluations the first one built. For operations in particular, see forward deployed engineers in oil and gas.
Two things we will not do. We do not automate through hardware we have to install, and we do not promise integrations where a vendor will not grant access. If a workflow depends on either, we say so in the first week rather than the third month.
If one of these tables describes a queue that is costing you today, book a working session and a forward deployed engineer will tell you whether it is the right place to start.
Frequently asked
- What can AI automate in a company?
- Work that arrives as a request, a document or a record, follows rules most of the time and is already recorded somewhere: routine calls, service-desk tickets, invoice matching, HR requests, supplier documents, maintenance notifications, shift handovers and recurring reports. Judgement, liability and rare cases stay with a person.
- Where should we start with AI automation?
- With the workflow that has the most volume, the clearest rules and the data already in place. A forward deployed engineer finds it by spending the first week reading tickets, listening to calls and walking the systems, not by asking which department wants AI.
- Will AI write to our control or safety systems?
- No. In operational settings Voho reads from control systems and historians but never writes to the control or safety layer. Actions go to business systems such as the maintenance system, and only after the approval your process requires.
Keep reading