Decide · the cost of a closed alert

Email surveillance software, priced per closed alert

Email surveillance software is usually priced per monitored person, but what it costs a firm is reviewer time, and that is set by how many alerts are noise. The honest unit is the closed alert: licence, reviewer minutes, translation and second review, divided by alerts decided. This guide shows how to build that number, how to measure false positives yourself, and where Electronic Communications Surveillance lowers it.

Updated · 12 min read

Email surveillance software reviews a firm's emails and chats for misconduct, flags messages that match lexicons or models, and records each reviewer's decision. Its price is usually quoted per monitored person or per message volume, but vendors do not publish prices, and the licence is rarely the largest cost. The largest cost is people reading alerts, and most alerts are noise: research footers, newsletters, market colour, out-of-office replies. So the useful unit is the closed alert, everything spent in a month divided by the alerts decided, and the lever is the number of alerts a reviewer must read for each one that matters. Botminds' Electronic Communications Surveillance lowers that cost by having agents read each flagged conversation and propose a reason, which reviewers check in batches.

The figures from the solution on this page come from a fictional sample firm, Quillfield Capital, monitoring 2,140 people across New York, London and Singapore. They show how to measure, not what any customer achieved.

Nine in ten lexicon hits close as false positives, rule by rule

Inside information: 860 phrases, 7,412 hits
96.4%
Off-channel phrases: 1,214 phrases, 6,880 hits
95.1%
Collusion and price coordination: 312 phrases, 1,960 hits
93.8%
Gifts and entertainment: 190 phrases, 1,388 hits
91.0%
Complaints: 540 phrases, 4,210 hits
90.2%
Share of each lexicon's September hits closed as false positives, in the fictional sample firm's detection rules. These are sample data; no regulator or independent study publishes false-positive rates for asset managers' communications surveillance, so each firm has to measure its own.

How much does email surveillance cost?

Vendors do not publish prices, and no regulator or independent study publishes what firms spend, so the only reliable number is one a firm builds from its own books. Build it per closed alert. Add the month's licence and run costs, the reviewer hours at a loaded rate, the cost of translation and native-language review, and the cost of second review and quality checks; divide by the alerts decided that month.

The cost of a closed alert: add four terms, divide by alerts decided

+

Licence and running

monthly fee + hosting + archive connectors

The number vendors quote. Ask what it scales with: people, messages, channels or languages.

Procurement and IT

+

Reviewer time

alerts × minutes per alert × loaded rate

Usually the largest term, and the one noise drives.

Head of surveillance

+

Language

foreign-language alerts × (translation + native review)

Rule 3110 review in every business language costs real money on a global desk.

Head of surveillance

+

Second review and QA

countersigns + re-review sample × minutes × rate

The checks that make the first review defensible.

Compliance supervisor

Our method. Divide the sum by alerts decided in the month to get the cost of a closed alert, and track it with the share of alerts escalated; a falling cost with a stable escalation share is the sign of less noise, not less care.

The structure shows why per-seat comparisons mislead. Two products at the same licence price can differ widely in cost per closed alert if one sends twice the noise to reviewers. A product with a higher licence that closes noise with reasons a reviewer can approve in batches can cost less overall. Price the term that moves.

What share of surveillance alerts are false positives?

No regulator or independent study publishes a false-positive rate for communications surveillance at asset managers, and vendors' figures are not comparable because each counts differently. What is published is the direction of travel: the FCA saw banks "exploring AI to filter out false alerts" alongside their lexicons (FCA, August 2025), and the Financial Stability Board noted in 2017 that investigating suspicious transactions "often suffers from a high rate of false positives" in the anti-money-laundering field (FSB, November 2017).

Measure your own in one month. For each lexicon or model, count alerts by disposition: closed as false positive, closed with a coaching note, escalated. Then count again after a blind re-review of a sample, because a false positive that a second reader would have escalated was not false. In the sample firm's September, 9,104 of 9,860 alerts closed as false positives, 668 with coaching notes and 88 were escalated.

Where a month of alerts goes in Electronic Communications Surveillance's sample firm

September: 9,860 alerts

92.3%
6.8%
0.9%
  • Closed as false positive: 9,104 · 92.3%
  • Closed with coaching: 668 · 6.8%
  • Escalated: 88 · 0.9%
Fictional sample firm, September 2026. Every close carries a written reason and a named reviewer; a blind re-read of 489 closes reopened 7.

How many emails does a surveillance system flag?

It depends on the lexicons more than on the email. FINRA's guidance asks for a lexicon "comprehensive enough to yield a meaningful sample of 'flagged' communications", sized to the firm, its business, customers and locations, including foreign-language terms for branches that need them (FINRA, Regulatory Notice 07-59). A lexicon that flags too little is blind; one that flags too much buries the real alerts.

One month at the sample firm, from capture to escalation

4.62m

communications captured from seven sources

30,412

flagged messages, about 0.7% of those captured

9,860

alerts after grouping flags into conversations

88

escalations, under 1% of alerts

Fictional sample firm, September 2026, from the monthly surveillance report. Grouping flagged messages into conversations cut the review units by two-thirds before anyone read them.

Three ratios are worth tracking every month: flagged messages per thousand captured, alerts per flagged message, and escalations per thousand alerts. The first is set by the lexicons, the second by how well the system groups messages into conversations, and the third is the signal. When the first rises and the third does not, the extra hits are noise.

Where the reviewer's minutes go

Most of a reviewer's time on a real alert goes on finding things, not judging them. Our estimate for one multilingual alert that ends in an escalation is six hours by hand: an hour and a half finding the rest of the conversation, an hour each on translation, the call check and the reason, and the rest on orders, registers and the supervisor's re-read. With agents doing the finding, the same alert takes under an hour of people's time, nearly all of it reading and writing. That is our estimate on the sample firm's workflow, not a measured result.

Noise alerts cost minutes each, but there are thousands of them. The saving there comes from grouping by reason and approving in batches, with a reason on each alert, rather than opening each one. A reviewer who checks 412 footer alerts with the same reason, sends back any whose body carries risk and approves the rest has reviewed each, and has spent a fraction of the time.

Assigning foreign-language alerts to a native reader, in plain words

The Head of Surveillance's morning screen with the agents' panel. After the Risk agent's overnight summary, she has typed 'Assign Portuguese alerts to Marta', and the agents reply: Done, 38 open Portuguese alerts are now assigned to Marta Kowalczyk, who reads Portuguese natively; 6 were with another reviewer's backup queue; logged as your instruction. The left column lists what needs her: countersign 3 escalations, approve rule change v15, 3 QA reopens needing a second reviewer, 41 alerts near the review deadline and a Singapore mobile capture feed 2 hours 10 minutes behind.
Fictional sample data. Routing by language is a cost decision as much as a quality one: a native reader closes a foreign-language alert faster and more safely than a reviewer with a translation tool.

Noise is a lexicon problem first

The cheapest alert is the one that should never have fired. FINRA asked for lexicon systems able to exclude "any trailers or disclaimers used by the member", because such text "would 'flag' every such email", and for periodic review of the word list, adding and deleting terms (RN 07-59). A suppression is still a risk: a rule that hides a phrase in a footer must not hide it in a message body.

So test every suppression before it goes live. In the sample firm, a proposed suppression of the standard research distribution footer was run against September: it would have removed 1,140 of 9,860 alerts, missed none of the 88 escalations and affected none of the QA reopens, and every message was still captured and archived. It waits for the head of surveillance to approve it; the person who submitted it cannot.

A suppression back-tested on last month before anyone approves it

Detection rules. A proposed change, Exclusions and suppressions v14 to v15: suppress the standard research distribution footer in its three firm templates, proposed by the Risk agent on October 18 after reviewers closed 1,140 September alerts on exactly this text, submitted by Ravi Menon. Back-test figures: alerts in September 9,860 to 8,720, minus 1,140; escalations missed 0 of 88; QA reopens affected 0 of 7; messages still captured 100%, suppressed from alerts, never from the archive. Maker Ravi Menon, checker Priya Ramanathan, with Approve and Reject buttons. Below, the live rules with phrases, hits and the share closed as false positive for each.
Fictional sample firm. The back-test is the price check on noise reduction: 1,140 fewer alerts a month, at no cost in missed escalations on last month's data.

What does SEC guidance on email surveillance expect?

The SEC sets the recordkeeping duty and leaves the method to the firm. Advisers must keep written communications about recommendations and advice, funds and securities, orders and performance (17 CFR 275.204-2(a)(7)), whatever the medium. In a December 2018 risk alert on electronic messaging, the SEC's examiners described practices they had observed, among them, where advisers allowed social media or personal email for business, contracting with software vendors to monitor and archive those communications and compare them against "a lexicon of key words and phrases"; they also noted advisers that did no testing or monitoring of their own policies (SEC risk alert, December 2018).

For fiscal 2027 the SEC's examiners say generative "super intelligence (SI)" tools now do surveillance work at some firms, and that they judge the results by the standards that applied before those tools arrived (SEC, FY2027 examination priorities). Buying surveillance software that uses AI is therefore not itself a compliance answer; showing that its closes are reviewed and right is.

The cost of the alert that was not closed well

The other side of the account is a miss. Off-channel recordkeeping cases alone cost firms $2.3 billion in SEC penalties across 95 actions to early fiscal 2025, by the SEC's own count (SEC 2026-34), and the full history is in what the SEC's off-channel sweeps cost firms. Most of those cases began with a message that existed somewhere and was not kept, not with a lexicon miss, but the pattern is the same: the expensive event is the one nobody looked at properly.

The FCA puts the business case in plainer terms. Without effective recording and monitoring, it says, there is "a real risk of loss of monitoring and surveillance capability", and of losing the evidence that settles disputes between a firm and its clients over transaction terms (FCA, Market Watch 66). A cheap surveillance system that cannot show why it closed an alert has not saved that money.

How to compare email surveillance tools on cost

Eight things to ask before comparing email surveillance quotes

  1. What does the price scale with?

    People, messages, channels, languages or alerts: the one that grows fastest at your firm decides the bill.

  2. How many alerts will reach a person on our data?

    Run last month through it and count; a demo on vendor data proves nothing about your noise.

  3. How many reviewer minutes does an alert take, by type?

    Time a pilot on noise, on coaching cases and on escalations separately.

  4. How does it handle languages?

    Translation beside the original, a confidence per message, and routing to native readers.

  5. Can reviewers approve noise in batches, with a reason on each alert?

    Batching without per-alert reasons saves time and loses the evidence.

  6. How are suppressions and lexicon changes tested?

    A back-test on last month, a submitter and a different approver.

  7. What does connecting to our archive cost, and who does it?

    Connectors, data transfer and the IT time to grant read-only access.

  8. How is quality measured, and is it in the price?

    A blind re-read sample, reopen rates and seeded tests, reported monthly.

Our checklist for a cost comparison. The cost per closed alert, with the escalation share beside it, is the number to compare.

Where Electronic Communications Surveillance changes the cost

Electronic Communications Surveillance changes the reviewer-time term. Its agents rebuild each flagged conversation across channels, put English beside the original, check off-channel moves for a recorded follow-up and propose a disposition with a written, cited reason, so the reviewer reads and decides rather than hunts. Noise arrives grouped by reason for batch approval; alerts below the confidence threshold go to a person as needing judgment; and the QA agent re-reads a sample of closes blind. The design target is every alert closed with a written reason and a named reviewer, which is what the cost per closed alert should buy.

It does not change the licence of the archive or the recorder the firm already runs; it reads them. Going live on that archive is set out in eComms surveillance software on your existing archive, and what the agents may and may not decide is in who may close an alert.

Questions people ask

Is email surveillance software priced per user or per message?

Both models exist, and some vendors price by channel or language as well; prices are not published. Ask for the total for your people, channels and languages over three years, then convert it to a cost per closed alert using your own alert volumes.

How do you reduce false positives in email surveillance?

Exclude your own disclaimers and footers, group flagged messages into conversations, and review lexicon terms against their dispositions regularly, as FINRA's guidance suggests. Back-test every suppression on a past month to show it would not have hidden an escalation, and keep a blind re-review to catch false negatives.

Do small advisers need email surveillance software?

The rules require keeping and supervising communications, not buying software. FINRA's 2007 guidance noted that some small firms could not afford lexicon or sampling programs and allowed manual or combined methods suited to the business. The method must still be reasonable and evidenced.

What does the SEC say about email surveillance?

The SEC requires advisers and broker-dealers to keep business communications, and its examiners have described vendor monitoring and archiving against a lexicon of key words as a practice they observed, and faulted advisers that did no testing or monitoring of their policies. Its fiscal 2027 priorities say the same of surveillance done with what the SEC calls "super intelligence".

How many alerts can one reviewer handle?

No regulator publishes a benchmark. Measure alerts decided per reviewer-hour by alert type, with the blind re-review disagreement rate beside it; a reviewer clearing more alerts with a rising disagreement rate is not more productive. The sample persona in Electronic Communications Surveillance reviews about 140 alerts a day by hand.

Is surveillance software cheaper than outsourcing review?

Compare both on cost per closed alert, including what the outsourcer's reviewers read, how they record reasons and how their quality is checked. FINRA keeps the supervising principal responsible however the work is done, so the firm pays for oversight either way.

Electronic Communications Surveillance.
See it on your own files.

An agentic solution from Botminds. Reviews flagged emails, chats and calls in any language and closes each alert with reasons Book a demo, or explore how it works.