Your Client Already Named the Job. A Script Should Not Ask Again
A client messages about a tutoring session for their child, names the subject, the grade level and a preferred evening, and gets back a reply about general opening hours. The detail they gave was specific. The answer that came back was not.
What a knowledge base reply is built to do
Auto-reply tools trained on a business’s own FAQ page are genuinely useful for exactly what they are built for: answering the same handful of questions over and over, opening hours, areas covered, how to book. For that narrow job, matching a phrase to a documented answer saves real time.
Why a documented answer misses a real enquiry
A booking enquiry is rarely a documented question. It carries a subject, a grade, a preferred evening, sometimes a note about a specific weakness the parent wants covered. None of that fits neatly into a pre-written answer about general availability. The client reads the reply, does not see their own detail reflected back, and starts wondering whether anyone actually read the message.
What actually reassures a client
Ask yourself something. Surely any quick reply beats silence? No. A quick reply that ignores the detail the client gave can read worse than no reply at all, because it signals nobody is paying attention. What reassures a client is a response that repeats their own detail back: the subject, the grade, the evening they asked for, confirmed.
Why YunaChat wins
YunaChat is the sales assistant that keeps the job thread built from exactly what the client says: the subject, the grade, the preferred time and any note about what they need covered, all inside one WhatsApp conversation on the tutor’s own number. It reflects that detail back in the reply, asks only what is still missing, and hands the tutor a complete brief to confirm. No FAQ reset, no generic hours message standing in for an answer, no reply that makes a specific enquiry feel unread. See how it fits your bookings at pricing.
Answer the actual question they asked
