Install in minutes
The Outlook add-in deploys org-wide through the Microsoft 365 admin center, and the Chrome extension covers Gmail. No new tab, no change to how the team works.
HR & Recruitment › References
"Between us, I would not rehire him, he was difficult and probably dishonest." An informal reference can be defamation or a negligent-reference claim. VerbaPulse flags it before the email sends.
Real output from the product. For a disclosure the safe move is removal, not a reword. VerbaPulse marks the exact span while the message is still a draft.
Outlook, Gmail and LinkedInWhere your team already writes
Microsoft 365 CertifiedOutlook add-in
Azure, SwedenEU processing on the cloud edition
No content retained by defaultRisk type and action only
Giving a reference is a minefield: say too little and it is unhelpful, say too much and it is actionable. The risk is the candid, unsubstantiated line: I would not rehire him, she was let go for stealing, he was probably dishonest. Written in an email, that can be defamation or a negligent misstatement, and "off the record" does not protect it.
The writer is being honest with a peer. But an opinion stated as fact, about a named person, in writing, is exactly what a reference claim needs.
VerbaPulse reads the draft as it forms and flags the span that creates the exposure, with a plain reason.
Install in minutes
The Outlook add-in deploys org-wide through the Microsoft 365 admin center, and the Chrome extension covers Gmail. No new tab, no change to how the team works.
Write as usual
As the draft forms, a risky span is flagged with severity and a plain reason, so the writer sees the exposure in the line they just wrote.
Fix before it sends
Apply the more careful wording, or remove the line, while the message is still a draft. By default, metadata-only events feed an audit trail your team can show.
VerbaPulse does not set your reference policy or give legal advice. It catches the disparaging, unsubstantiated language in the draft, while the wording can still change, so a candid line does not become a defamation or negligent-reference claim. It is one control inside email compliance for HR and recruitment, and it complements the systems you already run.
For the evidence behind this, our language risk benchmark runs real, anonymized cases through the product and reports what it flags.
An opinion stated as fact about a named person, especially an unsubstantiated one, can be defamation, and an inaccurate or careless reference can be a negligent misstatement. "Off the record" in an email does not protect it. This page describes language risk and is not legal advice.
It flags the disparaging, unsubstantiated line as it is written and marks it for removal. For example, "I would not rehire him, he was difficult and probably dishonest" is flagged as a disparaging comment with no legitimate content.
No. It does not draft references or decide what to say. It only checks the outbound email for disparaging or unsubstantiated language before it leaves.
Not by default. Drafts are analyzed in memory and never written to disk, and they are never used to train AI models. By default the audit trail keeps risk events (type, severity, action taken) with no message text and no user identity. An organization can opt in to keeping the flagged phrase, the suggested rewrite and the explanation.