How a Financial Advisory Firm Automated Multi-Event Reminder Operations Across Paid and Free Webinars

A financial advisory firm was running three different types of events simultaneously. Paid tax planning webinars, every two weeks. Paid 3-day live courses on personal finance. Free weekly webinars for warm prospects — people who had attended paid events but had not yet signed up for financial planning services.

Each event type had its own audience, its own message content, and its own reminder schedule. Six to seven reminder points per event, each sent across two channels — email and WhatsApp. And every single campaign was set up manually.

Over time they ran more than 100 events and reached 30,000+ attendees. For three years, every reminder sequence across every event was set up by hand.

The Problem

The firm used two tools for attendee communication. Brevo handled email reminders. Wati handled WhatsApp messages. Both required the participant list to be uploaded or updated manually before campaigns could be scheduled.

With one event type, this was painful but manageable. With three simultaneous event types — paid webinars, paid multi-day courses, and free weekly webinars — it became operationally chaotic.

Each event type had a different audience. Paid webinar registrants came in through the payment gateway via Zapier. Free webinar registrants submitted a form on the website. The paid course had its own registration flow. Each list lived separately. Each needed to be exported, cleaned, and imported into both tools before campaigns could be set up.

Then each reminder campaign — a separate setup in each tool, at each time interval, per event — had to be created with the right message for the right audience, scheduled for the right time, and pointed at the right list. Twelve to sixteen setups per event. Three hours of work. Multiple events running in parallel.

The risks were real and recurring. A campaign sent to the wrong list meant paid webinar registrants receiving messages about the free webinar and vice versa. A forgotten campaign meant a segment of registered attendees received no reminder and did not show up. A late registrant who joined after the manual sync was done received nothing.

The firm knew exactly what reminders were worth. Paid webinar attendance without reminders ran at 70-80%. With consistent reminders it reached 90%. Free webinar attendance without reminders sat at around 20% — a figure typical for free online events where commitment is low. With reminders it reached around 40%. In both cases, reminders were not administrative overhead. They were a direct driver of event ROI.

What Was Built

PhotonMan built an Airtable-based system that eliminated all manual campaign work across all three event types. The architecture has one governing principle: Airtable is the single source of truth for every participant list. Nothing else is.

How the system works

• All registrations flow into Airtable regardless of event type. Paid webinar and course registrations arrive via Zapier, triggered by the payment gateway when a transaction completes. Free webinar registrations arrive from a website form. Every registrant is tagged with their event type and associated with a batch that maps to a specific event date.
• When the team is ready to open a new webinar cycle, they switch the active batch in Airtable. One field change. One minute.
• Automated reminders are pre-configured with message content and timing — 7 days, 2 days, 1 day, 12 hours, 4 hours, 1 hour before the event. These do not need to be recreated for each webinar. They are part of the system.
• At each scheduled send time, the system reads the current participant list for the active batch from Airtable, passes it to Brevo for email delivery and to Wati for WhatsApp delivery, and sends.
• Any registrant who joins after the first reminder has already fired will receive all remaining scheduled reminders automatically. There is no manual intervention required to include late registrants.
• The batch history stays in Airtable. Every past webinar's participant list and send records are retained for reference.

No campaigns to create. No lists to export and import. No sync between tools to maintain. The system runs on its own from the moment the batch is switched.

Why Airtable as the backbone

The root problem was that two separate tools each had their own copy of the participant list, and keeping them in sync was manual work that created errors. The fix was not to find a better way to sync two tools. The fix was to eliminate the duplication entirely by making one system the source.

Airtable was already in use for client operations. Extending it to webinar participant management was a natural fit. It provided the relational structure needed to associate registrants with batches and batches with schedules — something a simple spreadsheet could not reliably maintain at scale.

See our Airtable consulting approach for how this single-source-of-truth pattern applies across other operational contexts.

The Results

The most direct impact was time. Three hours of setup work per event, across multiple simultaneous event types, was a significant recurring drain. That entire category of work was eliminated.

Paid webinar attendance held consistently at 90% once reminders were firing reliably at every interval without manual gaps. Free webinar attendance improved from around 20% to around 40% — a doubling of show rate for an audience that had low-commitment registration behaviour. Both improvements came from the same source: reminders that fired correctly, to the right list, every time.

The multi-event chaos was resolved. Three event types — paid webinars, paid courses, free webinars — all ran from the same Airtable base with no additional campaign setup per event. The system knew which audience each registrant belonged to, which message template applied, and which schedule to follow. Confusion between event lists was eliminated entirely.

The late-registrant problem was also solved without anyone noticing it had been solved. Previously, a registrant who joined after the manual sync missed all reminders. In the new system they received every reminder that had not yet fired for their batch. For an audience registering close to the event — already highly motivated — this made a measurable difference to show rates.

What This Means for Similar Businesses

Any business running recurring events — webinars, training sessions, product demos, onboarding calls — with a participant list that changes up to the event date will recognise this problem. The solution pattern here is not specific to financial services or to any particular tool.

The architecture is: one system owns the list, reminders read from that system at send time, no campaigns are pre-built and pre-targeted. The specific tools change depending on what the business already uses. The principle stays the same.

The leverage point is the batch switch. Once the system exists, the only human action required to run a new event's entire reminder sequence is updating a single field. Everything else is automated.

See our marketing automation consulting work for how this and similar patterns apply to sales and marketing operations for service businesses.

What We Learned

The original problem looked like a reminder scheduling problem. It was actually a data fragmentation problem. Multiple event types, multiple audiences, multiple tools — each maintaining their own copy of the truth. Automating reminder sending on top of that fragmented structure would have meant automating the sync between tools, which adds its own maintenance overhead and its own failure modes. Consolidating ownership of the participant data first, then building reminders that read from that single source, was the right sequence.

The delayed implementation is worth noting. The manual Brevo setup ran for two to three years before this system was built. That is a long time to absorb a recurring 3-hour cost. The reason it persisted that long is understandable — when a business is growing fast, the problems that are actively breaking things get fixed first. A process that is painful but functioning gets tolerated. The lesson is that the cost of tolerated inefficiency compounds quietly over years, and that the fix, when it eventually gets built, often turns out to be simpler than expected.

Three hours per event sounds manageable in isolation. Across 100+ events of multiple types running in parallel, it compounds into hundreds of hours of pure setup work. That is not a small operational tax. It is a significant one — and it was generating errors, confusion, and audience trust damage every time a campaign went to the wrong list or a reminder was missed. The one-time system build eliminated the entire category.

Anmol Gupta

Builder of systems, breaker of manual processes. Founder of PhotonMan. 12 years running a FinTech firm taught him that the best hire is often a well-designed workflow.