Free Study Schedule Planner Chatbot: Build a Plan in Chat

The Study Schedule Planner is a structured intake that turns a student's vague intention to revise into a concrete, written plan. It asks nine questions in a deliberate order — who you are, what you are working toward, over what period, which subjects, on which days, for how many hours, at what time of day — and then renders a schedule from the answers.

The value is not that the bot is clever about study science. It is that the questions are the right ones and they arrive one at a time. Anyone who has tried to make a student fill in a revision timetable template knows the failure mode: the blank grid is intimidating, so it never gets filled in. A conversation that asks "how many hours can you dedicate each day?" and validates the answer against a sensible range gets a usable plan out of a student who would have abandoned the spreadsheet.

It ships as seventeen connected nodes in the chatbot builder, ending in an HTML node that renders the schedule and a satisfaction check that routes unhappy students to a live study advisor rather than leaving them with a plan they will not follow.

1. Welcome. "Welcome to the Study Schedule Planner! I'm here to help you create an effective study plan tailored to your needs and goals."

2. Name. Captured into student_name, with the greeting "Great to meet you, {name}! Let's create your study plan." The name is reused later in the flow, so this is not a throwaway field.

3. Study goal. A free-text question — "What's your main study goal? (e.g., exam preparation, skill improvement, etc.)" — into study_goal. Left open on purpose: the answers here are the most interesting data the flow produces, because they tell you in students' own words what they are actually trying to achieve.

4. Duration. A choice node offering one week, two weeks, one month, or a custom duration, stored as study_duration. Choosing custom drops into a validated number question asking for a day count between 1 and 365, stored as custom_duration, then rejoins the main path.

5. Subjects. A multi-select — Mathematics, Science, Literature, History, Languages, Other — into study_subjects. Multi-select rather than single choice matters here: real revision periods span several subjects, and a planner that assumes one is useless.

6. Other subjects. A free-text follow-up into other_subjects for anything the list missed.

7. Available days. A calendar node — "Please select your available study days for the upcoming week" — into study_days. It is configured to hide past dates and to skip time selection, so the student picks days rather than fiddling with clock times at this stage.

8. Daily hours. A number question validated between 1 and 24, into daily_study_hours. Combined with the day selection and the duration, this is the arithmetic backbone of the schedule.

9. Time of day. Morning, afternoon, evening or no preference, into study_preference. All four options converge — the answer shapes the rendered plan rather than the conversation.

10. Generation. A message acknowledging the inputs and announcing that the plan is being built, then "Here's your personalized study schedule:", then an HTML node that renders it. The HTML node is where you lay the schedule out as a real table using the captured variables.

11. The satisfaction check. "Are you satisfied with this study schedule?" — yes or no. A yes gets encouragement to stick to it and take regular breaks. A no goes to a human handover node: medium priority, automatic assignment, five-minute maximum wait, with a waiting message explaining that a study advisor will help refine the plan and a fallback for when advisors are all busy.

12. Close. Both paths land on the same sign-off about consistency being the key to achieving study goals.

Tutoring companies and revision services get a lead magnet that is genuinely useful rather than a gated PDF: a student walks away with a plan, and you walk away with their goal, subjects, availability and the fact that they are actively revising. That is a far better qualified enquiry than a contact form produces.

Schools and colleges can offer it through a learning support page during exam season, when demand for one-to-one planning far exceeds the staff available to provide it. The handover branch means the students who genuinely need a person still get one.

Online course providers and bootcamps can run it at enrolment to set a realistic pace before a learner falls behind — the daily-hours answer is an early warning signal for who will struggle.

Student-facing apps and university study-skills services can use it as a self-service front door that runs outside office hours.

Related flows in the same category: the Exam Preparation Guide goes deeper on a single exam, the Homework Helper handles day-to-day questions, and the personalized learning path creator covers longer-term skill sequencing. Browse the rest at education and training templates.

1. Build the HTML node properly

This is the node that determines whether students take the plan seriously. Lay the schedule out as a table — days down one side, subjects allocated across the selected days, with the daily hour total visible — and interpolate the captured variables so the student sees their own name, goal and subjects rather than a generic grid. A plan that looks like it was made for them gets followed; a paragraph of text does not.

2. Do the arithmetic with math nodes

The flow captures daily hours, chosen days and a duration, which is everything you need to compute the total study time available and split it across subjects. Add math-operation nodes before the HTML node to derive a per-subject allocation, then reference those results in the rendered schedule. Students find "18 hours for Mathematics across 9 sessions" far more motivating than a list of subjects.

3. Sanity-check the hours

The shipped maximum on daily hours is 24, which nobody should be revising for. Lower it to something defensible — six or eight — and add a message for high answers that gently pushes back and reminds the student about breaks. A planner that endorses a twelve-hour day is doing harm, and it is a single node to prevent.

4. Match the subjects to your students

Mathematics / Science / Literature / History / Languages / Other is a school-shaped list. A professional certification provider, a language school or a medical course needs entirely different options. Edit the multi-select, and keep the free-text "other" follow-up — it is how you discover what to add next.

5. Deliver the plan somewhere it survives

A schedule that only exists in a chat window is forgotten by Tuesday. Add an email capture and send the plan through the Gmail integration, or push the selected days into Google Calendar so the sessions appear alongside everything else in the student's week. Both are shipped native integrations. For your own records, log the responses to Google Sheets, Airtable or Notion, or push them to your systems via webhook on a paid plan.

6. Staff the advisor branch

Live chat handover and the unified inbox are on every plan including Free, so the capability is there. Decide who covers it and during which hours, then set the maximum wait and rewrite the fallback message to match reality. Replace the placeholder support address in the fallback before launch.

Ask for exam dates, not just a duration. A calendar node capturing the date of each exam lets you weight the schedule toward whatever comes first — the single highest-value change you can make to the generated plan.

Ask which subjects are weakest. One multi-select after the subject question, reusing the same options, gives you a basis for allocating more time where it is needed instead of splitting hours evenly.

Add a check-in loop. Capture an email and follow up a week later asking whether the student kept to the plan. The answers make a second, more realistic schedule and give you a retention hook.

Build in breaks explicitly. A choice node offering study techniques — pomodoro, ninety-minute blocks, and so on — lets you render sessions with breaks already marked, which is more useful than raw hour totals.

Offer a downloadable version. Pair the HTML render with an emailed copy so the plan lands somewhere permanent. Students revise from their phones and their inbox, not from a chat transcript.

Branch by student type. A full-time student and a working adult studying evenings need different defaults for both hours and time of day. One question at the top can set sensible defaults for the rest of the flow.

Convert at the right moment. For a commercial tutoring service, the strongest offer lands right after the plan renders, when the student can see exactly how many hours of Mathematics they are facing. A booking step there converts better than any banner.

Channels are not plan-gated in Conferbot, so this flow runs anywhere. The website widget is the obvious home — put it on revision-resource pages and course pages, where students arrive already thinking about how to organise their time.

WhatsApp suits this flow unusually well: students plan revision on their phones, and a plan that arrives in the same thread they use daily is a plan they will re-read. Microsoft Teams fits institutions on Microsoft 365, and Discord is the right call for bootcamps and university cohorts whose study groups already live there. Telegram, Messenger, Instagram, LINE and the mobile SDK are also available on every plan.

The free plan covers 600 conversations a month and one chatbot — enough for a full exam season at department scale. Paid plans start at $19/month and add webhooks, API access and branding removal; Pro adds A/B testing if you want to compare two versions of the schedule layout properly. See pricing.

The plan is arithmetic, not pedagogy. The flow allocates time from the student's own inputs. It does not know which topics are hardest, how fast the student learns, or what the syllabus weighting is — unless you add questions that capture those things. Describe it as a planner, not a tutor.

A schedule is not adherence. Generating a plan feels like progress and often substitutes for it. The check-in extension above is the antidote, and it is worth building before you promote the bot widely.

Do not promise what you will not staff. The handover branch is the template's best feature and its biggest risk. If no advisor is available at 11pm during exam week — which is exactly when students use this — the fallback message is what they will remember. Write it as something genuinely useful rather than an apology.

Used honestly, this is one of the highest-value education flows to run in 2026: it costs almost nothing, it produces something the student keeps, and it tells you more about your audience than a survey ever would.