Skip to content
Eleven screens, drawn with sample data

Every screen in Insoora, at full size.

The agent dashboard, bulk upload, extraction and review, the policy list, a customer's history, the renewals view, exports and the customer's own portal — the whole product, in the order the work happens.

Every screen below is a drawing, not a screenshot. The policies, names, numbers and premiums on them are invented, and each view carries a “Sample data” marker in its own chrome. No production record, no real policyholder and no genuine insurance document appears anywhere on this website — which is also why these are built in markup rather than exported as images.

Act one · Getting documents in

Getting documents in

Everything Insoora knows, it read off a document somebody gave it. These are the three screens that happen between a PDF arriving and a record existing.

Bulk upload

Drop in one policy or a folder of them. Each file reports its own state — read, needs review, or failed — so your attention goes only where it is needed.

A failed file is reported, not hidden. One failure does not stop the rest of the batch, and nothing is retried silently.

Agent portal — Upload
Sample data

Extracted details, beside the document

The fields Insoora read, shown next to the PDF they came from. The record and the document never separate, so any value can be checked against its source.

No confidence percentage is published on this screen or anywhere else — only whether a field was read cleanly or flagged.

Agent portal — Extracted details
Sample data

The review queue

A field that could not be read confidently is handed back with the region of the page it came from highlighted. You confirm it, or you correct it.

Correcting changes the record, never the PDF. The document stays exactly as the insurer issued it.

Agent portal — Review a flagged field
Sample data

Act two · Working the book

Working the book

Once documents are in, the product stops being an extractor and starts being a place to work. This is the part an agent actually opens every day.

The agent dashboard

What is in the book, what needs attention, and what is expiring — the four counts an agent checks first, with recent activity beside them.

Every figure here is sample data in a drawn screen. None of it is a statistic about Insoora's usage; the site publishes no customer counts.

Agent portal — Dashboard
Sample data

The policy list

Every policy in one list, searchable by customer, insurer or policy number and filterable by status and expiry window.

Search covers the extracted fields and the customer record — not the full text inside every PDF.

Agent portal — Policies
Sample data

A customer's policy history

One customer's cover, year by year, across insurers — with the original document kept against every past policy.

History starts at the first upload. Years that were never added to Insoora cannot be recovered by it.

Agent portal — Policy history
Sample data

Building an export

Choose the columns, choose CSV or Excel, and take the list into whatever you already use for calls and reporting.

Export is an agent capability. Policyholder accounts download their own documents but do not export lists.

Agent portal — Build an export
Sample data

Act three · What your customer sees

What your customer sees

The policyholder's side is a different product with the same documents behind it: no book of business, no search across customers, just their own cover.

The customer portal

A year-wise history of the policies their agent has shared with them, with the original PDFs to download.

A customer can only ever open a policy assigned to them, and never another customer's records.

Customer portal — My policies
Sample data

Renewal tracking

Built from the expiry date printed on the policy, not from a reminder somebody set. A policy uploaded and forgotten still appears when its month arrives.

Insoora sends no reminder emails, SMS or push notifications. The renewals view is a list you open.

Agent portal — Renewals
Sample data

Who can reach what

Access is decided by role and checked on the server for every request — agents, sub-agents and policyholders each reach only what their role permits.

Insoora holds no security certification, has not been penetration tested, and does not yet offer multi-factor authentication.

Agent portal — Access by role
Sample data

On any screen

Your customer will open this on a phone.

The agent portal is a working tool and earns a desk. The policyholder's side is opened at a dealership counter or in a hospital corridor, and it is built for that.

Customer portal — My policies
Sample data
Customer portal on a phoneSample data

Side by side

Flick between the views

The same product in one frame, six views, switchable — useful for comparing two screens without scrolling between them.

All Policies
Policy NumberPolicyholderInsurerPolicy TypePremiumRenewal DateStatus
1412769663Rahul MehtaHDFC LifeTerm Insurance₹12,45010 Jan 2027Active
2201987764Priya ShahICICI LombardCar Insurance₹8,20022 Feb 2027Active
3321098876Amit PatelStar HealthHealth Insurance₹18,50005 Mar 2027Active
4412998871Neha DesaiSBI LifeEndowment₹15,00018 Apr 2027Pending

Want the reasoning behind each of these screens rather than the screen itself? The how it works page walks the same workflow step by step, and features sets out what each capability does and where it stops.

Get started today

These are drawings. Yours would have your policies on them.

Create an agent account and upload a few of your own PDFs — it is the only way to find out how well Insoora reads the insurers you actually deal with.