Policy issuance
Application, ID, proof of address and regulatory forms, checked for validity, completeness, signature and consistency across documents.
In major medical insurance, issuance and reimbursement start with an agent's email and a handful of PDFs that someone opens, re-keys and sends back for whatever is missing. orbit intake picks up that email, classifies the case, reads and cross-checks the documents and leaves a rule-based pre-adjudication for the control desk to decide.
The agent emails the policy application or the reimbursement claim with the ID, proof of address, medical report and invoices attached. An operations clerk opens every file, checks expiration dates, compares names, CURP and addresses across documents, adds up invoices against the expense breakdown and writes the return email listing what's missing. If a file came as a Drive link instead of an attachment, the case stalls and nobody knows why. Every round trip restarts the clock, and medical judgment gets applied late.
A multitenant platform that puts document intelligence at the front door of both major medical processes: it reads the agent's email, classifies it as issuance or reimbursement, reads the documents with OCR and vision, extracts the fields, cross-checks them in a correspondence matrix, applies a configurable rule catalog and leaves a pre-adjudication that a person approves or rejects before replying on the same thread.
From the agent's email to the reply on the same thread, with the decision in a person's hands.
A new email creates a folio in seconds; a reply on the thread updates the same case. Cases can also be filed from the portal.
The case is classified as issuance or reimbursement, each document is recognized and its fields extracted. Every document gets a status, including the ones that never arrived.
The matrix compares name, CURP, RFC, address and amounts across documents; the rules check expiration dates, medical coherence and per-item eligibility.
The case stops at pending decision. The control desk approves or rejects, and a short email with the observations PDF goes out on the thread.
It doesn't adjudicate on its own: the output is a pre-adjudication and the final decision belongs to the control desk. Medical review, fraud and high amounts are escalated to a person. It doesn't issue policies or pay claims: in the proof of concept the core system, medical bureau, e-signature and payment gateway are simulated, and real integration with the insurer's core is part of a pilot.
The modules that exist today in the proof-of-concept environment.
Application, ID, proof of address and regulatory forms, checked for validity, completeness, signature and consistency across documents.
Medical report, accident notice, expense breakdown and CFDI invoices, with medical coherence and per-item eligibility.
Every case with type, status, pre-adjudication, document progress and number of returns.
Turn rules on or off and adjust thresholds; the next pre-adjudication uses them right away, with no code changes.
Files sent as Drive or OneDrive links are logged with the reason, and the return email asks for them again.
Each insurer on its own subdomain, with its own branding, email alias, rules and isolated data.
Five differences from reviewing the case file by hand.
Request demoFields are extracted from the document and the matrix compares them; the person reviews what doesn't match.
The checklist shows, rule by rule, what passed, what gets returned and which value in the file triggered it.
The pre-adjudication waits for the control desk; medical, suspicious and high-value cases are escalated.
The agent's reply on the same thread updates the case and runs the rules again.
Amount thresholds, recurrence windows and the maximum number of returns are changed from the control tower.
An honest comparison between a hand-reviewed inbox and an inbox with pre-adjudication.
Built around an insurer's major medical operation, with the agent as the only point of contact.
Issuance and reimbursement, the case the proof of concept was built on. Buying teams: operations, claims and underwriting.
The same file reading and per-item eligibility serve any line that reimburses medical expenses against invoices.
In 30 minutes we'll tell you whether orbit intake fits your process, what it integrates with and what it doesn't, and what a pilot looks like. If it doesn't fit, we'll tell you that too.
Run the discovery with rocky