Marketing
GoTo Webinar
Connect your AI to GoTo Webinar
Marketing managers, event coordinators, and sales development reps run webinars in GoTo Webinar, but knowing who registered, who attended, who asked a question, and who never showed up means exporting reports after every session. AI can turn that into follow-up lists in seconds, but only if it treats registrant data with care and only registers people through steps you approve.
Why it matters
Capabilities that matter most for GoTo Webinar
01
Follow-up lists without exports
Lists of registrants, attendees, questions and no-shows are ready after every session, without downloading a report.
02
Attendees beside your CRM
Join webinar attendees with CRM lists to see which accounts and deals each session reached.
03
Registrations through approved steps
AI tools register people only through actions you approve, and registrant data stays within per-user security.
Use cases
Example AI Use Cases for GoTo Webinar
scenario
-
After a webinar, getting attendees into Capsule CRM means exporting the list, searching each email, and guessing whether a near match is the same person. Done in a hurry, it fills the CRM with duplicates or leaves new leads out entirely.
What popdock provides
--
Name the webinar, and optionally its date and an owner for new contacts. It finds the webinar in GoTo Webinar, reads who actually attended, and checks Capsule CRM for each person by email and then by name. Anyone found by name with a different email is set aside as a possible duplicate rather than created. You see the people to create and the possible duplicates as a table, nothing is written until you confirm, only people are created, and it reports what was created, skipped and failed.
Business outcome
---
New webinar attendees land in Capsule CRM ready for follow-up, without duplicate contacts to clean up later.
scenario
-
To know whether a contact or their company is engaged with your webinars, you have to search GoTo Webinar email by email for registrations, attendance and questions. For an organization with many people, that turns into an afternoon of lookups.
What popdock provides
--
Name a Capsule CRM person or organization, or give an email, and how far back to look. It finds the contact in Capsule CRM, and for an organization gathers the emails of the people who work there. It then checks GoTo Webinar for each email's registrations, attendance and questions, telling no-shows apart from webinars that have not happened yet. You get a dated table, the questions asked with their answers and a one-line engagement summary. It only reads, and caps an organization at 25 people, saying how many were left out.
Business outcome
---
You know exactly how engaged a contact or account is with your webinars before you reach out.
scenario
-
People who registered for a webinar but did not show up are warm leads, yet following up means comparing registrant and attendee lists, finding each person in Capsule CRM and creating a task with the recording link. It usually gets skipped.
What popdock provides
--
Name the webinar, and optionally its date and how many days until tasks are due. It confirms in GoTo Webinar that the webinar has already happened, works out who registered and did not attend, leaving out cancellations, and finds the recording link. Each no-show is matched to Capsule CRM by email, ambiguous matches are listed rather than guessed, and contacts that already have a task for the webinar are skipped. You see the planned tasks for each owner before anything is created, and nothing is written until you confirm.
Business outcome
---
Every webinar no-show gets a follow-up from their owner with the recording link, while interest is still warm.
scenario
-
Questions asked during a webinar are buying signals, but they sit in GoTo Webinar where the account owner never sees them. Some were never answered on the day, and without a follow-up the person who asked hears nothing.
What popdock provides
--
Name the webinar, and optionally its date and the number of days before tasks fall due. It reads the questions in GoTo Webinar, groups them by who asked, and matches each person to Capsule CRM by email. It plans one task per contact for their owner, listing every question and marking the unanswered ones, and skips contacts that already have an open task for the webinar. You confirm the tasks before anything is created, and askers not found in Capsule CRM are reported with their questions so nothing is lost.
Business outcome
---
Every webinar question reaches the right owner as a follow-up, with the unanswered ones flagged first.
scenario
-
A contact who just spent an hour in your webinar is a sign their deal is warm, but that signal lives in GoTo Webinar while the deal lives in Capsule CRM. Linking the two means checking every contact on every open deal by hand.
What popdock provides
--
Name an owner, or leave it blank, and how far back to look. It reads the open Capsule CRM opportunities, gathers the emails of the people on each deal, and checks GoTo Webinar for their registrations and attendance. Deals are ranked by minutes attended, with the webinars and no-shows listed, and the top three get a suggested follow-up. It reports how many deals were checked and how many had no email, reviews at most 25 deals, and changes nothing.
Business outcome
---
You prioritize the deals whose people are actively engaging with your content, using attendance rather than guesswork.
scenario
-
Webinar attendance rarely makes it into Capsule CRM, so reps reaching out later have no idea a contact sat through a full session or asked a pointed question. Adding notes one by one is slow and easy to duplicate.
What popdock provides
--
Name the webinar, and optionally its date. It reads attendance and questions from GoTo Webinar, totals minutes across sessions, and matches each attendee to Capsule CRM by email. Contacts whose history already mentions the webinar are skipped, ambiguous matches are listed, and unmatched attendees are never created. You see each note before it is written, nothing is saved until you confirm, and the report lists what was added, skipped and failed.
Business outcome
---
Each contact's Capsule CRM history shows the webinars they attended and what they asked, ready for the next conversation.
scenario
-
After a webinar, sales wants to know which attendees are existing contacts, who owns them and whether they have deals in progress. Answering that means cross-checking every email between GoTo Webinar and Capsule CRM.
What popdock provides
--
Name the webinar, and its date if several share the name. It reads the attendees from GoTo Webinar, totals their minutes across sessions, and matches each to Capsule CRM by email. Matched attendees are shown with their owner and open opportunities, with any deal found only through the organization name marked as such, and unmatched attendees are listed separately. Duplicate Capsule records for one email are flagged, and nothing is written in either system.
Business outcome
---
Owners know which of their contacts attended and which deals to follow up, the same day the webinar ends.
scenario
-
Inviting a set of Capsule CRM contacts to a webinar means building the list, checking who is already registered and typing each one into GoTo Webinar. It is slow, and it is easy to register someone twice or for the wrong session.
What popdock provides
--
Name an upcoming webinar and describe who to invite: an owner, an organization, a location or a list of emails. It finds the webinar in GoTo Webinar, asks for the organizer key if you did not give one, and finds the matching people in Capsule CRM, stopping if more than 50 match. Anyone already registered is skipped. You see the plan before anyone is registered and nothing is written until you confirm; it never registers anyone for a past webinar, and stops after the first rejected organizer key rather than repeating the error.
Business outcome
---
The right contacts are registered for the webinar in one pass, with no duplicate registrations.
scenario
-
After a webinar, attendees need to reach sales quickly, but importing them into Dynamics 365 Sales by hand creates duplicates of people who are already contacts or leads, and the context of what they asked during the session is lost. By the time the list is cleaned up, interest has cooled.
What popdock provides
--
Name the webinar, and optionally include no-shows, and it reads attendees, registrants and questions from GoTo Webinar, then drops anyone already a contact or lead in Dynamics 365 Sales, matched by email only. You review the list, can remove rows, and nothing is created until you confirm. Up to 25 leads are created per run, each with a note of attendance and questions quoted as asked. People missing an email or last name are listed, not created, and each lead is checked afterwards.
Business outcome
---
Webinar attendees reach sales as new leads with context, without duplicating anyone already in the CRM.
scenario
-
Account managers rarely know which people at a customer have been attending webinars. Finding out means listing the account's contacts and leads in Dynamics 365 Sales and searching GoTo Webinar for each email across registrations, attendance and questions.
What popdock provides
--
Name the account and a lookback period, and it finds the account's contacts and leads in Dynamics 365 Sales, then checks each email in GoTo Webinar for registrations, attendance, no-shows and questions. Matching is by email only, never by name. You get a table of active people, a count of those with none, the most engaged person and any webinar several people attended. People without an email are marked not checked. No contact or lead is created.
Business outcome
---
Account managers see who at a customer is engaging with webinars before their next conversation.
scenario
-
Judging whether a webinar campaign paid off means combining registration and attendance figures from GoTo Webinar with campaign costs and pipeline in Dynamics 365 Sales. Matching attendees to contacts and leads, then finding their accounts' open deals, is slow by hand.
What popdock provides
--
Name the campaign, and optionally the webinar, and it reads the Dynamics 365 Sales campaign and the matching GoTo Webinar session counts and attendee emails. Up to 50 emails are matched to contacts or leads, attendees first, and open opportunities at their accounts are totalled. You get a funnel table and cost per attendee when a cost exists. The report says the pipeline is associated with the webinar, not caused by it, and notes when counts are a lower bound. The campaign and its contacts stay untouched.
Business outcome
---
Marketing reports a webinar campaign's funnel and associated pipeline with honest caveats.
scenario
-
After a webinar, sales wants to know who registered: which are existing contacts, which are leads already being worked, and which are new names. Checking hundreds of registrants against Dynamics 365 Sales one email at a time is not practical, so the list often goes to sales unchecked and full of known names.
What popdock provides
--
Name the webinar, and optionally its date, and it reads GoTo Webinar registrants and attendees, marks who attended, then looks each email up in Dynamics 365 Sales as a contact, then a lead. Matching is by email only, attendees are checked first, and it stops after 50 and says how many were left. You get a summary and three tables with owners, and duplicate contacts are flagged. No lead or contact is created by this check.
Business outcome
---
Sales knows within minutes which webinar registrants are customers, active leads or brand new.
scenario
-
Not every webinar attendee deserves the same follow-up. Someone who stayed the whole hour, asked questions and answered the survey is far warmer than someone who dropped in for five minutes, but GoTo Webinar engagement data rarely makes it to the Dynamics 365 Sales owner.
What popdock provides
--
Name the webinar and how many top attendees you want, and it scores attendees from GoTo Webinar on minutes attended, questions, poll answers and survey responses, stating the rule once. The top attendees are matched by email to Dynamics 365 Sales contacts or leads, with owners and open opportunities at their accounts. Each gets a suggested next step based on what they asked, quoted as written and treated as data. Ties go to time attended, and nothing is changed.
Business outcome
---
Sales follows up the most engaged webinar attendees first, with context for every call.
scenario
-
Inviting the contacts at a key account to an upcoming webinar means exporting them from Dynamics 365 Sales and registering each one in GoTo Webinar, while checking nobody is already registered and remembering that every registration sends an email. One slip means a contact gets invited twice.
What popdock provides
--
Name the account and the upcoming webinar, and it finds only future sessions in GoTo Webinar and needs the organizer key, asking rather than guessing. It lists the account's contacts from Dynamics 365 Sales and skips anyone already registered. You see the webinar and people, are reminded each gets a confirmation email, and nothing is registered until you confirm. Up to 25 people are registered per run, contacts missing details are listed, and each registration is checked with its join link.
Business outcome
---
Key account contacts are registered for the right webinar once, with no double invitations.
scenario
-
Questions left unanswered at the end of a webinar are a buying signal that usually gets lost. Getting each one to the right person means finding the asker in Dynamics 365 Sales, working out who owns them, and checking whether their company already has an open case.
What popdock provides
--
Name the webinar, and optionally its date, and it finds the unanswered questions in GoTo Webinar and looks each asker up by email in Dynamics 365 Sales as a contact, then a lead. Questions are grouped by owner with the company and any open cases, up to five per company, and askers with no match go in a separate group. Questions are quoted as asked and treated as data, not answered unless you ask. No case, task or note is created.
Business outcome
---
Every unanswered webinar question reaches the person who owns the relationship, along with any open cases at that company.
scenario
-
Cancelling someone's GoTo Webinar registration means finding the right session, locating their exact registration and having the organizer key to hand. A partial email match or the wrong webinar cancels the wrong person, and the cancellation cannot be undone.
What popdock provides
--
Give the email and the webinar, and it finds the upcoming webinar, asking you to choose if several match and stopping if it has already happened. The registration is matched on the exact email only. It uses the organizer key from the webinar or the one you supply, and never guesses it. You see the registration and are reminded the cancellation is permanent, and nothing happens until you confirm. It cancels once, then checks the registration is gone.
Business outcome
---
The right person's registration is canceled, once, with a check afterwards that it really went.
scenario
-
Comparing webinars in a series means exporting session numbers from GoTo Webinar, lining them up in a spreadsheet and working out attendance and retention rates for each. Small sessions skew the averages and the trend across the series gets lost.
What popdock provides
--
Give a name term and a lookback period, and it reads every session whose webinar name contains it and groups them by webinar. It calculates sessions, attendance rate, retention, attentiveness, interest rating and questions per session, weighting rates by registrants and leaving out empty sessions, which it counts. Webinars are ranked and the series trend is called rising, falling or flat. It refuses to compare fewer than two sessions. Nothing in GoTo Webinar is changed.
Business outcome
---
You see which webinars in a series perform best and why, from properly weighted numbers.
scenario
-
Attendees ask good questions in a webinar that nobody has time to answer live. Afterwards those questions sit in GoTo Webinar, unreviewed, along with the people who are still waiting for a reply and the themes that would make good content.
What popdock provides
--
Name the webinar and a lookback period, and it reads every attendee question, separating answered from unanswered and treating placeholder answers such as will follow up as unanswered. Unanswered questions are grouped into themes, near duplicates merged, with each asker's email for follow-up. It suggests the three themes that would make the best follow-up content. Questions are quoted as asked, nobody is contacted and nothing is changed.
Business outcome
---
Every unanswered question gets a follow-up, and recurring themes feed your next piece of content.
scenario
-
Before a sales call you want to know how a contact has engaged with your webinars, but GoTo Webinar spreads it across registrations, attendance, questions, polls and surveys. Pulling it together for one person takes several searches and a fair amount of copying.
What popdock provides
--
Give an email and a lookback period, and it reads that person's registrations and attendance, then their questions and poll and survey answers. It rates engagement as high, medium or low with the rule that produced the rating. You get totals, a webinar by webinar table, their questions quoted and answers that show interest or intent. It uses only the exact email given, infers nothing the records do not show and changes nothing.
Business outcome
---
You walk into a conversation knowing exactly how a contact has engaged with your webinars.
scenario
-
After a webinar, the follow-up list is the most valuable output, but building it means comparing registrants with attendees, spotting people who joined another session, and finding the recording link. Done by hand, people who did attend get a no-show email.
What popdock provides
--
Name the webinar, and optionally the session date, and it compares approved registrants with attendees, matching on registrant key and then email. People who attended a different session are kept off the no-show list, and those who stayed under a quarter of the session are listed as left early. It finds the recording link and drafts a short follow-up email. Uncertain matches stay on the list and are marked. Nothing is sent and nothing is changed.
Business outcome
---
No-shows and early leavers get the recording quickly, and nobody who attended gets a wrong email.
scenario
-
Judging how a recurring webinar is doing means pulling session numbers from GoTo Webinar and working out turnout, how long people stayed and whether they engaged. Without a benchmark, a 25 percent attendance rate can look fine when it signals a reminder problem.
What popdock provides
--
Name the webinar and a lookback period, and it reads every session in the window for registrations, attendance, time attended, attentiveness, interest, questions and polls. It interprets them against stated benchmarks, checks the scale of percentage fields before comparing, and works out the trend. Sessions with no registrants are shown but left out of averages. You get a verdict, a session table with totals and recommendations tied to specific numbers. It reads from GoTo Webinar but writes nothing back.
Business outcome
---
You know whether a webinar is improving and what specific change would lift turnout or retention.
scenario
-
A webinar falls flat when nobody notices beforehand that registrations are low, approvals are pending, there is no backup host or no dial-in numbers. Checking every upcoming session means opening each one, its registrants and its settings in turn.
What popdock provides
--
Give a number of days ahead and a registration threshold, and it reads each upcoming webinar's registrants by status, panelists, co-organizers and dial-in numbers. It flags low registration, people awaiting approval without a join link, no backup host, missing dial-in, password protection and an empty description. You get a table in date order with times in each webinar's own zone, an action per flag, soonest first, and the webinars that are ready. Nobody is approved or removed.
Business outcome
---
Upcoming webinars are ready to run, with problems caught days before the audience arrives.
scenario
-
Registering a contact for a GoTo Webinar session on their behalf means finding the right upcoming webinar, checking they are not already registered and having the organizer key. Duplicate registrations and past webinars cause confusion and extra emails.
What popdock provides
--
Give the person's name and email and the webinar, and it finds the upcoming webinar only, asking you to choose if several match. If the person is already registered it reports their status and join link and stops. The organizer key comes from the webinar or from you, never a guess. You confirm the details, and the registration is made once, then read back with its status, explaining when approval is still needed.
Business outcome
---
Contacts are registered once for the right upcoming webinar, with their join link confirmed.
scenario
-
Survey and poll results from a GoTo Webinar session are spread across several reports, and the open-text answers, often the most useful part, are rarely read at all. Turning them into concrete actions for the next session takes time nobody budgets for.
What popdock provides
--
Name the webinar, and optionally the session date, and it reads the session's survey and poll results and every open-text answer. You get the response rate, leading responses with negative ones called out, polls kept separate from the survey, and open-text themes with short quotes. Feedback is kept anonymous, small samples are named as such, and three actions are tied to specific results. A session with no survey is not read as negative. No record in GoTo Webinar is touched.
Business outcome
---
Audience feedback becomes three concrete improvements for your next session, without exposing who said what.
scenario
-
Webinar attendees who stayed for most of the session are warm leads, but turning them into Pipedrive leads means checking each one for an existing person, open deal or lead first. Skip that and you create duplicates or step on a deal a colleague owns.
What popdock provides
--
Name the webinar and a minimum number of minutes, and it reads the attendees who stayed that long, combining people who joined several sessions. Each is checked in Pipedrive by email: people with open deals or open leads are skipped, and name-only matches are listed for you to check rather than created. You see who gets a new person and lead and who is skipped, and nothing is written until you confirm. A person whose creation fails gets no lead.
Business outcome
---
Engaged attendees become Pipedrive leads the same day, without duplicate people or clashes with open deals.
scenario
-
Inviting the people on deals in a Pipedrive stage, or everyone at a key account, to a webinar means exporting contacts, splitting names and registering each one in GoTo Webinar. People who are already registered get a second confirmation email, and names get split wrongly.
What popdock provides
--
Name the webinar and either a Pipedrive stage or an organization, and it gathers the people on open deals or at that organization, dropping anyone with no email. Each email is checked in GoTo Webinar and existing registrants are skipped. You see names as they will be split, with uncertain splits shown, and are reminded each person gets a confirmation email. Nothing is registered until you confirm and the organizer key is known. An organizer key error stops the run rather than repeating.
Business outcome
---
Your pipeline contacts are invited to the right webinar once each, without duplicate confirmation emails.
scenario
-
Salespeople want to see in Pipedrive that a contact attended a webinar and what they asked, but copying attendance and questions across by hand rarely happens. When it does, the same note often gets added twice by different people.
What popdock provides
--
Name the webinar, and optionally a session date, and it reads attendance and questions and links each question to its attendee. Attendees are matched to Pipedrive people by email only, and anyone who already has a note for this webinar is skipped. You see each note before it is written, and nothing is added until you confirm. Each matched person gets one note with time attended and their questions and answers, and failures are reported at the end.
Business outcome
---
Every attendee's Pipedrive record shows they attended and what they asked, without duplicate notes.
scenario
-
Before a webinar, account owners want to know which of their contacts are coming, but the registrant list lives in GoTo Webinar and the relationships live in Pipedrive. Matching them means searching Pipedrive for each registrant by hand.
What popdock provides
--
Name the webinar and it reads every registrant, then looks each one up in Pipedrive by email. When there is no email match it tries last name, accepting it only when the first name also matches and marking it as a name match. Registrants matching several people are flagged as Pipedrive duplicates. You get a table grouped by owner with organization and open and won deals, and a separate list of registrants not in Pipedrive. Nothing in GoTo Webinar or Pipedrive is changed.
Business outcome
---
Each owner sees which of their contacts registered, so they can follow up before and after the session.
scenario
-
Preparing for a call with a contact or a whole account, you want to know which webinars they registered for, which they attended and what they asked. That history sits in GoTo Webinar, searchable only one email at a time, and rarely makes it into the CRM.
What popdock provides
--
Give a Pipedrive person's email, or an organization to cover everyone there, and a lookback period. It reads the people from Pipedrive, then carries each email into GoTo Webinar for registrations, attendance and questions with their answers. Someone who attended without a registration still counts as attended, and people with no email are listed as not checkable. You get a webinar history per person and a total. It reads from GoTo Webinar and Pipedrive but writes nothing back.
Business outcome
---
You see a contact or account's full webinar history before the conversation, without searching person by person.
scenario
-
Leadership asks how much pipeline a webinar touched, and answering means matching attendees to Pipedrive and adding up the open deals at their organizations. Deals get counted twice when several people from one company attend, and currencies get mixed.
What popdock provides
--
Name the webinar, and optionally a session date, and it reads the attendees and matches them to Pipedrive people by email. It reads the open deals at each matched organization once, however many people attended from it. You get open deal value totalled per currency, never mixed, a table per organization with attendees and deals, and lists of matched people with no deal or no organization. If deal reads return nothing it says the filter may not be working instead of reporting zero pipeline. No record in GoTo Webinar or Pipedrive is touched.
Business outcome
---
You can state the open pipeline a webinar reached, counted once per deal and per currency.
scenario
-
People who registered but did not attend are still interested, yet follow-up calls only get scheduled when someone builds the no-show list and creates activities one by one. People who already have a follow-up planned get a second one.
What popdock provides
--
Name the webinar, and optionally an activity type and due date, and it works out the no-shows by comparing registrants with attendees. It confirms the activity type exists, matches no-shows to Pipedrive people by email only and skips anyone who already has an open follow-up for this webinar. You see each planned activity and nothing is created until you confirm. Each person then gets one follow-up with a note on when they registered.
Business outcome
---
Every no-show in Pipedrive gets a scheduled follow-up the next business day, without duplicates.
scenario
-
Turning webinar attendees into Salesforce leads means checking every email against contacts and leads first, then filling in a company GoTo Webinar never captured. Skip the check and you create duplicate leads for people who are already customers.
What popdock provides
--
Name the webinar, and optionally a minimum time and lead source, and it reads the attendees and checks each email against Salesforce contacts, then leads. Only people unknown to Salesforce go forward, and ambiguous matches are listed, never picked. A business email domain is proposed as the company, and personal addresses wait for you to supply one. You review and edit the list, nothing is created until you confirm, and duplicate emails produce at most one lead.
Business outcome
---
New webinar attendees become Salesforce leads with no duplicates of existing contacts or leads.
scenario
-
Sales wants webinar attendance recorded on each contact or lead in Salesforce, but logging a task per attendee by hand is slow. Done twice, the same person shows two attendance tasks for one webinar and the activity history looks inflated.
What popdock provides
--
Name the webinar, and optionally a task status, and it reads the attendees and matches each email to a Salesforce contact, then lead, never on name alone. Anyone who already has a task for this webinar is skipped, and unknown or ambiguous attendees get nothing. You see the list and nothing is created until you confirm. Each match gets one task with minutes attended and the webinar date, and a rejected status stops the run after the first failure.
Business outcome
---
Webinar attendance shows on every matched Salesforce contact and lead exactly once, ready for sales follow-up.
scenario
-
After a webinar, reps need to know who to call first, but engagement such as time attended and questions asked sits in GoTo Webinar while lead status and open deals sit in Salesforce. Ranking attendees by hand rarely gets past the first few names on the list.
What popdock provides
--
Name the webinar and how many to rank, and it scores each attendee on minutes attended, questions asked and polls answered, showing each part of the score. The top attendees are matched to Salesforce contacts and leads by email, with open opportunities read for contacts. Each is placed in call now, nurture, not in Salesforce or check for ambiguous matches. Missing poll or question data is named rather than hidden. Nothing in GoTo Webinar or Salesforce is changed.
Business outcome
---
Reps call the most engaged attendees with open opportunities first, guided by a score they can inspect.
scenario
-
A webinar's Salesforce campaign should reflect who registered and attended, but members get added late, responses go unmarked and some registrants never make it in. Campaign reports then understate the event and its influence on pipeline.
What popdock provides
--
Name the webinar, and optionally the campaign, and it reads registrants and attendees, then finds the matching Salesforce campaign and its members. Everyone is compared by email only and placed as attended, no-show, webinar only or campaign only. Members whose responded flag disagrees with attendance are flagged, and duplicates and members with no email are listed. It ends with the biggest gap and what would close it, without doing it.
Business outcome
---
Your campaign results match who really registered and attended, with every gap listed.
scenario
-
Questions asked in a webinar often signal buying interest, but they sit in GoTo Webinar where account owners never see them. Routing each one means finding the asker in Salesforce, identifying the record owner and creating a task for them by hand.
What popdock provides
--
Name the webinar and it reads the questions, unanswered ones by default, grouped by asker. Each asker is matched to a Salesforce contact or lead by email, and each owner is resolved to an active user, left unresolved rather than guessed. You see the questions and owners and confirm which rows get a task. Each confirmed asker gets one task with their questions, set to high priority when any are unanswered. Unknown askers and anonymous questions are listed for a person to pick up.
Business outcome
---
Every webinar question reaches the right account owner as a follow-up task.
scenario
-
Before an account review you want to know whether anyone at the account has been registering for or attending your webinars, and whether that lines up with open deals. Checking means listing the account's contacts in Salesforce and searching GoTo Webinar for each of them in turn.
What popdock provides
--
Name the Salesforce account and a lookback period, and it reads the account's contacts and open opportunities, then the webinars in the window. Each contact's email is checked in GoTo Webinar for registrations and attendance, and only contacts on this account count, never a domain search. You get engaged contacts by webinar, the contacts with no activity, and each open opportunity marked when someone attended within 30 days before its close date. It reads from GoTo Webinar and Salesforce but writes nothing back.
Business outcome
---
You see how an account engages with your webinars alongside its open deals, ready for the account review.
scenario
-
Before an account review, nobody checks whether the people on the account registered for or attended your webinars, because it means looking up each contact in two systems. Webinar behaviour that signals interest never makes it into the conversation.
What popdock provides
--
Name a Nutshell company and it lists the people on that account, then checks GoTo Webinar for their registrations and attendance by email. It shows who registered, who attended and who did neither, next to the account's open leads. If it finds no webinar activity it says so rather than guessing. It only reads, nothing is changed in either system.
Business outcome
---
Account reviews include real webinar interest from the people on the deal, found in one request.
scenario
-
After a webinar, reps do not know which attendees already have live deals, so the hottest follow-ups wait while cold contacts get called. Matching the attendee list to the CRM is a manual spreadsheet job.
What popdock provides
--
Name a webinar and it lists the attendees from GoTo Webinar, then matches them to Nutshell people by exact email. Attendees with open leads are ranked by lead value so the biggest opportunities come first. It does not add up values across different currencies. It only reads, nothing is changed in either system.
Business outcome
---
Reps follow up with the attendees who matter most first, ranked by the value of their open deals.
scenario
-
Finding the people who registered but did not attend means comparing two exports by hand. The no-shows with deals in play are the ones who most need the recording, and they are the ones who never get it.
What popdock provides
--
Name a webinar and it finds the registrants who did not attend, then matches them to Nutshell people with open leads by exact email. It lists them for follow-up with their leads and, where available, the webinar recording. If the webinar has not happened yet it stops. It only reads and never registers anyone or changes the CRM.
Business outcome
---
No-shows with live deals get the recording and a follow-up, instead of being lost in two exports.
scenario
-
Marketers export a webinar's registrants and eyeball them against the CRM. New leads and existing customers get mixed up, and nobody knows which registrants the sales team already works with.
What popdock provides
--
Name a webinar and it lists the registrants from GoTo Webinar, then checks Nutshell people for each one. A match counts only on an exact email. A match on name alone is labelled possible, and anyone with no match is labelled new to the CRM. It only reads, and nothing is added, updated or deleted in either system.
Business outcome
---
Marketing knows which registrants are existing contacts and which are new, without comparing two exports.
scenario
-
Staff retype a CRM contact's details into the webinar tool to register them. That invites typos and duplicate registrations, and nobody checks first whether the person is already signed up.
What popdock provides
--
Name the Nutshell contact and the webinar, and it looks up the person in Nutshell and checks GoTo Webinar for an existing registration. It shows the details it will use and waits for your explicit yes before the single registration is made. It never invents missing details and never deletes a registration. Afterwards it checks that the registration landed.
Business outcome
---
Contacts are registered once, with the right details, after you have approved them.
scenario
-
Questions asked during a webinar sit in a report with no sign of who asked them or whether they are a customer. Answers go to the wrong people or to no one, and a question from a big prospect looks the same as any other.
What popdock provides
--
Name a webinar and it lists the questions asked from GoTo Webinar, then matches each asker to Nutshell by exact email. For each match it adds the contact, the account owner and any open leads. Askers who are not found in Nutshell are grouped separately. It only reads, and nothing is added or changed in either system.
Business outcome
---
Webinar questions reach the right owner with the account and deal context already attached.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.