BW-207 · commercial invoice
Commercial invoice CI-207 is attached for the Shanghai to Manila shipment.
For shipment coordinators
Track shipment documents.
See what arrived, what is missing, and the source email behind each item.
No signup. Fictional emails and results.
Document receipt · acceptance pending
BW-207 · Shipment documents
- Bill of lading: missing
- Commercial invoice: received · CI-207.pdf
- Packing list: received · PL-207.pdf
Purpose supplied for this example
Shanghai → Manila · 22 October 2026 · 2 × 40-foot containers · 240 cartons
Evidence collected from email keeps its source linked. Your team checks document acceptance.
A coordinator selects BW-207 when routing these emails. A subject code such as [BW-207] can route matching emails automatically.
Two emails, one shipment checklist
BW-207 · packing list
Packing list PL-207 is attached. The carrier has not sent the bill of lading.
Fictional email and output, shown for illustration.
Beyond reading and replying
An output that fits the job.
Fewer details to copy into a spreadsheet. Fewer messages to piece together for a checklist or report.
Useful rows for a spreadsheet.
Bring order, invoice, or enquiry details from emails and attachments into a comma-separated values (CSV) file. Keep the records together instead of copying each detail.
Know what is still missing.
Follow requirements across multiple messages. See which shipment documents have arrived and which still need attention in an ongoing checklist.
- Delivery confirmed
- Signed note received
- Invoice still needed
Keep the updates together.
Collect incoming updates into a plan with source evidence. Generate a text report when ready; later emails update the plan until you generate again.
For the work your team knows
Find your use case.
See how incoming emails can become records, checklists, and reports for a specific workload.
Construction
Quality records, inspection evidence, and ISO documentation.
Travel
Trip confirmations, traveler forms, and missing documents.
Logistics
Shipment paperwork, document checklists, and status updates.
Accounting
Incoming invoices, spreadsheet records, and supporting files.
Have a different workflow?
Tell us what arrives by email and what you need it to become. Discuss help setting up your use case or an action tailored to your team.
Show us your email task
Start with one recurring task and the output your team needs.
The context behind the result
Keep the source
in sight.
Source emails and files stay linked to the output. Your team can check a result against the original message and attachment.
Review and correct proposed records and report sections. Checklist evidence shows what supports each requirement, while your team keeps the final judgment.
When a detail needs a person
Check the uncertain part. Keep the result.
An email and its signed delivery note disagree. Here is how a person can resolve that in Review. This is a fictional example.
- 1 / Source email
The email and the note disagree.
Email: “HS-206: all 24 cartons delivered.”
Signed delivery note: “20 cartons received; four outstanding.”
- 2 / Proposed row in Review
A value needs confirmation.
In this example, Gent flags the conflicting quantities. The proposed quantity is blank and the row waits for a person to check it.
Order: HS-206 · Delivered: awaiting review
- 3 / After human correction
20 delivered. Source retained.
The reviewer checks the signed note, enters 20, and accepts the row. The CSV keeps its link to the source email.
Order: HS-206 · Delivered: 20
Gent can miss conflicts or extract a value incorrectly. Check important results against their sources.
Before you start
A small start. A result you can check.
Does Gent need my whole mailbox?
Forward selected emails and attachments to a Gent inbox. Your filters choose which messages run an action. Invited users can access only their assigned inboxes.
How do messages reach the right file or case?
Keep everything in one output, or use codes to separate projects, trips, shipments, or months. For separate outputs, matching emails use a subject code such as [INV-2026-10]. You can also select the output manually. A missing or invalid required code leaves the message in Inbox for you to route. You choose the grouping; Gent does not infer it from the message.
What if a result needs checking?
Check the suggested result against its sources before accepting it. CSV Review lets you correct a row; checklist Review lets you choose the items an email supports. Report Review changes the plan before you generate the report. Missing CSV values can wait for Review, stay blank, or use your default; flagged conflicts need Review.
What can my team review and export?
Review proposed rows, checklist evidence, and report-plan updates with their source links. Download CSV output for your spreadsheet. Reports use your references to guide their structure and content, and are currently text in Markdown format. Choose when to generate or regenerate a report; later emails update its plan, not the saved report. Reproducing a branded Word or PDF layout is not currently included.
What should we agree before sending company records?
Start with approved samples. Selected email and attachment content can be sent to the configured AI provider for processing. Agree access, provider use, retention needs, and costs before forwarding sensitive records. The linked evidence helps people check results; it does not guarantee extraction accuracy or document acceptance.
What does it cost?
Your organization can start with one inbox at no charge. Additional inboxes require agreed pricing. AI processing, storage, and any custom work can add costs. Discuss those costs with Gent before agreeing to terms.
What happens after I describe my task?
Your receipt appears on the page. A person at Gent reviews your task and follows up at your work email. They can ask questions, discuss an evaluation, or explain where the task falls outside current capabilities. Agree on samples, the output, and costs before deciding whether to proceed. Sending the form creates no account or invitation. Once Gent contacts you, reply to that email with any updates.
One recurring task
Which email task takes up too much of your time?
Copying details into spreadsheets, checking which documents have arrived, or assembling updates into a report?
Bring us one recurring email task. We’ll help you explore a workflow using a small set of approved sample emails and your team’s preferred output.
- Describe your task and the output you need.
- A person at Gent reviews it and follows up by email to ask questions or discuss an evaluation.
- Agree on approved samples, the output, feasibility, and pricing before deciding whether to proceed.
Start with a description, not private emails or files. Your receipt appears on this page; a person at Gent follows up by email. Sending this form does not create an account.