The buying question arrives in the support inbox.
It always did. Aqvitus notices it, answers it from the knowledge you already wrote, qualifies the lead and books the meeting — on the same customer record, in the same conversation.
- Nadia Okoye · Brightfold Ltd seat limit
“We’ve run out of seats again — what does the next plan up give us?”
score 78 Next: meeting booked, Thu 10:00 - Ben Arkwright · Marlow & Co pricing
“Is there a discount if we pay annually?”
score 41 Next: qualify — seats unknown
Example data. Every signal shows the message it came from.
Six kinds of signal, all with their receipts
The runtime that reads support conversations reads sales ones too. A signal is recorded with the exact turn it came from, so you can always see why it is on the list.
-
Pricing
Someone asks what it costs, or what a bigger plan includes.
-
Expansion
A customer describes a use you sell more of.
-
Seat limit
They hit the ceiling on their plan — from the conversation, or from a product event through a workflow.
-
Feature gate
They ask for something their plan does not include.
-
Competitor
They mention someone else by name.
-
Renewal risk
They say something that reads as leaving.
Signals score the lead, and the score and its provenance both show in the Sales view. A workflow can raise one from a product event too — a seat limit hit twice, for instance.
It can take the conversation further than an answer
A qualifying procedure runs the same way any other procedure does: written in plain language, compiled, and checked by your rules before it does anything.
“We’ve run out of seats again — what does the next plan up give us?”
- Seats
- 24
- Sites
- 3
- Timeline
- this quarter
- Authority
- can decide
- New
- Qualified
- Meeting
- Closed
Linked back to the conversation and the turn that created it · counted as a qualified lead, never as a support resolution.
Example data. Booking, quoting and creating a deal are actions like any other — your rules check them before anything happens.
- A buying question arrives in the support inbox, the way it always did.
- The same runtime records it as a signal, with the exact turn it came from.
- It answers from the knowledge you already wrote, and asks for the four things it is missing.
- It books against a real calendar — which is why the meeting is still there the next morning.
- The deal lands on the customer record support already uses. It is never counted as a support resolution.
Answers from the same knowledge
Product and pricing questions are answered from your articles and learned answers, not from a separate sales script that drifts out of date.
Qualifies on four things
How many seats, how many sites, what timeline, and whether the person can decide. It asks for what it is missing and stops when it has it.
Books against a real calendar
Not a suggested time. It reads availability and books the meeting, which is why the meeting is still there the next morning.
Quotes inside your rules
A quote is an action like any other, so your discount limits are checked by the rules engine before it goes anywhere.
Creates the deal
On the same customer record support is already using, linked back to the conversation and the exact message that started it.
Hands over with a packet
When it passes to a person, it passes the context with it — what was asked, what was answered, what was qualified.
A qualified lead is its own outcome. It is never counted as a support resolution.
How the numbers are definedA pipeline, not a second CRM
Deals sit on the customer record support is already using — same person, same history, same conversations. Your stages, named your way.
- A deal links back to the conversation and the turn that created it.
- Meetings carry a notes field, and stay attached to the account.
- Nobody has to retype what the customer already told the AI.
- New
- Qualified
- Meeting
- Closed
- Seats
- 24
- Sites
- 3
- Timeline
- this quarter
- Authority
- can decide
From the chat on 12 March · example data
Four measures, four definitions, reported apart
Attribution is where support software usually gets generous with itself. These four are written down, kept separate, and every figure traces to the conversations underneath it.
-
AI‑sourced
The AI found the intent, qualified it and booked the meeting with no person involved before that meeting.
-
AI‑assisted
The AI qualified it and a person closed it within thirty days.
-
Save
An intention to cancel reversed within fourteen days of something being done about it — by a procedure or by a person — valued at the recurring amount kept.
-
Support‑influenced
A deal closed won where any support conversation touched the account in the previous ninety days.
How this connects
Every channel
A buying signal in an SMS is the same signal as one in chat, on the same thread and the same customer.
Every channelWorkflows
A product event can raise a signal, create a deal or open the conversation first — inside the consent rules.
WorkflowsAnalytics
The revenue tab reports the four attribution measures separately and the pipeline by where the signal came from.
AnalyticsApprovals
Booking, quoting and creating a deal are actions. They pass the same checks as a refund.
Approvals
AI First. Human Always.
Stop losing the buying question because it arrived in the wrong inbox.