The idea of introducing an AI chatbot to a school can feel daunting. There are questions about technical requirements, data protection, safeguarding, branding, and whether the office team will need weeks of training before anything goes live. For school leaders already stretched thin, the prospect of another technology project — one that might require IT support, lengthy procurement, or a steep learning curve — is enough to push it to the bottom of the priority list.

Ask.School is an AI-powered parent communication platform for UK schools that can be set up in under an hour with no technical expertise required. A school business manager, office administrator, or senior leader can move from creating an account to having a fully branded, safeguarding-compliant chatbot live on the school website in a single sitting. No coding, no IT department, no consultants.

Ask.School walks through every step of that process below, covering account creation, document uploading, calendar connection, branding configuration, safeguarding preferences, and website embedding. It also addresses the three concerns that come up most often: “Do I need IT support?”, “How long will this actually take?”, and “What if we get it wrong?”

For schools already exploring whether an AI chatbot is the right investment, the procurement checklist for evaluating AI tools provides a useful framework for comparing options before committing.

What does the full setup process look like?

The entire setup can be broken down into six steps. Each one is straightforward, and the total time from start to finish is typically between 30 and 55 minutes, depending on how many documents the school chooses to upload in the first session.

Here is the overview before the detailed walkthrough:

Step What it involves Estimated time
1. Create your account Register, name your school, choose your plan 3 minutes
2. Upload your documents Add policies, handbooks, prospectus, key documents 10–20 minutes
3. Connect your calendar Link your school calendar feed 3 minutes
4. Configure your branding Set colours, logo, welcome message 5 minutes
5. Set safeguarding preferences Review and customise safeguarding guardrails 5–10 minutes
6. Embed on your website Copy and paste the embed code 5 minutes

Total estimated time: 31–46 minutes

The rest of this guide explains each step in detail, including what to prepare in advance, what decisions to make along the way, and how to avoid the most common mistakes.

What should a school prepare before starting?

A small amount of preparation makes the setup process significantly smoother. None of this requires technical knowledge — it is simply a matter of gathering the right materials and having a few decisions made in advance.

Documents to have ready

The chatbot’s ability to answer parent questions accurately depends entirely on the documents it has been trained on. Schools should gather the following before starting:

  • School prospectus — the most commonly requested document by prospective parents
  • Behaviour policy — parents frequently ask about consequences, rewards, and expectations
  • Uniform policy — one of the most searched-for topics on school websites
  • Attendance policy — covers term-time absence, lateness, and reporting procedures
  • Term dates — a document that generates more phone calls than almost any other
  • SEND information report — required by law and frequently requested by parents of children with additional needs
  • Admissions policy — particularly important during admissions season
  • Safeguarding policy — helps parents understand how the school keeps children safe
  • Key contact information — office hours, email addresses, phone numbers
  • Any parent handbooks or welcome packs — these often contain exactly the kind of practical information parents search for

Schools do not need to upload every document on day one. The chatbot can be launched with as few as five or six core documents and then expanded over time. The most effective approach is to start with the documents that generate the most phone calls and parent queries, then add others as the team becomes more familiar with the platform.

For a deeper look at how AI chatbots handle document management, see the guide on how schools can use AI to manage documents and policies.

Calendar feed URL

If the school uses a digital calendar system — Google Calendar, Microsoft Outlook, or a school-specific MIS that supports iCal exports — having the calendar feed URL ready will save time during step three. This is usually a URL that ends in .ics and can be found in the calendar’s sharing or export settings.

Schools that do not have a digital calendar feed can still use the chatbot. Calendar events can be entered manually or added later. The chatbot will simply answer questions based on the documents it has, and calendar integration can follow when the school is ready.

For a detailed walkthrough of calendar integration, including how to find the feed URL in different calendar systems, see the guide on how to connect your school calendar to an AI chatbot.

Branding assets

Having the following ready will make the branding step faster:

  • School logo — in PNG or SVG format, ideally on a transparent background
  • School colours — the hex codes if possible (e.g. #003366 for a dark blue), or simply the colour names
  • Welcome message — a short sentence or two that parents will see when they first open the chatbot (e.g. “Welcome to Oakfield Primary. Ask me anything about our school.”)

A decision about who will manage the chatbot

Before starting, it is worth deciding who will be the primary administrator. In most schools, this is the school business manager, the office manager, or a member of the senior leadership team. The administrator does not need any technical skills — the role involves uploading new documents, reviewing the chatbot’s activity, and updating information when policies change.

Some schools choose to have two administrators: one for day-to-day management and a senior leader who oversees safeguarding settings. This is particularly common in schools where safeguarding governance sits with a specific member of the leadership team.

Schools that use a management information system — SIMS, Arbor, Bromcom or ScholarPack — can also connect it to Ask.School through Wonde to automate user management entirely. This eliminates the need to create accounts manually and ensures leavers are deactivated automatically. See the guide on how to connect your school MIS to Ask.School for the full process.

How does account creation work?

Account creation is the fastest step in the process. It takes approximately three minutes and requires only basic information about the school.

Step 1: Register at ask.school

Navigate to ask.school/register and enter the following (the signing up guide covers this in detail):

  • School name
  • School type (primary, secondary, special, all-through, or independent)
  • School postcode
  • Contact name and email address
  • A password for the account

There is no requirement to enter payment details during the trial period. Ask.School offers a 14-day free trial with full access to all features, so schools can complete the entire setup and test the chatbot with real parent queries before making any commitment.

Step 2: Confirm the school profile

After registration, the platform presents a school profile screen where the administrator can confirm or update basic details. This includes the school’s full name, address, and website URL. These details are used to customise the chatbot’s responses — for example, when a parent asks “Where is the school?”, the chatbot uses the address from the profile.

The school profile can be updated at any time, so there is no need to worry about getting every detail perfect during the initial setup.

Common concern: “Do I need IT support for this?”

No. Account creation requires nothing more than a web browser and an email address. There is no software to install, no server to configure, and no network settings to change. The entire platform runs in the browser, which means it works on any computer, tablet, or phone.

The only step where IT involvement might be helpful is the final one — embedding the chatbot on the school website. Even then, it requires only copying and pasting a single line of code, which any website administrator can do. Many schools find that the person who updates the school website (often the office manager or marketing lead) can handle this without IT support.

How does document uploading work?

This is the most important step, and the one that takes the longest. The chatbot’s usefulness depends directly on the quality and breadth of the documents it has access to. Schools that upload comprehensive, up-to-date documents from the start see significantly better results than those that begin with only one or two files.

Supported file formats

Ask.School accepts the following file formats:

  • PDF — the most common format for school policies and handbooks
  • Microsoft Word (.docx) — widely used for internal documents
  • Plain text (.txt) — useful for simple information sheets
  • Web pages — the platform can crawl and import content directly from the school website

How to upload documents

The document upload screen is accessible from the main dashboard. Schools can either drag and drop files into the upload area or click to browse and select files from their computer. Multiple files can be uploaded simultaneously.

Each document is processed automatically. The platform reads the content, indexes it for search, and makes it available to the chatbot. Processing typically takes between 30 seconds and two minutes per document, depending on length.

What makes a good document for the chatbot?

Not all documents are equally useful. The most effective documents for a school chatbot share these characteristics:

  • They answer questions parents actually ask. Term dates, uniform expectations, lunch arrangements, drop-off and pick-up times, and key contact details are the documents that will be used most heavily.
  • They are current. An outdated behaviour policy or last year’s term dates will generate incorrect answers. Schools should upload the most recent version of each document and remove outdated ones.
  • They are clearly written. The chatbot can only be as clear as the source material. Documents written in plain English, with clear headings and straightforward language, produce better chatbot responses than dense, jargon-heavy policy documents.
  • They contain practical information. A safeguarding policy that explains how parents should report concerns is more useful to the chatbot than one that only contains the legal framework.

How many documents should a school upload?

There is no upper limit, but as a starting point, most schools find that 10 to 15 core documents provide enough coverage to handle the majority of routine parent queries. The following table shows a recommended starting set:

Document Why it matters Query examples it answers
Term dates Highest-volume query for most schools “When does half term start?”, “What are the term dates?”
Uniform policy Consistently in the top three parent searches “What colour jumper do Year 3 wear?”, “Can my child wear trainers?”
Behaviour policy Parents want to understand expectations and consequences “What happens if my child is in detention?”, “What is the reward system?”
Attendance policy Covers absence reporting and term-time holidays “How do I report my child absent?”, “Can I take my child on holiday in term time?”
SEND information report Required by law, frequently requested “What support is available for children with dyslexia?”, “How does the school support SEND?”
School prospectus Comprehensive overview for prospective parents “What is the school’s ethos?”, “How many pupils are in each class?”
Admissions policy Essential during admissions season “What are the admissions criteria?”, “How do I apply for a place?”
Lunch menu / catering info Daily practical query “What is on the lunch menu today?”, “How do I pay for school meals?”
Parent handbook Broad practical guide “What time does school start?”, “Where do I park for drop-off?”
Safeguarding policy Shows parents how the school keeps children safe “Who is the designated safeguarding lead?”, “How do I raise a safeguarding concern?”
Extra-curricular clubs list Popular with parents of new starters “What after-school clubs are available?”, “How do I sign up for football club?”
Key contacts Directs parents to the right person “Who do I contact about SEND?”, “What is the school office email?”

Schools can add more documents at any time. Many find it useful to add new documents in the first few weeks as they notice gaps — for example, if parents start asking about the school’s homework policy and that document has not yet been uploaded.

What happens when documents change?

School policies and documents are updated regularly. When a document changes, the administrator simply uploads the new version. The platform automatically replaces the old content and updates the chatbot’s knowledge base. There is no need to retrain anything manually or wait for a technical update.

For schools that update documents frequently, Ask.School also supports website crawling, which means the chatbot can automatically pull the latest content from specified pages on the school website. This is particularly useful for term dates, lunch menus, and other information that changes regularly.

How does calendar connection work?

Connecting the school calendar allows the chatbot to answer time-sensitive questions such as “When is parents’ evening?”, “Is there a non-uniform day this week?”, or “What time is the Year 6 production?”. Calendar events are automatically synced, so the chatbot always has the most up-to-date information.

Step-by-step calendar connection

  1. Find the calendar feed URL. This is available in the sharing or export settings of most calendar applications. In Google Calendar, it is under Settings > [Calendar Name] > Integrate calendar > Public address in iCal format. In Microsoft Outlook, it is under Calendar > Share > Get a link.

  2. Paste the URL into Ask.School. In the Ask.School dashboard, navigate to the Calendars section and paste the feed URL into the provided field.

  3. Verify the connection. The platform will display a preview of upcoming events. Check that the events look correct and that the calendar is showing the right information.

The entire process takes approximately three minutes if the calendar feed URL is already available. If it is not, finding the URL may take an additional five to ten minutes depending on the calendar system.

What if the school does not use a digital calendar?

Some schools, particularly smaller primary schools, still manage their calendar through a page on the school website rather than a synchronised digital calendar. In this case, there are two options:

  • Upload a term dates document that includes key events. The chatbot will be able to answer questions based on this document, though it will not automatically update when events change.
  • Add events manually through the Ask.School dashboard. This is practical for schools with a relatively small number of key events.

Calendar integration can always be added later. Schools should not delay launching the chatbot simply because the calendar connection is not yet ready.

For more detail on the different calendar systems and how to connect them, see the guide on how to connect your school calendar to an AI chatbot.

How does branding configuration work?

A chatbot that looks and feels like part of the school’s own website builds trust with parents. If it looks generic or off-brand, parents are less likely to use it and more likely to revert to calling the office. Ask.School provides straightforward branding controls that require no design skills — the style guide documentation walks through each option.

What can be customised?

Element What it controls Example
Primary colour The main colour of the chatbot widget and header School’s primary brand colour (e.g. navy blue)
Secondary colour Accent colour for buttons and highlights School’s secondary colour (e.g. gold)
School logo Displayed in the chatbot header The school’s badge or wordmark
Welcome message First message parents see when they open the chatbot “Welcome to Riverside Academy. Ask me anything about our school.”
Chatbot name The name displayed in the chatbot header “Riverside Assistant” or simply the school name
Position Where the chatbot widget appears on the website Bottom-right corner (most common) or bottom-left

Tips for effective branding

  • Use the school’s exact brand colours. Parents should feel that the chatbot is an official school tool, not a third-party add-on. If the school website uses a specific shade of blue, the chatbot should match it.
  • Keep the welcome message short and practical. One or two sentences that tell parents what the chatbot can help with are more effective than a long introduction. “Welcome to St Mary’s. I can answer questions about term dates, uniform, policies, and more.” is clear and helpful.
  • Use the school’s official logo. A high-resolution logo on a transparent background looks cleanest. Avoid using a cropped photograph or a low-resolution image.
  • Choose a sensible chatbot name. The school name followed by “Assistant” or “Helper” is a safe choice. Avoid overly casual names that might undermine the professional tone.

For a comprehensive guide to creating a chatbot that reflects the school’s identity, see the detailed post on how schools can create a branded AI chatbot.

How do safeguarding preferences work?

Safeguarding is non-negotiable for any technology used in a school context. The Department for Education’s guidance on generative AI in education makes clear that AI tools must meet safeguarding requirements, and the UK government’s Generative AI Product Safety Standards set out specific expectations for products used in educational settings.

Ask.School includes safeguarding guardrails that are active by default. During setup, the administrator reviews these settings and can customise them to match the school’s specific requirements.

What safeguarding features are included?

Content boundaries: The chatbot only answers questions based on the documents the school has uploaded. It does not generate creative content, provide medical advice, offer counselling, or respond to questions outside its knowledge base. If a parent asks something the chatbot cannot answer, it directs them to contact the school directly.

Safeguarding escalation: If a parent or user raises a safeguarding concern through the chatbot — for example, by mentioning abuse, self-harm, or neglect — the chatbot immediately provides the school’s safeguarding contact details and, where appropriate, external helpline numbers. It does not attempt to handle safeguarding disclosures itself.

No personal data collection: Ask.School does not require parents to create accounts or provide personal information to use the chatbot. This means there is no personal data to protect, store, or potentially breach. Conversations are processed to generate responses but are not stored against identified individuals.

Data residency: All data is hosted in the UK on ISO 27001-certified infrastructure. No data is transferred outside the UK, and no conversation data is used for model training.

Age-appropriate responses: The chatbot is configured to provide responses appropriate for a school audience. It will not generate content that is inappropriate for children or young people, even if prompted to do so.

How to review safeguarding settings

During setup, the safeguarding preferences screen presents each setting with a clear explanation of what it does and why it matters. The administrator can:

  • Review the default safeguarding message — the response the chatbot gives when a safeguarding concern is raised. This should include the school’s designated safeguarding lead (DSL) name and contact details, plus any external helpline numbers the school wishes to include.
  • Confirm the escalation behaviour — what happens when the chatbot detects a safeguarding keyword or phrase. The default behaviour is to immediately display safeguarding contact information and stop the conversation about that topic.
  • Set content boundaries — schools can specify topics the chatbot should decline to discuss. For example, some schools prefer the chatbot not to answer questions about individual staff members, even if that information is in the uploaded documents.
  • Enable or disable conversation logging — schools can choose whether to retain anonymised conversation logs for quality monitoring purposes. Some schools find this useful for identifying gaps in their documentation; others prefer not to retain any conversation data.

Meeting KCSIE and the AI Product Safety Standards

Part 2 of Keeping Children Safe in Education (KCSIE) 2025 requires schools to have appropriate filtering and monitoring for any technology in use. Ask.School meets this requirement through its content boundaries, safeguarding escalation, and the fact that it only responds based on school-approved documents.

The Generative AI Product Safety Standards set out 14 requirements for AI products used in education. Ask.School meets all 14, including requirements around data protection, content safety, transparency, and user control. Schools can request a detailed compliance mapping document that shows how each standard is addressed.

Common concern: “What if the chatbot says something inappropriate?”

This is the concern that comes up most frequently, and it is a reasonable one. The key safeguard is that Ask.School does not use a general-purpose AI model that can discuss any topic. The chatbot only draws on the documents and information the school has provided. It cannot invent facts, share opinions, or generate content outside its knowledge base.

If the chatbot does not have the information to answer a question, it says so and directs the parent to contact the school directly. This “fallback to human” design means the chatbot never guesses or improvises.

Schools can also test the chatbot extensively before making it live. The preview mode allows administrators to ask questions and see exactly how the chatbot responds, without any risk of parents seeing those test conversations.

How does website embedding work?

The final step is making the chatbot available to parents on the school website. This involves copying a short piece of code from the Ask.School dashboard and pasting it into the school’s website.

Step-by-step embedding

  1. Copy the embed code. In the Ask.School dashboard, navigate to the Embed section — the chatbot sharing and access guide covers the full range of embedding options. A single line of code is displayed — it looks something like <script src="https://ask.school/widget/your-school-id.js"></script>.

  2. Paste it into the school website. The code needs to be added just before the closing </body> tag on every page where the chatbot should appear. In most website management systems (WordPress, Wix, Squarespace, or school-specific CMS platforms), this can be done through a “custom code” or “header/footer scripts” section in the settings.

  3. Save and refresh. Once the code is saved, the chatbot widget will appear on the website. It typically shows as a small icon in the bottom corner of the screen, which parents can click to open the chatbot.

Where should the chatbot appear?

Most schools choose to display the chatbot on every page of the website. This is the recommended approach because parents may arrive at any page — the homepage, the admissions page, the calendar page — and should be able to access the chatbot from wherever they are.

Some schools prefer to limit the chatbot to specific pages, such as the homepage and the parent information section. This is also straightforward — the school simply adds the embed code to the relevant pages rather than the site-wide template.

What if the school uses a managed website provider?

Many UK schools use website providers such as School Jotter, e4education, Greenhouse, Primary Site, or Cleverbox. These platforms typically offer a way to add custom code, but the exact method varies by provider.

For schools using a managed provider:

  • Check for a “custom code” or “JavaScript” section in the website settings. Most providers include this somewhere in the dashboard.
  • Contact the provider’s support team and ask them to add the embed code. This is a routine request that most providers can handle within a day.
  • Ask your Ask.School account manager for provider-specific guidance. Ask.School maintains documentation for the most common school website providers.

Common concern: “What if we get it wrong?”

The embed code is a single line that displays the chatbot widget. If it is pasted in the wrong place, the worst outcome is that the chatbot does not appear — it will not break the website or affect any other functionality.

If the chatbot does not appear after embedding, the most common causes are:

  • The code was pasted into the wrong section of the website editor (it needs to go in the HTML/code section, not a text content area)
  • The website has caching enabled and needs a cache clear to show the new code
  • The code was accidentally modified during copy-and-paste

All of these are easy to fix, and Ask.School’s support team can walk through the process with any school that encounters difficulties.

What does the complete timeline look like?

Here is the full timeline for a school that has prepared its documents and branding assets in advance:

Time Activity Notes
0:00 – 0:03 Create account and confirm school profile Requires only basic school information
0:03 – 0:05 Navigate the dashboard Brief familiarisation with the interface
0:05 – 0:25 Upload documents 10-15 documents is typical for the first session
0:25 – 0:28 Connect calendar feed Paste the iCal URL and verify events
0:28 – 0:33 Configure branding Logo, colours, welcome message
0:33 – 0:43 Review safeguarding preferences Review defaults, add DSL contact details
0:43 – 0:48 Test the chatbot in preview mode Ask sample questions, verify responses
0:48 – 0:53 Embed on the school website Copy and paste the embed code
0:53 – 0:58 Final check Verify the chatbot appears and responds correctly

Total: approximately 55 minutes for a thorough setup, including testing. Schools that are comfortable moving quickly, or that upload fewer documents initially, can complete the process in as little as 30 minutes.

What should a school do in the first week after setup?

The setup is only the beginning. The first week is an important period for refining the chatbot and building confidence in its responses.

Monitor the chatbot’s activity

The Ask.School dashboard provides an activity overview that shows:

  • How many conversations the chatbot has had
  • What questions parents are asking
  • Whether there are questions the chatbot could not answer (indicating a gap in the uploaded documents)
  • Peak usage times (useful for understanding when parents are looking for information)

Fill document gaps

The most valuable insight from the first week is identifying questions the chatbot cannot answer. If parents are asking about breakfast club and that information has not been uploaded, the solution is simple: upload the breakfast club information.

Schools that actively monitor and fill gaps in the first week typically see a significant improvement in the chatbot’s usefulness by the end of the second week.

Encourage parents to use it

The chatbot is only useful if parents know it exists. Schools should consider:

  • A brief announcement via the usual communication channel (email, text, app) letting parents know the chatbot is available on the website
  • A mention in the next newsletter explaining what the chatbot can help with
  • A note on the website homepage highlighting the new feature

The messaging should be practical: “You can now get instant answers to common questions on our website. Ask about term dates, uniform, clubs, and more.”

Gather feedback

Some schools find it helpful to ask a small group of parents to test the chatbot in the first week and provide feedback. This can highlight issues with specific responses, unclear language in uploaded documents, or questions that parents expected the chatbot to answer but could not.

How long does setup actually take for different types of schools?

The timeline above assumes a single school with a straightforward website. Different types of schools may have slightly different experiences.

Primary schools

Primary schools often have the fastest setup times because they typically have fewer policies and a simpler organisational structure. A primary school with 10-12 core documents can often complete the full setup in 30-35 minutes.

The most common challenge for primary schools is that policies and key information are sometimes stored on individual staff members’ computers rather than in a central location. Gathering the documents before starting the setup is the most time-consuming part.

Secondary schools

Secondary schools generally have more documents, more complex organisational structures, and larger websites. Setup typically takes 45-55 minutes, with the additional time spent on document uploading and configuring the chatbot to handle a wider range of queries.

Secondary schools may also want to configure different responses for different audiences — for example, ensuring the chatbot provides appropriate information for both current parents and prospective families during admissions season.

Special schools

Special schools often have highly specific documentation around SEND provision, therapies, and individual support programmes. The setup time is similar to that of a primary school, but the administrator may want to spend additional time reviewing safeguarding preferences to ensure the chatbot handles sensitive queries appropriately.

Multi-Academy Trusts

MATs face a unique challenge: they need consistency across all schools in the trust while allowing each school to maintain its own identity. Ask.School supports MAT-wide deployment, where a central team can manage shared documents (trust-wide policies, for example) while individual schools customise their own branding and school-specific information.

For a MAT with 10 schools, the central team might spend an hour setting up the first school and then 20-30 minutes for each subsequent school, as the shared documents and trust-level configuration only need to be done once.

Independent schools

Independent schools often have extensive prospectuses, detailed information about co-curricular programmes, and specific requirements around admissions. The setup process is the same, but independent schools may choose to upload more documents initially to ensure the chatbot can handle the wider range of queries their parent community typically has.

What are the most common setup mistakes?

Having supported hundreds of schools through the setup process, Ask.School has identified the most common mistakes and how to avoid them.

Uploading outdated documents

This is the single most common issue. A chatbot trained on last year’s term dates will give parents the wrong information. Before uploading any document, check the date and confirm it is the current version.

Solution: Create a simple checklist of documents to upload, note the date of each one, and verify that it is the most recent version.

Writing an overly long welcome message

Some schools write a welcome message that is several paragraphs long, explaining the chatbot’s capabilities, limitations, and data protection policies. Parents do not read long welcome messages. They want to ask their question.

Solution: Keep the welcome message to one or two sentences. “Welcome to [School Name]. Ask me anything about our school.” is sufficient.

Not testing before going live

It is tempting to complete the setup and immediately embed the chatbot on the website. But spending five minutes testing in preview mode can catch issues that would otherwise reach parents.

Solution: Before embedding, ask the chatbot the ten most common questions parents call the office about. If it answers them correctly, it is ready to go live.

Delaying the launch until everything is perfect

Some schools spend weeks gathering every possible document before launching. Meanwhile, parents continue to call the office with routine questions that the chatbot could already answer.

Solution: Launch with the core documents and add more over time. A chatbot that answers 80 per cent of routine queries today is more valuable than a chatbot that answers 100 per cent of queries in three months.

Forgetting to update the chatbot when documents change

Setting up the chatbot is not a one-time task. When policies are updated, term dates change, or new information becomes available, the chatbot needs to be updated too.

Solution: Add “update the chatbot” to the school’s document review process. Whenever a policy is approved, the new version should be uploaded to Ask.School at the same time it is published on the website.

What ongoing maintenance does the chatbot require?

Once the chatbot is set up, the ongoing maintenance is minimal. Most schools spend less than 30 minutes per month on chatbot management.

Regular tasks

Task Frequency Time required
Upload updated documents When documents change (typically termly) 5 minutes per document
Review activity dashboard Weekly or fortnightly 5 minutes
Fill document gaps As identified from parent queries 5-10 minutes per gap
Update safeguarding contacts When DSL or deputy DSL changes 2 minutes
Review welcome message Termly 2 minutes

Seasonal updates

Some updates are predictable and can be planned in advance:

  • September: Upload new term dates, updated policies, new staff contacts, revised uniform information
  • January: Update term dates for the spring and summer terms, refresh any documents that were reviewed at the start of the academic year
  • Admissions season: Ensure the admissions policy, prospectus, and open day information are current
  • Before Ofsted: Verify that all published policies are up to date and that the chatbot’s responses accurately reflect current school practice

How does Ask.School compare to setting up other chatbot tools?

Schools evaluating AI chatbot options will find significant differences in setup complexity across providers. Some general-purpose chatbot platforms require schools to manually create conversation flows, write individual responses, and program decision trees. This approach can take weeks of work and requires ongoing technical maintenance.

Ask.School is purpose-built for UK schools, which means:

  • No conversation flows to design. The chatbot understands natural language and draws answers from uploaded documents automatically.
  • No technical configuration. There are no APIs to configure, no databases to manage, and no code to write.
  • Safeguarding is built in. Schools do not need to programme safeguarding responses or content boundaries — these are included by default and meet KCSIE and the AI Product Safety Standards.
  • School-specific features. Calendar integration, term date handling, and policy management are designed specifically for how schools work, not adapted from a business chatbot template.

For a broader framework for comparing AI tools, the procurement checklist for evaluating AI tools covers the key criteria schools should assess.

What impact can schools expect after setup?

Schools that have completed the setup and launched their chatbot typically report noticeable changes within the first few weeks.

Reduced phone calls

The most immediate impact is a reduction in routine phone calls to the school office. Questions about term dates, uniform, school times, and other frequently asked topics are handled by the chatbot instead. For more on this, see the detailed analysis of how AI chatbots reduce school office phone calls.

Out-of-hours support

A significant proportion of chatbot conversations happen outside school office hours — evenings, weekends, and holidays. These are questions that would previously have waited until Monday morning or resulted in an email that the office team would need to respond to.

Better-informed parents

When parents can get instant answers to their questions, they are more likely to engage with school information and less likely to miss important details. Schools report that parents arriving at events, trips, and the school gate are better prepared when they have had access to the chatbot.

Staff time recovered

Office staff spend less time answering routine questions and more time on the work that requires human judgement — safeguarding administration, attendance follow-up, admissions processing, and supporting families with complex needs.

What if a school needs help during setup?

Ask.School provides several levels of support for schools going through the setup process:

  • In-app guidance: Each step of the setup process includes contextual help text explaining what to do and why.
  • Knowledge base: A comprehensive set of articles covering every aspect of setup and ongoing management.
  • Email support: Available during UK business hours, with responses typically within two hours.
  • Onboarding call: Schools that prefer guided support can book a 30-minute onboarding call where a member of the Ask.School team walks through the setup process together with the school administrator.

The onboarding call is particularly popular with schools that want reassurance about safeguarding settings or that have questions about how to handle specific types of parent queries.

Is setting up a school AI chatbot really that straightforward?

The short answer is yes. The process described in this guide — creating an account, uploading documents, connecting a calendar, configuring branding, setting safeguarding preferences, and embedding on the website — can genuinely be completed in under an hour by a single person with no technical expertise.

The longer answer is that the setup is only the starting point. The chatbot becomes more useful over time as the school uploads more documents, fills gaps identified through parent queries, and refines its configuration based on real-world usage. But the barrier to getting started is deliberately low.

Schools do not need to wait for a perfect setup. They do not need IT consultants, extended procurement processes, or staff training days. They need an hour, a collection of their core documents, and a willingness to try something that will make the school office’s life significantly easier.

For schools ready to take that step, Ask.School offers a 14-day free trial with full access to all features. Start your free 14-day trial at ask.school/register.