Yes, if session-level spot counts live in a custom field on each session post. SleekAI reads the field on every conversation. When an admin updates the count after each enrolment, the bot reflects the change in seconds. For higher-volume camps, fire a webhook from your registration tool (CampMinder, ActiveNet, CampBrain) to update the field automatically when deposits clear.

Yes, and that's where it earns its keep. First-time-camper parents have a predictable set of concerns: separation anxiety, homesickness protocol, how counsellors handle bedtime, what 'no phones' actually looks like, and whether the camper can switch out if they hate it. Configure the prompt with your published protocols on each, and the bot answers reassuringly without overpromising. Most camps see first-time-camper conversion lift after tuning these answers.

Yes. Summer camps typically have tiered refund windows (full refund through March, 50% through May, none after) plus illness and weather exceptions. The bot quotes your published policy verbatim. For edge cases (death in the family, late-season medical emergency), the bot collects the situation and routes to a director, which is the right escalation.

Yes. Hand off enrolment via deep link or webhook. The bot collects camper name, age, session preference, and emergency-contact basics in conversation, then either passes the parent to your enrolment link with the session pre-selected or fires a webhook that creates the reservation server-side. Most camps prefer deep links for support simplicity.

High-level only. The bot collects 'has allergies', 'needs daily medication', or 'has dietary restrictions' as a flag, then surfaces the formal intake form for the parent to complete with detail. Sensitive medical information should not live in chat logs; configure the prompt to defer medical specifics to the intake form. For severe medical situations, the bot routes to a director call.

Yes, if those are published on your tuition page. The bot reads sibling-discount percentages, multi-session bundles, and early-bird pricing, and applies them in the quote. For custom arrangements (one camper extending mid-season, sibling spread across age bands), the bot can also escalate to a director for final confirmation.

Yes. Summer camps that publish parents' weekend dates, schedules, and visitor policies see the bot quote them accurately when parents ask about visiting. That alone reduces a meaningful percentage of inbound calls during enrolment season. Keep the parents'-weekend page current and the bot stays current with it.

Yes. Run a different bot per program using display conditions (URL pattern, taxonomy, or custom field), or use one bot with branch logic in the prompt. Most camps with both formats find the dual-bot approach cleaner: day-camp parents get day-camp logistics, overnight-camp parents get overnight logistics, and the conversation logs stay separately reviewable per program.