Gemma, the AI chief of staff for the modern insurance broker.
Forward a client email or loop her into an iMessage thread and Gemma takes the busywork (intake, COI sends, ACORD fill) so you can focus on placement and bind.
How Gemma fits into your day
She lives in the channels your clients already use. You stay in the loop. No new portal to log into.
Forward or CC Gemma
Forward a client's email or loop Gemma into an iMessage thread. She picks up tone, context, and history from prior conversations with the same insured.
Gemma drafts and gathers
She replies in the thread to collect missing intake, pulls the right COI, or fills the ACORD, and remembers the insured across channels so the next request starts where the last one ended.
You review and bind
Every quote package, COI send, and filled ACORD lands in your queue. You approve, edit, or take it from there. Gemma defers to you on every bind and outbound send.
Two channels, one brain.
Gemma is the same agent on both surfaces. An insured who texts on Tuesday and emails on Thursday picks up where they left off.
iMessage & SMS
Replies feel native: read receipts, typing indicator, photo and PDF attachments. Most insureds never realize they are texting an AI.
Forward client threads to gemma@latentinsure.com and she replies in-thread, extracts attached PDFs, and threads the response back into your own inbox.
What Gemma handles today
Scope is intentionally narrow. These three workflows cover the bulk of broker inbox volume.
Intake
Gemma walks the insured through a structured question set in their normal text thread (legal name, locations, revenue, payroll, operations, special exposures) and hands you a clean submission ready for carrier markets.
- Structured intake in plain conversation
- Business enrichment from address or name
- Submission-ready package
COI & policy retrieval
When a client texts "send my COI to my landlord" or asks for a copy of their declarations, Gemma pulls the right document for the right policy and drops it into the thread. No ticket, no inbox triage.
- On-demand certificates of insurance
- Full policy PDF lookup by insured
- Additional-insured + holder routing
ACORD form fill
Forward an inbound email or photo of an existing application and Gemma extracts the fields, asks the insured for whatever is missing, and produces a filled ACORD PDF for you to review.
- PDF extraction from inbound docs
- Conversational gap-filling
- Reviewable PDF, not just JSON
Pricing
Flat monthly, no per-message metering. Beta pricing, locked for early customers.
Gemma Chief of Staff
Per broker seat, billed monthly.
Includes
- Unlimited insured threads
- iMessage + SMS
- Intake in plain conversation
- COI & policy retrieval
- ACORD form fill
- PDF extraction on inbound docs
- Long-term memory across channels
Questions brokers ask
How autonomous is Gemma?
Broker-in-the-loop by default. Gemma drafts replies, fills forms, and pulls documents, but a human broker reviews before anything goes to a carrier or is sent on a binding basis. You set the level of autonomy on routine asks like COI sends.
Which channels does Gemma run on?
iMessage (with SMS fallback) and email. The brain is shared. An insured who texted last week and emails today picks up in the same conversation.
What does the $100/month cover?
One broker seat, unlimited insured threads on iMessage and email, intake, COI/policy retrieval, ACORD form fill, and PDF extraction on inbound documents. Beta pricing, locked for early customers.
Where does the data live?
Conversations, attachments, claims, and form submissions are stored on Latent's secured infrastructure. Long-term memory of returning insureds persists across conversations. Nothing is sold or used to train third-party models.
What is Gemma not doing yet?
Binding policies, issuing payments, direct carrier portal submission, and AMS integrations are not in scope yet. We are explicit about this.
See Gemma run on a real broker workflow.
30 minutes. We'll show the iMessage flow live, walk through a filled ACORD, and answer your data and pricing questions.
Book a demo