A single pipeline for every inbound document
Email, upload, scan, or sync: every document enters through one inbound router, gets stored once, and parses and classifies in the background. The groundwork the smarter inbox is built on.
The unified inbox is where bills, receipts, statements, and compliance docs land. This is a look underneath it. Over the last few weeks we pulled every way a document can enter Zeno onto one shared pipeline, so email, upload, and sync from another system all take the same path.
Every entry point lands in the same router
Forwarded email, drag-and-drop upload, a check scan, a vendor statement, an MMS photo from a customer’s phone: each had its own entry point and its own quirks. They hit one inbound router now, get stored once in object storage, and join a single processing queue. The original file is preserved exactly as it arrived, and everything downstream reads that immutable copy.
Parsing happens out of band
Once a document is in the queue, parsing and classification run in the background, so an upload never blocks on them. By the time you open the inbox, Zeno has proposed what the document is (invoice, bill, receipt, statement), who sent it, and which property or project it belongs to. An ambiguous item waits in the queue showing what Zeno has worked out so far, rather than disappearing or committing to a guess.
What consolidation buys
Merging the entry points is housekeeping. The payoff is that an improvement to parsing, deduplication, or routing lands for every document at once, instead of for the one entry path someone remembered to update. Several of those improvements ship in the coming weeks, and this is the groundwork under them.
The inbound pipeline runs behind the inbox for every organization. Questions: [email protected].