What is redaction in call records?

Card details are the classic case. A caller reading a long number aloud leaves it in the transcript unless something takes it out.

Pattern matching does the easy work. A sixteen-digit string in a run of four groups is unmistakable.

Everything else is much harder. A medical detail or a complaint about a named third party looks like ordinary conversation to a matcher.

Audio redaction is harder again, because the recording has to be edited rather than the text filtered.

Timing matters as much as coverage. Filtering a transcript after it has already been copied into a CRM leaves the original sitting somewhere nobody is auditing.

Say a caller to your flower shop wants to pay by phone and starts reading before anyone can stop her: "It's 4111 1111 1111 1111, expires 08 27, and the code is 123." That's a standard test number, but picture a real one. Within a minute you hold it in the audio, the transcript, the emailed summary and whatever your CRM copied across.

A text filter looks for 13 to 19 digits that pass the Luhn checksum, the arithmetic test every real card number satisfies. It would turn the first part into a row of asterisks. Catching the expiry and the three-digit code is harder, because "08 27" and "123" look like any other numbers in a sentence. Card industry rules say you must never store the security code after a payment is authorized. That short number is the one that can hurt you most.

Order matters, so ask when redaction runs. If it happens before the transcript is saved, the digits never land on a disk. Run it as a nightly cleanup job and the full number sat in storage all day, along with every copy made in the meantime.

Ask what happens to the audio too. Some systems pause recording while digits are spoken, and plenty leave the recording untouched while your transcript looks clean. You should also ask whether emailed summaries and CRM copies pass through the same filter. A redacted transcript next to an unredacted email isn't much protection.

Then test it on your own line. Read the test card number 4111 1111 1111 1111 slowly, once in groups of four and once as "forty-one, eleven" pairs. Spoken numbers reach the filter in whatever form the transcriber chose, and the second style slips past more filters than you'd expect.

GreetKeeper is not built to take payments, so card numbers should not be arriving in your transcripts in the first place.

Where you handle payment, point callers at a payment link or a transfer instead of taking digits on the call.

Retention is the other lever. A transcript you no longer keep cannot leak, and the retention setting is yours.