08 — inbox & crm

Your sales inbox
already knows who that is.

One shared inbox for the whole team, with a prospect pipeline attached to it. Every thread gets an owner, staff-only notes, and a link to the member, company, prospect or event case it is actually about.

shared inbox · prospects crm · gmail sidebar · send from your own address

One inbox. One owner.
One record attached.

what's included

A CRM that lives in the inbox.
Not next to it.

inbox

Shared team inbox

Assign an owner, open or close the thread, leave a staff-only note, and link it to the member or event case it concerns — filterable down to "unread, assigned to me".

prospects

Prospects kanban

A drag-and-drop board across six lead types where every card already knows its next action: a day-pass lead offers "send payment link", a virtual-office lead offers "request documents".

send-as

Send as yourself

Staff connect their own Gmail or Microsoft 365 once, and every reply, quote and invoice then leaves from their real address and lands in their real Sent folder — if a token breaks, the platform sends it anyway and tells them.

triage

AI thread intelligence

Each inbound mail is classified, then matched to the exact record it concerns — this event case, this unpaid invoice, this booking — and answered with a draft only a human can send.

sidebar

Gmail sidebar

A panel inside the staff Gmail with who the sender is in tersOS, their whole history with the space, a thread summary, and one click to create a prospect or advance a stage.

quotes

Quotes, proposals, compose

Event proposals and billing quotes on one model — versions, expiry, accept, convert to invoice — written in a docked compose window and logged with the provider message ID, so "did we actually send that?" has an answer.

The Tuesday enquiry

An enquiry lands at 08:41.
Nobody has to work out what it's about.

tersAI reads it, decides it is an event enquiry, and matches it to event case EV-2026-0114 — the September offsite that has been open since March. The thread gets linked to the case, the next action gets suggested, and a reply gets drafted in the tone you picked.

Then it stops. A human always clicks send — that is deliberate, not a missing feature. Same reason the inbox blocks remote images by default: a 1×1 tracking pixel tells a sender the exact second your staff opened their mail, and that is nobody else's business.

tersAI · inbox

New mail from amina@kolektiv.ba — "Following up on the September offsite. Is the amphitheatre still free on the 12th?"

tersAI — Event enquiry. Matched to event case EV-2026-0114 (Kolektiv, September offsite, open since March, toured in the spring). Thread linked. Want a draft?

"Yes — friendly, confirm the 12th."

Drafted. The 12th is free 09:00–18:00. It is sitting in your compose window and will go out from your own Gmail — I don't click send.

fig. 02 — classified, matched, drafted · a human still sends it · 08:41
"Nobody opens an email
asking who this is any more."
— the team behind tershouse, sarajevo

The context is already there.
Stop looking it up.