Every ticket comes with the customer attached.
Website chat, calls, texts and email land in one list, on the same record sales and success work from.
Opens the application form.
Sample workspace
Support sees what sales and success see.
No helpdesk to sync.
A conversation sits on the customer's timeline, next to their deals, calls and docs.
Every channel, one list.
Website chat, calls, texts, email and Slack threads, filtered by channel, status or outcome.
Stella takes the first pass.
She sums up a thread, sorts it and files the ticket, and asks before she changes anything.
Every call rings whoever is on.
Rules pick who gets a call or chat by day, hour and channel. On‑call rotas pick whose turn it is.
Ring all, or one by one
The whole team at once, or each person in turn.
Only people who can pick up
Skip anyone away, offline or at their limit.
Rotas with cover
Shifts hand off on their own, and a teammate can cover a day.
Nobody answers?
Try the next rule, or send it to voicemail.
Both sides prove themselves.
Every other verification flow asks only the customer. One email carries both halves, your agent's words first.
Two words, out loud. The customer checks them against the email before giving anything away.
Six digits, out loud. The code never appears in your agent's panel, so it can't be typed for them.
- Their email and phone can't be changed
- Their record can't be shared
- Their record can't be deleted
A lead can override with a written reason, and every attempt is logged, including a customer telling you somebody else phoned them pretending to be you.
One shift on the support desk.
Everything from overnight, in one list.
Each conversation already has an owner, and anything quiet for a day shows up in Signals.
- Chat, calls, texts and email in one list
- An owner on every conversation
- Slack threads land here too
- Filters by channel, status and outcome
The answer bot goes first, then hands off.
It answers from your own website, and passes the chat to a person when asked or when it has no source.
- A chat widget on your site
- Answers only from pages it has read
- Hands off the moment a visitor asks
- Visitors keep their past chats
Call back from the record. The notes are waiting.
Every phone field has a Call button. The call is recorded, transcribed and summarized with its outcome.
- Calls from any phone field
- Recording, transcript and AI summary
- Voicemails transcribed too
- Scorecards for coaching support calls
Stella turns the thread into a ticket.
She sums up the email and files a Ticket record on the account, once you say yes.
- Tickets as your own object
- Status and priority you define
- Linked to the customer's account
- Snippets in email replies
Priority hits Urgent. The lead knows at once.
A property agent sets priority when a ticket is made, and a workflow runs the moment it changes.
- Property agents fill topic and priority
- Workflows on any field change
- Reassign and notify a teammate
- Post to a Slack channel
See what's still waiting before you sign off.
Channel dashboards count what's waiting and unassigned, and every conversation carries its outcome.
- Waiting, unassigned and unread voicemails
- Conversations and calls by day
- Outcomes you can chart
- Totals for each teammate
Your support stack, on one subscription.
Tickets, chats and accounts stop living in separate tools.
HelpdeskConversations and tickets on the customer recordShared inboxChat, calls, texts and email in one listLive chatA chat widget with an answer botDialerCalls from any phone field, recordedCall coachingScorecards with an AI first draftReportingChannel dashboards and outcomes
Questions support teams ask.
Do we still need Zendesk or Intercom?
Most teams won't. Conversations, the chat widget, routing, calls and reporting are built in, on the records sales and success already use. There's no customer help center or satisfaction survey yet, so keep a tool for those if you rely on them.
What does the AI do with a new conversation?
If you turn it on, the answer bot replies from your website and hands off to a person. In the app, Stella sums up a thread, sorts it and files a ticket once you approve. Property agents fill fields like priority when a ticket is created.
Which channels land in the list?
Website chat, calls, texts, Slack threads and meetings. Email joins once your inbox is set to turn new mail into conversations. Voicemails are transcribed and kept with the call.
How do routing and escalation work?
Routing rules send a new conversation to a person, a team, a rotation or whoever is on call, by day, hour and channel. Escalation is a workflow on your ticket's fields: set priority to Urgent and it can reassign, notify the lead and post in Slack. Response-time targets aren't tracked yet; conversations quiet for a day are flagged.
Does support see what sales and success see?
Yes. A conversation sits on the customer's record, so the account, open deals, past calls and docs are all in one place.
Is there a customer portal?
No. Customers get replies on the channel they wrote in on, and the chat widget keeps their past chats.
Run support on the customer record.
Chat, calls, email and the account behind them, in one workspace.
Plans from $39 a seat a month, billed annually. See pricing