Every Spend Request. Every Channel.One Decision.

The Intake Agent is Blackbee AI's front door. It reads spend intent from Slack, email, Teams, or any system, and converts it into a structured, policy-evaluated financial decision. No forms. No procurement knowledge required. No manual triage.

See all agents
Where It Listens

Every Channel Your Team
Already Uses.

The Intake Agent doesn't require employees to change how they work. It listens where requests already happen, and brings them into a single governed pipeline.

One agent, listening everywhere your team asks.

  • Slack
  • Microsoft Teams
  • Email
  • API / Automation tools
  • ERP system events
Slack#procurementPriya S.

“Need 3 new servers for the data pipeline, around $24k.”

SlackCapturedSpend Policy v2EvaluatingAudit logOpen
The problem

One request. Four people. Zero judgment required.

None of it needs human judgment. All of it eats human time.

  1. Request
  2. PO check
  3. Find approver
  4. Chase approval
  • Shadow spend

    Up to 60% of spend starts in Slack, email or a hallway, and reaches the ERP after the money's promised.

  • Classification burden

    CapEx? OpEx? PO? Employees shouldn't have to know. The system makes them guess.

  • Approval overload

    Everything goes to a human “just in case”, because the system can't tell low risk from high.

What It Does

It Answers One Question First:
What Is This and What
Should Happen Next?

The Intake Agent doesn't process transactions. It classifies intent. It reads the request, evaluates it across multiple dimensions simultaneously, and produces a structured financial decision, before any downstream agent touches it.

  1. The agent distinguishes purchase requests from noise. Informational messages, non-actionable queries, and system events that require no financial action.

    3 messages scanned
    1 purchase request found. The rest need no financial action.
    Need 3 new servers, ~$24kSpend request
    Thanks, the laptops arrivedNo action
    Where do I find the travel policy?No action
  2. Invoice, purchase request, PO, payment intent, amendment, or cancellation, classified automatically with a confidence score attached.

    Purchase request
    Classified from the message, with a confidence score.
    Purchase request94%
    PO amendment4%
    Payment intent2%
  3. Based on category, amount, vendor type, and policy. The agent decides Yes, No, or Unknown (requires escalation). No manual judgment required.

    PO required
    Decided from category, amount, vendor and policy.
    YesNoUnknown
    Amount$24,000
    CategoryIT hardware
    VendorNorthwind Systems
  4. Goods, services, subscription, capital expenditure detected from the request context and mapped to the correct financial treatment automatically.

    Capital expenditure
    Mapped to the right financial treatment automatically.
    SignalReading
    Item typePhysical hardware
    Useful life3+ years
    AmountAbove $5k cap limit
    CapExCapital policy applies
  5. Low, medium, or high confidence based on amount, vendor history, category norms, and policy signals. Determines whether the request routes automatically or needs review.

    Medium risk
    Routed for review instead of auto-approval.
    Low
    Medium
    High
    Amount vs category normTypical
    Vendor historyFirst order in category
    Policy signalsCapEx review
  6. Purchase requests go to the Commit Agent (PO), invoices to the Parse Agent, payment intents to the Route Agent, and anything high risk or ambiguous to human review. Ownership is always explicit.

    Handed to Commit Agent
    Ownership moves to exactly one place.
    Purchase requesttoCommit AgentThis one
    InvoicetoParse Agent
    Payment intenttoRoute Agent
    High risk or uncleartoHuman review
Five ways it decides

Every request type. One agent.

Five distinct request scenarios, each with a different decision outcome. No manual routing. No exception queues.

  • Auto-approvedLow risk, under threshold
  • PO requiredRaised by the Commit Agent
  • CFO approvalHigh value, escalated
  • No action neededNo spend intent, logged
  • ClarificationAsks for amount, vendor, purpose
Explainability

Every decision. Fully explained.

The Intake Agent never makes a silent decision. Every classification comes with a human-readable explanation.

  • Classified asWhat the request is
  • Policy appliedWhich rule decided it
  • ConfidenceHow sure the agent is
  • ReasoningWhy, in plain English
Visible toRequesterFinanceProcurementAudit log
Simulation Mode

Change Policy Safely.
See It Before It's Live.

Replay past requests under a new rule and see exactly what would change.

What if we

Raise the non-PO threshold to $7,500?

21%
fewer POs triggered
What if we

Require POs for all software?

44
more POs a month
What if we

Auto-approve known-vendor renewals?

18
fewer approvals a month

Nothing goes live until you apply it.

Agent Handoffs

The Intake Agent Decides.
Then Hands Off.

The Intake Agent does not execute. It classifies and routes. Once a decision is made, ownership transfers explicitly to the right downstream agent.

If no PO is required and no downstream action is needed, the Intake Agent intentionally does nothing. Restraint is a design principle.

Get Started

See the Intake Agent
Process Your Requests.

We'll show you exactly how the Intake Agent handles your organisation's spend patterns, live, in your ERP environment.

See All Agents
Next: Procurement Agent