Platform

The dashboard your compliance team actually reads.

Every check leaves a trace: the category, the severity, the department, and whether the writer took the suggestion. No names, no message content. That is enough to see where communication risk lives, prove the control works, and send the right training to the right team.

Book a demo → See the audit trail

The problem

A control nobody can measure is a control nobody trusts

Most compliance programs can describe their policies but cannot show what happened this quarter. Incident counts only appear after something goes wrong, and training completion says nothing about behaviour. VerbaPulse produces the missing number: how often risk was written, how often it was fixed, and where it concentrates.

Risk becomes visible

Every flag is counted by category, severity, department and platform. You see the shape of your exposure without reading anyone's mail.

Behaviour becomes measurable

Acceptance rate shows how often people take the safer wording. It moves when training lands, and it drops when a team is under pressure.

Proof becomes exportable

The same record produces a quarterly evidence pack and a CSV audit trail, mapped to ISO 27002 controls.

Explore the platform

Four surfaces, one record

Everything below is built from the same anonymized event stream. Each area is a deep dive into what it shows and what it deliberately does not.

What it shows

The five numbers on the front page

These are the metrics the dashboard opens with, for the week, month or quarter you select.

Messages analyzed

Total drafts checked in the period, across Outlook, Gmail and the browser.

Risk rate

The share of analyzed texts that contained at least one flag. This is your baseline, and it should fall.

Acceptance rate

How often a writer applied the suggested wording instead of dismissing it. This is the adoption signal.

Risks resolved

Flags that ended in a rewrite or a removal, rather than being kept.

High-severity neutralized

The critical and high findings that did not survive into a sent message.

Built for your constraints

Aggregate by design, not by policy

The privacy posture is structural. There is no per-person view to switch on, because the product never records who wrote which sentence. Coaching is private to the writer; leadership sees categories, departments and periods. That is what makes the tool survive a works council review, and it is the reason adoption holds after the first month.

Read the full commitment on Privacy by Design.

FAQ

Common questions

Can managers see who wrote what?

No. Coaching is visible only to the writer. Everything in the dashboard is aggregated: counts by category, department, and period. There is no per-person view, no named log, and no message content anywhere in the product.

Where does the data in the dashboard come from?

Every check produces metadata: the risk category, the severity, which platform it happened on, the department, whether the suggestion was accepted, and a timestamp. That is the entire record. The draft itself is analyzed in memory and discarded.

How small can a department be before it becomes identifying?

Departments below a minimum size are not broken out separately, so a two-person team never becomes a de facto individual report. This is a deliberate constraint, not a setting to disable.

Can we export it?

Yes. Analytics and the audit trail export to CSV, and the Evidence Pack exports as a PDF for a chosen week, month, or quarter.

Do we need to configure anything to get the dashboard?

No. It populates itself as your team writes. Uploading your own policies adds a policy-violation category on top of the built-in ones, but the dashboard works from the first day without it.