Enquiry Tracking

What this is

When a family fills in an enquiry form on your site, the enquiry lands in a shared list. You give it a stage, assign someone to it, and write notes as you go. Everyone with an account sees the same list.

Think of it as a shared spreadsheet that is harder to lose and easier to search.

How it works

• Enquiries from your BackPR forms arrive in the list automatically. You can add others by hand.
• You define the stages you use - enquired, visited, applied, offered, enrolled, or whatever fits your school.
• Each enquiry has one owner and a free-text history of what was said and when.
• You can filter by stage or owner, and export the list as CSV.

Where it stops

• It is a record of follow-up, not a system that follows up for you. There are no automatic nudges and no timers on hot leads.
• Tuition forecasting, scholarship modelling and financial projections are not part of it.
• It does not talk to your SIS or your payment provider, so reconciliation stays manual.
• Multiple campuses are handled with tags and filters.

Who suits this

A small admissions team - one to five people - currently tracking families across email threads and a spreadsheet. If you already run a CRM you are happy with, keep it.

Questions and answers

Who owns this internally? Whoever handles admissions at your school. We build and maintain the tool; your pipeline stays yours to run.

How long does it take to set up? Adding your stages and importing a list takes an afternoon. Getting your team to use it takes longer, and that part is up to you.

What data do you need? Your stage names and, if you want history, a CSV of existing enquiries.

Does it send the follow-up emails? No. You write and send those yourself.

Who builds it? BackPR, from Messina, Italy. Write to support@backpr.com.

Related

• Analytics & Reporting
• Registration & Payment Links