If you've ever had an insured call furious because they just received 200 emails in the span of an hour — all from your agency — you already know what this post is about. If you haven't had that call yet, keep reading. Because it's a matter of when, not if.
The Setup
CSR24 is a powerful tool. Certificate processing, self-service portals, renewal batches — when it's configured correctly, it saves your team hours every week and keeps your insureds happy. But there's one account-level setting that behaves completely differently depending on whether you're issuing a daily certificate or running a renewal batch. And if your CSRs don't know about it, they will cause a problem — probably right in the middle of your busiest renewal cycle.
The setting is called "Send a copy of all certificates to this insured."
What It Does (And Why It's a Problem at Renewal)
For daily certificates — the one-off, ad hoc requests your team handles throughout the week — this setting is straightforward. If it's set to By Email, the insured gets a copy of each cert as it's issued. That's usually exactly what they want.
But at renewal time, everything changes.
When you run a renewal batch, CSR24 issues certificates to every active holder on the account in a single run. A mid-size commercial account might have 50 holders. A large contractor or property manager? Easily 200 or more.
It's Not Just About That One Setting
The renewal batch vs. daily distinction affects more than just the copy-to-insured field. Here are the other things your CSRs should be reviewing before every renewal run:
- Renewal Subject and Message — These fields control the email subject line and body that goes to your certificate holders during renewal. Leave them blank and holders get generic, boilerplate messaging with no context. Customize them and you look professional and prepared.
- Renewals / Batch Instructions — If your organization uses certificate instructions, these display on the batch page before processing begins. It's worth reviewing them each cycle to make sure they reflect any changes in the account.
- Confirmation Email Address — Staff changes happen. If that address hasn't been updated since last year, every cert confirmation is going to the wrong person — or worse, someone who no longer works at the company.
- Cert Naming Structure — Whatever naming convention is set at the account level will populate on every single cert in the batch. Easy to fix before you run it. Painful to fix after 300 certs have already been issued.
What Good Looks Like
Before a renewal batch, a well-trained CSR should be running through a quick mental (or literal) checklist:
- Turn off "Send copy to insured" for the duration of the batch
- Verify the confirmation email address is still current
- Customize the Renewal Subject and Message
- Confirm the cert naming structure is correct
- Review batch instructions
After the batch is done? Restore "Send copy to insured" back to By Email if that insured normally receives copies. It's a small step that's easy to forget — and forgetting it means the next daily cert won't copy the insured the way it should.
Why This Matters Beyond the Mechanics
This isn't just a software training issue. It's a client experience issue. An insured who gets flooded with certificate emails during renewal loses trust in your agency's ability to manage their account professionally. A certificate holder who gets a generic, context-free email wonders if something is wrong with their coverage. A confirmation that goes to the wrong address means someone at your agency isn't getting the verification they need.
The details of how CSR24 is configured at the account level are invisible to your clients — until they aren't. When something goes wrong, the client doesn't see a misconfigured setting. They see your agency.
The Fix Is Simple
Build account-level reviews into your renewal workflow. Make it part of your process, not an afterthought. Document the differences between daily and batch processing so your CSRs aren't discovering them for the first time during a live renewal run. Your technology should be working for you — and a few minutes of preparation before each batch run makes sure that it is.