The Book creates the work row and sends the carrier or TPA message so the AM is not writing it from scratch.
The Book
The Book sends.
You finish.
Loss runs, Schedule As, audits, and renewal outreach should not begin by starting the email from scratch. The Book opens the work row, addresses the right carrier on that line, and sends the request. Review, exceptions, and client decisions stay with your team.
Hosted workspace. No separate CRM to buy. Sits next to your AMS it does not replace it, issue certificates, or file forms.
Commercial P&C agenciesEmployee benefits shopsP&C and EB in the same shop
The BookClient companies · active view
Needs attentionMy workAwaiting carrierRenewals
#
A · Company
B · LOB
C · Work
D · Status
E · Next broker action
01
Apex ManufacturingTravelers · Pol# 558821
P&C
Request 5-Year Loss Runs
Needs Broker
Review the overdue carrier request
02
Meridian LogisticsAnthem Group# 204817
EB
Schedule A Collection
Awaiting Carrier
Monitor the carrier reply
03
Riverstone AdvisorsPolicy context pending
EB
Renewal Options
Needs Client Info
Confirm the requested data
A. Client details and contactsB. Policy lines, carriers, IDsC. Renewal and task statusD. Carrier communication context
Schedule A to medical is not Schedule A to dental. Loss runs go to the writing company on that policy.
The Book sends the carrier follow-up. When the stall is the group, it sends that ask to the client. You review the reply and close the row. Status is work state, not a compliance opinion.
The file stays in Epic, AMS360, HawkSoft, or BenefitPoint. Certificates stay there too. This is the outreach layer.
What The Book sends
The same motion on both sides of the book.
A date hits. The Book opens a work row on the company, addresses the right contact for that line, and sends the request. If something is needed from the group first, the AM sends that ask. The carrier request waits. The broker still reviews the reply and closes the file.
P&C
Commercial carrier outreach
The pre-renewal pile every account manager already runs in Outlook.
- 5-year loss runs from the writing company
- Exposure, payroll, vehicle, and property schedule updates
- Incumbent renewal and wholesale market follow-up
- Workers-comp and general-liability audit coordination
- Subjectivity, binder, and issuance chase
Employee benefits
Each carrier on the case
One group is not one inbox. Medical, dental, vision, life, disability, and stop-loss each get their own request.
- Schedule A from every carrier and vendor on the case
- Renewal quotes and implementation follow-up by line
- Gag-clause attestation and RxDC coordination
- SBC, Part D creditable-coverage, and OE artifacts
- Census or missing data from the employer when that is the blocker
Not in founding scope: certificate issuance, ACORD production, live AMS or carrier downloads, or filing Form 5500 for the client.
From static sheets to connected work
A spreadsheet tells you what you have. The Book starts what has to go out.
The point is not a prettier grid. It is to take the recurring carrier request off starting the email from scratch and put it on the account, with the policy # or Group # already on the thread.
The old way
Scattered rows. Separate inboxes. Too much memory work.
A renewal date in one column. A carrier email somewhere else. A policy number in a note. A follow-up hidden in an inbox.
The Book
One client row opens the entire operating context.
A company becomes the anchor. Policy records, carrier contacts, policy # or Group #, work rows, status reasons, and threads stay connected to it.
01 Company — client, contact, owner
02 Policy — carrier, line, ID, term
03 Work — task, stage, next action
Built for the work behind the book
Start the request. Keep the judgment.
The best outcome is not a dashboard. It is an AM who is not rebuilding the same Travelers loss-run email or the same Anthem Schedule A request from memory every term.
Works alongside AMS360, Applied Epic, HawkSoft, NowCerts, BenefitPoint, Ease, and Employee Navigator. Those systems keep the file and the certificates. ComplyBroker starts the outreach those tools leave in inboxes.
See The Book →Dated work, already queued
Renewal minus 90, plan-year minus 120, audit period end. The row appears before someone remembers to start the email.
The right carrier on that line
Policy # or Group # goes on the subject. Medical is not dental. Travelers WC is not the GL market.
Client ask when the file is blocked
If something is needed from the group first, the AM sends that ask. The carrier request waits.
Clear workflow boundaries
The Book sends follow-up. It does not issue certificates, file 5500s, bind coverage, or decide compliance.
How The Book takes shape
Load your book. The Book sends. You finish.
Your spreadsheet and AMS export are the starting point. We structure companies, one policy record per line, and the carrier contact on that line.
Structure the book by line
Client, each policy or group line, term dates, and the carrier or TPA contact who actually gets the request.
Turn on the outreach calendar
Loss runs, Schedule As, audits, OE artifacts, and renewal follow-up fire on the dates your shop already uses. We configure and test before anything sends.
Broker finishes the file
Read the reply, chase what is missing, put the artifact in the AMS, and make the client decision. The Book does not close that loop for you.
Sending is configured, not guessed. A template does not email a carrier the moment you ask for it. We set the trigger, recipient, subject (policy # or Group #), and follow-up cadence, then test it on your book.
Built for the book, not another system of record
Your team logs into ComplyBroker. That is the only workspace they need.
ComplyBroker hosts The Book for your agency. Your team logs in here. The client row is the anchor. Each line has its own policy record and carrier contact, so a Schedule A to Anthem medical is not a Schedule A to the dental carrier, and a Travelers loss-run request is not a wholesale follow-up.
LayerWhat the broker sees
CompanyClient, owner, primary contact, renewal window.
PolicyCarrier, line, policy # or Group #, term dates.
WorkTask, status reason, owner, next broker action.
ThreadCarrier or client mail filed on that company.
CONNECTED RECORDS
The client row is the start of the story, not the end of it.
Each layer answers: what is this account, what needs attention, and what happens next?
Get started
Start with a clearer view of the book.
Founding is The Book configured plus guided setup. Growing is a scoped conversation for larger books and multi-producer teams. Explore The Book before you buy.
Founding agency
$297/month
For agencies ready to stop starting loss runs and Schedule As by starting the email from scratch.
- Client, per-line policy, and carrier-contact structure
- P&C and EB outreach templates with tested send + follow-up
- Hosted workspace and user logins included
- Guided setup on your current book
Setup is normally $500. Founding seats include it. First charge $297, then $297 each month. Cancel anytime under the terms at checkout.
Claim founding rate →Growing agency
Built around your team
For larger books, multiple producers, or agencies that need a scoped implementation before choosing an operating setup.
- Map your current book and team workflow
- Discuss fields, views, and approved task requests
- See the completed Book first
Questions, answered
A clear operating model before you commit.
No. Keep AMS360, Epic, HawkSoft, NowCerts, or BenefitPoint as the system of record. ComplyBroker starts the carrier and client outreach those systems leave in inboxes. We do not issue certificates, produce ACORD forms, run carrier downloads, or store the policy file.
No. ComplyBroker is a hosted agency workspace. Users get a ComplyBroker login. You do not purchase or administer another platform to use The Book.
Yes. Medical, dental, vision, life, disability, stop-loss, and other vendors on the case each get their own work row and thread. A Schedule A request is not one group email. The same rule applies on P&C: the writing company on that line gets the loss-run or audit request.
Then The Book starts there. Census, exposure schedules, and missing plan data go to the employer or risk manager first. Status stays Needs Client Info until the carrier request can go out clean.
Not as a live two-way sync today. We import the book and send from The Book. Wholesale and surplus follow-up is a work type — a thread to the wholesaler not a market-submission network. Live AMS sync is roadmap, not founding.
Mail is filed on the company and on the line. The subject carries the policy line and the policy # or Group #. From the thread you open the work row without searching Outlook. This is not a full archive and not a document vault.
No. Status means the request is late, waiting on a carrier, or waiting on the client. The Book does not file Form 5500, attest gag clause, issue certificates, or decide coverage.
Client list, each line’s carrier and ID, renewal or plan-year dates, and who owns the account. That is enough to start the first outreach calendar.
The next view of your book
See the request leave the row.
Open the The Book and look at a loss-run thread and a Schedule A thread. Then book a conversation about your book.
Privacy
How book data is handled.
ComplyBroker Technologies provides a hosted agency workspace. Client, policy, contact, and work records you enter are used to operate that workspace for your agency. We do not sell book data.
Access is limited to your invited users and to ComplyBroker personnel who need it to implement, support, or secure the workspace. Infrastructure is provided by contracted processors. A list of subprocessors is available on request.
For a privacy question or deletion request, use the demo booking form or email the address collected at checkout. This page is a working notice, not a substitute for a signed data-processing addendum if your counsel requires one.
Terms
Founding is $297 per month. Setup included. First charge is $297. The subscription renews monthly until canceled under the terms presented at checkout. The The Book is a demonstration tenant with sample data. Do not enter real client data there.
ComplyBroker is a work-management layer. It does not provide legal, compliance, tax, or coverage advice and does not file regulatory forms.
Security
Traffic to the workspace is encrypted in transit. Each agency works in its own workspace. The public demo is separate sample data. We do not currently publish a SOC 2 report. If your agency requires a questionnaire, BAA discussion, or written security summary before loading a book, say so on the demo call.