Use cases
What it actually does on a Tuesday
Not a list of capabilities — a list of jobs, each one written up with what happens step by step and exactly which building blocks it is made of. Every action named on these pages is a real one.
Front desk & inbox
The messages nobody should have to answer twice
The routine half of an inbox — hours, prices, availability, rescheduling — handled the moment it arrives, so the half that needs a person actually reaches one.
The enquiry that arrives at 11pm
Answered now, not at nine tomorrow
Two thirds of the messages a small business gets arrive outside the hours it is open. Answering them the next morning is not slow service — it is losing the ones who asked three places at once.
Learn moreThe 3am reschedule
Moved, confirmed, and nobody was awake
A reschedule is four actions that all have to happen or none of them should: find the booking, check what is free, release the old slot, take the new one. Getting three of the four done is worse than doing nothing.
Learn moreThe voice note in Urdu at midnight
It listens, understands, and can reply the same way
In a lot of markets the voice note is the default, not the exception — and every one of them is a message somebody has to stop and listen to. This listens instead, and answers in the language it was asked in.
Learn moreThe customer who sends a photo
It looks, describes, and routes it to the right person
A photo is the fastest way for a customer to explain something and the slowest thing for a business to process, because it cannot be searched, sorted or read at a glance six weeks later.
Learn moreQualifying before anyone picks up
The three questions you always ask, always asked
Sales time is wasted on discovery that could have happened before the conversation started. The three questions are always the same, and the customer is perfectly willing to answer them at midnight.
Learn moreForty messages, five that matter
The routine handled, the rest escalated with context
The front desk is not slow because the work is hard. It is slow because thirty-five easy messages are standing between them and the five that need thinking about.
Learn moreSales & pipeline
The follow-up that never happens on a busy week
Every business loses deals the same way: not to a competitor, but to a message nobody got round to sending. These are the ones that get sent.
The deals nobody followed up
Found every Monday, chased with your approval
Nobody decides to abandon a deal. It just stops being the most urgent thing, fourteen times in a row, and then it is too late to message without it being strange.
Learn moreAnswering a new lead in ninety seconds
Because the one who replies first usually wins
Speed to lead is the least glamorous and most reliable finding in sales research. It is also almost impossible to hit consistently with people, because people are in meetings.
Learn moreThe quote that went quiet
Chased on a schedule you set, in your words
In business setup the quote is the whole sale, and the gap between sending one and hearing back is where most of them die — usually because the client is waiting for a nudge they think is coming.
Learn moreWhen a deal is won, the handover starts itself
The welcome, the note and the next step, on the drag
The gap between winning and onboarding is where new customers form their opinion, and it is almost always the least designed part of the process because the person who won them has moved to the next deal.
Learn moreThe pipeline review nobody has time for
A written summary, on your desk, every Monday
Every sales manager intends to review the pipeline weekly. What actually happens is a glance at the board in the meeting, which surfaces the deals that are visible rather than the ones that are stuck.
Learn moreMoney & collections
Getting paid without anyone playing bad cop
Chasing money is uncomfortable, so it slips. An assistant does not find it uncomfortable — and it still asks you before it says anything that carries your name.
Chasing what you are owed
Drafted by the assistant, sent only by you
Chasing money is the job everyone postpones, because every message is a small negotiation with a relationship you want to keep. The drafting is the uncomfortable part, and it is the part that can be done for you.
Learn moreRenewals that never sneak up
Sixty days out, thirty, seven — automatically
A renewal missed by a week is a fine and an apology. A renewal raised sixty days out is revenue, and the only reason it does not happen is that somebody has to be watching a spreadsheet of dates.
Learn moreThe thank-you nobody remembers to send
Paid, acknowledged, and the next step offered
The silence after a customer pays is short but it is the wrong kind of silence — they have just handed over money and heard nothing back, which is exactly when doubt arrives.
Learn moreThe documents you are still waiting for
Chased individually, by name, until they arrive
Nothing stalls professional services like paperwork nobody has chased. The client is not refusing — they have forgotten which two of the nine documents they still owe you, and so, quietly, have you.
Learn moreRetention & reputation
The customers you already won, kept
Asking at the right moment is most of reputation management, and the right moment is usually the same day. Nobody is at a desk on the same day.
Asking for the review on the same day
When they are still pleased, not next Thursday
Review volume is a timing problem, not a persuasion problem. The same request converts several times better on the day of the visit than a week later, and nobody is free on the day of the visit.
Learn moreThe customers who quietly stopped coming
Noticed at ninety days, not at never
Almost nobody announces that they have stopped being a customer. They simply do not come back, and the business finds out a year later when somebody looks at a report.
Learn moreStudents who have stalled mid-application
Nudged on the specific thing they are stuck on
A student who goes quiet is almost never a student who changed their mind. They are stuck on one thing — a transcript, a test date, a decision between two offers — and stuck feels like failure, so they stop replying.
Learn moreKnowing what your reviews actually say
Read, summarised and trending, every week
An average rating tells you almost nothing. The useful information is which specific thing three separate people mentioned this month, and that requires somebody to actually read them.
Learn moreBack office, overnight
Work that was waiting for you, already done
Nothing here involves a customer. It runs while the business is closed, splits itself across helpers when the job is big, and leaves you something to read.
Tomorrow, prepared overnight
Split across helpers while the building is empty
Preparing a clinic day is three unrelated jobs that all have to be done and none of which need each other. Done in sequence it takes an hour; done at once it takes as long as the slowest one.
Learn moreThe weekly digest that writes itself
What moved, what did not, and what to look at
Dashboards answer questions you already knew to ask. What a manager actually wants is the two numbers that moved unexpectedly, and finding those means reading all of them.
Learn moreReaching into a system we have never heard of
Your own API, as a tool the assistant can use
Every business has one system nobody else has — an inventory database, a warehouse API, a legacy booking tool. The assistant being unable to see it is usually the reason automation stops at the interesting part.
Learn moreKnowing exactly what it told your customer
Every action, every result, in plain language
The question anyone asks about an assistant is always the same, and it is always asked urgently: what did it actually tell my customer, and what did it change.
Learn moreNothing here is a mock-up
Every action on these pages is one the product has
Each page lists what its assistant can do in plain language — “made a booking”, “checked what times are free”. Those are not descriptions somebody wrote to sound plausible: each one is tied to a real capability, and a test refuses to let this library name a capability that does not exist, is not available to that kind of account, or is deliberately withheld from an autonomous assistant.
That last one matters more than it sounds. Some capabilities exist but are kept away from the autonomous assistant on purpose — it has no way to read a clinical record, for instance, because the tools that would let it are not offered to it at all. A use case claiming otherwise would be the most convincing kind of wrong, so the check is mechanical rather than editorial.
How the engine holds all this together — durability, approval gates, spend ceilings and what happens when a server dies mid-booking.
Your scenario is probably not on this list
Most are not — the building blocks recombine. Tell us what you would want it doing and we will tell you honestly whether it fits.
We reply in under an hourOr message us on WhatsApp