Quantum Customs Brokers Customer story

Take reconciliation from 42% of the day to 9%.

A three-person US brokerage kept re-keying the same numbers across invoices, packing lists and bills of lading. An email agent on one shared record gave those hours back.

Results by month three
  • Reconciliation42%9%Share of the working day
  • Throughput+79%Entries per broker per week
  • Near-miss rate1 in 61 in 28Entries caught by internal QA
  • Client replies4h 12m54mMedian reply time

Measured against a two-week baseline, same three brokers, no change in headcount.

Results by month three. Reconciliation: 42% to 9% (Share of the working day); Throughput: +79% (Entries per broker per week); Near-miss rate: 1 in 6 to 1 in 28 (Entries caught by internal QA); Client replies: 4h 12m to 54m (Median reply time).

What happened at Quantum Customs Brokers?

A workflow audit showed where the hours went, and a six-week build moved them back to broker work.

Quantum Customs Brokers is Arnoldo R.’s three-person US customs brokerage. In early 2026 each broker handled 50 to 100 emails a day, and 42% of working hours went to reconciliation: moving the same numbers between the Commercial Invoice, Packing List, Bill of Lading and ABI. GingerControl audited the workflow for two weeks, then built an email agent on one shared customer and case record in six weeks. By the third month, reconciliation was 9% of the day and each broker processed 79% more entries a week.

Case file
Quantum Customs BrokersPublished May 15, 2026
Engagement
Workflow audit + custom build
Industry
Customs brokerage, US
Team size
3 brokers
Build window
6 weeks
Arnoldo R., Founder of Quantum Customs BrokersArnoldo R.Founder, Quantum Customs Brokers

Case file for Quantum Customs Brokers: Engagement Workflow audit + custom build; Industry Customs brokerage, US; Team size 3 brokers; Build window 6 weeks.

Why did new software still feel slow?

The data lived in silos, so the same client shipping the same product showed up as a fresh record every time.

  • Each broker processed 50 to 100 emails a day, each with its own shipment, documents and question.
  • Every entry meant checking the invoice against the packing list and the bill of lading, then keying the numbers into ABI. One mismatch and the entry bounced.
  • The team already ran an AI-assisted ABI platform, yet brokers still copied between tabs to rebuild context it had captured hours earlier.
Arnoldo R., Founder of Quantum Customs Brokers

“It wasn’t that we lacked technology. It was that the technology didn’t know us.”

Arnoldo R., Founder
Sample entry · one shipment, four places
  • Commercial Invoice
    Gross weight
    1,240 kg
    Cartons
    48
  • Packing List
    Gross weight
    1,240 kg
    Cartons
    48
  • Bill of Lading
    Gross weight
    1,420 kg
    Cartons
    48
  • ABI entry
    Gross weight
    Keyed by hand
    Cartons
    Keyed by hand

MismatchGross weight differs on the Bill of Lading. Caught by internal QA before submission.

Illustrative sample, not client data: one shipment’s gross weight and carton count in the Commercial Invoice, Packing List and Bill of Lading, with the Bill of Lading weight flagged as a mismatch before the numbers are keyed into ABI.

Where did the hours actually go?

42% of working hours went to reconciliation and 19% to email triage. Only 27% went to licensed broker work.

  • A consultant sat with each broker for full days over two weeks and tagged every action from inbox to ABI.
  • CBP rejections were rare, but internal QA caught 1 in every 6 entries before submission.
  • Most catches were a number that was right in one document and wrong in another.

“We weren’t fighting bad data. We were fighting unconnected data.”

GingerControl diagnostic memo
Working hours by task

Timer-tagged audit across the three brokers, repeated 12 weeks after go-live.

  • Reconciliation labor
  • Email triage
  • Broker judgement
  • Admin and other

Bar chart of the brokers’ working hours by task. Before: reconciliation labor 42%, email triage 19%, broker judgement 27%, admin and other 12%. After go-live: 9%, 4%, 55% and 32%.

What did six weeks build?

An email agent that reads, acts and escalates, on one customer and case record the whole team shares.

Email agent · case activity

Shared recordOne record per client: shipments, documents, emails

  • Resolution detectionResolvedCorrected Commercial Invoice received. It matches the Packing List and Bill of Lading. Case updated.
  • Gap surfacingStill openReply received, case not closed. Still missing: gross weight on the Bill of Lading.
  • Graceful escalationTo brokerUnclear request. Sent to the assigned broker with a one-paragraph summary instead of the full thread.

Illustrative sample, not client data: the email agent’s case activity showing its three actions, a resolved case after a corrected invoice, an open case naming the missing field, and a thread escalated to the broker with a summary.

Shadow mode, day 1 to day 10

The agent proposed actions without taking them. Disagreements were reviewed nightly before going live.

  • Email intent
  • Document reconciliation
  • Live threshold 92%

Line chart of the agent’s agreement with the brokers over ten days of shadow mode. Email intent classification rose from 78% to 94% and document reconciliation from 82% to 97%, against a live threshold of 92%.

  • Every client, shipment, document and email points to one record, so a broker opening a case sees the full timeline and past classifications.
  • Four design sessions over three weeks set the email intents, one schema for the invoice, packing list and bill of lading fields, and when the agent may act alone.
  • Ten days in shadow mode: the agent proposed, the brokers decided, and the thresholds were tightened before going live.

What changed by month three?

Reconciliation fell from 42% to 9% of the day, with no change in headcount.

Before and after
MetricBeforeAfterChange
Reconciliation labor42% of hours9% of hours78.6% reduction
Email triage timeBaseline21% of baseline79% reduction
Entries per broker per weekBaseline+79%Throughput up
Internal near-miss rate1 in 61 in 2878.6% reduction
Median client reply4h 12m54m78.6% reduction

Before and after: Reconciliation labor, 42% of hours before, 9% of hours after (78.6% reduction); Email triage time, Baseline before, 21% of baseline after (79% reduction); Entries per broker per week, Baseline before, +79% after (Throughput up); Internal near-miss rate, 1 in 6 before, 1 in 28 after (78.6% reduction); Median client reply, 4h 12m before, 54m after (78.6% reduction).

Internal near-miss rate

Higher is better: 1 in N entries flagged by internal QA before submission to CBP.

Line chart of the internal near-miss rate from 8 weeks before to 12 weeks after go-live. It held near 1 in 6 before and settled near 1 in 28 after.

  • Email triage time dropped by 79%.
  • Median client reply went from 4 hours 12 minutes to 54 minutes, mostly because the agent flags a case as resolved the moment the document arrives.

“I have my evenings back. And my brokers are doing broker work.”

Arnoldo R., Founder

Why did it work when tools hadn’t?

Three calls made on purpose: diagnose before designing, fix the data before the agent, and agree on autonomy case by case.

Decision log
  • The diagnosis came before the designWe arrived with a stopwatch and a notebook, not a product. Neither side would have proposed the final design at the start.Decided
  • The data came before the agentAn agent built on fragmented records inherits the fragmentation, so the shared record came first.Decided
  • Autonomy was negotiated, not assumedThe shadow period is where the brokers drew the line, case by case, between what the agent does alone and what it asks.Decided

Decision log: The diagnosis came before the design; The data came before the agent; Autonomy was negotiated, not assumed.

See how a build starts today.

One call, then a Prototype Week, then a fixed price for the scope you sign.

Our Risk-Free Promise

Full refund.

If you’re not satisfied before MVP acceptance, get a full refund of your deposit.

Click Me!

See if you qualify