Submissions, renewals, certificates, and claims, worked by an agent instead of an inbox.

For brokers, agencies, and MGAs: Customers, Insurance, Clients, Inbox, Knowledge, and Finance around the agency management system and carrier portals you keep, with an agent that takes intake, drafts submissions, starts renewals on time, issues certificates, and opens claims, under your approvals.

ForCommercial brokersPersonal lines agenciesMGAs & wholesalersBenefits brokers
Minutesto a certificate of insurance, drafted from the policy and the holder in the email
90 daysahead: every renewal started on schedule, with the updated info already requested
1 agentper producer and account manager, working the inbox, the submissions, and the claims under your approvals
Before & after

Opser apps around the systems you keep.

Before
EmailEverything
Carrier portalsQuotes, binders
AMSPolicies
SpreadsheetRenewals
Word templatesCertificates, letters
Shared driveApplications, loss runs
After
Opser
  • Customers
  • Insurance
  • Client Portal
  • Inbox
  • Knowledge
  • Finance
  • + the workflows you describe
Connected, not replaced
Your AMSSystem of record
Carrier portalsQuotes, binders
AccountingCommissions, ledger
The problem

The book grows, and so does the inbox: every submission, renewal, certificate, and claim is a thread someone has to remember.

An agency runs on email. Applications arrive half-complete, carriers ask for the same documents twice, renewals are a spreadsheet someone checks on Monday, certificates are requested at 4pm for a site that opens at 8, and a claim is a phone call followed by a scramble for the policy and the photos. Account managers spend the day re-keying between the inbox, the carrier portal, and the AMS.

Opser puts an agent on every desk that reads the inbox and does the admin: it parses the application into a submission and flags what's missing, drafts the carrier submission and the quote comparison, starts renewals on schedule, issues the certificate from the policy, and opens the claim from the client's email. People decide; the agent drafts, chases, and files. Nothing here underwrites or makes a regulated decision.

AI workflows across the apps

From intake to claim, without the inbox running the agency.

Each one is a job your team does today by hand across several tools. On Opser one agent does it across the apps below and the systems you keep, and you approve.

01

Client or submission intake

  1. Inbox
  2. Customers
  3. Insurance
  4. Clients
Before

An application arrives as a PDF or an email with attachments. Someone re-keys it, notices what's missing a week later, and asks again.

With Opser

The agent parses the application and attachments into a submission on the client's record, flags the missing fields and documents, and drafts the request to the client.

New submission from Elektro Hub for property. Parse the application and tell me what's missing.

02

Submission → carriers → quote comparison

  1. Insurance
  2. Knowledge
  3. Inbox
  4. Your system
Before

Marketing a risk means the same email to five carriers, replies scattered across threads, and a comparison assembled in a spreadsheet.

With Opser

The agent drafts the submission per carrier from your appetite notes, tracks who replied and who declined, and builds the quote comparison and the proposal for the producer to approve.

Market the Rossi GL renewal to Generali, Allianz, and Zurich, and build the comparison when quotes are back.

03

Renewals started on time, every time

  1. Insurance
  2. Clients
  3. Inbox
Before

Renewals are a spreadsheet. The ones nobody looked at become a scramble the week before.

With Opser

Every policy enters the renewal pipeline 90 days out. The agent requests updated information, pulls loss runs, flags what should be remarketed, and drafts the renewal pack for review.

What renews in the next 60 days, what's not started, and which ones should we remarket?

04

Certificates in minutes, from the policy

  1. Inbox
  2. Insurance
  3. Clients
Before

A certificate request at 4pm means finding the policy, opening the template, and typing the holder by hand.

With Opser

The agent reads the request, drafts the certificate from the policy with the holder and wording from the email, and sends it once you approve. Logged on the policy.

Issue a COI for Rossi Costruzioni naming Comune di Milano as holder for the Via Roma site.

05

Claims intake and admin

  1. Inbox
  2. Insurance
  3. Your system
  4. Clients
Before

A claim is a phone call, then a hunt for the policy, the photos, and the carrier's form.

With Opser

The agent opens the claim from the client's email and photos, files the first notice on the carrier portal, collects the missing documents, and keeps the client posted at each step.

Casa Più reports a pipe burst at the Rome store. Open the claim and prep the FNOL.

Apps

The apps insurance assembles. And the part that's only yours.

Each app owns a business domain and comes configured for this industry. Open any of them to see the screens inside. The last card is the workflow we haven't built yet, because it's yours.

AI inside the system

The agent works the inbox, the submissions, and the renewals, so account managers advise instead of re-key.

Because clients, submissions, policies, certificates, and claims live in one system next to the inbox, an agent can act across them instead of your team copying between email, carrier portals, and the AMS.

  • Parses applications and emails into submissions and flags what's missing
  • Drafts carrier submissions from your appetite notes and builds the quote comparison
  • Starts renewals 90 days out, requests updated information, and drafts the renewal pack
  • Issues certificates from the policy on request, for approval
  • Opens claims from the client's email and photos and files the first notice
  • Answers "what's Tecnomat's fleet limit?" and "which policies renew in October?" in seconds

Every person gets their own agent; teams can share one. Sensitive actions wait for approval, and every action is logged with the data it used and the outcome.

What changes

From an inbox that runs the agency to a pipeline the agent works.

  • Every submission, renewal, certificate, and claim is a record with an owner and a next step, not a thread
  • Renewals start on schedule, with the updated information already requested
  • Certificates take minutes and are logged on the policy
  • Claims are opened the day they're reported, with documents collected without chasing by hand
  • Your AMS stays the system of record; the agent writes to it instead of your team
FAQ

What teams in your industry ask.

Does the agent make underwriting or coverage decisions?
No. It does the operational and administrative work: intake, drafting, chasing, comparing, filing, and answering from the record. Every coverage decision, recommendation, and binding action is made by a person, and the agent's drafts wait for approval.
We run an agency management system. Do we replace it?
No. Keep it as the system of record. Opser sits around it: the agent reads from it and writes to it, and your team works in Opser's apps and inbox instead of re-keying.
How do carrier portals fit in?
Where a carrier has an API, the agent uses it; where it doesn't, the agent prepares everything and a person submits, or the agent works the portal under your approval. Quotes and binders that come back by email are read into the submission.
Can clients request certificates themselves?
Yes. The client portal lets them request a certificate, report a claim, upload documents, and see their policies. The agent drafts the certificate from the policy and an account manager approves it.

See your submissions, renewals, and certificates on Opser.

Book a demo and bring a real application or renewal. We'll show you intake, marketing, the renewal pipeline, and a certificate issued from the policy, on one system.