A second pair of eyes on the sends that can cost you the most.
Every protected send becomes a request with an explicit state. Low-risk correspondence to a registered counterparty clears immediately; anything else must satisfy a human requirement — recipient verification, manager authorization, or both — before it can be dispatched.
A cleared request means cleared to send. A person still presses the button, and that press is recorded.
Even a low score cannot auto-clear a counterparty that is not in your trust list. Unknown means a human step.
Managers authorize from the VeridLock mobile app. The web console shows the queue and its outcomes.
The decision produced by the risk engine maps onto a request status. As each human requirement is satisfied, the request recomputes: clearing verification may still leave approval outstanding, and only when every requirement is cleared does the request become releasable.
The most common failure mode in outbound tooling is a low score releasing a message to a counterparty nobody has ever dealt with. VeridLock closes that path explicitly: auto-release requires a registered trusted domain or a verified recipient address. Any other counterparty is forced onto a human path regardless of score.
After a send has cleared both recipient verification and manager approval, and only then, the sender is asked whether to add that counterparty to the trusted database — as a single address or as a whole domain. Trust is never granted off a bare auto-release or an escalation that skipped verification.
The risk engine returns a decision for the composed message.
Untrusted counterparties are forced onto an approval path whatever the score.
Verification and authorization requirements are cleared independently.
A person releases the message; the action is written to the audit trail.
The outcome
High-value sends carry an accountable signature, and the audit trail answers who authorized what, when, and on what evidence.
Set up your organization in minutes — no inbound migration required.