Client
Freight forwarding team
Industry
Air Freight
Timeline
Approved answers before any new channel
Key takeaway
A shipment question gets one approved answer, under the access rules for the person who asked.
This forwarding team already had systems for tracking, documents, warehouse activity, and billing. What they did not have was a safe way to answer a question without touring all of them. Customers and internal staff needed different views of the same freight, and a release change could sit unnoticed until someone went looking. We added a controlled desk on top of those systems: approved status and release answers, document tasks, exception monitoring, and an audit of what was requested and returned.
The challenge
A routine question — where is it, has it released, can I have the paperwork — took a person who knew which system held the answer. That was slow for the customer and easy to get wrong. Access was informal, so the difference between what a customer should see and what an operator should see depended on who replied. Exceptions surfaced when someone checked, not when the status changed.
An answer assembled by hand
Shipment status had to be pulled together from several operational sources before anyone could reply.
Releases noticed late
A status or release change waited on manual monitoring, and the follow-up started after the delay was already visible to the customer.
One reply, two audiences
Customers and internal staff needed different slices of the same shipment, and that split was hard to hold in an email.
What we built
People ask from one desk and receive only the shipment, document, and release information they are allowed to see. Exception monitoring flags shipments and service issues for follow-up. Every request and response is recorded. Sensitive actions stay behind an approval instead of being fired off with the answer.
- One place to retrieve an approved shipment-status answer
- Release checks that show what still needs a person
- Document tasks for the paperwork a shipment requires
- Separate access for internal users and customers
- Monitoring that surfaces shipment and service exceptions
- A record of each request and the answer that went back
Before & after
Before
- Staff opened multiple systems to answer one shipment question
- Release and status changes depended on someone checking
- Customer and internal access were separated by habit
After
- Authorized users get an approved operational answer from one desk
- Shipment and service exceptions are monitored for follow-up
- What a person can see, and what was answered, is recorded
Built with
Our approach
01
Audit
We listed the questions the team answers all day, where the facts live, and who is allowed to hear them.
02
Build
We built the desk around approved status, document tasks, and release monitoring, with access split by role.
03
Pilot
The first release stayed on read-oriented answers the team was willing to stand behind.
04
Support
Further channels and reporting sit on the same access rules, and anything sensitive stays approval-gated.
Frequently asked questions
More engagements