For insurers, brokers and motor distributors
Motor endorsements, resolved without the manual work
Halley Desk reads the documents, runs each insurer's checks and chases what is missing. Your team sees only the cases that need a person.
Endorsement cases
Recent
- EN-20418 · Registration correctionResolved
- EN-20417 · Chassis correctionNeeds review
- EN-20416 · Address changeResolved
- EN-20415 · Nominee updateResolved
- EN-20414 · Hypothecation removalNeeds review
Illustrative example
- 88%
- of insurer checks decided with no person involved
- 94%
- of document fields read correctly on real customer documents
- 16 to 3
- human touches for one endorsement case
- 15 min
- to the first reply, down from about 4 hours
Measured on one live motor endorsement desk during 2026. These are indicative figures, not a guarantee of results on another book. A pilot replaces each one with a number measured on your own cases.
From 15 December 2026, motor policies move to a four-part format
Policyholders who already hold third-party cover can add occupant or pillion-rider liability cover during the policy term, with the same insurer. Each of those requests is a change to a policy already in force.
Source: IRDAI circular IRDAI/CIR/MOT/10/2026, dated 2 November 2026.
How it works
Every case runs the same eight stages
Each insurer wants different documents and different checks for each kind of change. Halley Desk holds that rulebook as configuration and applies it to every case.
- 1
Intake
The request arrives from your ticketing system or a shared mailbox.
- 2
Policy fetch
The policy is read from policy admin for that request only.
- 3
Document sufficiency
Documents are compared with what the insurer requires. Anything missing is requested.
- 4
Quality checks
Documents are read, including phone photos and scans, and the insurer's checks are run.
- 5
Reconciliation
The requested change is compared with what the documents say.
- 6
Inspection
Changes that affect the premium are routed for inspection and payment where required.
- 7
Execution
The request is submitted to the insurer and followed up until the endorsement copy arrives.
- 8
Resolution
The status and outcome are written back to your ticket.
Your team sees the exception and the reason
When a check cannot be decided, the case stops and a person takes over. They see the values in question and the rule that fired, so the decision takes seconds. Nothing is rejected automatically.
| On the policy | MA3EYD81S00 … 4417 |
|---|---|
| On the document | MA3EYD81S00 … 4471 |
| Rule that fired | Chassis number must match exactly |
| Next step | A person decides |
Illustrative example
Controls
Designed for a risk committee's first questions
It never decides money
Every premium, refund and payout comes from your systems. The model reads and words. It does not compute or choose a number.
Rules run before models
Plain rules settle everything they can. A model is called only when the rules cannot decide, and code checks its output.
People keep the exceptions
Anything uncertain goes to a person with the rule that fired and why. Nothing is rejected silently.
Every move is on the record
The system and your people change a case through one path. Each change goes to an append-only log with its reason.
Personal data is masked
Aadhaar and PAN numbers are masked to the last four digits before anything reaches a model.
You can switch it back
Any case type returns to manual handling with one setting. Your operations team owns the thresholds.
| Capability | Status | Note |
|---|---|---|
| Ticket import, policy fetch, document checks, document requests | Live | In daily use, across 36 endorsement types |
| Status written back to ticketing | Live | Switched on one case type at a time |
| Insurer submission and follow-up by email | Built | Switched on by case type and insurer |
| Claim intake and service tickets | Configurable | Same engine with new rules. About six weeks each. Not live yet. |
| Insurer-portal automation | Roadmap | Planned for insurers that take requests through a portal |
We have no third-party security certification yet. We work inside your security policies, give your team full access for review, and go live only after your audit and compliance teams sign off. 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.
Pilot
Ninety days on one line of business, reversible at every step
Weeks 1 to 2
Connect
Read access to policy admin and ticketing, single sign-on, a test environment and a security walkthrough. Your document lists and rules are loaded.
Weeks 3 to 8
Shadow
Halley Desk works every case beside your team and writes nothing back. We record where the two agree and where they do not.
Weeks 9 to 12
Live by case type
Write-back is switched on one case type at a time, and only after it clears a bar you set.
Five numbers, baselined before week one
- People time per case
- Cases closed with no person
- Turnaround time
- Cost per case
- Staff hours released
What we need from your IT 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
Products
Two more engines on the same rules and audit log
Halley Recon
Matches an insurer's statement against your policy book in eight gated steps. A cycle that took specialists a day runs in under ten minutes, and every gap becomes a file with an owner.
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.
Start with a desk assessment
Thirty minutes, at no cost. We ask how many endorsements you handle a month, how many people work them, and where cases get stuck. You leave with a view of which case types could run without a person.
Book a desk assessmentOr write to hello@halleydesk.com