Six weeks ago somebody had a phone call. Now there is a disagreement about what was said, and the only record is two people's memory — one of which is about to cost you a slab. Every call, written down, on the job it belongs to.
Calls and texts attach themselves to the customer automatically. Nobody has to remember to write a note.
Your team is on the phone all day — changes, confirmations, promises, and the odd thing they shouldn't have agreed to.
Every one of those calls on the customer's timeline, recorded, transcribed and summarised, searchable months later.
The part of the job nobody was writing down.
Drawings get saved. Quotes get versioned. Emails sit in a thread. The phone call — where the actual promises get made — evaporates the second somebody hangs up.
Then a customer says you agreed to a mitred edge, or a builder swears he told you about the second bathroom, and the whole argument comes down to who sounds more certain.
The one part of the job with no paper trail is the part where commitments get made.
Sometimes there's a note. It says “called cust.”
Whoever took the call is the only one who knows, and they're on a template today.
Nine times out of ten you remake it or discount it, because you can't prove otherwise.
Inbound and outbound calls find the customer by number and attach themselves.
Calls, texts, emails, quote revisions and photos in one chronological record.
Anyone picking the job up sees the history — not just whoever answered the phone.
Calls and texts attach themselves to the right customer and the right job automatically. Nobody logs anything, nobody writes “called cust” in a box.
Open the account and the phone calls are sitting there in the timeline next to the emails, the quote revisions and the site photos — one story, in order.
The recording stays attached to the job. Not in a phone system somebody has to log into, not on a rep's mobile — on the job, where the argument is going to happen.
Most of the time nobody plays them. The value is that on the day you need one, it exists.
Not a separate phone portal with its own login and its own retention policy.
The disagreement always arrives weeks later. So does the proof.
From the customer's timeline, not from a support ticket with your phone provider.
The whole call in text, on the job, searchable.
What was agreed and what changed — without listening to any of it.
Find the call where somebody said “waterfall” without knowing which job it was on.
Nobody is going to sit through a twelve-minute recording to find out whether a splash was discussed. So the AI transcribes it and writes the summary — what was asked for, what was agreed, what changed.
Which means the record is not just kept, it is actually readable by the next person who touches the job.
Every shop has somebody whose head holds twenty years of customer history. When they retire, that history normally walks out with them.
It does not have to. The calls they made are on the jobs they made them on, transcribed and summarised, and the person who takes over can read them.
The new person reads what was actually said instead of being briefed from memory.
The account history stops being a person and starts being a record.
Pricing rules, drawings and now conversations all live in the shop, not in one head.
Book a demo and bring a real dispute — the remake you ate, the change nobody logged. We'll show you what the record would have looked like if the call had been on the job.
Yes — recording consent law varies by state and province, and several require all parties to consent. SlabOS keeps the recording; making sure your greeting and your policy meet the rules where you operate is on your shop, and it's worth a five-minute conversation with your lawyer before you switch it on.
No. It connects to it. Calls and texts flow into SlabOS and attach to the right customer — your team keeps dialling the way they already do.
Same treatment. Inbound and outbound SMS land on the customer's timeline alongside the calls and emails, so the whole conversation reads in order.
Only if you want them to. Access follows the same role-based permissions as the rest of SlabOS, so you can scope recordings to owners and office staff and keep them off the crew app.
It's good, not perfect — a bridge saw in the background will cost you words. The summary is built to survive that, and the recording is always there underneath if a line matters enough to check.
