← ALL BLUEPRINTS / AGENT BLUEPRINT
Enrollment-calendar blog agent for education and training providers on Salesforce, writing separately for students, parents and institutional buyers
The Content Operator plans, briefs, drafts and QA-checks blog posts and high-intent program pages around the academic calendar, writing distinct content for prospective students, parents and institutional buyers from aggregated, FERPA-safe inquiry themes and search and AI-answer gaps. It moves a marketing team from two posts a month to one per business day without hiring, with output peaking ahead of application deadlines and every outcome or date claim checked against an approved source before publishing.
| ROLE | MARKETING | PLATFORM | CUSTOM |
|---|---|---|---|
| INDUSTRY | EDUCATION / TRAINING | ||
| DRAWN BY | HACKING DEMAND | ISSUED | OCTOBER 21, 2026 |
What The Term Planner does
A training and education provider with 200+ staff runs several program lines, sells to individual learners, to parents deciding for their kids, and to schools, districts or employers buying seats. Marketing publishes twice a month, usually late relative to the enrollment window, and wants daily publishing without adding writers. The Term Planner owns the content pipeline end to end: it builds a rolling calendar from term start dates and application deadlines, pulls aggregated questions from Salesforce inquiries and admissions FAQs (never student-level records), finds ranking and AI-citation gaps, writes audience-specific briefs, drafts posts and program pages in the right voice for each audience, runs editorial QA with schema, and routes anything touching outcomes, accreditation, tuition or financial aid to a named reviewer. It is built and maintained by an outside team, so the marketing lead approves the calendar and reviews content but does not babysit prompts, integrations or model changes.
Custom build
The provider runs Salesforce, so HubSpot Breeze agents are not an option and forcing a second CRM would split attribution. A custom Claude build fits better: Claude handles long briefs, multiple voice profiles and strict claim checking against source documents, n8n orchestrates the weekly pulls from the calendar, the aggregated Salesforce report, Moz and Rank Prompt, and publishing goes straight to WordPress with Salesforce campaign IDs. Reading Salesforce through a locked-down aggregated report (rather than broad API access) keeps the FERPA boundary enforced by design, and because the build is maintained externally, the team gets model upgrades and fixes without owning the plumbing.
What starts it
- The academic calendar source of truth is updated with a new term start, application deadline or cohort date, which opens a content window 6 to 10 weeks ahead
- Weekly digest of aggregated Salesforce inquiry themes shows a question cluster crossing a minimum volume threshold for a program or audience
- Search or AI-answer tracking shows a tracked prompt or keyword where competitors are cited and the provider is not
- A program page, tuition figure or accreditation status changes in the approved program fact sheet, flagging dependent posts for refresh
- A term closes, which kicks off the post-term refresh and prune pass on dated content
What it reads
- Academic and enrollment calendar (term dates, deadlines, cohort starts) maintained by admissions as the single source of truth
- Salesforce inquiry and application objects, read only through a pre-aggregated report of themes, program interest and audience type, with no names, IDs, grades or enrollment status
- Approved program fact sheets and admissions FAQ library (outcomes, accreditation, tuition, financial aid language) with owner and last-reviewed date
- Moz and Google Search Console for keyword gaps, rankings and page performance by program
- Rank Prompt for tracked AI-answer prompts and citation share across assistants
- Brand voice guide with three audience profiles (student, parent, institutional buyer) and a consent-logged testimonial library
How it works, step by step
- Build the term-driven demand mapEach week the agent reads the academic calendar and lays out content windows per program: awareness posts 8 to 10 weeks before a deadline, comparison and cost posts 4 to 6 weeks out, deadline and next-step posts in the final 2 weeks. Volume is weighted toward open windows, so daily publishing averages out across the year rather than staying flat. The calendar lands in Airtable for the marketing lead to approve.
- Mine aggregated questions and gapsAn n8n workflow pulls the aggregated Salesforce inquiry report, the admissions FAQ backlog, Moz keyword gaps and Rank Prompt citation gaps. The agent clusters them by program and audience (for example, parents asking about schedules and safety, students asking about workload and job outcomes, institutions asking about reporting and bulk enrollment) and ranks topics by window timing and intent.
- Write audience-specific briefsEach brief names one audience, one search or AI prompt target, the conversion action (inquiry form, info session, campus visit, institutional demo), the approved fact sheet entries it may cite, internal links to the matching program page, and the questions to answer in a direct, quotable format for AI answers. Topics that need different framing for parents and students get two briefs, not one blended post.
- Draft posts and high-intent pagesClaude drafts in the voice profile for that audience, with answer-first sections, FAQ blocks, and schema (Article, FAQPage, and Course or EducationalOccupationalProgram on program pages). High-intent pages such as program comparisons, cost and aid explainers and deadline guides get a clear single CTA and form placement tied to the Salesforce campaign.
- Run editorial QAA separate QA pass checks every date against the calendar, every outcome, tuition, aid and accreditation statement against the fact sheet, scans for any personal or student-identifying detail, verifies testimonials against the consent log, checks reading level for the audience, validates schema, and flags duplicate or cannibalizing topics. Failures go back to drafting or to a human, never to publish.
- Review, publish and attributeClean posts go to the marketing editor for a quick read; flagged claims go to the named reviewer. Approved content publishes to WordPress on WP Engine with UTM parameters and a Salesforce campaign ID, so inquiries and application starts from blog sessions are attributed in Salesforce.
- Refresh after each termWhen a term closes, the agent finds posts with expired dates, outdated tuition or slipping rankings and citations, proposes updates or redirects, and queues them ahead of the next window so last cycle's content keeps earning.
When a person takes over
- Program director or admissions lead approves any claim about job placement, completion rates, accreditation, credit transfer or learning outcomes, because these are regulated or reputational and the agent cannot verify them beyond the fact sheet
- Financial aid or bursar office reviews any content mentioning tuition, discounts, scholarships, payment plans or aid eligibility before it publishes
- Registrar or privacy officer reviews any post that uses a learner story or quote, or any topic where the inquiry data looks thin enough to identify an individual, and the agent stops until they clear it
- Partnerships or institutional sales lead reviews content aimed at schools, districts or employers, since pricing models, contract terms and reporting promises vary by deal
Rules it follows
- FERPA boundary: the agent never connects to student information systems or reads student-level Salesforce records; it only sees a pre-aggregated report with a minimum count per theme, and it never writes names, grades, attendance, enrollment status or details that could identify a learner
- Dates and deadlines come only from the academic calendar source; the agent never infers or extrapolates a term date, and posts with time-bound claims carry an expiry that triggers refresh
- Outcome, accreditation, tuition and aid statements must match an approved fact sheet entry that has been reviewed within the set period, or the claim is removed and escalated
- Each piece targets one audience with its voice profile; content for parents of minors avoids collecting data from minors and directs forms to the parent or guardian
- No testimonials, quotes or learner examples unless they exist in the consent-logged library with active consent for public use
How you know it works
- Posts and pages published per week versus the term-weighted target
- Non-brand organic clicks and rankings for program and audience keyword sets
- Citation share on tracked AI-answer prompts in Rank Prompt
- Inquiries, info-session registrations and application starts attributed to blog sessions in Salesforce, by audience and program
- Editorial QA first-pass rate and reviewer turnaround time
From pilot to live
- Pilot: one program, one upcoming windowConnect the calendar, aggregated Salesforce report, fact sheets and WordPress for a single program with a deadline 8 to 10 weeks out. Publish about three pieces a week for students and parents, with every piece human-reviewed, to tune voice profiles, QA rules and reviewer routing.
- Expand: all audiences and core programsAdd institutional buyer content and the remaining main programs, move to one piece per business day averaged across the term, and let clean posts pass with an editor read while flagged claims still go to named reviewers. Start Salesforce campaign attribution reporting.
- Full run: high-intent pages and refresh loopAdd comparison, cost and deadline pages, turn on the post-term refresh and prune pass, and run on a maintenance cadence covering model and prompt updates, integration monitoring, schema checks and a monthly performance review with the marketing lead.
Tools that fit
n8n
Workflow automation platform
Moz
SEO & digital marketing solution
Rank Prompt
AI search ranking (AEO)
WP Engine
WordPress hosting
Airtable
Visual data organization
Some tool links are partner links. Hacking Demand may earn a commission at no extra cost to you.
This blueprint is a version of The Content Operator (blog writer agent) ↗
Want The Term Planner built for you?
Our experts build it inside your stack. Then we hand it off, maintain it, or operate it with you. Agents and programs get better with tuning, so most teams keep us on to run them. Bring this blueprint to a scoping call.
Scope this agent ↗ Get your own blueprint ↗Good questions.
Straight answers.
How do we keep FERPA safe if the agent learns from our Salesforce inquiry data?
The agent never touches student-level records. Salesforce admins build a report that groups inquiries into themes by program and audience type, drops any theme below a minimum count, and strips names, IDs and status. The agent only gets that report. Any learner story requires a consent-logged entry and a registrar or privacy review before use.
Does daily publishing make sense when our demand is so seasonal?
Daily is an average, not a flat line. The agent weights output toward open enrollment windows (more deadline, cost and comparison content in the weeks before applications close) and uses quieter periods for refreshes, institutional buyer content and evergreen guides. You approve the term-weighted calendar each week.
Will this bury our admissions and financial aid staff in review work?
Only claims about outcomes, accreditation, tuition and aid route to them, and only when the claim is not already an exact match to a current fact sheet entry. Most posts cite approved language and go to a marketing editor alone. Keeping fact sheets current is the single biggest lever for reducing review load, and the agent flags which entries are blocking the most drafts.
Every good build
starts with a conversation.
New builds, remodels, and additions, powered by AI. Let’s plan the work.