Term-calendar webinar producer agent for education and training providers on Salesforce

What The Producer does

A small marketing team at an education and training provider runs info sessions, open houses and institutional briefings around each intake. Today every webinar starts from a blank page: someone rebuilds the registration page, rewrites emails, chases faculty for a run of show, and promotion goes out a week before the event, right when prospective students are already deciding. The Producer fixes the timing problem first and the busywork second. It reads the academic calendar and enrollment deadlines, proposes a webinar schedule for the coming term with promotion start dates locked in, and builds a reusable kit for each event in the right audience track (individual learners, parents, or institutions and employers buying seats). It owns the registration page, promotion emails, reminder ladder, Salesforce Campaign setup, run of show, panel questions, attendance sync, follow-up sequences and repurposing drafts. Marketing approves and presses send. Because the team chose a build-and-maintain model, the agent's templates, integrations and term calendar are kept current by an operator each term so it keeps working without internal engineering.

Custom build

The team runs Salesforce, so HubSpot Breeze agents are not the right fit; this is a custom AI build orchestrated in n8n. Salesforce Campaigns and Campaign Members hold registration and attendance so attribution and audience segmentation live where admissions and partnerships already work, and emails can send through Salesforce Account Engagement or the team's existing email tool. Demio handles registration, reminders and attendance data with a clean API. Airtable holds the term calendar, template library and claims library so non-technical staff can update deadlines and approved wording without touching the build. Castmagic turns recordings into repurposing drafts, and Zonka Feedback captures post-session feedback by track. Keeping student systems entirely outside this stack is what makes the FERPA boundary simple to enforce, and the build-and-maintain model fits a small team without in-house engineers.

What starts it

• A new term calendar or set of enrollment deadlines is added to the planning base, prompting a proposed webinar season with promotion start dates
• A marketer submits a short webinar brief (topic, audience track, presenters, date) for an ad hoc session
• A promotion milestone is reached on the timeline (for example, registration page due, first invite due, reminder due) and the next drafts are queued for approval
• The webinar platform marks an event as ended, kicking off attendance sync, follow-up and repurposing
• Registrations for an upcoming session fall below the target set for its audience track, prompting an extra promotion push draft

What it reads

• Academic calendar and enrollment deadlines (term start dates, application and payment deadlines, break and exam weeks) kept in an Airtable planning base
• Salesforce Campaigns, Campaign Members, Leads and Contacts with an audience-type field (learner, parent, institution) and email consent status
• Webinar platform registration, attendance, poll and Q&A data (for example, Demio)
• Approved template library and claims library: page and email templates per audience track, approved program descriptions, accreditation wording and outcome statements
• Past webinar Q&A logs and transcripts, de-identified, used to seed panel questions and FAQ drafts
• Brand and tone guide with separate voice notes for students, parents and institutional buyers

When a person takes over

• The marketing lead approves the proposed season schedule each term, because admissions priorities and budget decide which intakes get webinars, not the calendar alone
• Any question or reply that concerns a specific student (application status, grades, financial aid, enrollment) goes to admissions or student services staff, since the agent has no access to student records and must not answer
• Institutional and employer questions about seat pricing, contracts or cohort reporting are routed to the partnerships owner in Salesforce as a task, because those are sales conversations
• New outcome, accreditation or job-placement statements go to the academic or compliance owner for sign-off before they enter the claims library the agent can use

Rules it follows

• FERPA boundary: the agent connects only to marketing data in Salesforce (leads, contacts, campaign activity) and never to the student information system, LMS gradebook or any education record; prompts, logs and drafts must never include student record data, and student-specific questions are escalated rather than answered
• Audience separation: every send is filtered by audience type and consent in Salesforce, and parent communications never imply access to an adult student's records or progress
• Claims control: program, accreditation, financial aid and outcome statements come only from the approved claims library; the agent cannot invent or paraphrase them into stronger promises
• Calendar truth: deadlines and term dates are read from one approved calendar, and the agent flags any draft whose date conflicts with it instead of guessing
• Nothing publishes or sends without a named marketer's approval, and registrants under 18 are handled according to the provider's own minors policy, set during configuration

How you know it works

• Lead time between webinar approval and first promotion send, tracked per event against the planned timeline
• Registrations and show rate per webinar, broken out by audience track (learner, parent, institution)
• Marketing hours spent producing each webinar, compared with the pre-agent baseline the team records in the pilot
• Webinar-influenced applications, advising calls and institutional meetings attributed through Salesforce Campaign influence
• Share of follow-ups sent within the planned window after each event

From pilot to live

1. Pilot: one intake, one trackLoad the next term calendar and build the learner info-session kit only. Run two or three sessions with the full timeline, Salesforce Campaign sync and follow-up, while the team records time spent and checks that FERPA routing and claims control behave as designed.
2. Expand: all three audience tracksAdd parent and institutional kits, the full reminder ladder, panel prep for faculty and admissions staff, partnerships routing, and repurposing drafts. Tune send windows around exam weeks and breaks based on pilot results.
3. Full season and ongoing maintenanceThe agent plans each full term's webinar season on approval of the calendar. An operator maintains integrations, refreshes templates and the claims library each term, reviews track performance, and fixes anything that breaks when the webinar platform or Salesforce changes.