Insurance agency management software built around one shared book of business.
An agency's problem is not that policies are hard to store. It is that three people are storing them in three places, nobody can say what the agency holds, and the person who knows where last year's policy is went on leave. Insoora gives the agency one book, and gives each person exactly the access the agency granted them.
- One book of business, several people
- Capabilities granted per sub-agent
- The agency owns the plan and the credits
- Every upload attributed to who made it
On this page
How an agency is actually modelled
The agency is the account. Sub-agents belong to it.
Worth reading before anything else on this page, because it explains what you can and cannot delegate.
There is no separate agency portal and no agency role. The main agent account IS the agency: it holds the plan, it holds the policy credits, and it holds every policy anyone on the team uploads. A sub-agent is an employee of exactly one agency and has no plan, no credits and no book of its own.
That is a deliberately simple structure and it has one consequence worth stating: a sub-agent cannot take their policies with them. The records belong to the agency, which is usually the point of having an agency account at all — but it also means Insoora is not the right shape for a loose network of independent agents who each want to own their own data.
A sub-agent starts with read access and nothing else. Everything else is granted individually by the main agent, and anything to do with money or with the team itself cannot be granted at all.
- The agency's plan and policy credits cover every sub-agent's uploads
- Capabilities are granted per person, not per job title
- Billing and sub-agent management stay with the main agent and cannot be delegated
What it does not do
Nested structures are not supported. There are no branches, no regions and no sub-agents of sub-agents — the hierarchy is exactly two levels deep.
What changes
Three agencies, three things that stop happening
Each person keeps their own spreadsheet. The agency's total book is a question nobody can answer without an afternoon of merging columns, and two people have the same customer twice.
One book. Everyone uploads into it, the agency sees all of it, and a customer's policies gather under one record however many people sold them.
Only the owner is trusted with the system, so every policy any of the team sells comes back to one person as a WhatsApp forward to be entered later. Later is a backlog.
Sub-agents are granted upload — and only upload, if that is the decision. Policies arrive as they are sold and the owner reviews rather than transcribes.
Somebody new needs to answer customer calls about existing policies, which means read access to the whole book, which in a spreadsheet means edit access to the whole book.
Read access is the default a sub-agent starts with. Nothing is granted until the agency grants it, and nothing can be edited without the grant.
Delegating, concretely
What an agency can hand to a sub-agent
Eight capabilities, granted one at a time. This is the whole list — there is nothing else to give, and two things that cannot be given.
- 1
Read the book
Every sub-agent has this from the moment the account exists. They can see the agency's policies and documents without being granted anything. - 2
Upload policies
The capability most agencies grant first, and often the only one. The uploads spend the agency's credits and the resulting policies belong to the agency. - 3
Process, review and confirm
Three separate grants. An agency can let someone upload documents but keep the confirming of extracted fields with a senior person, which is the arrangement most agencies want while they are learning how well their insurers read. - 4
Assign a policy to a customer
For the policies whose mobile number did not match anyone on record. Granting this lets a sub-agent clear the assignment queue; withholding it keeps that judgement central. - 5
Export to CSV, and to Excel
Two grants rather than one. An export carries the same access rules as the screen it came from, so it can never contain a policy the person could not already open. - 6
Reveal masked contact details
Contact numbers are masked by default. Seeing them in full is a capability, which means an agency can staff a reviewing role without handing over its customers' phone numbers. - 7
What cannot be granted
Billing and sub-agent management. A sub-agent can never buy credits, change the plan, see payment settings, or add or remove another sub-agent — those stay with the main agent regardless of what else was granted.
The screens an owner works in
What running the agency looks like
Three views, drawn with invented data. The team, the book, and the export an accountant will ask for.
The team
Who is on the agency, what each person was granted, and how many policies each has uploaded.
The agency dashboard
The plan and credit position, how many documents are processing, how many need review, and what failed.
An export
Policy and renewal lists as CSV or Excel, with the fields chosen, following the exporter's own access.
Where this is not agency software
What an agency will not find here
The gaps most likely to matter to an agency owner, named rather than left to be discovered.
No commission or payout management
A commission rate stated on a document is stored with the policy, and each upload is attributed to the person who made it. There is no commission calculation, no split between sub-agents, no payout statement and no reconciliation against what an insurer paid.
No performance reporting
There is no league table, no target, no per-sub-agent revenue view and no growth comparison. Policies can be filtered and exported; what you do with the export is yours.
No branches or regions
The structure is two levels: an agency and its sub-agents. A multi-branch business cannot model its branches, and a network of independent agents cannot each own their own book.
No task assignment or internal messaging
Insoora does not assign work, track follow-ups, send internal notes or notify a sub-agent that something needs doing. The review queue is a shared list, not a workflow engine.
What the agency does get
Six things that come with one shared book
Attribution on every policy
Each policy records the agency it belongs to and the person who uploaded it, with an assignment history where it changed hands.
One search across everything
The whole agency's book by customer, insurer, policy number, status or expiry window — not three people's sheets merged by hand.
One renewal list
Policies ending in the next thirty days across the whole agency, built from the dates on the schedules.
Customers that gather
A policyholder served by two sub-agents is one record with both policies under it, matched by mobile number.
Exports for whoever asks
CSV and Excel, with the same access rules as the screen, for an accountant or an audit.
Access that is granted, not assumed
Every capability is an explicit decision, re-checked on the server for each request rather than enforced by hiding a button.
Frequently asked questions
Questions this page should answer
Keep reading
Where to go next
The pages that cover the next part of this, with what each one adds.
Create the agency account, then add your team.
The plan and the credits sit with the agency, so start there and grant capabilities afterwards.