How it works
Capture, remember, decide, report.
Every channel writes to one client record. Ash replies to what is safe, flags what is not, and tells you what happened each morning.
Every channel writes to one client record.
Most businesses do not have a communication problem. They have a filing problem. The call came in on a mobile, the follow-up went out by text, the paperwork moved over email, and the appointment ended up in a calendar none of those three know about. Nothing was lost, exactly. It is just that no single place knows the whole story, and the person who did know is now driving.
Ash starts from the other end. Every channel it handles writes into one record for that client, as it happens. A call at nine and an email at four are the same conversation, and Ash treats them that way — because the next time that person gets in touch, on any channel, what matters is everything they have already said, not the last thing they said on that particular one.
- Phone
- Ash answers, holds a real conversation, and writes down what was said.
- SMS
- Texts are answered in the same thread of context as the calls.
- Ash reads what arrives and drafts what should go back.
Ash answers what is safe to answer.
Not every message needs you. Someone asking what your hours are, whether you cover their area, what a process involves, or how soon you could see them — that is information you have already given a hundred times, and waiting six hours for it is the reason they call someone else.
Ash handles those, in your voice, immediately. What it will not do is improvise. If a question touches a price you have not set, a term you have not agreed, or a commitment it has no business making, Ash stops and hands it to you rather than guessing well. That boundary is the product, and it is described in full on the approval gate page.
It books into a real calendar, not a request queue.
A booking is only worth anything if the time is genuinely free. Ash offers a slot only when it falls inside the hours you have said you are bookable and the slot is actually open on your live calendar — and it checks again at the moment of confirmation, because the ten minutes someone spends deciding is exactly long enough for you to have filled it yourself.
What lands in your calendar is a real appointment with the client, the channel it came from, and the context attached. There is no separate inbox of booking requests to approve later, because a request queue is just a slower calendar.
You find out each morning, in one place.
Ash sends one digest each morning: who got in touch, what was handled, what is booked, and what is waiting on you. One message, before the day starts, instead of a notification every time something happens.
The part that matters is the last section. Anything Ash could not or would not answer stays on that list until it has actually been dealt with — it does not expire, and it does not get marked as read by being scrolled past. A follow-up that depends on somebody remembering is a follow-up that eventually will not happen.