Overview

WebinarStack is a webinar platform for building automated, replayable, measurable webinar funnels. It helps you create the webinar, publish attendee-facing pages, collect registrations, deliver the watch experience, route viewers through offers and interactions, follow up through automations, and measure what happened after launch.

The product is built around one practical idea: a webinar should not stop at playing a video. WebinarStack connects the webinar experience to audience behavior, automations, integrations, analytics, and AI-assisted workflows so your team can keep improving the funnel after it is published.

Use this overview when you are new to WebinarStack and want to understand the major parts of the platform before opening the detailed guides.

Product At A Glance

Area	What It Does	Where To Start
Webinar builder	Creates and edits the webinar draft, title, description, video source, schedule, replay behavior, and publish state.	Create your first webinar
Media Library	Stores hosted WebinarStack CDN videos and images, and helps teams choose between hosted media and external YouTube, Vimeo, or image URLs.	Media Library
Registration pages	Presents the webinar, collects attendee details, and sends registrants into the selected session flow.	Registration pages
Scheduling	Supports fixed sessions, recurring sessions, just-in-time sessions, blackout dates, and late-join controls.	Create your first webinar
Attendee experience	Controls the watch room, video source, chat, scripted messages, polls, CTA offers, replay behavior, and page routing.	Create your first webinar
Adaptive webinars	Lets a webinar use segment-level videos and branching paths so viewers can move through different experiences based on signals.	Create your first webinar
Automations	Runs rules based on registrations, attendance, watch behavior, poll responses, offer clicks, chat messages, schedule timing, adaptive branches, and more.	Automations
Email delivery	Sends attendee-facing email through connected providers such as SendGrid or Postmark.	Email Delivery
SMS delivery	Sends opt-in SMS reminders and follow-ups through Twilio.	Twilio SMS Integration
Live chat operations	Lets hosts manage live attendee chat inside WebinarStack or forward built-in chat into Slack.	Slack Chat Integration
Marketing integrations	Sends webinar events and attendee updates to tools such as Kit, ActiveCampaign, Mailchimp, MailerLite, Zapier, webhooks, and other connected platforms.	Kit Integration, ActiveCampaign Integration, Mailchimp Integration, MailerLite Integration, Zapier Integration, Webhooks
Analytics	Measures registrations, attendance, retention, funnels, revenue, attribution, attendees, and adaptive path performance.	Analytics
Developer and AI access	Uses API keys, REST API access, webhooks, and MCP so external systems and AI tools can work with WebinarStack.	API Keys, Claude Code MCP, Claude Web and Desktop MCP

The WebinarStack Workflow

Most teams use WebinarStack in a lifecycle like this:

Create a draft webinar.
Add the core title, public title, description, video source, and thank-you destination.
Configure the schedule with fixed times, recurring times, just-in-time availability, or a combination of them.
Customize the registration page and supporting attendee pages.
Configure the watch experience, chat behavior, polls, CTA offers, and replay behavior.
Connect the sending and integration systems the webinar will use.
Add automations for reminders, no-show follow-up, high-intent follow-up, CRM updates, webhooks, SMS, and marketing-list updates.
Preview the webinar, run test registrations, test the live room, and check the replay experience.
Publish the webinar.
Watch analytics, inspect attendee behavior, and improve the funnel over time.

A webinar starts as a draft. Publishing should happen only after the registration flow, session timing, watch experience, automations, and follow-up paths have been tested.

Core Concepts

Webinar

A webinar is the main object your team creates and manages. It has internal setup fields for your team and public-facing fields for registrants and attendees.

Important webinar setup areas include:

Internal title and public title.
Description.
Video source.
Schedule.
Registration and thank-you behavior.
Chat and interaction settings.
Replay settings.
Automations.
Pages.
Publish status.

The internal title helps your team find the webinar in the dashboard. The public title and description are attendee-facing.

Sessions

Sessions are the times attendees can register for and attend.

WebinarStack supports multiple scheduling models:

Schedule Type	Use It When
Fixed sessions	You want one or more exact dates and times.
Recurring sessions	You want a repeating weekly or recurring schedule.
Just-in-time sessions	You want visitors to see near-immediate session options when they arrive.
Blackout dates	You want to block generated sessions on specific dates.

You can combine schedule types. For example, a webinar can have a fixed launch date and a recurring schedule for evergreen traffic.

Visitors, Registrants, And Attendees

WebinarStack distinguishes between people at different points in the funnel.

Term	Meaning
Visitor	Someone who views a registration page or other public page before registering.
Registrant	Someone who submits the registration form and receives a session assignment or access token.
Attendee	A registrant who reaches the watch experience, live room, or replay experience.

Analytics and automations use these distinctions. A no-show automation is different from a low-retention follow-up because the underlying behavior is different.

Pages

WebinarStack creates and manages attendee-facing pages around the webinar flow.

Common page surfaces include:

Registration page.
Thank-you page.
Pre-webinar page.
Widget/embed experience.
Watch experience.
Replay experience.

The registration page collects signups. The thank-you page confirms registration or routes to your external destination. The pre-webinar and watch surfaces handle session access, countdown states, video playback, interactions, chat, and replay state.

Video And Media

A standard webinar can use WebinarStack-hosted media or a supported external video URL such as YouTube or Vimeo. Hosted media is uploaded and selected from the Media Library.

For adaptive webinars, video is managed at the segment level in the flow. Each segment can have its own timing and video source, which lets different branches use different content without forcing one linear recording for every attendee.

The Media Library also stores reusable image assets such as logos, header images, host avatars, widget logos, offer artwork, and page-builder images. Image fields can use an external URL or a WebinarStack CDN image from the library.

Interactions And Offers

Interactions are timed elements in the webinar experience.

The main interaction types are:

Interaction	What It Is Used For
Polls	Ask attendees a question, collect responses, and use responses for analysis or follow-up.
CTA offers	Show a call to action at the right moment in the webinar or replay.

Interactions can be useful on their own, but they become more powerful when connected to automations, analytics, and adaptive paths.

Examples:

Trigger follow-up when someone clicks an offer.
Segment attendees based on a poll answer.
Compare offer performance in analytics.
Route adaptive viewers through different paths.

Replay

Replay controls what happens after a session has ended.

Replay setup can include:

Whether replay access is enabled.
Replay expiration rules.
Replay video source.
Replay redirect behavior.
Replay chat behavior.
Replay-specific interactions.

Replay is not just a recording link. It is another stage in the funnel and can have its own follow-up logic.

Automations

Automations are rule-based workflows that run after attendee or webinar events.

Each automation has:

A rule name.
An enabled or disabled state.
A trigger.
Optional conditions.
An optional delay.
An action.
Delivery and execution history.

Triggers can come from registration, attendance, watch time, completion, offer clicks, poll responses, chat messages, scheduled timing, and adaptive webinar behavior.

Actions can send email, send SMS, call a webhook, or update a connected integration.

This is one of the most important parts of WebinarStack because it lets follow-up respond to what someone actually did, not just when they registered.

Integrations

Integrations let WebinarStack either send through your providers or notify external systems.

Important integration categories:

Category	Examples	What They Are For
Email delivery	SendGrid, Postmark	Sending registration confirmations, reminders, follow-ups, and automation emails from your provider.
SMS delivery	Twilio	Sending opt-in text reminders and follow-ups.
Live chat	Slack	Forwarding built-in attendee chat into Slack and sending Slack thread replies back to attendees.
Marketing lists	Kit, ActiveCampaign, Mailchimp, MailerLite	Updating subscribers, contacts, members, tags, lists, groups, custom fields, audiences, and related marketing-list state through automations.
No-code workflows	Zapier	Sending automation events into Zapier Catch Hook workflows.
Custom systems	Webhooks, REST API	Connecting WebinarStack to CRMs, internal apps, data warehouses, and backend workflows.
AI tools	MCP, Claude connectors	Letting AI tools inspect webinars, summarize analytics, and help create or update setup.

Credentials are stored and managed by feature area. A WebinarStack API key is different from a SendGrid key, a Postmark token, a Twilio credential, a Kit key, an ActiveCampaign key, a Mailchimp key, a MailerLite token, or a webhook signing secret.

Analytics

Analytics show how the webinar is performing across the funnel.

The analytics system covers:

Registrations.
Attendance.
Watch time.
Completion.
Retention.
Funnel conversion.
Offer clicks.
Poll responses.
Revenue attribution.
Attendee-level behavior.
UTM attribution.
Adaptive branch and segment performance.

Use analytics to find the next operational change. For example, low registration-to-attendance rate points toward reminders and registration-page expectation setting. Low retention before the offer points toward content pacing. Good attendance with weak offer clicks points toward offer timing, CTA copy, or segmentation.

API, Webhooks, And MCP

WebinarStack supports programmatic access for teams that want to connect the product to their own systems.

Surface	Use It For
API keys	Authenticate external systems to WebinarStack. Keys can be scoped by resource and surface.
REST API	Build backend workflows, imports, exports, sync jobs, and internal tools.
Webhooks	Send signed events to your own receiver or no-code tool.
MCP	Let compatible AI tools work with WebinarStack through typed tools instead of pasted context.
Claude connectors	Add WebinarStack to Claude Code, Claude Web, or Claude Desktop using the hosted MCP endpoint.

Use API keys and webhooks for systems that need deterministic automation. Use MCP when a human wants an AI assistant to inspect, explain, draft, or operate within approved boundaries.

Standard Webinars And Adaptive Webinars

WebinarStack supports both standard webinar flows and adaptive webinar flows.

Type	Best For	How It Works
Standard webinar	A single core presentation with shared timing, shared content, and shared offers.	The webinar uses the main video setup, timed interactions, registration flow, replay settings, and automations.
Adaptive webinar	Audience-responsive experiences where viewers may need different content, timing, offers, or follow-up.	The webinar uses segment-level content and branch logic so attendees can move through different paths based on behavior or responses.

Start with a standard webinar when you are validating the core offer, registration flow, and follow-up system. Use adaptive webinars when you know different attendee segments should receive meaningfully different content or offers.

Communication Channels

WebinarStack separates communication channels so each channel can use the right provider and consent model.

Channel	Managed In	Notes
Email	Settings > Email and webinar automations.	Connect SendGrid or Postmark before relying on attendee-facing automation email.
SMS	Settings > Integrations and webinar automations.	Requires Twilio, a valid sending identity, an attendee phone number, and SMS consent.
Chat	Webinar editor and optionally Slack.	Built-in chat can run inside WebinarStack and can be connected to Slack for host workflows.
Webhooks	Webinar automations or API webhook subscriptions.	Sends signed event payloads to external systems.
Marketing-list updates	Settings > Integrations and webinar automations.	Used for providers such as Kit, ActiveCampaign, Mailchimp, and MailerLite.

The same attendee behavior can often feed multiple channels. For example, an offer click can trigger a sales webhook, a Kit, ActiveCampaign, or Mailchimp tag update, a MailerLite group update, and an internal Slack alert through Zapier or another receiver.

Suggested First Setup Path

If you are setting up WebinarStack for the first time, use this order.

Read Create your first webinar and create a draft.
Add a video source and configure at least one schedule.
Review Registration pages and make the page match your offer.
Connect Email Delivery before relying on confirmations, reminders, or follow-ups.
Add the minimum automations from Automations.
Test registration, the watch room, interactions, replay, and each automation.
Publish the webinar.
Use Analytics to decide what to improve next.

After the base funnel works, add optional integrations:

Use Slack Chat Integration if hosts will answer attendee questions live.
Use Twilio SMS Integration if you want opt-in text reminders or follow-up.
Use Kit Integration if webinar behavior should update Kit subscribers, tags, or custom fields.
Use ActiveCampaign Integration if webinar behavior should update ActiveCampaign contacts, tags, lists, or custom fields.
Use Mailchimp Integration if webinar behavior should update your Mailchimp audience.
Use MailerLite Integration if webinar behavior should update MailerLite subscribers, groups, or custom fields.
Use Zapier Integration for no-code routing to CRMs, spreadsheets, alerts, or other apps.
Use Webhooks when your own backend or integration layer should receive signed events.
Use API Keys when external systems need authenticated REST API or MCP access.
Use Claude Code MCP or Claude Web and Desktop MCP when you want AI tools to work with WebinarStack.

Common Workflows

I Want To…	Use These Parts Of WebinarStack	Read This
Launch a simple automated webinar	Webinar builder, schedule, registration page, email delivery, preview, publish.	Create your first webinar
Run evergreen sessions	Recurring or just-in-time schedule, reminders, replay, analytics.	Create your first webinar
Segment follow-up by attendee behavior	Automations, poll responses, offer clicks, watch time, Mailchimp, webhooks, SMS.	Automations
Let hosts answer live questions from Slack	Built-in chat, Slack connection, webinar chat channel selection.	Slack Chat Integration
Send text reminders	Twilio connection, SMS consent, SMS automation action.	Twilio SMS Integration
Send webinar data to another app without code	Webhook automation and Zapier Catch Hook.	Zapier Integration
Build a custom integration	API keys, REST API, webhooks, signed payload verification.	API Keys and Webhooks
Ask an AI assistant to audit or update setup	MCP endpoint, Claude connector, scoped API key or OAuth grant.	Claude Code MCP
Understand why a webinar is underperforming	Analytics overview, retention, funnels, attendees, UTM, branch analytics.	Analytics

Operating Safely

WebinarStack can send real emails, SMS messages, webhooks, and integration updates. Treat production webinars carefully.

Before publishing or making large changes:

Keep the webinar in draft until setup is reviewed.
Preview registration and attendee pages.
Run a test registration.
Test the live room and replay state.
Confirm email delivery is connected and verified.
Confirm SMS consent is captured before SMS automations run.
Send test webhooks or Zapier samples before relying on them.
Keep API keys and provider credentials out of prompts, screenshots, support tickets, and source files.
Disable an automation when you want to pause it temporarily. Delete only when you intend permanent removal.
Review analytics before changing high-performing pages or automations.

How These Docs Are Organized

This help site is organized around user workflows rather than internal implementation.

Start with the overview and first-webinar guide if you are new. Use the integration guides when you are connecting external tools. Use the analytics and automations guides when you are optimizing an existing funnel. Use API, webhook, and MCP guides when another system or AI assistant needs to work with WebinarStack.

Internal engineering runbooks, source-code notes, production-only identifiers, secrets, and generated API reference pages do not belong in this help site.