Keep Your Dance Studio AI Answers Current When Schedules Change

A receptionist can only give useful answers when the information behind it is current. For dance studios, that means class times, tuition, trial rules, recital details, and closures need a clear update process. Uploading another handbook without retiring the old answers can leave parents hearing both versions.

Use this workflow whether staff answer the phone, a website chatbot handles FAQs, or an AI receptionist uses your approved information.

Separate submission from approval

When someone uploads a document or types a change, record when it arrived, who submitted it, the affected topic, and when it should take effect. Treat it as received until the responsible person reviews it. A timestamp proves a submission arrived; it does not prove every statement is correct.

Use four stages: received, being reviewed, approved for an effective date, and active. Keep the previous approved answer until its replacement is ready to take effect.

Change the matching topic

A new ballet schedule should replace the old ballet schedule for the relevant location and season. It should not delete the pickup policy, office hours, or unrelated programs. Identify exactly which answer changes and which stays the same.

For example, “Tuesday beginner ballet moves from 5 p.m. to 5:30 p.m. on November 1” needs a future effective date. Until then, the current answer remains 5 p.m. After the change, archive the older version and stop using it for current questions.

A short update form

Ask for the topic, current wording, replacement wording, affected classes or locations, effective date and timezone, source document, and approving contact. Give the owner a place to explain whether this is a correction, a future change, or a temporary notice.

Topic: [Class schedule/policy]
Replace: [Old approved detail]
With: [New detail]
Applies to: [Location, class, season]
Effective: [Date, time, timezone]
Approved by: [Responsible person]
Source: [Document or page]

Keep private student information in secure records. An operational update form should not become a general collection point for health details, card information, or individual complaints.

Resolve contradictions deliberately

Compare the new submission with the current approved source. If the website says one price and the uploaded handbook says another, ask the owner which applies and when. Do not let the bot choose the newest file simply because it was uploaded last.

The useful rule is: the newest approved, currently effective information wins for the same topic. Future changes wait. Unrelated answers remain intact.

Apply and test the change

Update the authoritative schedule or policy, then the matching receptionist knowledge and staff instructions. If the platform does not automatically replace an old source, the reviewer must remove or deactivate it through the supported process.

Ask the revised question in several ways. “What time is beginner ballet?” and “Is the Tuesday class still at five?” should both reflect the correct effective schedule. Check the next-day or next-month version if a future change is pending.

Keep a useful audit trail

Retain submission timestamps, archived documents, review decisions, the approving person, and test results. A receipt date and last-reviewed date are different. Show customers both where possible so they know whether an update has merely arrived or has been checked.

A repeat update should not reset a studio's completed onboarding or mark its receptionist live. Review status and launch status describe different work.

Set a faster path for temporary notices

Weather closures and urgent location changes need a designated reviewer and a clear expiry or reopening instruction. Update the official notice, staff response, and active receptionist source. If the system cannot reliably reflect the change, use an approved staff handoff until it can.

Review temporary notices after their expiry. Old closures are a common source of confusion when they remain in active documents.

Make one person responsible

Assign a knowledge owner and backup. Review recurring questions and unresolved contradictions regularly, and check seasonal materials before enrollment and recital periods.

Start with our parent communication templates for consistent messages. Hear the StudioConnect demo to explore sample answers; each real studio's information and update process must be reviewed and tested.