Webinar Registration Funnel Built for Show Rate

Between 28 and 46 percent of people who register for a Hebrew-language webinar actually appear, and the distance between those two figures is reminder plumbing and start time, not the registration page. This engagement is built around the seated number. What gets built: A registration page with four fields at most: name, mobile, company, and one qualifying question that decides which reminder track the registrant enters. Mobile numbers are normalised to E.164 at entry, because an Israeli number typed as 052-1234567 will not receive a WhatsApp message and nobody finds out until the day of the event. Registration posts to the Zoom Webinars or Livestorm registrant API and returns a per-person join URL, so attendance is attributable to the ad that produced the registration rather than to a shared link. The reminder path: Three messages: 24 hours, one hour, ten minutes. The ten-minute message carries the join link and nothing else. On WhatsApp these go out as pre-approved utility templates through the WhatsApp Business Cloud API, submitted at kickoff because approval takes days, and because a free-form message sent outside the 24-hour customer service window will not deliver at all. Email carries the same sequence for the segment that never opens WhatsApp. Add-to-calendar rate at registration is the leading indicator we read on day one; it predicts the seated count better than registration volume does. Time handling: The ICS file ships with a VTIMEZONE block for Asia/Jerusalem rather than a fixed offset. Israel's daylight saving does not move with Europe's, so an event scheduled in September for late October lands an hour off for every registrant whose calendar app trusted the offset. Israeli B2B sessions run Sunday to Thursday; a Thursday evening slot is dead and a Sunday morning slot competes with the start of the working week. We will argue about the time before we argue about the headline. Replay: One replay page with a stated expiry and its own call to action, and no pretence that the recording is still live. Attendance and replay watch time are posted back as offline conversions into Google Ads against the stored GCLID and into Meta through the Conversions API, so the media buyer optimises toward people who sat through it instead of people who filled a form. What is not included: We do not write the session, build slides, or rehearse the presenter. We do not run the ad campaign. We do not supply the webinar platform and will not migrate you onto one you are not already paying for. We do not build evergreen sessions dressed as live events, and we will not install a countdown that resets on refresh. If the reason the last webinar underperformed was the content itself, this work will not fix it, and we will say so on the first call rather than after invoicing. Who this is wrong for: Companies running fewer than four sessions a year, where the reminder engineering does not pay back. Teams with no named presenter who will be live on the call. Consumer list blasts where the mobile numbers sit against records with no consent trail; Israeli privacy rules and WhatsApp's own policy both bite there, and we will not build a route around either. Reporting: One document per event: registered, seated, median minutes watched, the timestamp where the room emptied, replay opens, and the source breakdown for each. Three pages, and it names the single thing to change before the next one.