The agent portal, screen by screen, with nothing invented but the policies.
This is where an insurance agent works: upload documents, read what came out of them, fix what was flagged, find a customer, see what expires this month, take a list away as a spreadsheet. Nine destinations, and every one of them is drawn below with an invented policy rather than described in the abstract.
- Nine real destinations, named as the product names them
- Six document states on the dashboard
- Three alert counts, not a vague bell
- Every figure below is sample data
On this page
Start with these three
The screens an agent opens every day
Of the nine destinations, three carry almost all the work. The other six are things you do occasionally.
Dashboard
Your plan and credit position, how many documents are processing, how many came out clean, how many need review, and what failed.
Upload Policies
One file or a few hundred, processed together, with the state of each one visible as it goes.
Policies
The whole book, searchable by customer, insurer or policy number and filterable by expiry window.
The landing screen
What the dashboard actually counts
Six states, and they are six because a document can fail in more than one way and the differences matter.
Every document you have uploaded sits in one of six states: uploaded in total, currently processing, successfully processed, skipped, needing review, or failed. Lumping "needs review" together with "failed" would be the obvious simplification and the wrong one — a flagged field is two minutes of your attention, and a failed file is a document that has to be sourced again.
Beside the counts is the plan position: which plan the account is on, its status, and how many policy credits remain against the limit. On a sub-agent's screen those figures are the agency's, because it is the agency's credits a sub-agent's uploads spend.
The alert bell carries three counts rather than one: policies expiring soon, extractions still waiting for review, and policies not yet shared with their customer. Those are the three backlogs that quietly turn into lapses, and a single undifferentiated notification count would hide which one you are behind on.
- Six document states, counted separately
- Plan, status and remaining policy credits
- Three alert counts: expiring, awaiting review, unshared
What it does not do
There is no revenue figure, no target, no growth chart and no league table. The dashboard counts documents and credits, which is what the platform actually knows.
One policy, end to end
What you do with a document that just arrived
Five actions in the portal. Two of them you will usually skip, because the document read cleanly.
- 1
Upload it
From the Upload Policies screen, alone or in a batch. The file is checked and classified as an insurance document before any extraction runs; a duplicate of something you already hold is recognised rather than charged for again. - 2
Read what came out
The extracted fields are shown beside the document they were read from — policy number, insurer, insured name, the period dates, the premium breakdown, and the vehicle or coverages where the line of business has them. - 3
Confirm, or fix what was flagged
A field the parser could not read confidently is marked rather than guessed. You confirm or correct it against the page. By default nothing is written to the policy record until a person confirms it. - 4
Check who it was filed under
The mobile number on the document is matched against the numbers you hold, and the policy is filed under that customer. If nothing matched, the policy waits in a queue for you to assign rather than landing on a near-enough name. - 5
Share it, if the customer has a login
Sharing a policy is what makes it visible in that policyholder's own portal. Until then it is visible only to your agency — which is why unshared policies are one of the three alert counts.
The screen that answers phone calls
Customers, and whether they can help themselves
The customer list has one column most people do not expect, and it is the useful one.
Search by name or by mobile number, open a policyholder, and every policy they hold and have held is there, by year, each with the document it was read from. That is the screen that answers "what cover do I actually have?" without opening a shared drive.
The column worth noticing is the portal state: whether this customer has a login and uses it, has been given one and never signed in, or has none at all. That is the list of people who will keep ringing you for copies of their own policies, and it is actionable rather than informational.
Contact numbers are masked by default. Seeing them in full is a capability an agency grants deliberately, which means a reviewing role can be staffed without handing over customers' phone numbers.
- Search by name or mobile number
- Every policy a customer holds, by year, with its document
- Portal state per customer: active, invited, or no login
What it does not do
There are no custom fields, tags, segments or notes on a customer. The record holds what the platform stores, and there is no deduplication tool — the same person under two mobile numbers stays two records until merged by hand.
The rest of the sidebar
The six destinations you use less often
Named as the portal names them, including the two that only appear if the account was granted them.
Search
A search across the agency's policies from the top bar of any screen, rather than only from the policy list.
Renewals
Policies ending within the next thirty days, sorted by date and built from the expiry on each schedule.
Sub-Agents
Your team and what each person was granted. Appears only on a main agent account with sub-agent management.
Exports
CSV and Excel downloads of policy and renewal lists, following the same access rules as the screen. A granted capability.
Plan & Credits
The subscription and policy credit position, and top-ups. Main agent only — a sub-agent can never reach billing.
Profile
Your own details and password. The one destination every account has regardless of what was granted.
About these pictures
What you are looking at, and what you are not
Two things to be clear about before you judge the product on this page.
These are drawings, not screenshots
Every figure on this page is built in markup from the product's own colours, type and components, with an invented policy and a "Sample data" marker. They are faithful to the real screens' structure and are not photographs of them.
Why there are no real screenshots
A screenshot of a signed-in agent screen carries a real policyholder's name, mobile number, policy number and premium. Publishing one would expose a customer's records to make a marketing page look more convincing, and no amount of cropping makes that a reasonable trade.
Your sidebar may be shorter
Sub-Agents, Exports and Plan & Credits appear only where the account has them. A sub-agent sees what its agency granted, and every page re-checks that on the server rather than relying on what the sidebar showed.
The product changes
A drawing can drift from the screen it describes. If something here does not match what you see after signing in, the product is right and this page is behind — tell us and we will fix the page.
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 an agent account and open the actual portal.
Upload three policies; the screens above are the ones you will land on.