StudioBot only answers confidently from knowledge you’ve verified. The Knowledge area is how you teach your studio’s truth — hours, policies, dress code, and FAQs — without waiting for a developer.

Studio Facts

Path: Knowledge → Studio Facts

Facts are short, verified statements about your studio (for example: “Lobby opens 10 minutes before class”).

Pending vs verified

  • Pending — often from a website sync; review before StudioBot trusts them
  • Verified / accepted — available for answers
  • Dismissed — ignored going forward

What to do

  1. Review pending facts after onboarding or a website refresh
  2. Accept accurate facts; dismiss wrong or outdated ones
  3. Edit wording so parents hear your voice
  4. Add manual facts for anything the website doesn’t cover

Website or conversation sync

If your studio has sync enabled, StudioBot may propose new facts from your site. Treat them as suggestions — always accept or dismiss deliberately.

FAQs

Path: Knowledge → FAQs

FAQs are explicit question-and-answer pairs. Use them for:

  • What to wear / bring
  • Parking and entrance instructions
  • Make-up class policy (if you want the bot to answer it)
  • Sibling discounts only if you’re comfortable stating them without a pricing conversation

Write answers the way you’d text a parent — short and clear.

Documents

Path: Knowledge → Documents

Upload handbooks, welcome packets, or policy PDFs. StudioBot can use them as source material. Prefer clear, current documents — don’t upload drafts full of old prices you’re not ready to discuss in chat.

Teach StudioBot from real conversations

You don’t have to manage knowledge only from these pages. When you reject a bad draft in Needs Review or mark a Test Lab answer wrong, use Teach StudioBot to add a fact in context. Those facts land in Studio Facts for later review.

Best practices

  • Fewer accurate facts beat a pile of half-true ones
  • Never leave tuition amounts in knowledge unless staff is okay with the bot stating them (most studios hand pricing to humans)
  • Re-check facts after seasonal changes (summer hours, recital blackout, holiday closures)
  • After big knowledge updates, run a few Test StudioBot scenarios

Related articles