The problem
Shared inboxes mix invoices, contracts, IDs, and everything else. People open each file just to decide which queue it belongs in. Misroutes sit for days because the only record is a folder name someone typed.
How the workflow runs
Upload a document
The hosted classifier accepts a file plus optional notes. The run starts from that submit, so there is a status to check instead of an untracked email attachment.
Classify by type
The starter predicts one of four categories: invoice, contract, ID, or other. If a classification agent is available it uses that model. Otherwise the workflow falls back to a classify step with those same categories.
Show the category
The predicted type is written onto the run and shown on the results page. Downstream solutions such as the customer portal can classify first and then extract fields.
What the hosted app shows
Operators drop a file on a hosted intake page and see the predicted type with the original document. The app is meant as a sorting surface, not a full review queue.
Who it is for
Operations teams that receive mixed document packets and need a first-pass type before extraction, review, or a customer portal takes over.
Questions
Yes. Open the canvas and edit the classify step. The starter uses invoice, contract, ID, and other so a new workspace has a working route on day one.
This starter returns the category only. Pair it with invoice desk, contract review, or the customer portal when you also need fields pulled out of the file.
The hosted app shows the predicted type. Add automations or extra workflow steps on the canvas when a category should start a different process.