The Inbox — documents arrive as email

Opening a thread

Selecting a thread fills the reading pane with the subject, the sender, and the full message body exactly as it arrived. For carrier billing that body is often the only place the human context lives — a note about a re-bill, a reference to a previous dispute, an apology for a late submission.

Attachments carry their pipeline status

This is where the Inbox stops being a mail client. Each attachment shows the status KnowDoc has already given it — the walkthrough opens an invoice PDF that is already wearing a Flagged badge. You are looking at the email and the extraction outcome in the same view, so "why is this flagged?" and "what did the carrier say about it?" are one question rather than two screens.

• Extracted — Read cleanly; already downstream.
• Flagged — Hit an exception — jump to Flagged for the reason.
• Needs review — Read fine, waiting on a person to approve.

Replying from a template

Reply opens a composer with a Templates picker. Picking one types a canned reply straight into the body — the recurring carrier conversations (chasing a missing load number, requesting a proof of delivery, acknowledging a re-bill) are already written. Edit before sending; the template is a starting point, not a form letter.

Send, and the thread stays with the document

Sending keeps the reply on the same thread, so the next person to open that document sees what was already asked and when. Two rules keep the queue honest: always reply from the thread rather than a separate mail client, so the record stays complete, and check the attachment's badge before you write — the answer to the carrier is often already on screen.