sumlabsBring a workflow
01

WORKFLOWS / MILES CAPABILITY MAP

What happens after RC‑4821.pdf hits the broker inbox.

No agent theater. Each workflow below names the real trigger, the durable system steps, the moment a person takes authority, the partner integration required, and the metric that proves it works.

Choose the first workflow ↗

Watch the authority change hands.

The moving signal follows one job from intake to recorded outcome. The orange checkpoint is where policy requires a person—not where the demo quietly assumes one.

AVAILABLE

A rate confirmation becomes a structured freight job.

The system advances only through the authority assigned to this workflow.

OPERATING MODEAvailable foundation + human control
SOURCE RECEIVED
Broker inbox · Load #4821RC-4821.pdfReceived now
SSUMLABS
RUNTIME
Fresno, CA → Chicago, IL05/15 · 42,000 lbPickup time: missing
H
HUMAN CHECKPOINTA required pickup time is missing

Ask operations before record creation

REVIEW
OUTPUTStructured tender + exception✓
01Available

Tender email → parsed, classified thread

TRIGGERA broker inbox receives “Load #4821” with a rate confirmation attached.

SYSTEM SEQUENCE
  1. 01

    Verify the inbound webhook and deduplicate the delivery.

  2. 02

    Store the message in its thread and upload attachments with checksums.

  3. 03

    Link the sender only when email identity resolves to one exact account.

  4. 04

    Start asynchronous document parsing and configurable inbox classification.

  5. 05

    Surface missing data, an unmatched sender, or conflicting terms to an operator.

HUMAN CHECKPOINTThe operator resolves identity or document ambiguity before a freight record is committed.
PARTNER EXTENSIONFreight-field mapping and the TMS create/update tool are scoped during implementation.
SUCCESS METRICParse completion, correction rate, exception rate, duplicate suppression.
EVIDENCE IN MILES
Mailgun inboxThreadingAttachment storageDocument parsingClassification
02Available

Pricing PDF → review-ready quote draft

TRIGGERA customer or operator uploads a quote document with line items, totals, dates, and notes.

SYSTEM SEQUENCE
  1. 01

    Queue the document and retain its source relationship.

  2. 02

    Parse the file into normalized text.

  3. 03

    Extract line items, quantity, unit price, currency, dates, and notes.

  4. 04

    Create a draft quote record tied to the document and customer when resolvable.

  5. 05

    Present the draft for review instead of sending or inventing missing figures.

HUMAN CHECKPOINTA person checks commercial values and decides whether the draft is ready for the customer.
PARTNER EXTENSIONA logistics partner can map the same pattern to a customer rate, carrier offer, or accessorial review.
SUCCESS METRICField accuracy, operator corrections, time from document arrival to approved draft.
EVIDENCE IN MILES
Document ingestStructured extractionDraft quotesSource traceability
03Available

Inbound request → contextual, human-controlled reply

TRIGGERA customer or carrier replies on an active operational email thread.

SYSTEM SEQUENCE
  1. 01

    Persist the full thread before an agent activation starts.

  2. 02

    Resolve the sender or new participant with exact-only identity matching.

  3. 03

    Read linked customer and quote context; never manufacture pricing.

  4. 04

    Choose a durable next action: draft, ask a human, pause, or complete.

  5. 05

    Send only when the workflow policy allows it; otherwise leave a reviewable draft.

HUMAN CHECKPOINTAmbiguous identity, missing context, pricing, and approval-sensitive messages stop for an operator.
PARTNER EXTENSIONPartner policy determines which message classes may send and which always remain draft-only.
SUCCESS METRICDraft acceptance, response time, identity-link accuracy, escalations resolved.
EVIDENCE IN MILES
Email coordinatorExact identity toolsQuote readsDraft + send modesask_human
04Available

Open operational item → task + reviewed follow-up

TRIGGERA scheduled routine finds a pending quote, open task, or customer follow-up condition.

SYSTEM SEQUENCE
  1. 01

    Run the saved schedule and query only the allowlisted customer, quote, task, and meeting tools.

  2. 02

    Evaluate the matching condition against current records.

  3. 03

    Create or update the internal task immediately when policy permits.

  4. 04

    Stage customer-facing email or SMS in draft mode by default.

  5. 05

    Let the owner review, send, edit, or reject the proposed communication.

HUMAN CHECKPOINTCustomer-facing communication defaults to draft unless the partner explicitly authorizes send mode.
PARTNER EXTENSIONUse this for pending-rate follow-up, missing documents, check calls, or account-specific service routines.
SUCCESS METRICItems cleared, drafts accepted, touches saved, overdue tasks reduced.
EVIDENCE IN MILES
Scheduled routinesRead toolsTask writesDraft delivery modeOwner attribution
05Partner preview

Inbound SMS → version-safe operator escalation

TRIGGERA driver, carrier, or customer texts an operational exception to a business number.

SYSTEM SEQUENCE
  1. 01

    Persist the inbound message and increment the conversation revision.

  2. 02

    Link a customer only on a unique exact phone match.

  3. 03

    Start or signal the thread-specific background agent.

  4. 04

    Reject stale tool decisions when a newer message has arrived.

  5. 05

    Reply when safe, or call ask_human and mark the thread waiting_for_human.

HUMAN CHECKPOINTThe thread visibly pauses in waiting_for_human until an operator supplies approval, data, or policy judgment.
PARTNER EXTENSIONLive provider delivery and the freight-specific response policy are confirmed during implementation.
SUCCESS METRICException acknowledgment time, stale actions blocked, human wait time, resolution rate.
EVIDENCE IN MILES
SMS threadsRevision safetyExact phone matchingask_humanActivity events
06Roadmap

Carrier offer → verified booking in the TMS

TRIGGERA qualified carrier accepts an offer for an open load.

SYSTEM SEQUENCE
  1. 01

    Load the offer, customer policy, rate ceiling, and allowed carrier criteria.

  2. 02

    Verify carrier identity, authority, insurance, and configured fraud signals.

  3. 03

    Escalate any rate, compliance, identity, or service exception.

  4. 04

    Require approval until automatic-booking policy is proven for the tenant.

  5. 05

    Commit the booking and write the auditable result into the partner TMS.

HUMAN CHECKPOINTBooking authority remains human-gated until the verification path, rate policy, connector, and audit trail pass acceptance tests.
PARTNER EXTENSIONThis loop requires verified carrier-data and TMS connectors; it is not represented as shipped from the current Miles repository.
SUCCESS METRICBookings written back, margin to ceiling, verification failures, manual touches, rollback rate.
EVIDENCE IN MILES
Target workflowConnector requiredAcceptance gateNo unsupported availability claim

Automation stops where proof stops.

The current Miles repository supports the communication, document, quote, routine, identity, event, and human-escalation foundations above. It does not prove a complete carrier verification, rate-ceiling negotiation, booking, and TMS-writeback loop.

That final loop becomes available only after the partner connector, verification path, booking policy, audit trail, and rollback behavior pass acceptance tests.

01

Carrier identity + compliance

A live verification source in the booking path.

REQUIRED
02

Rate authority

Explicit ceilings, exceptions, and human approval policy.

REQUIRED
03

TMS transaction

A tested partner tool that creates the exact booking record.

REQUIRED
04

Booking audit

A durable event trail from offer through commit and rollback.

REQUIRED
05

FIRST WORKFLOW

Choose a workflow with
a visible human decision.

Bring one customer process, its real inputs, and the system where the approved outcome must land.

Map the first workflow ↗