Module: Signals

Your customers tell you what they want every day. Ada writes it down.

Every question that went unanswered, every conversation handed to a human and every answer scored by quality supervision builds a picture no survey gives you: what your customers are actually trying to get done.

Records without sensitive content · redaction before writing, not after · retention set per customer

Three sources already building a picture of demand

01

The gap register as a map of demand

A question with no coverage in your materials is not lost. The system stores its fingerprint, counts repeats and orders the list by how often it comes up. After two weeks you have an editorial queue built from real conversations rather than from what somebody assumed was important.

02

A record of every turn

The audit log records every turn in append only form, after redacting document, account, card and phone numbers. You know what happened and when, without keeping in the log what does not belong there.

03

Quality supervision as a measure

Answers are scored by a rule layer and, on a sample, by a second model acting as reviewer. Scoring runs beside the critical path and never blocks an answer, so the customer never waits for a quality check and you get a number instead of an impression.

What your team does with it

A signal is worth as much as the decision it triggers. These three are triggered today.

You know what to add to the knowledge base
The order of topics comes from counts, not opinions. The most repeated unanswered question sits first in the queue.
You know where the agent hands over
Handover reasons come from a closed list, so they can be counted. A recurring reason usually means a gap in materials or a process that cannot be self served.
You know whether quality is improving
Answer scoring is a number over time, not an impression formed after reading a few conversations at random.

What we deliberately do not collect

A module that collects everything is convenient until the first audit. That is why these boundaries sit in code.

ItemCommon approachHere
The text of an unanswered questionFull text kept foreverA fingerprint and a counter, plus a masked sample with an expiry
Sensitive data inside a conversationRedaction at viewing timeRedaction before writing: what we do not want in the log never gets there
The agent's decision traceFull prompts and tool outputsCodes, versions and measures, without raw conversation content
Retention periodOne default for everyoneSet per customer and enforced by a daily job
In progress

Where this module is heading

The foundation, meaning recording and scoring, works. The layer that turns it into an account view and a sales alert is still being built.

Visitor qualification

Your own definition of a good fit, checked during the conversation and visible on every enquiry.

Notify me

Signals from website traffic

What a given company reads and how often it comes back, gathered into one arc of interest.

Notify me

Account view

Every conversation, message and meeting from one company on a shared timeline, instead of in four places.

Notify me

Alerts for the team

A notification the moment an interesting account returns to the site or asks to be contacted.

Notify me

Funnel view

Conversations, enquiries, booked meetings and the ones that happened, in one place with a weekly trend.

Notify me

Questions we get most often

What exactly do I see today, and what is still being built?
Today: the gap register, a record of every turn in the audit log and quality scoring of answers. Being built: visitor qualification, signals from website traffic, the account view, alerts and the funnel report. We separate the two plainly, because that is the difference between a report and a promise.
Do conversation records contain sensitive data?
Redaction happens before writing, not at viewing time. Document, account, card and phone numbers are masked before anything reaches the log. That is pseudonymisation, not severing the link to a person, and we call it that.
Do signals change what Ada answers?
No. The agent's knowledge comes only from published content. Signals tell you what to write, but that does not make them a source of answers.
How long do you keep this data?
As long as you set. A daily job clears sample content and old traces, leaving the counter and the fingerprint. A category with no configured window is skipped, not wiped with a default value.

See what your customers are asking about

During the demo we run Ada on your content and show what the list of missing topics looks like after a handful of conversations.