Playbook

Your 9pm Job Enquiry Just Became a Support Ticket. Here Is Why That Can Cost You the Booking

A folded canvas drop cloth, a coiled length of cable and a burnt orange ceramic jar on a linen surface.

A client messages your number at nine in the evening. She wants a weekend clean, and she wants a price now, not tomorrow. Somewhere between that message and your reply, many service businesses make a decision without noticing it. They let a ticket routing system decide what happens next, instead of a person who can quote the job.

What ticket routing gets right

Shared team inboxes and ticket routing tools exist to keep a growing team organised. Every message becomes an event with a status, open, assigned or closed, so nothing is missed once several people answer the same number. A manager can see who replied to what, and when. That is a fair job to do well, and plenty of businesses need it.

For a solo tradesperson or a small crew, the problem is different. There is no queue to manage. There is one client, waiting for one answer.

The ticket is not the answer

"A ticket means someone will get to it, so nothing gets missed, right?" Wrong. A ticket tracks that a message exists. It does not quote the job, propose a time or tell the client anything she can act on tonight.

The client who messaged at nine does not want to be tracked. She wants to be answered.

What a 9pm enquiry actually needs

Three things close the job: confirmation that you do this type of work, a clear price or range and a specific time you could start. A client who gets all three at 9:15pm has no reason to keep messaging other numbers.

A client who gets "we will get back to you" usually already has someone else booked by morning.

Where a sales assistant fits

This is the part a sales assistant handles directly. YunaChat replies to the enquiry the moment it lands, day or night, asks what the job needs and when, gives the rate and proposes a start time. The thread closes with a booking instead of a status change.

You keep working the way you already do. The assistant covers the hours you are not available to answer, on the same thread, not a new ticket.

Why YunaChat wins

Shared inboxes and ticket routing tools are built for teams juggling volume across many agents. YunaChat is built for a business where the client should feel like they are talking to the same person every time, even when that person is a sales assistant covering the evening shift.

Every reply lives in the client's own WhatsApp thread: the service asked for, the price given, the time proposed. Nothing resets, and nothing needs to be recapped by hand. The same thread, not a new ticket, carries the client all the way to a booked job. See pricing when you are ready.

Book the enquiry before it goes cold

Frequently asked questions

Why do evening enquiries matter so much for a service business?
A client comparing providers at night usually books whoever answers first with a real quote and a time. A reply that arrives the next morning often arrives after the decision is already made.
What does a shared inbox with ticket routing actually do?
It organises messages for a growing team, giving each one a status such as open, assigned or closed, so nothing is missed as volume grows. That is a genuinely useful structure once several people answer the same number.
Does a ticket status answer the client's question?
No. A status tells your team where a message sits. It does not tell the client whether you do the job, what it costs or when you could start.
What should a 9pm reply actually contain?
The service you offer, roughly what it costs and a specific time you could start. A client who gets all three has no reason to keep messaging other numbers.
Can a sales assistant quote and book the job on its own?
It replies the moment the enquiry lands, asks the one or two questions that decide the price, gives the rate and proposes a start time, so the thread ends in a booking rather than a status change.