Nine out of ten jobs still start with a phone call
And most of them get answered from a truck, a crawlspace, or not at all. That's not a software problem you fix with another app to check — it's a phone problem. So we started at the phone.
Kaboota was built alongside a working mechanical-services company, not in a demo. The first version didn't talk to anybody. It just listened, wrote the job down, and showed the owner what the week actually looked like. Everything since has been earned one call at a time.
Autonomy is earned, not assumed
It starts by listening and recommending. Every step up in authority is a decision you make, workflow by workflow.
Never guess on a customer's behalf
If the call didn't say it, the field stays empty. A blank is honest; a fabrication costs you a job.
Show the math
Every minute has a cost, and you can see it. We'd rather suggest you downgrade than lose your trust.
Never the system of record
You keep whatever you run today. We're the intelligence between the conversation and it — replaceable underneath, portable on top.
Owner-readable, not admin-readable
Plain language settings, big numbers, one green that always means money.
“It was already worth it the first week, when it caught the two calls we never knew we'd lost.”
PILOT CUSTOMER · MECHANICAL SERVICES · 20–40 CONVERSATIONS/DAY
90%
of service work still starts as a conversation
1
star code to go live — nothing to install
kaboota.cloudmantra.ai · *72 · 877 570 5946
Built alongside a working mechanical-services company, one call at a time.
Four commitments that cost us deals
Principles are easy to publish and hard to keep. These are the ones we have actually lost or slowed a deal over, which is the only test that means anything.
We will not invent a number to win a deal
Every figure we publish carries the window it was measured over, and anything extrapolated says so on its face. If a pilot is one account and one month, that is what it will say.
We will not put a capability on a page before it ships
Live and coming mean two different things, and they are marked separately per channel and per integration. You should never learn from a support ticket that something was a slide.
We will not let the AI confirm what did not happen
No booking it did not make, no part it did not check, no promise it cannot keep. A blank field is honest; a confident fabrication costs you the customer.
The boring answers, written down before you ask
Recording a customer's call is a serious thing to do on someone's behalf. Here is how it is handled, in the detail a procurement review actually wants.
TLS in transit, AES-256-GCM at rest with a fresh IV and auth tag per record. Provider keys are validated per vendor and never leave the server.
Every read is gated on your organisation from the query up. One account cannot see another's conversations, records or numbers by construction, not by filter.
A disclosure line in your own wording plays before capture, consent is tracked per customer, opt-outs are honoured automatically and marketing messages are blocked outside legal hours.
Conversation data belongs to your tenancy. It is not pooled, not sold, and not used to train models that serve anyone else.
Every conversation, agent action and admin change is logged and queryable, so you can show exactly what was said and done on your behalf.
Records export in full and delete on request. Leaving should cost you a support ticket, not a quarter.
Formal certification status is stated on request rather than implied by a badge on a marketing page. If you need a questionnaire answered, ask and we will tell you plainly what we hold today and what we do not.
Bring us the account. Keep the relationship.
We do the build and the ongoing tuning so your team does not have to add a head to support it. You stay the one the client calls.
You own the spend
Show which of the marketing budget produced a booked job rather than a click, and keep the account on the strength of it.
Recommend it, don't staff it
An answering layer you can put in front of a client without hiring for it or maintaining it afterwards.
Sit on top of what you sell
Add conversation capture and reporting above the field-service system already in the account.
One layer, many boards
Per-location rules and routing under a single agreement, with reporting that rolls up and breaks down.
Bring us an account
Tell us about the client and how you work. We come back within one business day with the partner brief, commercial terms and a walkthrough on one of your accounts.
Or just forward your line
Two weeks, your own number, listen-only to start. Nothing speaks to a customer until you say it may.