$ bh run ./use-cases/email-triage

Email triage & response▌

The routine inbox gets read, categorised and answered for you.

inboxdraftingroutingfollow-up
problem.txt

the problem

Your inbox buries the important messages under routine requests. Every morning starts with triage instead of the work that matters.

fix.sh

how agents fix it

Agents read incoming mail, categorise it by type and priority, and draft replies to routine requests in your voice. Only the decisions that need you reach you.

$ ls ./outcomes --long

What you get

outcomes.log
-> auto-categorised inbox, every morning
-> drafted replies in your voice
-> only real decisions escalate to you
$ # ready to scope this in your stack?▌
$ ls ../ --long

Related use cases

document-intelligence.md

Document intelligence

drwxr-x— ./use-cases/document-intelligence

Agents that read, extract and structure documents at the scale your team can’t.

  • extract fields from thousands of docs in minutes, not weeks
  • route contracts by clause, expiry and risk
read the case
customer-support.md

Customer support

drwxr-x— ./use-cases/customer-support

First response in seconds, routine tickets resolved without a human.

  • instant first response, 24/7
  • routine tickets deflected and resolved
read the case
lead-qualification.md

Lead qualification

drwxr-x— ./use-cases/lead-qualification

Score, enrich and qualify every inbound lead before your team spends a minute.

  • enriched, researched lead profiles on arrival
  • scored pipeline ranked by fit and intent
read the case
$ grep -R "related" . --no-filename

Related reading

related.log

$ book --type discovery --duration 30m --cost $0

Thirty minutes.
Zero dollars. Real answers.

Bring the problem, the half-built prototype, or just the hunch that agents could change how you work. We’ll tell you straight what’s worth building — and what isn’t.

Book a free 30-min discovery call->

# no deck, no pressure, no obligation. exit code 0 either way.