Halley Recon
Reconciles an insurer's statement against your policy book in eight controlled steps. A cycle that took specialists a day completes in under ten minutes, and each discrepancy is logged with an owner.
Motor endorsement processing for insurers and brokers
Halley Desk reads each endorsement request and its documents, checks them against the insurer's requirements, and follows the case until the endorsement is issued. Your operations team works only the cases that need a decision.
In daily use on a live motor desk, across 36 types of endorsement.
Results from a live motor endorsement desk
- 88%
- of insurer checks completed without a person
- 94%
- of document fields read correctly from customer documents
- 16 to 3
- manual touches per endorsement case
- 15 minutes
- to first response, down from about 4 hours
Measured on one motor endorsement desk in 2026. These figures are indicative, and results on another book will differ. A pilot measures the same things on your own cases.
How a case moves through Halley Desk
Each insurer asks for different documents and checks for each type of change. Halley Desk stores those requirements as configuration and applies them to every case in the same order.
Intake
The request is picked up from your ticketing system or a shared mailbox.
Policy lookup
The policy is read from your policy administration system.
Document check
Submitted documents are compared with the insurer's list. Missing ones are requested.
Verification
Documents are read, including scans and phone photos, and the insurer's checks are applied.
Reconciliation
The requested change is compared with what the documents show.
Inspection and payment
Changes that affect premium are routed for inspection and payment where required.
Submission
The request is sent to the insurer and followed up until the endorsement copy is received.
Closure
The outcome and status are written back to your ticket.
Cases that need a decision go to your team
When a check cannot be settled automatically, Halley Desk stops and assigns the case to a person. The reviewer sees the values in question and the rule that applied. Nothing is rejected automatically.
Chassis number does not match the policy
Needs review
| On the policy | MA3EYD81S00 … 4417 |
|---|---|
| On the document | MA3EYD81S00 … 4471 |
| Rule applied | Chassis number must match exactly |
| Next step | Assigned to a reviewer |
Illustrative example
Controls and security
Halley Desk is built for regulated operations. These controls apply to every case.
Amounts come from your systems
Premiums, refunds and payouts are taken from your policy administration system. The software does not calculate or choose an amount.
Rules first, models second
Fixed rules settle every check they can. An AI model is used only where rules cannot decide, and its output is validated by code.
People decide exceptions
Uncertain cases go to a reviewer, with the rule and the reason shown.
Complete audit trail
Every change to a case, by the software or by a person, is recorded with its reason in a log that cannot be edited.
Personal data is masked
Aadhaar and PAN numbers are masked to the last four digits before any text reaches an AI model.
Manual fallback
Any case type can be returned to manual handling with a single setting. Your operations team sets the thresholds.
What is available today
| Capability | Status | Detail |
|---|---|---|
| Ticket import, policy lookup, document checks and document requests | Live | In daily use across 36 endorsement types |
| Status updates written back to ticketing | Live | Enabled one case type at a time |
| Submission to insurers and follow-up by email | Built | Enabled per case type and insurer |
| Claim intake and service tickets | Configurable | Uses the same engine with new rules. About six weeks each. Not yet live. |
| Automation of insurer portals | Planned | For insurers that accept requests through a portal |
Security review
We work within your security policies and give your team full access for review. Go-live follows sign-off from your audit and compliance teams. Hosting can be in your cloud account, in ours, or in a private environment in the region you require. Client data is not used to train any model.
Motor policy changes from 15 December 2026
IRDAI's circular of 2 November 2026 moves motor policies to a four-part structure from 15 December 2026. Policyholders with third-party cover will be able to add occupant or pillion-rider liability cover during the policy term, with the same insurer. Each such request is a change to a policy already in force.
Source: IRDAI circular IRDAI/CIR/MOT/10/2026.
How a pilot works
A pilot runs for 90 days on one line of business. Each step can be reversed.
Weeks 1 to 2
Connect
Read access to policy administration and ticketing, single sign-on, a test environment and a security walkthrough. Your document lists and rules are configured.
Weeks 3 to 8
Shadow run
Halley Desk processes every case alongside your team and writes nothing back. Where the two agree and differ is recorded.
Weeks 9 to 12
Go live by case type
Write-back is enabled one case type at a time, after it meets a threshold you set.
What we measure, from a baseline taken before week one
- Staff time per case
- Cases closed without a person
- Turnaround time
- Cost per case
- Staff hours released
What we need from your team
- One integration engineer for about two weeks
- API read access and single sign-on
- A test environment
- A security review slot
- A named owner in operations
Other products
Two further products use the same rules engine and audit trail.
Halley Assist
A chat and voice assistant for agents. It answers payout questions and takes a motor policy from quote to issued document in one conversation, in English or Hinglish.
Request a desk assessment
A desk assessment is a 30-minute call at no cost. It shows which of your endorsement case types could be processed without manual work.
- Send the form with your details.
- We reply by email to arrange a time.
- On the call we ask about your monthly volume, your team and where cases are delayed.