banhworks.
USE CASES

Where we start.

Each of these is a queue of similar cases that people read one at a time. We answer the questions your team asks, apply your rules, and hand the uncertain ones back.

  1. 01 / WARRANTYWarranty & claims triageRoute obvious claims, ask for missing evidence, and send uncertain claims to your team.
  2. 02 / SUPPORTSupport triageKnow what a ticket is about and how urgent it is before anyone opens it.
  3. 03 / RETURNSReturns reviewApprove routine returns and flag the ones that need inspection or a decision.
  4. 04 / OPERATIONSOperational reviewTurn any repetitive document, request, or case review into a structured decision.
01 / WARRANTY

Warranty & claims triage

Most claims fall into a handful of patterns your team already recognizes. We read the description, the order, and the evidence, answer the same questions your reviewers ask, and apply your policy to the answers.

A GOOD FIT WHEN
  • Claims arrive as free text, photos, or forms
  • Reviewers follow a written or unwritten policy
  • Most claims are clear-cut, but still read by hand
WHERE CASES GO
  • APPROVE
  • SHIPPING_CLAIM
  • MORE_INFO
  • MANUAL_REVIEW
WORKS WITH
  • Warranty portal
  • Order history
  • ERP
  • Email
warranty claim#4172
INCOMING

“The upper limb cracked while drawing the bow. Bought in August, photo attached.”

  1. YES / NO

    Does this appear eligible for warranty?

    Yes94%
  2. ONE OF

    What is the most likely cause?

    Manufacturing91%
    Shipping5%
    Misuse3%
  3. SCALE

    How severe is the damage?

    1. Cosmetic
    2. Minor
    3. Significant
    4. Unusable
RULE

eligible ≥ 0.90 and cause = manufacturing

OUTCOME

APPROVE_REPLACEMENT

One claim, before and after.

TODAY
  1. Customer submits claim
  2. Employee opens claim
  3. Employee reads description
  4. Employee reviews evidence
  5. Employee checks policy
  6. Employee decides what happens

× 50 a day

WITH BANH WORKS
  1. Customer submits claim
  2. Your existing application gathers evidence
  3. Banh evaluates the claim
  • APPROVE
  • MORE_INFO
  • MANUAL_REVIEW

Instead of replacing your warranty platform, we add a decision layer inside the process you already use.

02 / SUPPORT

Support triage

The first minutes on every ticket go to reading it and deciding where it belongs. We classify intent and urgency as tickets arrive, so outages reach the right people immediately and routine questions land in the right queue.

A GOOD FIT WHEN
  • High ticket volume across several queues
  • Urgent issues get lost among routine ones
  • Agents spend time re-routing misfiled tickets
WHERE CASES GO
  • ESCALATE
  • ROUTE_BILLING
  • ROUTE_TECHNICAL
  • SELF_SERVE
  • MANUAL_REVIEW
WORKS WITH
  • Help desk
  • Shared inbox
  • Chat
  • CRM
support ticket#88104
INCOMING

“Checkout has been down since 9am. None of our customers can pay.”

  1. YES / NO

    Does this need immediate attention?

    Yes97%
  2. ONE OF

    What is the customer asking about?

    Outage89%
    Billing6%
    How-to5%
RULE

urgent ≥ 0.85

OUTCOME

ESCALATE_ON_CALL

03 / RETURNS

Returns review

Return requests mix easy cases with ones that need a closer look. We classify the reason and condition against your return policy. Clear cases are approved, and anything outside policy or uncertain goes to inspection or a person.

A GOOD FIT WHEN
  • Return reasons arrive as free-text notes
  • Policy depends on reason, condition, and timing
  • Inspection capacity is limited
WHERE CASES GO
  • AUTO_APPROVE
  • INSPECT
  • MANUAL_APPROVAL
  • REQUEST_INFO
WORKS WITH
  • Returns portal
  • Order history
  • Warehouse system
  • Email
return request#R-2291
INCOMING

“Jacket arrived in the wrong size. Worn once, tags removed.”

  1. YES / NO

    Is this within the return policy?

    Yes62%
  2. ONE OF

    Why is it being returned?

    Wrong size84%
    Defect9%
    Changed mind7%
  3. SCALE

    What condition is the item in?

    1. Like new
    2. Worn
    3. Damaged
RULE

within_policy < 0.75

OUTCOME

INSPECT

04 / OPERATIONS

Operational review

Many back-office queues are the same review done over and over: invoices, requests, applications, exceptions. If your team can describe the questions they ask, we can usually turn them into a workflow and send only the real exceptions to people.

A GOOD FIT WHEN
  • A queue of similar documents or requests
  • Reviewers answer the same few questions each time
  • Exceptions matter more than routine cases
WHERE CASES GO
  • AUTO_MATCH
  • ROUTE_TO_BUYER
  • AP_REVIEW
  • REQUEST_INFO
WORKS WITH
  • ERP
  • Document store
  • Shared inbox
  • Forms
invoice exceptionINV-88213
INCOMING

“Invoice total is 4.2% above the purchase order. Supplier notes a freight surcharge.”

  1. YES / NO

    Is the difference within tolerance?

    No81%
  2. ONE OF

    What kind of discrepancy is this?

    Added charge78%
    Price change15%
    Quantity7%
RULE

not within tolerance and type = added charge

OUTCOME

ROUTE_TO_BUYER

Examples are illustrative. The questions, thresholds, and outcomes for your workflow are set with your team during the pilot.

Don't see your workflow?

If your team reviews the same kind of case over and over, it's probably a candidate. Tell us about it.

Talk about a workflow