
Following up with a freight forwarder becomes repetitive when the team starts from the inbox for every dossier. It finds the missing piece, retrieves the reference, writes the request and checks whether a response already arrived.
For an import manager, automating this work starts with a precise request and reliable status. The number of messages sent does not measure the quality of follow-up.
Prepare a request the recipient can act on
The register should identify the dossier or shipment, expected document, required version and the check it blocks. Add the requested party and internal owner.
Confirm that the forwarder is the correct party to contact. Depending on the document, they may need to relay the request to a supplier or carrier. The workflow should not assign them correction authority they do not have.
Distinguish an absent document, unreadable page, document for another shipment and outdated version. Each needs a different request.
Example of a document follow-up
Fictional wording to adapt after checking references and recipients:
Subject: Dossier IMP-306, confirmed bill of lading required
Hello, we received the draft bill of lading for dossier IMP-306. To prepare the internal review, we need the confirmed version for this shipment. Could you send it, or confirm who must issue it and when it is expected? Please retain reference IMP-306 in your response.
The message names the document, version and next useful information. It invents neither a regulatory deadline nor a promised delivery date. For an unreadable page, request a legible copy of the identified page.
OCRAgent's role in the process
OCRAgent can read received documents, retain facts with page sources and present conflicts or uncertainty for review. This helps establish what remains to check after receipt.
Required-document rules need configuration with your team. Identifying a gap then supports a follow-up action.
OCRAgent alone is not a complete external follow-up connection. Kaliits must scope messaging, authorized recipients, drafts, cadence and response detection. The first version can prepare requests with human approval.
What Smatch contributes as experience
In the Smatch workflow described by Mehdi Kourchal, every lead in the flow received a response. This result concerns commercial follow-up, with no conversion rate or revenue claim.
The transferable lesson is to make each received item visible and give it a next action. It does not prove deployed forwarder reminders or a document turnaround time. Read the Smatch case.
The Tedi Services / Delassus test concerns a document conflict in a real dossier. It helps explain evidence review, without a published measurement of follow-up time saved.
Stop on the right evidence
A received response does not always resolve the gap. It may promise a date, attach the wrong document or provide a new version with a remaining conflict.
Distinguish message received, document received, usable document and resolved issue. A new version triggers the relevant check before closure.
Test stopping after resolution, recipient changes, absent replies and sending failures. If response detection is unreliable, keep a human check. “Prepared” and “sent” are different states.
Measure preparation without promising the response
Count time searching for the piece, preparing the request and checking replies. Measure external turnaround separately.
Illustrative assumption: 60 monthly requests requiring 3 rather than 7 minutes release 4 hours. Value those hours using your costs and subtract operating expense. This guarantees neither a faster response nor port fees avoided.
Track unnecessary reminders and wrongly addressed requests. A preparation saving that creates incorrect messages is not an acceptable outcome.
From register to pilot
Start with one document type and channel. Test the register and drafts, then replies and stop conditions. Agree operational sending with the responsible team before expansion.
Review import dossier control, then scope the follow-up workflow. Describe the document required, request volume, channel and how you currently confirm that a gap is resolved.
Template for an incorrect version or unreadable page
Example to adapt: “Hello, for dossier [reference], we received [document, version, date]. To check [specific point] before [stage], we need [confirmed version or readable copy of page X]. Could you send this document with the dossier reference? We will confirm receipt after review. Thank you.”
Replace the bracketed fields and approve the message under your procedure. A version request should name the version already received; a readability request should identify the useful page and field.
Does the response close the follow-up?
- Check that the piece concerns the same shipment and reference.
- Check the required version, readability and field that blocked review.
- Preserve the earlier piece and record the new version used.
- Close the request when the issue is resolved; otherwise name the remaining gap without requesting the entire packet again.
Use the import dossier review register to distinguish a sent request, received response and genuinely resolved issue.

