Back to case studies
French group of 10 schoolsMulti-campus organisation

Share a common foundation while keeping each school's rules

How to read this page

This page describes an implementation pattern. It publishes neither a testimonial nor a quantified client result.

The context

A French group of 10 schools needs shared answers while respecting each brand's programmes, campuses, contacts and rules.

What the flow needs to cover

  • Separate shared information from school-specific content
  • Identify the school, campus and programme concerned by the request
  • Route the record to the relevant team with conversation context

The mechanism

The deployment separates a shared knowledge base from school-specific scopes, then applies routing rules approved by the group.

  • Shared content is prepared once and reviewed by the group's owners.
  • Each school adds its programmes, events and contacts to that foundation.
  • The conversation clarifies the scope before offering local information.
  • Routing sends the request to the team assigned to the school and topic.

Organisation and responsibility

Content and access governance is defined with the group. Each team remains responsible for its information and follow-up.

Explore this approach for your school

Book a demo

One night, played twice.

Read the transcript

At 11:47 pm, Léa, seventeen, is looking for a school. An advert takes her to a website, but a fifteen-field form stops her. Six hours pass: she is not in any CRM. The same night starts again with Skolbot. At 1:12 am, she asks about co-op options and gets an immediate answer. She leaves her first name and number. In the morning, her record and a summary of the conversation are waiting in the CRM. Today, Léa starts her program.