Loading
Every AI assistant answers questions, drafts replies and offers a chat widget. The list is not where they differ.
They differ in what happens when the assistant does not know. These features are arranged around that moment, because it is the one that decides whether anybody can rely on the rest.
Every entry below names the products it is joined to. Those joins are the specification, not a footnote.
A branded assistant on your site, one per audience, installed with a snippet and styled to match.
What the assistant is allowed to know: your site, your documents, your FAQs — and nothing else.
The point where the assistant stops and a person takes over, carrying the whole conversation with it.
Leads the assistant captured and the questions it could not answer, both landing in Flow.
One half faces your team: asking the company, cited sources, drafts and follow-ups, automation proposals, recall across threads. The other faces your customers: the widget, what it was trained on, how it hands over, and what it captures.
The rule is the same on both sides. An answer that cannot cite a source is not sent — enforced outside the model rather than requested of it — and anything that would commit the company hands to a person.
It holds no data of its own. Everything it answers from is either a record another product wrote or a source you gave it, which is what makes it auditable.
Ask about an account and the answer arrives in a sentence with the invoices, tickets and timesheets it read listed underneath. Checking takes a click, which is what makes it usable in a meeting.
Not add-ons and not an enterprise tier. These behave the same whether you run one product or all seven.
Read cited sources first, then the guardrails. Together they describe the only property that matters in a business assistant: that a wrong answer is a fixable defect rather than a mystery.
If you are evaluating us against another assistant, use our own trust checklist on both. It is written to be applied to us as well, and the refusal test is the one that separates them.
Yes. Every feature listed here works with Pulse alone. Where one says it joins another product, that join simply waits — switching the other product on later needs no migration, because the record it wants is already there.
No. Custom fields, permissions, automations, the audit trail and the API behave the same on the smallest plan as on the largest. The list on this page is the whole list.
Work backwards from the handover that costs you most. The feature that removes a manual step between two teams is worth more than the one with the longest description.
Fourteen days, every module, no card. Or half an hour with someone who will use your own numbers.