Secure Voice™ screens every inbound and outbound call through a pipeline of controls. When a control trips, it emits a signal and your action runs: allow, block, redirect or alert.
robocalls to U.S. consumers in 2025
estimated lost to contact center fraud in 2024
rise in deepfake fraud attempts in 2024
contact center calls was fraudulent
A control in the pipeline evaluates the call.
When the control trips, it emits a signal.
An action block catches the signal and runs your response.
Or any response you define.
Block and redirect action blocks ship ready to use. Write your own action block to catch any signal and do whatever your policy requires.
Move controls up or down to set the order they run on every call.
Each control shows its ID and a plain-language description.
Open the reference data behind a control.
Configure each control’s thresholds and actions, or remove it.
Set the default action, add controls from the library, and test before saving.
Outbound controls evaluate the called number, with their own order and default action. Use them to stop toll fraud, keep calls inside the allowed calling window for each destination country, and block calls to high-risk countries.
Check how a pipeline handles a call before your changes go live.
Enter the from and to numbers, direction, caller IP, P-Asserted-Identity and TN-Validation status.
Run the test call against the tenant’s pipeline.
See the decision, the control that made it, and how the tenant was identified.
Allow, Flag and Block bands for the Scam Score Decision control.
Observe-only mode: every call’s zone is classified and logged, with no automatic action.
A 1, 2 or 3 month decay window sets how much signal history each score uses.
Search complaint counts by exact number or prefix, with sync and expiry time for every record. This data backs the FCC Complaint Lookup control.
Register the number ranges you own, singly or by CSV upload. Inbound calls that present one of them as caller ID are caught.
The gray-list and black-list table used by the inbound and outbound FATF controls.
Suspicious calls are redirected to the Voice Bot Screener, which answers the call and profiles the caller to separate people from automated and AI-driven callers.
The suspicious call is redirected to the Voice Bot Screener, which answers it.
The caller is profiled to separate people from automated and AI-driven callers.
Allowed callers are connected to the number they dialed. Denied calls are rejected.
Handle each department or customer separately, each with its own admin, reporting, controls and pipeline, on one shared platform.
Connect Secure Voice™ with AWS Connect, Genesys Cloud and any other CCaaS provider.
Works with any SBC over SIP.
Email notifications and dashboard alerts.
Threats active now, with type and time.
Inbound, outbound and remote worker threats over 15 and 60 minutes.
Calls allowed, blocked and redirected over 1, 15 and 60 minutes.
Status, version, CPU, memory and uptime for every node.
Reminders, such as when the FATF gray and black lists are due for review.
Summary and detail reports for screening, remote worker, CDR, blocked IPs, Voice Bot Screener and caller reputation, plus a full audit log.
A report covering the last 24 hours. Pick the report groups, recipients, send time and timezone.
Filter calls by time, number, correlator ID, direction and decision. Expand a call to see every pipeline stage, its result and a plain-language detail.
100% on-premises, inside your own network.
Run in the private cloud you already operate.
Run in the public cloud.
Spam and TDoS, spoofing, number validity, geographic risk, FATF, toll fraud
Toll fraud, time-of-day compliance, geographic risk, FATF, number validity
Brute force, enumeration, impossible travel
Low-duration and dead-air call campaigns
Inbound and outbound controls check SIP signaling on every call. Remote worker and CDR controls detect attacks after the event, from SBC registration logs and CDR files.
Carrier filters stop known bad numbers. SBC rules do only what they were set up to do. Secure Voice™ catches the attacks that get past both.
Typical capabilities by category. Individual vendors vary.
A check that evaluates each call, such as Geo Fence, PAI Validator or Single Source TDoS.
The ordered list of controls a call runs through. Inbound and outbound calls each have their own.
The response that runs when a control emits a signal: allow, block, redirect, alert or your own logic.
Telephony denial of service: a flood of calls that ties up lines so real callers can’t get through.
Countries the Financial Action Task Force flags for weak controls against money laundering and terrorist financing.
Voice security for contact centers. It screens inbound and outbound calls through a pipeline of controls you choose, order and tune, and runs your action when a control trips.
Yes. Add controls from a library of 33, set the order they run, tune each control’s thresholds and actions, and test a call before saving.
It works with any SBC over SIP, and its native REST API connects with AWS Connect, Genesys Cloud and other CCaaS providers.
Suspicious calls are redirected to the screener, which answers the call and profiles the caller. People are connected to the number they dialed; automated and AI-driven callers are rejected.
Yes. Each tenant has its own admin, reporting, controls and pipeline on one shared platform.
On-demand summary and detail reports, a daily email, a full audit log, and a per-call trace showing every pipeline stage and its result.
On-prem, in your private cloud or in public cloud.
Book a demo and a specialist will walk you through the pipeline, controls and reports on your platform.
Fill in your details and we will email the PDF to you.
