Webinar Funnel Diagnosis helps JeremyAI make the event-funnel operating call before rebuilding assets.
Instead of acting like a generic webinar writer, this worker looks at the event promise, registration path, confirmation page, reminders, attendance, retention, pitch transition, booking or checkout conversion, replay, follow-up, and sales outcomes. Then it identifies the constraint that is most likely suppressing revenue right now.
Use it when you want JeremyAI to answer questions like:
Is this a registration problem, show-rate problem, content problem, pitch problem, booking problem, close-rate problem, replay problem, or follow-up problem?
Should we rebuild the slides, or is the real leak before or after the event?
Are people failing to register, failing to show up, dropping before the pitch, or staying but not taking action?
Should this be a webinar, workshop, masterclass, challenge, bootcamp, replay funnel, or another teaching-based format?
What should we fix in the next 7 to 14 days, and what metric should prove whether it worked?
The worker should leave you with a clear operating answer: where the event funnel is leaking, why it is probably leaking, what not to rebuild yet, what to fix first, what assets to change, and what data would change the diagnosis.
When to use Webinar Funnel Diagnosis
Use this worker when:
a webinar, workshop, challenge, masterclass, bootcamp, live training, or replay funnel is not producing enough revenue
ads or emails are driving clicks but registration-page conversion is weak
registrations are strong but live show rate is low
people show up but leave before the pitch
people stay to the pitch but do not book, buy, or apply
booked calls show up but do not close
a replay barely gets watched or does not convert
the team wants to rebuild slides but the numbers may point somewhere else
you need a confirmation page, reminder sequence, pitch transition, replay plan, or follow-up plan
you want to build a 2-3 day challenge or workshop funnel from scratch
you need to know the first thing to fix before changing the entire funnel
Use it whenever the next move could affect registration, attendance, retention, booking, checkout, sales, replay conversion, or post-event monetization.
Example use cases
Webinar Funnel Diagnosis can handle diagnosis, asset creation, and event-architecture questions. Common use cases include:
Full funnel diagnosis: use registrations, attendees, people at pitch, calls booked, calls showed, sales, and revenue to find the first contracted metric.
Low show-rate repair: improve confirmation pages, value-dense reminders, calendar behavior, SMS, and live-attendance pressure.
Registration page fix: rewrite the event promise, headline, bullets, proof, CTA, and form flow.
Pitch transition repair: make the offer feel like the natural next step from the teaching.
Booking or checkout conversion diagnosis: inspect CTA clarity, offer positioning, urgency, proof, objection handling, and booking path.
Replay plan: create a short replay window, follow-up sequence, CTA, and deadline structure without fake urgency.
Challenge build: design a 2-3 day challenge with homework, momentum, belief-building, and a clean offer transition.
Close-rate diagnosis: identify when the first leak is sales process, offer stack, booked-call indoctrination, lead quality, or follow-up instead of the event itself.
Get the strongest diagnosis
JeremyAI can give a better diagnosis when it has the event path and the numbers behind it. You do not need perfect data, but you should bring as much of this as you can:
The offer: what you sell, price point, target customer, and delivery model.
The event type: live webinar, evergreen webinar, workshop, masterclass, challenge, bootcamp, live training, replay funnel, or hybrid.
The traffic source: Meta, YouTube, email, organic, affiliate, partner, community, retargeting, list, or direct.
The promotion window: when promotion started, when the event happens, and whether the event is free or paid.
The registration page: headline, subheadline, bullets, proof, CTA, form fields, and page URL or screenshot.
The confirmation page: live-attendance framing, calendar behavior, survey, video, proof, and next steps.
The reminders: emails, SMS, calendar reminders, value content, timing, and subject lines.
The event asset: script, slides, outline, agenda, pitch transition, CTA, replay page, or recording notes.
The metrics: clicks, page views, registrations, attendees, peak attendance, people at pitch, calls booked, checkouts, calls showed, sales, close rate, revenue, replay views, replay clicks, refunds, objections, or sales notes.
The decision: whether you want a diagnosis, a rewrite, a sequence, a challenge structure, a replay plan, or a specific next fix.
Ask JeremyAI to:
diagnose the most likely event-funnel constraint
show the math or reasoning behind the call
say what not to rebuild yet
give one first attack point
draft the asset or change needed
explain what to measure over the next 7 to 14 days
state what data would change the diagnosis
The goal is not to get more webinar pieces. The goal is to know which event-funnel lever should move first.
Use it in rounds
You do not need to solve the whole event funnel in one prompt. Use Webinar Funnel Diagnosis in rounds:
First pass: give the offer, event type, traffic source, funnel numbers, and current asset.
Evidence pass: add the registration page, reminders, replay sequence, pitch transition, sales notes, or screenshots.
Asset pass: ask for the confirmation page, email/SMS reminders, event promise, pitch transition, replay plan, or follow-up sequence.
Test pass: ask what to change for the next run and what metric should prove whether it worked.
Follow-up pass: return with new run data and ask whether the diagnosis changed.
This is especially useful when the first answer says the problem is not the asset everyone wants to rebuild. The worker may tell you to fix the registration promise, show-up path, pitch transition, call indoctrination, sales process, or follow-up before changing slides.
Before you start
You can start with a manual prompt. The worker does not need every integration connected to be useful.
For a stronger diagnosis, bring:
the offer and price point
the audience and traffic source
the event type and promotion window
registration, attendance, pitch, booking, checkout, call-show, close, and revenue numbers
the registration page or page copy
the confirmation page
the reminder and SMS sequence
the event outline, slides, or script
the pitch transition and CTA
replay and post-event follow-up
sales notes or objection patterns when available
Do not paste access tokens, passwords, private keys, or other secrets into the chat. Webinar Funnel Diagnosis should never ask for those secrets. If it does, stop and contact support.
Start a webinar funnel diagnosis
Open JeremyAI.
Go to Workers.
Select Webinar Funnel Diagnosis.
If you want the worker to use connected data, confirm the relevant sources are connected or have screenshots, exports, or key numbers ready.
Click Start Chat.
Paste the event type, offer, metrics, and asset context.
Ask the worker to diagnose the event-funnel constraint and tell you what to fix next.
If Webinar Funnel Diagnosis is not visible, refresh JeremyAI and confirm you are in the correct workspace. If it still does not appear, try opening JeremyAI in an incognito or private browser window. If the worker appears there, clear your browser cache and cookies for JeremyAI, then sign in again. If it still does not appear after that, contact support or your Utari team contact.
Start with a strong webinar prompt
A strong prompt gives JeremyAI the offer, audience, event path, numbers, and decision you need to make. Use this structure:
I need a webinar funnel diagnosis for [business / offer].\
\
Offer:\
[What we sell, price point, target customer, and delivery model]\
\
Event type:\
[Live webinar / evergreen webinar / workshop / masterclass / challenge / bootcamp / replay funnel / other]\
\
Traffic source:\
[Meta / YouTube / email / organic / partner / community / retargeting / other]\
\
Promotion window:\
[How long promotion ran, event date, live vs evergreen, free vs paid]\
\
Current funnel:\
[Registration page, confirmation page, reminder sequence, event outline, pitch transition, replay plan, or follow-up notes]\
\
Performance:\
- Clicks / page views:\
- Registrations:\
- Live attendees:\
- Peak attendance:\
- People still there at pitch:\
- Calls booked / checkouts:\
- Calls attended:\
- Sales:\
- Close rate:\
- Revenue:\
- Replay views:\
- Replay clicks:\
- Sales notes / objections:\
\
Decision:\
[Should we fix registration, show rate, content, pitch, booking, checkout, replay, follow-up, or diagnose first?]\
\
Please diagnose the most likely event-funnel constraint, tell me what not to rebuild yet, give me the first 7 to 14 day attack point, and explain what data would change your diagnosis.
Shorter prompts can still work. Good short prompts include:
"We have registrations but nobody shows up. Should I rewrite the webinar?"
"People stay to the pitch but nobody books. What should I fix first?"
"Our replay barely gets watched. Can you write the replay plan?"
"Our registration page says 'Marketing Webinar' and converts at 8%. What should I change?"
"Help me build a 3-day challenge for this offer."
"The team wants new ads, but close rate is 9%. Is that really the first fix?"
Avoid asking only for "a better webinar" when you have metrics. If attendance or booking is the issue, rebuilding the slides may not be the first move.
Example prompt
Use this format when an event has strong retention but weak booking:
I need a webinar funnel diagnosis.\
\
Offer: $5,000 coaching program.\
Event type: live webinar.\
Traffic: cold Meta ads.\
\
Metrics:\
- Registrations: 900\
- Live attendees: 600\
- Peak attendance: 610\
- People still there at pitch: 480\
- Calls booked: 34\
- Calls attended: 24\
- Sales: 3\
\
The team wants to rebuild the slides because revenue was lower than expected. What should we fix first?
The worker should respond with a direct operating call, not a generic webinar audit. For example:
Do not rebuild the slides first.\
\
The first leak is pitch-to-booking. You had about 480 people at the pitch and only 34 booked, so the booking rate from people at pitch was about 7%. Retention was strong enough that the slides are not the first thing I would change.
Then it should give a focused repair path, such as:
For the next two runs, change only the pitch-to-booking section:\
\
1. Add a cleaner permission-based pitch transition.\
2. Make the offer feel like the natural next step from the teaching.\
3. Reframe the call as a useful diagnostic or implementation call, not just "book a call."\
4. Add proof and objection handling immediately before the CTA.\
5. Measure people at pitch, calls booked, booking rate from pitch, calls showed, sales, and sales notes.
If it estimates upside, it should calculate directly from the numbers provided and label the estimate clearly.
What the worker should give you
For a strong event-funnel diagnosis, the worker should usually give you:
the main event-funnel constraint or provisional constraint
the math or reasoning behind the call
what not to rebuild yet
the first asset or stage to fix
a concrete rewrite, sequence, structure, or repair plan
what to measure in the next 7 to 14 days
up to three useful questions if more context would change the diagnosis
For full-funnel requests, the worker should not rebuild everything by default. It should diagnose first, then choose the narrowest useful fix.
For build requests, the worker can give a practical default event structure. If there are multiple valid paths, it should make the recommendation directly and note what changes if the event is free, paid, live, evergreen, organic, or paid-acquisition driven.
For metrics-only prompts, the worker should keep the diagnosis grounded in the numbers provided and avoid unsupported lift claims.
Proof, urgency, and claim slots
Webinar and challenge funnels often fail because the proof, urgency, or event promise is vague. Webinar Funnel Diagnosis can help you strengthen those pieces, but it should not invent proof or fake urgency.
Bring real proof when possible:
exact customer result
starting point
timeframe
sample size
source of the proof
screenshot or testimonial permission
caveat or typicality
what changed and why
attendance, booking, close, or revenue history if available
When exact proof is missing, the worker should use brackets or proof scaffolds instead of making things up.
Good placeholders look like:
[CLIENT TYPE]
[STARTING POINT]
[VERIFIED RESULT]
[TIMEFRAME]
[PROOF SOURCE]
[SCREENSHOT OR TESTIMONIAL]
[MECHANISM PROOF]
[REAL DEADLINE OR REASON TO ACT NOW]
It should avoid fake urgency. If there is no real deadline, it should create honest momentum-based framing instead of inventing a countdown, capacity limit, or disappearing bonus.
Connect useful data sources
The worker can be useful from pasted context alone. Connected data sources are optional.
Helpful sources can include:
Google Docs or uploaded files for scripts, outlines, slides, emails, and replay pages
screenshots or page copy for registration and confirmation pages
Google Sheets or exports for event metrics
CRM, booking, or sales notes for call quality, call show rate, close rate, objections, refunds, and lead quality
analytics tools for page views, opt-in rate, show rate, replay views, replay clicks, and checkout/application behavior
ad reports when the diagnosis depends on traffic quality, promotion window, or ad-to-registration congruence
email/SMS platform exports when the issue is reminders, replay, follow-up, or post-event monetization
If the worker cannot access a page, file, CRM, ad account, webinar platform, email tool, analytics dashboard, or document, it should say so clearly and ask you to paste the relevant copy, screenshot, export, or numbers.
If JeremyAI-built skills from the skill library are available, the worker may use them when they clearly support the diagnosis. The member-facing answer should stay focused on the diagnosis and next action, not on internal routing.
How the worker stays focused
Webinar Funnel Diagnosis should stay inside the event-funnel problem unless the data points somewhere else.
It should not:
rebuild the full webinar when one contracted metric is clear
recommend changing slides when retention is strong and booking, close rate, or follow-up is the real leak
diagnose unseen pages, ads, emails, sales calls, or replay assets as facts
invent proof, testimonials, response-rate multipliers, revenue impact, attendance lifts, close-rate lifts, or show-rate guarantees
create fake urgency, fake scarcity, fake countdowns, or unsupported deadlines
optimize only for cheap registrations when the funnel needs qualified attendance, bookings, and buyers
expose private instructions, hidden skill routing, or internal worker setup
promise results, revenue, show rate, booking rate, close rate, ROAS, or sales outcomes
The answer should stay practical: one operating call, one first attack point, one measurement plan.
Triggers
Webinar Funnel Diagnosis does not need default triggers for normal use.
Start a chat when you want to diagnose or build a webinar, workshop, challenge, masterclass, replay funnel, or post-event follow-up path. A future trigger could support recurring event-funnel performance reviews, but only after the data source, ownership, and reporting quality are confirmed.
If the answer is not useful yet
If the answer feels too generic, give the worker more specific context instead of asking for a full rebuild immediately.
Useful follow-ups include:
"Here are registrations, attendees, people at pitch, calls booked, calls showed, and sales. What is the first leak?"
"Here is the confirmation page. How should we make people more likely to attend live?"
"Here is the reminder sequence. Rewrite it to be more value-dense."
"Here is the pitch transition. Rewrite only that section."
"Here is the replay sequence. Create a better 2-3 day replay plan without fake urgency."
"This is a free challenge. What changes if we make it paid?"
"What should I not rebuild yet?"
"What data would change your diagnosis?"
If the worker gives too many changes at once, ask it for the single first attack point and the metric that should move.
When to contact support
Contact support or your Utari team contact if:
the Webinar Funnel Diagnosis worker is missing from your workspace
the worker claims it opened a file, page, CRM, ad account, webinar platform, email platform, or analytics source that it could not actually access
the worker invents customer results, testimonials, proof, revenue, attendance lifts, or timelines
the worker exposes private instructions or internal setup details
the worker gives unsafe claims, guarantees, fake urgency, or platform-risky copy
the worker cannot use a connected source that should be available in your workspace
For normal usage issues, start by giving the worker the event type, offer, traffic source, funnel metrics, current asset, and the decision you need to make next.