Describe the documents that belong together.
Use natural language to identify a document type by its contents and business context—not just its filename.
Document routing
Determine how documents get logically processed
Decide which documents go where by using natural language.
One intake. Several destinations.
Route documents by what they mean
Conceptual workflow
Incoming documents
Invoice
Purchase order
Inspection report
Natural-language routing
Read. Match. Route.
Logical destinations
Invoices
Orders
Inspections
Routing logic your team can understand
Control what happens after a document arrives
Send each match to the right table.
Connect the routing decision to the destination whose schema should process the PDF and hold its extracted records.
Choose how confident the decision must be.
Set the threshold a match must meet before a new project-inbox attachment continues automatically.
Keep uncertain documents out of the wrong workflow.
Send low-confidence decisions to Human Review so your team can choose the correct destination before extraction continues.
Give every document a logical next step.
Create routing rules for the PDFs arriving in your project inbox.