Everything Insoora does, and where each feature stops.
Insoora reads insurance policy PDFs, files them under the right customer and tracks renewals. Below is each capability in detail — including the limits, because those are what you need before you commit a book of business to it.
On this page
Feature 01
Automated policy data extraction
Insoora reads an insurance policy PDF and pulls out the fields an agent would otherwise type: policy number, insurer, insured name, cover start and expiry dates, premium, and vehicle or asset details.
The document's own text layer is parsed first. When a page is a scan with no text, OCR runs over the image and the result is parsed the same way.
Each extracted field is saved against the customer with the original PDF attached, so the record and the document it came from never separate.
A field the parser cannot read confidently is marked as needing review rather than filled in with a guess, and is shown beside the document for you to confirm.
What it does not do
Accuracy depends on the document. Insurer-issued digital PDFs read best; photographs of printed policies and low-quality scans read worst. Insoora publishes no accuracy figure because it does not measure one it could stand behind.
Feature 02
Bulk policy upload
Upload many policy PDFs in one action and let them process together, instead of handling one document at a time.
The uploader shows the state of every file in the batch — read, needs review, or failed — so your attention goes only to the ones that need it.
A file that fails does not stop the rest of the batch.
What it does not do
Very large files and very long documents take longer to process; the batch view is where progress is visible.
Feature 03
Policy search, filters and sorting
Find any policy by customer, insurer, policy number, status or expiry window, then sort the result.
The same filters drive the renewals view, so a search can be turned straight into a working list for the week.
Results are paginated and keep their filters in the URL, so a filtered view can be bookmarked or shared with a colleague who has the same access.
What it does not do
Search covers the fields Insoora extracted and the customer record — it is not a full-text search inside the body of every PDF.
Feature 04
Customer-wise policy organization
Every policy is linked to its policyholder, so one search shows everything that customer holds and has ever held.
A policy finds its customer by the mobile number on the document, matched against the number the agent holds on record.
For an agency, sub-agents upload into the same book of business, and the agency sees the whole of it while each person sees only what their role allows.
What it does not do
Matching depends on the mobile number being read correctly and being the one on file; when it is not, the policy waits for an agent to assign it.
Feature 05
Historical policy access
Each customer's policies stack up year by year, with the original PDF kept against every past policy.
A past year's document can be opened, downloaded or shared without going back through email or a shared drive.
Policyholders see the same history in their own portal, for the policies their agent has shared with them.
What it does not do
History begins when a policy is uploaded. Insoora cannot recover documents for years that were never added to it.
Feature 06
Expiry and renewal tracking
The renewals list is built from the expiry date printed on the policy itself, not from a reminder someone remembered to set.
Policies ending within the next 30 days appear on the renewals view, sorted by date.
Because the date comes from the document, a policy that was uploaded and then forgotten still appears.
What it does not do
If the expiry date was one of the fields flagged for review and never confirmed, that policy's renewal date is only as good as the extraction. Confirming flagged fields is what keeps the list trustworthy.
Feature 07
Secure document access
Policy PDFs are held in private storage with no public URL, and every download is served through a link that expires within minutes.
Access is decided by role and checked on the server for every request: agents, sub-agents, policyholders and administrators each reach only what their role permits.
A policyholder can only ever open a policy assigned to them, and never another customer's records.
What it does not do
Insoora holds no security certification, has not been penetration tested, and does not yet offer multi-factor authentication. Those are stated plainly rather than implied away.
Feature 08
CSV and Excel export
Agents onlyAuthorized agents export policy and renewal lists as CSV or Excel for their own records and reporting.
An export follows the same access rules as the screen it came from, so it can never contain a policy the person could not already open.
What it does not do
Export is an agent capability. Policyholder accounts download their own documents but do not export lists.
Feature 09
Insurer template rules and extraction review
Admin configuredAn administrator can add per-insurer field aliases, regular expressions and validation rules, and test them against a real document before saving.
This is how a stubborn insurer layout gets read correctly: the rule is written once for that insurer, and later policies from them are parsed with it.
A separate corrections view shows where extraction was changed by hand, which is what tells an administrator a new rule is worth writing.
What it does not do
These rules are configured deliberately by an administrator. Insoora does not learn an insurer's layout on its own, and no machine-learning model is trained on your documents.
Try it with your own policy PDFs.
Create an agent account and upload a few documents — that is the only honest way to judge how well it reads your insurers' layouts.