Robocall and spam-text evidence tool

What it is

Illegal calls and texts are worth money under the TCPA, but only if they are documented properly. This app captures them, identifies the callers, cross-references the FCC complaint data and counts the damages the way the statute does: the right subsection, the right per-violation figure and no double counting between them.

It ends with a demand letter sized to the evidence. Built after one too many illegal calls. Used on a real case.

Under the hood

• Statute-accurate tallying: §227(b)(3) and §227(c)(5) counted separately, with no double counting, which is where most tallying goes wrong.
• Caller enrichment: carrier lookups and normalization so the same violator is one entity, not six phone numbers.
• FCC cross-reference: complaint history against the unwanted-calls dataset.
• Importers and capture: call and text exports in, structured evidence out.
• Demand letter generation: a letter that cites the tally and the statute, ready to send.
• A 21 MB evidence database, built for exactly one user, which is the point.

Design note

Most spam-tracking advice is wrong about what matters. The damages argument is not about how many calls arrived, it is about who is behind them and which subsection each call violates. The app is built around that: identify first, count second, letter last.

Stack