Race week, without the spreadsheet.
An endurance race series moved registrations and email onto one platform, so every race starts from a live list instead of an export.
Where it started.
The series puts on races in several states. Registrations came in through its own site, the newsletter went out from a separate email tool, and race-week messages came from somewhere else again.
Every race started the same way: export the registrations, clean the spreadsheet, import it, and hope the list was current. One broad send to an old, cold list could hurt every email that came after it.
Built around how it already works.
Registration sync
Each registration lands on the athlete's record in the CRM the moment it's made, tagged by race and distance. No export, no import.
Email from the series' own domain
Campaigns and automated flows go out from the series' verified domain. Race-week reminders send themselves to the people registered for that race.
A look per race
Each race has its own brand look, so its emails carry its own colours and fonts while the whole series shares one account.
Sends that protect the list
Campaigns are targeted by engagement, a send that starts bouncing pauses itself before it can do damage, and every sent campaign is audited after it goes out.
Running every day.
- +Every registration lands in the CRM, tagged by race and distance
- +Race-week reminders go out on their own
- +Campaigns to a list in the tens of thousands
The staff work from one list. A new race is a new tag and a new look, not a new tool.