Webhooks, never polling
Your team connects a mailbox — typically something like pricing@forwarder.com — through the Microsoft Graph API. From then on, a webhook subscription notifies Quotiveo the moment a new email arrives. No polling loops, no delays, no missed RFQs at 2am.
Microsoft Graph → Webhook → Quotiveo → New email detected
Connection
- ✓OAuth mailbox connection
Secure, scoped, revocable — your IT stays in control.
- ✓Instant detection
Graph change notifications fire on every new message.
- ✓Attachment download
Every attachment pulled and queued for processing automatically.
Classifier output
Only genuine RFQs and relevant follow-ups enter the pipeline. Everything else is filed away.
Every email, classified
Not everything in a pricing inbox is a quote request. An initial classifier sorts each message — new RFQ, follow-up, customer clarification, booking, invoice, general email, spam — so only real RFQ traffic consumes processing.
Threads stay together
This is critical: a customer replying "cargo ready September 10" must update RFQ #10482, not create RFQ #10483. Quotiveo tracks Outlook conversation IDs, message IDs, reply headers and customer matching to keep every message, attachment and clarification on the right shipment.
Company → Customer → Email thread → RFQ → Messages → Attachments. One hierarchy, no duplicates.
Attachment classification
Each attachment is classified so the pipeline knows what it's looking at:
| File | Document type |
|---|---|
Packing_List.pdf | PACKING_LIST |
Cargo_Details.xlsx | CARGO_DETAILS |
Invoice_Q3.pdf | COMMERCIAL_INVOICE |
unknown_scan.jpg | AI-classified |
Ingested. Now extract.
With the email classified, threaded and its attachments sorted, the document pipeline takes over: parsing, OCR and structured AI extraction with a source citation on every field.
Continue to AI extraction →See ingestion on your own inbox.
Connect a mailbox in a pilot and watch RFQs classify, thread and queue themselves — before your team has finished their coffee.
Book a pilot