Data breach intake that captures identity theft signs up front
Confirm whether the breach exposed Social Security numbers, financial accounts, or login credentials, capture any identity theft or fraud losses since the breach, and collect the breach notice or supporting documentation up front.
The exact intake your data breach claims leads complete
This is the real 7-question guided intake for Data Breach Claims — the same flow your customers finish before you ever pick up the phone.
What a qualified data breach claims lead should tell you
Claims brought on behalf of an individual whose personal information (SSN, financial accounts, medical records, login credentials, etc.) was exposed in a company's data breach, distinct from breaches affecting only business data.
- Contacting Us About Own
- Know Name Company, Service,
- Breach Happen Or Were
- Exposed Information Include Sensitive
- Since Breach, Have Had
- Have Out- -Pocket Losses
- Still Have Documentation Can
The questions your team needs answered
Every data breach claims intake asks these — and why each one matters.
| Question | Why it matters |
|---|---|
| Are you contacting us about your own personal information (not a business’s data) being exposed in a data breach? | A 'no' here typically means the inquiry is about a business's exposed data rather than the client's own, which is outside the scope of most personal data breach claims. |
| Do you know the name of the company, service, or organization that had the breach (or sent you a breach notice)? | Being able to name the breached company makes the claim verifiable against public breach notices or class settlements, which strengthens the matter significantly. |
| Did the breach happen or were you notified about it within the last 3 years? | How recently the breach occurred affects whether the claim falls within a viable filing window, so older breaches are still captured but weighted lower. |
| Did the exposed information include sensitive details like your Social Security number, driver’s license number, financial account information, medical information, or login credentials? | Exposure of SSNs, financial accounts, medical records, or credentials indicates a higher-risk breach that's more likely to support a viable claim than exposure of low-sensitivity data. |
| Since the breach, have you had identity theft, fraudulent charges, an account takeover, a tax/benefits fraud issue, or had to freeze your credit or replace accounts/cards because of it? | Documented identity theft, fraud, or account takeover after the breach is often the clearest evidence of actual harm, which is central to the strength of the claim. |
| Did you have out-of-pocket losses or spend significant time dealing with the breach (for example, fees, lost money, time on calls, filing reports, or monitoring accounts)? | Out-of-pocket costs and time spent responding to the breach quantify damages the client may be able to recover, beyond the breach itself. |
| Do you still have documentation you can share, such as a breach notice, emails, screenshots, credit report alerts, bank statements, or police/FTC reports? | Retained documentation like the breach notice, statements, or fraud reports lets the attorney assess the claim's strength before ever picking up the phone. |
How Cliont scores data breach claims leads
Every answer is weighted automatically — no manual review required.
Value signals
- Contacting Us About Own: yes
- Know Name Company, Service,: yes
- Breach Happen Or Were: yes
- Exposed Information Include Sensitive: yes
- Since Breach, Have Had: yes
- Have Out- -Pocket Losses: yes
See the lead your team receives
Data Breach Claim - Identity Theft & Fraud
From first click to qualified lead
Follow people and businesses seeking counsel through one smooth, guided flow.
They land & meet you
Your video greeting plays instantly — a real face instead of a blank form.
They explain the matter
Smart questions adapt to their matter and capture the full scope.
They share the documents
The facts, dates, and any paperwork come attached, so you can assess the matter before the consultation.
You get a ready lead
Scored and qualified — waiting for you to win it.
Built for data breach claims workflows
| Cliont capability | Data Breach Claims application |
|---|---|
| Weighted scoring engine | Combines the identity-theft, fraud-loss, and sensitive-data answers into a single score, so a client with SSN exposure and confirmed fraud ranks well above someone with only a notice and no harm. |
| Document upload widget | Collects the breach notice, screenshots, credit report alerts, or bank statements referenced in the intake before the consultation, so the attorney reviews evidence instead of asking for it live. |
| CRM routing with lead scoring | Sends qualified data breach inquiries to your CRM tagged with their score, so leads with confirmed identity theft or financial loss surface ahead of notice-only inquiries with no reported harm. |
| Guided intake branching | Structures the seven breach-specific questions — personal data, named company, timing, sensitive data type, harm, losses, documentation — into a short guided flow instead of a generic contact form. |
Common data breach claims lead scenarios
Confirmed harm with documentation
The prospect names the breached company, had SSN or financial data exposed, already saw fraudulent charges or a credit freeze, and still has the breach notice and bank statements — this combination scores highest.
Breach notice, no harm yet
The client received a notice naming the company and sensitive data type, but reports no identity theft or fraud losses so far and hasn't tracked out-of-pocket costs, landing as a lower-scored but still trackable lead.
Business data, not personal
The inquiry is about a vendor or employer's systems being breached rather than the individual's own personal information, which the intake flags early through the personal-data question so it doesn't consume consultation time.
Old breach, outside recent window
The exposure or notice happened more than three years ago; the intake still captures the details but weights the lead lower given the timing question, useful for deciding whether it's worth a look.
Unnamed source, unverified breach
The prospect suspects their data was exposed somewhere but can't name the company or organization involved, which pulls the score down since that question carries meaningful weight.
Connect Cliont to your workflow
Send leads
HubSpot, HighLevel, Salesforce, JobNimbus
Book matters
Google Calendar, Outlook Calendar, Calendly
Notify your team
Email, SMS, Slack
Automate follow-up
Zapier, Webhooks, API
Simple, transparent pricing
Choose the plan that works for your business.
Professional
Unlimited intake forms and leads for your growing business.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Advanced analytics dashboard
Pay Per Lead
Only pay when you receive a qualified lead.
- Unlimited intake forms
- Custom video greetings
- AI-powered voice bot
- English + Spanish support
- Automatic lead scoring
- Digital estimates & e-signatures
- Photo, video & file upload
- Charged only for submitted leads
More consumer law intake templates
Data Breach Claims lead-intake FAQs
How does the intake tell a real breach victim from a vague inquiry?
It asks directly whether the exposed information is the person's own and whether they can name the company or organization that had the breach — both carry real weight, so unclear or third-party inquiries score lower automatically.
What if the client doesn't have documentation yet?
The intake asks whether they still have a breach notice, emails, screenshots, or statements, but a 'no' answer doesn't disqualify the lead — it simply lowers the score slightly compared to someone who can substantiate the claim immediately.
Can the intake handle breaches that happened years ago?
Yes — it asks whether the breach or notice occurred within the last three years. Older breaches still come through but score lower, which helps you triage by timing without turning anyone away outright.
What counts as 'sensitive' exposed information for scoring purposes?
The intake specifically asks about Social Security numbers, driver's license numbers, financial account details, medical information, or login credentials — these carry the highest weight in the catalog since they drive real harm.
How does the intake capture damages before the client ever talks to an attorney?
It separately asks whether the client has experienced identity theft, fraud, account takeover, or benefits fraud, and whether they've had out-of-pocket losses or spent significant time on the issue — both are heavily weighted signals.
Will this catch inquiries that are really about a business's data, not the person's own?
Yes — the very first question asks whether the exposed information is the client's own personal data. A 'no' answer scores much lower, helping you avoid spending consultation time on matters outside this practice area.
Turn data breach claims visitors into qualified cases
Give every data breach claims visitor a guided intake instead of a dead contact form — and get a scored, qualified lead before you book a consultation.