Learn
Can AI agents run front-office work, or only back office?
How front-office and back-office processes differ for an agent platform, and what stays the same.
The short answer
Both. Back-office work is evidential and rule-heavy. Front-office work is customer-facing and judgement-heavy. The common assumption is that agents suit one and not the other, but the difference is narrower than it looks.
What actually differs
- Tolerance for latency. A customer waiting on a reply sets a much tighter clock than a reconciliation that runs overnight.
- Who is allowed to see what. Front-office steps involve people outside the company, so the audience for each artifact is narrower and more explicit.
- Where the human sits. In the back office the human is usually an approver. In the front office the human is often the person in the conversation.
What does not differ
The need for governance is identical. Both need scoped permissions, a defined point where a person decides, a record of what was done and by whom, and a versioned process so a change is visible rather than silent. A customer-facing process does not get to skip any of that.
Where VeroTX sits
The same engine and the same governance run both. Front-office WorkStreams are composed in the studios today, using the same stages, agents, and approval points as back-office ones. Revenue-touching steps stay held for a person in the front office exactly as in the back office, and every action lands in the Execution Ledger either way.
Where to next
Read deeper
Product and platform pages on the same topic, drawn from the VeroTX knowledge base.
Search everything in one place in the Research Center, or ask Veroli, which answers from the same knowledge base.