AI case / 08 · Authority, tools & human commit

Redesigning RFQ processing around AI without moving commercial authority to the agent

A case readable through two lenses—AI & Agentic Workflows and Operating Model & Process Design. It is not about the model: it is about moving work between people, rules and an agent without moving authority.

The case in brief

Current reality

RFQs arrive as free-text email and attachments, and an agent is expected to “handle them”—with nobody having said what it may do.

What must become true

Every RFQ is drafted in minutes with evidence for each value; ambiguity is flagged, not guessed; nothing reaches pipeline or the customer without a named person’s approval; every run can be reconstructed.

Design question

When is a customer match trusted, what happens with an ambiguous product—and what may the agent never do, however confident it is?

01The reality · current state

What happens today—or in the pilot.

A B2B supplier receives requests for quotation by email in every format. The governance of complex requests is designed separately (see the RFQ governance case): what each class requires and who decides. This case redesigns the intake work itself—which parts an agent may prepare, which rules must stay deterministic and which authority stays with people.

  • Inside sales retype RFQ lines into the CRM from PDFs and spreadsheets
  • Customer identification depends on who reads the email
  • Product references use customer and competitor codes
  • A proof of concept let the model create opportunities directly
  • Nobody can say why the proof of concept picked a product
  • The same email forwarded twice produced two opportunities

Reasoning, rules and authority

Before the agent was given a single tool, the work was divided by what it requires: reasoning an agent can prepare, deterministic rules a system can enforce, and authority that stays with people.

The agent prepares

  • Reads and classifies the request
  • Extracts lines and quantities
  • Identifies customer and product candidates
  • Retrieves context and history
  • Flags uncertainty
  • Drafts the record and assembles the evidence
  • Recommends

Rules enforce

  • Validate deterministic conditions
  • Route by class and owner
  • Enforce completeness
  • Apply thresholds
  • Block impossible actions
  • Record traceability

People decide

  • Commercial commitments
  • Meaningful exceptions
  • Sensitive pricing
  • Governed Go / No-Go decisions
  • Irreversible customer-facing actions
  • Ambiguous identity or product above policy

The agent’s tools were built from this table: it can call only what the first column allows.

The pointDesign the authority before giving the agent tools.

02Agent workflow

Each step with its actor, its tool and its authority.

Systems and partiesMailboxAI agentCRMProduct catalogue

Walk the workflow step by step, or select any step.

Step 1 of 7

01Receive email

The message and attachments get a source request ID—the idempotency key for the whole run.

Who acts
System
Authority
Read

02Classify request

RFQ, order question, complaint or other—against the written RFQ definition.

Who acts
Agent
Authority
Execute
Tool
setClassification

03Identify customer

Ranks account candidates by domain, signature and history, with evidence.

Who acts
Agent
Authority
Recommend
Tool
searchAccount

04Identify products

Matches each line to catalogue or cross-reference; flags lines with more than one plausible product.

Who acts
Agent
Authority
Recommend
Tool
matchProducts

05Prepare CRM draft

Creates a draft with every value and its source; invisible to pipeline and customer.

Who acts
Agent
Authority
Draft
Tool
createOpportunityDraft

06Human review

The account owner approves, edits, rejects or asks for more context—with a reason code.

Who acts
Human
Authority
Human approval
Tool
requestReview

07Commit

The system—not the agent—turns the approved draft into an opportunity.

Who acts
System
Authority
Execute

03Key dimension · Authority, tools & human commit

Seven questions the agent design must answer

Each answer is a rule the tools and the review model enforce—not a sentence in a prompt.

  1. 01When is a customer match trusted?

    When a key matches (a known contact on an active account) or a person confirms a candidate. A high similarity score alone is a recommendation.

  2. 02What if product identification is ambiguous?

    The line is flagged with its alternatives and evidence. The agent never substitutes; the reviewer chooses or asks the customer.

  3. 03Which records can be drafted?

    Opportunity drafts only—invisible to pipeline, forecast and customer, and expiring if not reviewed.

  4. 04Which actions require approval?

    Creating the opportunity, any customer communication and anything that commits price or delivery.

  5. 05What evidence is shown?

    For every value: the source (email line, record, history) and the confidence—plus what approval will do.

  6. 06What if no customer is found?

    A lead in a holding queue with an owner. The agent never creates an account.

  7. 07What if confidence is high but the consequence is high?

    Human approval. The score changes how the draft is presented, not who commits it.

The proof of concept failed on the last question: a 97 % match on the wrong legal entity created a real opportunity. Confidence was treated as authority.

04Authority

What the agent may do—and what it may not.

Actions and the authority the agent has for each
ActionAuthorityWhy
Classify the requestExecuteReversible, visible and checked by the reviewer
Search accounts and catalogueExecuteRead-only, within the requester’s visibility
Confirm customer identityRecommendA wrong match spreads to every later step
Create opportunity draftExecuteInvisible and reversible by design
Create opportunityHuman approvalEnters pipeline and forecast
Reply to the customerHuman approvalExternal and irreversible
Create accountForbiddenIdentity is owned by the customer lifecycle, not the agent

05Ambiguity policy

When the agent is unsure.

  • Classification below thresholdAsk

    Routed to inside sales for classification

  • Two customer candidatesEscalate

    Both shown with evidence; the owner confirms

  • No customer candidateStop

    Lead in a holding queue; no draft is created

  • Ambiguous product lineContinue

    Draft continues with the line flagged and alternatives listed

  • Mandatory data missingRetrieve

    Checks history; otherwise asks the requester

  • Same source request seen againStop

    Returns the existing draft; nothing new is created

06Evaluation

Scored per dimension—never one accuracy number.

Evaluation dimensions: what each proves, its question, measure and target
DimensionQuestionMeasureTarget
ClassificationIs it an RFQ?Correct class on the evaluation set≥ 95 %
ExtractionAre lines, quantities and dates captured?Required fields correct≥ 90 %
Entity matchingRight account, right products?Correct top candidate; correct set in top three≥ 90 % · ≥ 98 %
AuthorityDid it stop when it had to?Required stops honoured100 % — release gate
EvidenceIs every value sourced?Values with a cited source≥ 95 %

07The trade-offs

Credible options, judged against these premises.

Rejected

Agent creates opportunities directly above a confidence threshold

Low-value, known customers, standard products

Cost: Wrong entities reach pipeline; confidence becomes permission
Rejected

Extraction only; people do everything else

Very low volume

Cost: Most of the clerical effort remains
Selected

Agent drafts with evidence; people commit

Mixed customers and ambiguous product references

Cost: A review step and a review card to design

Design decision

Give the agent execute authority only over reads and reversible drafts; make customer confirmation a recommendation and every commit a human approval—enforced by the tools, not by the prompt.

08The second layer

Questions that change the design.

Identity

  1. Which key confirms a customer?
  2. What happens with a new contact at a known account?
  3. Who owns the holding queue?

Authority

  1. Which tools can write—and what exactly?
  2. Which checks live in the tool, not the prompt?
  3. Who can widen the agent’s authority?

Quality

  1. Which cases are in the evaluation set?
  2. How do corrections become new cases?
  3. What blocks a release?

09Decisions & outputs

What the work produces.

  1. 01Agent workflow
  2. 02Authority matrix
  3. 03Tool contracts
  4. 04Ambiguity policy
  5. 05Review card
  6. 06Evaluation set
  7. 07Audit model