The Inbox — documents arrive as email
Threads, the reading pane, attachments that already carry their status, and replying from a template.
Threads on the left, reading pane on the right
The layout is familiar: the list of threads on the left, the selected message on the right. The list header shows the total and how many are unread ("100 threads · 98 unread" in the filmed account), with a search box for sender or subject. Each row shows the sender, the time, the subject and how many attachments it has. Unread threads have a dot and bold text.
Opening a thread
Click a thread to open it on the right, with a lavender highlight on its row. The header shows the subject ("INVOICE i5672 … 474941") and "1 message" with the sender's address. Below it are the sender name and date, then the message exactly as it arrived. Often there's very little: the filmed thread just says "Thank you," plus an inline-image reference. The real content is in the attachments.
Attachments carry their pipeline status
This is where the Inbox does more than an email client. Each attachment chip shows the status KnowDoc has already given it. In the walkthrough, both files on the thread, INVOICEi5672.pdf and 474941.pdf, already show a red Flagged badge. You see the email and the extraction result side by side, so "why is this flagged?" and "what did the sender say about it?" are answered on one screen.
- 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.
Next, without going back to the list
Next, at the top right of the reading pane, opens the following thread. With 98 unread threads, mostly from the same few senders, you can work through the queue without going back to the list each time.
Replying from a template
Under the message is a reply box ("Write a reply…") 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.
Run your messiest freight bills through it.
Send us a few of your hardest multi-page freight bills, and see the split, the checks and the audit for yourself.
More resources