Skip to main content
No email to forward? Use the upload button in the header to upload documents directly. Uploaded items show an upload marker. The Inbox lists the newest 100 emails received across your mailboxes. Older messages may not appear. Filter it with the chips at the top: All, Awaiting review, Completed, or Failed.

​
Reading an email

Click any email to open its detail view — a sheet on the dashboard, a pushed screen in the mobile app. Use the back button in the header to return to the list. Status chip — where the email is in the pipeline: Under the subject, a meta line shows the sender, recipients, and received time. Not processed — emails that weren’t processed because of your plan (TRIAL ENDED, LIMIT REACHED, PAYMENT FAILED, PLAN INACTIVE) show a card at the top explaining why, with an Open billing button. Once you choose a plan, held TRIAL ENDED emails process automatically; for other blocked emails, ask the assistant to reprocess them. Original email evidence — a collapsed card; expand it to read the retained source (fetched on first open). When the source has expired or retention failed, structured order records may remain. Original attachments — each attachment shows its filename and parse status: ok (parsed), skipped (not usable, e.g. an unsupported type), or failed. Supported types open inline with View: PDFs and jpeg/png/webp images render in place, and spreadsheets (xlsx/xls/csv) show their extracted text. Download saves the original file. What needs your attention — problems found in the source. For orders they’re grouped by order line in plain language; for invoices and other templates each problem is listed as written, with its line number when it belongs to one. A ⚠ marker means the issue blocks delivery. Missing, unreadable, or otherwise unusable source input shows an Approve anyway — tell us why field: explain why approval is appropriate anyway, or leave it blank to keep the issue unresolved. Non-blocking notes (no ⚠) cover inferred facts — a unit prefilled from the catalog, a unit price derived from total ÷ quantity — and a possible duplicate when the same order reference was already extracted from another email on this mailbox. A currency that can’t be resolved to an ISO 4217 code blocks delivery until you set it. Approved history used as context — past approved orders that informed this extraction. Past orders are suggestions, not authority for current quantities, units, prices, or ship-to facts.

​
Order review

For order emails, the Review the order form is where you correct the draft before approving. Check each line against the read-only source evidence; model confidence or text similarity is not a calibrated probability that the order is correct.
  • Customer account — who placed this order, used for delivery and product memory. Choose deliberately for forwarded orders or shared sender addresses.
  • Currency — the order’s ISO 4217 code (e.g. USD, EUR). Edit it when the extracted currency is wrong or ambiguous; an unresolved symbol blocks approval until a valid code is set.
  • Per line — the extracted evidence stays read-only (raw text, code, quantity, unit, and where it was found). Edit the Product SKU (from your active catalog), Description, Ordered quantity, Ordered unit, Unit price, and Line total. A Needs resolution note flags what the matcher could not settle. When the model’s pick falls below the auto-select confidence bar, the line stays unresolved and the candidate appears as a suggested entry in the SKU list — pick it per line, or use Accept all suggestions above the lines. Apply catalog units fills every empty unit field with the selected product’s catalog unit. + Create catalog SKU inside the SKU list adds the product without leaving the review. Remove line drops a line that isn’t part of the order.
  • Remember this customer code — when a customer is selected, save the intent to map the source’s code to the chosen SKU for that customer, optionally replacing a conflicting mapping. The mapping is committed when you approve the revision.
  • Add a line — append a line the extraction missed.
Click Save draft to store your edits. The form is editable while the email is awaiting review; after approval it is read-only.

​
Actions

Download data — appears in the header next to the status chip on every email that has an extraction result, whatever the mailbox’s output mode (in the mobile app it’s a row in the pinned bottom bar). Pick CSV, JSON, or Excel (.xlsx) to save the extracted data as a file. The action bar stays pinned to the bottom of the detail view:
  • Approve & deliver — appears on AWAITING REVIEW emails; saves any pending edits first, then sends the saved revision to the configured outputs. On an approved email whose delivery failed, it becomes Retry approved delivery.
  • Save draft — stores review corrections without approving.
  • Skip email — dismisses an email you never want processed (spam, noise, order confirmations the mailbox shouldn’t handle). Available on AWAITING REVIEW, FAILED, TRIAL ENDED, LIMIT REACHED, PAYMENT FAILED, and PLAN INACTIVE emails that aren’t approved. The email moves to SKIPPED — its source is kept and you can bring it back with Reprocess in the assistant (MCP reprocess_email). Emails already processing or carrying an approved revision can’t be skipped. Approving sends the order to your delivery targets. It does not confirm stock or fulfillment.

​
Delivery log

The DELIVERY ATTEMPTS section lists every delivery attempt: Use the log together with Troubleshooting when something doesn’t arrive. The mobile app shows the same sections — meta line, collapsible source evidence, attachments, the attention card, the order review form, and the pinned action bar.