All-in-one is the most overused phrase in studio software. For a music school it should mean something specific: one calendar, one student record, one phone number, and one place where a text message and a lesson booking agree with each other. Everything else is a feature list.
The four surfaces that have to agree
A music school runs on four things. The lesson calendar, which holds recurring series with a named teacher. The student record, which holds the family, the instrument, the level, and the notes from lessons. The phone, which is how new families arrive. And messaging, which is how existing families are reminded and re-enrolled.
When those four live in four products, the school spends its admin time moving information between them. When they live in one, a single action updates all four. That is the whole promise, and it is worth testing against a real week before you believe it.
Where separate tools break
Picture a normal Tuesday. A parent books a trial online. On Thursday she calls to move it, because her daughter's hockey schedule changed. The call goes to a message service that cannot see the calendar, so it writes a note. The note arrives by email to an account nobody checks during lessons. On Saturday the parent arrives at the old time.
Nothing in that chain is a software failure. Each tool did its job. The failure is the seam, and every seam between booking, phone, and messaging is a place where a family can fall out of the schedule.
Texting tools add a second seam. A messaging product sends from a different number than the one parents call, so replies land in a thread nobody monitors, and the opt-out record lives somewhere the calendar cannot see.
What Elevoi combines
Elevoi is a Canadian product that puts three of the four surfaces in one place: booking, AI phone answering, and text messaging. A call is answered in the school's name at any hour, availability is read from the live schedule, and a booking made on the phone appears in the same calendar the teachers read. The caller's details are stored on one record that the text reminders also use.
That means a parent who calls on Thursday to move a lesson gets it moved, not noted. And the confirmation text comes from the number she already has.
What it does not replace
Payroll is not in it. Bookkeeping and tax filing are not in it. Instrument inventory and rental agreements are not in it. Exam registration with outside conservatories happens on their systems, not yours. If your school has a retail counter selling reeds and strings, that is a point-of-sale problem, not a scheduling one.
A platform that claims all of that usually does each part badly. The honest test is whether the combined pieces share one record, or merely sit behind one menu.
A checklist for comparing platforms
- Does the phone answering service read the same calendar the booking page writes to?
- Is the text message sender the number parents already call?
- Does one student record hold both siblings, with separate teachers and instruments?
- Can a teacher see their week without seeing the billing?
- Do recurring series survive a term rollover without re-entering every student?
- Is consent for marketing texts stored on the record, with a date?
- Can you export students, lessons, and history in a form you could move elsewhere?
- Is support in your time zone, and does the vendor answer the phone themselves?
Where a stack of separate tools wins
If your calendar already works and your teachers are fluent in it, switching costs are real, and a suite that does everything adequately can be worse than a calendar that does one thing well. A school with a full-time administrator, no missed calls, and an established messaging tool has little to gain from consolidation.
The case for one product is narrower and more practical: the phone rings during lessons, the front desk is part-time, and the same family appears in three systems under slightly different names.
See how Elevoi works for music schools, or read about missed call answering for music schools.