Using Automation
The follow-ups that run themselves: welcome series, renewal reminders, birthday touches, and reply handling.
What automation covers
- Lifecycle: welcome messages for new clients, ID-card follow-ups about two weeks after an enrollment becomes effective, birthday and holiday greetings.
- Renewals: reminders driven by policy effective dates, so renewal season starts itself.
- Replies: inbound texts are classified: interest creates follow-up tasks; opt-outs are honored instantly; questions queue for a human.
Turning automations on
Each automation has its own page with an on/off switch, template editing (English and Spanish), and an audit log of exactly what was sent to whom. Start with the welcome series and renewal reminders: they pay for the setup time first.
The safety model
Automations share one suppression layer: do-not-contact flags, opt-outs, quiet hours, daily caps, and velocity limits apply to every send path. You cannot accidentally configure your way around them.
A sensible rollout
- Week 1: welcome series + ID-card follow-up.
- Week 2: renewal reminders (verify your policies have effective dates, the import guide covers this).
- Week 3: birthday/holiday touches and your first campaign.
Ready to put this to work? Launch ChronosCodex and follow along in your own workspace, or learn about the platform if you don't have one yet.