TL;DR
- A generic contact form cannot separate a retainable criminal defense case from a non-retainable one.
- Charge type and jurisdiction are the two fields that do the most routing work before intake staff pick up the phone.
- A custody-status question surfaces urgency without making the page feel hostile.
- Conditional form logic can send an immediate alert for high-priority signals without changing the visible experience for most leads.
- A public-defender question routes a specific non-retainable subset to a separate CRM stage automatically.
- Form length should be tested against lead quality, not just submission volume.
Why Generic Contact Forms Waste Criminal Defense Ad Spend
When a criminal defense firm runs Meta ads or Google search campaigns, every click that lands on the page costs money. The question is not whether the page captures a submission. The question is whether the submission tells intake anything useful before they pick up the phone.
A form that asks only for name, phone, and email answers none of the questions that determine whether a case is retainable:
- Is this a misdemeanor or a felony?
- What state and county is the case in?
- Is the person currently in custody?
- Has an attorney already been retained or appointed?
Without those answers, intake staff are essentially cold-calling every submission and discovering on the call whether the firm can actually help. That is an expensive way to qualify leads, and it means the fastest, most motivated callers are mixed in with leads that were never retainable.
A criminal defense landing page that asks only name, phone, and email cannot separate a DUI case from a federal drug charge, and it cannot tell you whether the caller already has a public defender.
The fix is not a longer form. It is a smarter form with the right fields in the right order, built around the decision tree intake already uses on the phone.
Charge Type and Jurisdiction Fields That Route Cases Correctly
Charge type and jurisdiction are the two fields that do the most filtering work on a criminal defense qualifying page, because they route the lead before any staff member picks up the phone.
Charge type tells the firm which practice area bucket the lead falls into. A dropdown or button-select with categories such as DUI or DWI, drug offenses, assault or domestic violence, theft or fraud, sex offenses, federal charges, and other covers the vast majority of criminal cases without requiring the lead to type anything. The "other" option with a short text field catches edge cases.
Why this matters for routing: a firm that handles DUI and misdemeanor drug cases but does not take federal matters needs to know that before intake invests time in the call. A firm with a separate federal practice may route federal leads to a different intake team entirely. The charge-type dropdown makes that routing automatic.
Jurisdiction is the second critical field. Criminal defense is almost entirely local. A firm licensed in California cannot represent someone charged in Texas. Even within a state, a firm that primarily practices in Los Angeles County may not want cases filed in San Bernardino County if they do not have local counsel relationships there.
A state dropdown, followed by a county or city field that populates conditionally based on the state selection, handles this in two steps without overwhelming the lead.
Example: a criminal defense firm's qualifying page might include a charge-type selector with six to eight categories, a state dropdown, and a county field that appears only after a state is selected. A lead who selects a state the firm does not serve sees a message that routes them out of the intake pipeline before any staff time is spent.
Questions That Surface Conflicts Before the Call
Two questions surface conflicts that make a case non-retainable even before the charge type and jurisdiction check.
Has an attorney already been retained in this case?
This question catches leads who have already hired someone and are either comparison shopping or looking for a second opinion. That is not automatically a dead end. Some firms welcome consultations for second opinions and charge for them. But the intake path is different, and the page can route accordingly.
Has a public defender been assigned?
If a lead reports that a public defender has already been assigned and they are not seeking to replace counsel, that is a non-retainable signal that should be routed to a separate CRM stage rather than the main intake pipeline.
A lead with an appointed public defender who is actively seeking private counsel is retainable. A lead with an appointed public defender who is not seeking to replace them is not, at least not for the standard intake path.
The distinction matters because the page cannot make that determination alone. The right approach is to ask the question, flag the answer in the CRM record, and let intake handle the nuance on the call rather than auto-disqualifying. What the page accomplishes is tagging the record so intake knows what they are walking into before the call starts.
Phrasing matters here. "Do you currently have an attorney or public defender representing you in this case?" is a plain, non-judgmental way to ask. It does not imply the person did something wrong by having a public defender. It is just a routing question.
Asking About Custody Status Without Sounding Like a Script
A custody-status question phrased as 'Is this person currently in custody?' surfaces urgency without making the page feel like a police intake form.
Custody status is one of the highest-urgency signals in criminal defense intake. A person in custody may have a bail hearing in hours. They may need representation at an arraignment the next morning. The intake path for an in-custody lead is fundamentally different from the path for someone who was cited and released and has a court date in six weeks.
The phrasing of this question shapes how the page feels to the person filling it out. Aggressive or clinical phrasing increases abandonment. Plain phrasing does not.
Framing that works: "Is the person this case is about currently in custody?" This acknowledges that the person filling out the form may be a family member, which is common in criminal defense. It is neutral and direct.
Framing that pushes people away: "Are you currently incarcerated?" This assumes the person is the defendant, excludes family members who are often the ones reaching out, and carries a tone that feels institutional rather than helpful.
The custody-status answer feeds two things: the CRM record tag and the conditional logic that determines what happens after submission.
Form Logic That Routes Urgent Cases to Immediate Call Alerts
Conditional logic on a landing page form can detect a high-priority signal, such as in-custody status, and trigger an immediate Slack or SMS alert to intake staff without changing anything the lead sees.
The lead fills out the same form regardless of their custody status. What changes is what happens behind the scenes after they submit.
A standard submission, where the person is not in custody, has no court date in the next 72 hours, and is not flagged for an immediate conflict, routes to the standard intake sequence: an automated acknowledgment, a CRM record creation, and a queued callback from intake during business hours or the next morning if it is after hours.
An in-custody submission triggers a different backend sequence. The form logic detects the custody-status answer and fires an immediate notification: a Slack message to the intake lead, an SMS to the on-call attorney or after-hours intake team, and a high-priority tag on the CRM record. The lead sees the same thank-you page either way.
This is the difference between a form that collects and a form that routes. The routing logic is built into the form, not added later by a staff member who reads through submissions at 9 a.m.
Systems that connect form submissions to CRM records in real time make this possible. The form submits, the CRM record is created with all fields populated, the conditional rule fires based on the custody answer, and the alert goes out. The whole sequence runs in under a minute without anyone touching it. That is what CRM and intake automation is built for in a criminal defense context.
The same conditional logic applies to court date urgency. A field that asks "Is there a court date scheduled in the next seven days?" can trigger an elevated-priority flag for leads who answer yes, even if they are not in custody.
Testing Form Length Against Lead Volume and Quality
Testing form length matters because criminal defense leads are often in a time-pressured emotional state, and a form with more than five to six visible fields at once tends to reduce completions.
The tension in criminal defense landing page design is real. More fields produce better-qualified leads. More fields also reduce the number of people who complete the form. The right balance depends on what the firm is optimizing for.
A one-step form with name, phone, and a charge-type dropdown produces more submissions. Most of those submissions are under-qualified, and intake spends significant time on cases that were never retainable.
A multi-step form that shows two to three fields per step, then advances to the next set, reduces the psychological weight of the full field set. The lead sees "What type of charge is this?" and a dropdown, then clicks Next and sees "What state is this case in?" The total number of questions is the same, but the experience is lighter.
A/B testing a short form against a multi-step form on the same landing page, with the same ad traffic, tells you where the quality-versus-volume tradeoff sits for that firm's specific case mix. The metric to watch is not form completions. It is qualified leads per hundred submissions, measured by how many reach the intake-qualified stage in the CRM.
That means the CRM has to be configured to record which form version each lead came from. Without that tag on the CRM record, the A/B test produces submission counts but no quality signal. Conversion tracking that reaches back to the signed case, not just the form fill, is how the test eventually closes: which form version produced more signed retainers?
Meta's ad platform can receive the signed-retainer signal via the Conversions API, which means the platform can optimize toward the form version that produces signed cases rather than the one that produces the most clicks. That requires the CRM to pass the signed-case event back to Meta with the click ID attached to the original lead record. Without that signal, Meta is optimizing toward form fills, and a short form that produces more low-quality fills will look like the winner.
For more on how that signal loop works in a law firm context, see the Meta Ads for law firms section of the RGDM service stack, and the broader system overview at law firm marketing.
What a Well-Configured Criminal Defense Qualifying Page Looks Like
Putting the pieces together, a qualifying page for a criminal defense firm handles the following in sequence:
Step one: charge type (dropdown, required) and state (dropdown, required).
Step two: county or city (conditional on state selection), and whether there is a scheduled court date in the next seven days (yes or no).
Step three: custody status (yes or no), and whether an attorney or public defender is currently representing the person in this case (yes or no, with an optional text field for context).
Step four: name, phone number, and best time to call.
Each step advances only when the required fields are complete. The form does not show all steps at once. The submit button appears only on step four.
Behind the form: conditional logic fires on the custody and court-date answers. In-custody submissions and submissions with a court date in the next seven days trigger immediate intake alerts. All other submissions enter the standard follow-up sequence.
The CRM record created on submission includes every field answer, the form version tag, the ad click ID, the timestamp, and the routing flag. Intake opens the record before making the call and already knows the charge type, jurisdiction, custody status, and whether there is an existing attorney relationship to navigate.
That is a different call than one that starts with "So, how can we help you today?"
If you want to see how this page design fits into a full criminal defense case acquisition system, including the ad that drives traffic to it and the intake process that converts the qualified leads, the Case Acquisition Review is where we start. We pull the firm's current numbers or build the target model from scratch.
Frequently Asked Questions
What questions should a criminal defense landing page ask?
A criminal defense landing page should ask for charge type, state and county jurisdiction, custody status, whether a court date is scheduled within the next seven days, and whether an attorney or public defender is already involved in the case. Name and phone number are collected last, after the qualifying questions, so the form captures routing-relevant information even from leads who do not complete all steps.
How do you filter out leads with public defenders already assigned?
A direct yes-or-no question asking whether an attorney or public defender is currently representing the person in the case surfaces this information before the intake call. Leads who answer yes are tagged in the CRM with a separate routing flag rather than automatically disqualified, because some are actively seeking to replace appointed counsel. Intake reviews the flag before the call and approaches the conversation accordingly.
What form fields improve criminal defense lead quality?
Charge type and jurisdiction are the two fields that do the most to improve lead quality, because they allow the firm to route out cases it cannot handle before any staff time is spent. Custody status and court-date urgency improve intake prioritization. The combination of these fields, delivered through a multi-step form that shows two to three fields per step, tends to produce higher-quality submissions than a single-page form with all fields visible at once.
Should a criminal defense intake form be one page or multi-step?
Multi-step forms tend to produce fewer but better-qualified submissions in criminal defense because they reduce the visible complexity of the qualification process. The lead answers one set of questions, advances, and answers the next set. A/B testing a multi-step form against a shorter single-step form, with quality measured at the intake-qualified CRM stage rather than the submission stage, is the only way to know where the tradeoff sits for a specific firm's case mix and ad traffic.
How does form conditional logic work for urgent criminal defense cases?
Conditional logic detects specific field answers after the form is submitted and triggers backend actions based on those answers. A lead who answers yes to the custody-status question triggers an immediate Slack or SMS alert to the intake team, a high-priority tag on the CRM record, and routing to an urgent callback queue. The lead sees the same thank-you page as every other submission. The differentiation happens entirely in the backend workflow, not in the visible experience.
Can landing page form answers feed directly into a CRM?
Yes. Form submissions connected to a CRM via API or a native integration populate the CRM record in real time, including every field answer, the routing flag determined by conditional logic, the form version tag for A/B testing, and the ad click ID that traces the lead back to the specific ad that drove the visit. That click ID is what allows a signed retainer to be attributed to a specific ad when the signed-case event is later passed back to the ad platform.
How many fields is too many for a criminal defense landing page form?
There is no universal number, but forms that display more than five to six fields at once on a single visible screen tend to see higher abandonment rates among the emotionally pressured, time-sensitive audience that criminal defense pages attract. Multi-step forms that show two to three fields per step allow the firm to collect the same total information with less friction. The right answer for a specific firm comes from A/B testing completion rate against lead quality at the intake-qualified CRM stage, not from submission volume alone.