Connect Gmail or Outlook once. Everything SlabOS sends goes out from your own address — quotes, invoices, purchase orders, contracts, payment confirmations — and when they reply, the reply lands back inside SlabOS, attached to the record it belongs to.
No forwarding rules. No BCC discipline. No hunting through somebody's personal inbox to find out what was agreed.
Settings → Profile, Connect Gmail or Connect Outlook. Your signature imports with it.
Every thread about a quote, job, invoice, PO or supplier, sitting on that record — readable, replyable, searchable by meaning, with opens tracked.
The mail engine, short version — your address, the job's memory.
The drawing is in the software. The quote is in the software. The conversation that decided both is in somebody’s personal Gmail, and he’s on a template until Thursday.
So the job gets run twice — once by the person who remembers the emails, and once by everyone else guessing.
Every question about a job starts with somebody searching their own inbox.
The account history is a person, not a record.
The rule works right up until the week everyone's busy.
You chase a quote that was never opened, and don't chase the one that was.
Not notifications@. Customers and suppliers reply to you and it works.
Gmail signatures come across on connect. Outlook users paste theirs once.
Full editor, attachments, inline images — from the job page, not a second tab.
Connect Gmail or Outlook and everything the platform sends for you goes out from the address your customers already recognise — quotes, invoices, purchase orders, contracts, payment confirmations.
They reply to you like they always have. The reply comes back into SlabOS, onto the record, without anybody forwarding anything.
Threads match themselves to the quote, job, invoice, purchase order, supplier or lead they concern, and show up on that page automatically — with an AI summary of the key points at the top so you can catch up in ten seconds.
Invoices and POs are captured too, even for shops with no mailbox connected at all, and re-sends stack into one conversation per invoice instead of scattering.
Quotes, jobs, invoices, POs, suppliers and leads each carry their own conversation.
Key points first. Read the thread only if you need the detail.
See when a quote or invoice was actually opened before you chase it.
Chase an invoice three times and it's still one conversation, not three.
Zero shared words needed. It matches the ask, not the phrasing.
The AI pass is a bonus layer — literal matches never wait on it.
Each semantic hit carries a short reason it was surfaced.
Results open the thread and expand the exact message that matched.
Type “asked about the deposit” and it finds the message that means that — even when the email never used the word deposit. Every email panel in the platform has it.
Two passes run at once: instant exact-text matching, and an AI pass that reads the record’s conversation and matches the statements, requests and tasks inside it. Semantic hits come back tagged with a short reason they matched.
One button on the quote’s email panel: Audit requests vs quote. The AI pulls every concrete request out of the customer’s emails, dates them, and checks each one against what is actually in the quote — the areas, the cutouts, the line items.
Each request comes back done, missing, or unclear. It knows when you last revised, so anything asked for after that revision is flagged as missing rather than assumed. And it re-runs itself when the quote changes.
Extracted from the emails and matched against the quote's real contents.
Requests emailed after your last revision can't have been actioned — it says so.
Change the quote and the audit updates itself in the background.
“You forgot the sink we emailed about” stops being a thing that happens.
Book a demo and we'll connect a mailbox live on the call, send a quote from your own address, and search the thread by meaning while you watch.
No. It works with the conversations that concern your shop's records — threads matched to a quote, job, invoice, purchase order, supplier or lead. Personal mail isn't pulled into the business record, and visibility follows the same role permissions as everything else in the platform.
No, that's the point. You connect the address you already use and everything sends from it. Customers and suppliers never see a different sender and reply exactly as they always have.
Invoices, purchase orders and payment confirmations are still captured and threaded against their record, so those conversations stay on the job. You just won't have your personal customer threads flowing in, and sends go from the platform rather than your address.
Yes, temporarily. Google caps apps at 100 connected Gmail accounts until security certification completes, and we're partway through that queue. Outlook has no cap. If Gmail is full when you onboard, connect Outlook or wait for the certification to clear.
Two passes. An instant literal match on the text, plus an AI pass over the record's recent conversation that matches statements, requests and tasks by meaning. The AI layer is best-effort by design — if it's slow or unavailable, your literal results still come back immediately.
Never. Drafts land in the editor for you to read, change and send. The request audit reports, it doesn't act. Nothing leaves your shop without a person clicking send.
