Skip to content
Talk to us
MenuClose
All Insights

Agentic workflows in practice

By Sam Patel

Follow three workflows from their evidence to a recorded decision: an invoice exception, a new starter’s onboarding and a customer request. Each shows what agents prepare and what people decide.

In this article

In short

Invoice exceptions

A useful agentic workflow starts with a specific piece of work. Here, an invoice does not match the purchase order or goods receipt. Agents bring the evidence together and prepare a resolution. A finance reviewer decides what happens next.

Invoice exceptions are a common problem for finance teams. A mismatch holds up payment until someone traces the invoice, purchase order and receipt by hand. The workflow below shows where agents take on that preparation and where a person keeps the decision; the distinction between preparing work, making a decision and carrying out an approved action matters at every step.

Workflow · Invoice exceptions

Evidence moves forward.
Finance keeps the decision.

  • Invoice
  • Purchase order
  • Goods receipt

Starts withInvoice mismatch flagged

OutcomeResolution recorded

Ownership and operation

Access · Evaluation · Monitoring · Release

  1. AgentsDocument agent

    Read the evidence

    Hands over: Source-linked comparison

  2. AgentsReconciliation agent

    Explain the mismatch

    Hands over: Draft resolution with evidence

  3. PeopleFinance reviewer

    Review the resolution

    Hands over: Recorded finance decision

  4. SystemsWorkflow automation

    Update the record

    Hands over: Closed or escalated exception

Exception

Request more evidence or escalate

Finance can ask for further evidence or escalate the case.

  • Shared intelligence platform

    Models · Agents · Tools · Knowledge

  • Data and distributed systems

    Accounts payable · ERP · Document store

Keep source references and the finance decision with the case. Update only permitted fields. An unresolved discrepancy remains an exception.

The agent cannot authorise payment or change supplier bank details. A changed supplier bank account is held for the existing verification process.

The controls belong in the workflow.

The comparison uses the invoice, purchase order and goods receipt. Reconciliation adds the agreed matching rules. Finance receives the draft resolution and supporting documents; automation receives an approved resolution. Each handover carries the evidence needed for the next task.

Invoice exceptions, step by step: what each step works from, does, may not do and hands over.
StepWorks fromWorkControlHands over
01 · Document agentRead the evidenceInvoice, purchase order and goods receiptExtract the references and compare line items against the source records.Uncertain fields stay flagged, with their source document attached.Source-linked comparison
02 · Reconciliation agentExplain the mismatchComparison and agreed matching rulesIdentify a price, quantity or missing-receipt exception and draft the next action.Apply the agreed rules; an unresolved discrepancy remains an exception.Draft resolution with evidence
03 · Finance reviewerReview the resolutionDraft resolution and supporting documentsAccept the explanation, request more evidence or escalate it.The agent cannot authorise payment or change supplier bank details.Recorded finance decision
04 · Workflow automationUpdate the recordApproved resolutionUpdate the permitted case fields and notify the responsible team.Keep the decision and source references with the case.Closed or escalated exception

Employee onboarding

Coordinate HR, IT and the hiring manager around one new starter, with people approving access and resolving exceptions.

Workflow · Employee onboarding

From signed offer to a ready first day.

Starts withSigned offer received

OutcomeFirst-day plan confirmed

Ownership and operation

Access · Evaluation · Monitoring · Release

  1. AgentsIntake agent

    Check starter details

    Hands over: Validated starter brief

  2. AgentsPlanning agent

    Prepare the plan

    Hands over: Draft onboarding plan

  3. PeopleHiring manager

    Approve access

    Hands over: Approved access request

  4. SystemsWorkflow automation

    Coordinate tasks

    Hands over: Tracked tasks and first-day summary

Exception

An access request outside the approved role goes to the hiring manager and IT owner.

  • Shared intelligence platform

    Models · Agents · Tools · Knowledge

  • Data and distributed systems

    HR system · Identity provider · Service desk

Employee onboarding, step by step: what each step works from, does, may not do and hands over.
StepWorks fromWorkControlHands over
01 · Intake agentCheck starter detailsSigned offer and starter recordCheck required fields and flag missing or inconsistent information.Missing details return to HR; the agent does not invent them.Validated starter brief
02 · Planning agentPrepare the planStarter brief and approved role templateDraft the HR, equipment and induction tasks for the agreed start date.Use the approved role template and retain the source for each task.Draft onboarding plan
03 · Hiring managerApprove accessProposed access and equipmentReview the proposed entitlements and any exceptions.A named person approves access before provisioning.Approved access request
04 · Workflow automationCoordinate tasksApproved access request and onboarding planCreate the permitted tasks and collect their completion status.Only agreed system actions; failed tasks go to the service desk.Tracked tasks and first-day summary

Customer requests

Connect incoming requests to approved knowledge and case history, so service teams review a prepared answer rather than start from scratch.

Workflow · Customer requests

A useful response, with the context behind it.

Starts withCustomer request received

OutcomeReviewed response sent

Ownership and operation

Access · Evaluation · Monitoring · Release

  1. AgentsTriage agent

    Triage the request

    Hands over: Categorised case brief

  2. AgentsResponse agent

    Prepare an answer

    Hands over: Source-linked draft response

  3. PeopleService adviser

    Review the response

    Hands over: Approved response

  4. SystemsWorkflow automation

    Complete the case

    Hands over: Response and case history

Exception

A request for a refund outside policy is escalated rather than promised by the agent.

  • Shared intelligence platform

    Models · Agents · Tools · Knowledge

  • Data and distributed systems

    Shared inbox · CRM · Knowledge base

Customer requests, step by step: what each step works from, does, may not do and hands over.
StepWorks fromWorkControlHands over
01 · Triage agentTriage the requestIncoming request and permitted case historyIdentify the request type, urgency and missing information.Sensitive or out-of-scope requests go to the responsible specialist.Categorised case brief
02 · Response agentPrepare an answerCase brief and approved knowledgeRetrieve relevant guidance and draft an answer with its sources.Do not make commitments unsupported by the approved policy.Source-linked draft response
03 · Service adviserReview the responseDraft answer, sources and uncertainty flagsCheck the answer, edit it and decide whether it can be sent.A person handles exceptions and approves the customer response.Approved response
04 · Workflow automationComplete the caseApproved responseSend through the agreed channel and update the case record.Write only to permitted fields and retain the review decision.Response and case history

Test the whole workflow

Start with an operational owner, a clear problem and a process the team can describe. Map the inputs, outputs, decisions and handovers before choosing a model. Agree which records an agent can read, which tools it may use and which actions need a person’s approval.

Then test representative cases alongside the difficult ones: missing evidence, uncertain fields, failed integrations, exceptions and work that should stop. Check whether the proposed answer is grounded in its sources, whether the right person receives the exception and whether every system action stays within its permission.

Compare the whole workflow with the current process, including the review and operating work left to people. Measure routine effort and exception handling separately. A faster draft is useful only if the resulting decision and record are dependable.

Our workflow mapping guide explains how to capture that baseline. The simulation guide includes a calculator for exploring capacity assumptions. Those assumptions need measured inputs and representative tests before they can support a delivery decision.

Turn an example into a delivery brief

A useful brief names the work, its owner, the available evidence, the permitted actions and the decisions people keep. It also describes how to recognise a successful outcome, how exceptions will be handled and what happens when a tool or integration fails.

Deeplight’s practitioners help organisations do this as tailored professional services. The design, platforms and models follow the organisation’s needs. Foundry supports how we organise the engagement and agent-assisted work.

Talk to us