A childcare CRM checklist for enquiries, tours and follow-up

A childcare CRM should help your team understand where a family is in the inquiry process and what needs to happen next.

Before comparing screens or feature lists, write down the journey you need to manage. A parent makes contact, asks questions, may arrange a tour and eventually decides whether to proceed. Your team needs a reliable record through those steps, including the conversations that do not lead to enrollment.

Use the following questions to evaluate whether a tool fits that work.

Can the team see the whole inquiry?

Ask how inquiries enter the system and how staff add a phone conversation or another contact that starts elsewhere. Check what happens when the same family contacts you more than once.

Look for a clear record of the current stage, the responsible person and the next action. A list of contacts is useful, but it does not by itself tell you who needs to do something today.

Does it support your tour process?

Walk through booking, confirming, rescheduling and cancelling a tour. Ask what the parent receives and what the team sees. Then try an ordinary exception, such as the usual staff member being unavailable.

Check whether the record can capture the family’s unanswered questions after the visit. Follow-up is more useful when it reflects what the parent actually needed to know.

What can each person access?

Decide what information is needed before enrollment and who should see it. Ask the provider about permissions, retention, deletion and export. Avoid collecting sensitive information simply because a field is available.

Use appropriate test details for demonstrations. You do not need to put a real child’s information into an unfamiliar system to find out whether an inquiry workflow makes sense.

What happens when the usual routine breaks?

Ask to see an overdue task, a duplicate inquiry and a team member handing work to a colleague. Find out how the school would continue if the service were unavailable, and how its records could be retrieved if you changed providers.

These questions are often more informative than a demonstration where every step goes exactly as expected.

Can your team maintain it?

Have the people who will use the CRM try the ordinary tasks. Notice where they need help and how much information must be entered twice. Establish who will keep stages and follow-up tasks current.

A useful comparison records what you actually saw, what the provider confirmed and what remains unanswered. Keep advertised features separate from demonstrated capabilities and anything still planned.

Explore Preschool Boss as one option in that review. Ask about its current availability and request a demonstration using your inquiry, tour and follow-up requirements. Decide from the work it can currently support, with clear answers about any remaining gaps.

The right next step is a clear operating process and a tool your team can use consistently. Start with that process before committing to a system.