CRM
The book, and everything that happens to it.
Leads, pipelines, the calendar, client records and every conversation. The base every other tool plugs into.
Its own address: app.virtualcloser.com. Every app runs at app.virtualcloser.com until each one moves to its own.
Mortgage Protection pipeline
One board per product line · drag to re-disposition
What's inside
6 parts, and you get all of them.
AI that texts and books
Every lead gets a real conversation, in minutes.
It reads the thread, answers what was asked, handles the objection and books the time — at 9pm, on a Sunday, with nobody at a desk.
It answers what was asked
It reads the whole thread and replies to the specific thing in it — including the price question, which on most lines is the qualifying question rather than a stall.
It writes per product line
A mortgage protection opener references the house. A final expense one uses plain language. Eight lines, eight sets of prompts and cadences.
It knows where to stop
Underwriting, coverage and eligibility go to a licensed human — and the Underwriting Assistant is what that human opens next. STOP is instant and cancels the appointment. Quiet hours follow the lead's timezone.
It never pretends to be your producer. It identifies as the assistant on a named producer's team, and a check runs before every send to stop it claiming otherwise. Research on this is one-sided: 85% of policyholders say they want to be told when AI is involved.
Copilot
The AI that sets the CRM up, then works it with you.
The AI Lead Assistant talks to your leads. This one sits on your side of the screen — it configures the account, tells you why something is not working, and does the admin that piles up behind every conversation.
It works on what you are looking at
Open a lead and ask for the rundown, or name a record and ask about that one. It answers about a specific row and tells you which row it answered about — so an answer can never quietly be about somebody else.
Four things it can change, and no more
Add a note, create a follow-up task, complete a task, move the disposition. That is the entire write surface. It does not send texts, dial, book, reassign, or touch anything in bulk.
It asks before it changes anything that matters
A note is written when you ask for one. Moving a disposition shows you the record, the current state, the requested state and what follows — and waits. Cancel and nothing happened.
It reports what the database kept
A disposition can be reverted by the rules that protect your pipeline. When that happens Copilot tells you the change did not take, rather than reporting the value it asked for.
Priced, not yet purchasable. Copilot is unlocked for everyone — there is no seat to buy and no queue to join. It covers setting the account up as well as working it. You pay for what it actually runs, from AI credits you top up, and plenty of what it does costs nothing at all because the quick answers run no model.
Product pipelines
One household. Several policies. Nothing overwritten.
Each product line gets its own row for the household — its own disposition, owner and history — so a pivot never overwrites what came before.
A row per product
The same household can be Application Submitted on health and Interested on final expense at the same time. Two rows, two dispositions, one person.
An owner per product
The producer who owns the mortgage protection conversation isn't automatically the one who owns the annuity. Routing and aging handoffs follow the line.
A conversation per product
The board is shared; the talking isn't. Each line has its own openers, objection handling and AI prompt, because an IUL buyer and a final expense buyer don't respond to the same message.
Several products per household — one conversation at a time. The record is multi-product; the texting deliberately isn't. The AI works whichever line is live and picks up the next when it becomes live, so nobody gets two of your numbers about two policies on the same afternoon.
Email that sits beside the lead, not in another tab.
Most insurance email tools are broadcast tools. This is the other kind: the thread with one client, in the CRM, ranked by what actually needs a reply.
Sorted by what needs answering
Threads are triaged by urgency rather than arrival, so a client asking about a claim doesn't sit under a newsletter reply. The producer works a list, not an inbox.
Sent as the producer, attached to the record
Mail goes out from the producer's own address and the thread stays on the client, so the next person to open the record sees the conversation instead of asking who said what.
Templates and documents
Reusable templates for the messages every agency sends twice a day, with attachments, so a policy summary or a form goes out without rebuilding it each time.
This is not a marketing email platform. There is no campaign designer, no drip-newsletter builder and no subscriber list management, and we are not planning to become that — an agency that wants to send a monthly newsletter to twelve thousand contacts should use a tool built for it. What this replaces is the tab where a producer keeps client email that the CRM never sees. If broadcast marketing is the job you need done, this is the wrong half of the product to judge us on.
Clients & retention
Most CRMs go quiet the moment you sell.
Written business gets its own side of the system — servicing, messages, billing and the book — because what happens after the signature is what decides the year.
A client record worth reading
Policies, documents, payment status and history in one place — so the next conversation starts from what they already have rather than from scratch.
Servicing that isn't the producer's inbox
Client messages, a client-side command centre and billing live on their own screens, so routine service stops interrupting selling.
Persistency as an early warning
Lapses tracked by producer and by line of business, visible while there's still time to intervene.
This is servicing, not policy administration. We hold the client, the policies you wrote and what they're worth to you. We are not a policy admin system and there are no carrier data feeds — policy status changes come from you, or from a policy export you upload, not from an automated carrier connection.
Lead source ROI
The cheapest lead source is usually the most expensive.
Cost per lead is the number that's easy to get, so it's the one agencies optimise. This joins what you spent to what actually issued, per source.
Cost per acquisition, not per lead
What it actually cost to get one issued policy from a source — which regularly reorders the table against what cost-per-lead suggested.
Conversion at each step
How a source performs from contact to appointment to issued, so you can tell a data problem from a working problem.
Return, per source
Revenue against spend for each vendor and campaign, in one table, so renewing or cutting a source is an evidence decision.
It's only as honest as what you record. This joins lead purchases to prospects to clients. If policies get written outside the system, or spend arrives as a lump sum with no source attached, the table will be confidently wrong — and that's worth knowing before you rely on it.
Worth knowing
This is the one you cannot switch off.
Every other app reads or writes these same records, so the CRM is the base rather than an option — switching it off would leave the rest with nothing to work on. What you can do is buy nothing else. An agency that wants a book, a pipeline and a calendar and no phone system, no recruiting and no quoter is a complete customer, and the launcher shows them one tile.