Quick Answer
If you want to know which questions belong on a wage and hour landing page, here is the short version.
- Ask about pay frequency and hours worked before you ask for a name or email.
- Ask about employer size early. FLSA coverage has a threshold.
- Ask when the last paycheck was. Statute of limitations kills more wage cases than any other factor.
- Ask whether coworkers were paid the same way. That is your collective action signal.
- Route those collective action candidates into a separate follow-up sequence.
- Fire your conversion event on the completed qualifying form, not on the raw page visit.
- Test question order on a live page before you call anything final.
Everything below explains why each of these decisions matters and how to structure the page so the form does the screening work before your intake team picks up the phone.
Why Wage and Hour Pages Attract High Volume and Low Case Value
Wage and hour is one of the highest-volume practice areas for paid acquisition. The surface area is enormous: unpaid overtime, meal and rest break violations, misclassification, tip theft, off-the-clock work. Broad Meta audiences contain a large pool of workers who believe they were underpaid. Click volume follows.
The problem is not the volume. The problem is that a significant share of inbound wage claims are not viable cases. The employer may be too small to trigger federal coverage. The claimant may have been correctly classified. The last paycheck may have cleared four years ago. Or the worker's situation may be a genuine grievance that has no legal remedy in the jurisdiction.
None of that disqualifies the worker as a person. All of it disqualifies the inquiry as a case worth your intake team's time.
A qualifying page on your firm's domain, sitting between the ad and the intake call, does the filter work. The claimant answers structured questions. The form logic routes them. Your team sees only the records that clear the screen. Your ad platform receives a conversion signal tied to a screened submission, not a raw click.
Ask about pay frequency, weekly hours, and employer size before you ask for a name or an email on a wage and hour landing page.
This is the structural point. Most law firm lead forms ask for contact information first. That is backwards for wage and hour. The qualifying data is what determines whether contact information is worth collecting.
The Overtime and Classification Questions That Matter Most
Pay frequency and classification are the first gate.
The most important question on a wage and hour page is not "were you paid fairly?" It is a structured question about how the claimant was paid.
Example: a wage and hour qualifying page might ask:
- "How were you paid?" with answer options: hourly, weekly salary, piece rate, day rate, or other.
- "Were you told you were not eligible for overtime because of your job title or job duties?"
A prospective claimant who was paid a flat weekly salary and told they were exempt is one of the strongest early signals of a misclassification case.
This question surfaces two of the most common FLSA violation patterns: the misclassified salaried worker and the worker paid a flat day rate regardless of hours. Both require the claimant to understand how they were compensated, which means someone who genuinely experienced the violation can answer accurately.
Hours worked per week is the second gate.
Federal overtime under the Fair Labor Standards Act applies to non-exempt employees who work more than forty hours in a workweek. If the claimant regularly worked fewer than forty hours, a federal overtime claim likely does not exist. State law may still apply depending on the jurisdiction, but federal exposure is off the table.
Ask this directly: "On average, how many hours did you work per week?" with structured ranges rather than a free-text box. Structured options produce cleaner data and faster routing logic.
Employer Size and Industry as Early Filters
Employer size matters because the Fair Labor Standards Act covers employers with annual dollar volume of business of at least five hundred thousand dollars, among other coverage thresholds.
This is one of the clearest early filters available on a wage and hour qualifying page, and most firms do not use it. The FLSA's enterprise coverage standard sets a dollar volume threshold for enterprise coverage, and individual employee coverage applies separately based on whether the employee's work involves interstate commerce. A domestic worker employed by a small household may not be covered under enterprise coverage at all.
The page does not need to explain FLSA doctrine. It needs a question that surfaces the signal.
Example: a qualifying page might ask "Approximately how many employees does your employer have?" with ranges such as fewer than ten, ten to forty-nine, fifty to two hundred forty-nine, or two hundred fifty or more. A firm specializing in large-employer class actions can immediately deprioritize the sub-ten bucket. A firm that pursues individual claims against small employers reads the same data differently.
Industry is a secondary filter with real case-value implications.
Certain industries generate wage and hour claims at higher rates and with clearer fact patterns: hospitality, healthcare, retail, warehouse and logistics, construction, and home care. Others generate high complaint volume but lower recovery per worker.
If your firm has a preferred case profile, the qualifying page can ask industry and route accordingly. This is not about turning away claimants. It is about giving your intake team the context to prioritize before they dial.
Statute of Limitations Language That Self-Selects Serious Claimants
Statute of limitations language on the page itself filters out claimants whose potential claims have already expired, which saves your intake team from spending time on legally dead leads.
The FLSA's general statute of limitations is two years for non-willful violations and three years for willful violations. Many states have their own wage statutes with different limitation periods, some longer and some shorter.
A qualifying page can handle this without giving legal advice. The mechanism is a structured question: "When did you last work for this employer?" or "When was the last paycheck you received from them?" paired with a conditional routing rule. A claimant whose last workday falls outside the relevant window is routed to a different outcome than one whose claim is still timely.
The page can also display a brief factual statement, clearly framed as general information rather than legal advice, noting that wage claims generally must be filed within a certain number of years of the last violation. This serves two purposes. First, it pre-screens claimants whose claims are legally stale before they enter the pipeline. Second, it signals to the claimant that this is a serious legal process, which filters out inquiries that were not genuine from the start.
State-specific limitation periods vary materially. California's statute of limitations for wage claims under the Labor Code can extend beyond the federal period. New York's differs again. Any static language on the page about time limits should note that periods vary by state and that the claimant should not rely on general information to determine whether their claim is timely. This is standard attorney-advertising caution, consistent with the requirement under ABA Model Rule 7.1 that communications not be false or misleading. Verify the specific disclosure requirement against your state bar's advertising rules before publishing.
Routing Collective Action Candidates Differently From Individual Claims
Collective action candidates, meaning people who worked alongside others in the same role under the same pay policy, should be routed to a different follow-up sequence than individual claimants.
A single unpaid overtime claim has a different case profile than a potential collective or class action involving dozens or hundreds of similarly situated workers. The collective action candidate is typically higher priority for the firm, faster to evaluate for viability, and worth a more senior intake conversation.
The qualifying page surfaces this with one question: "Were other people in your role or department paid the same way?"
The answer does not tell you whether a collective action is legally viable. That requires attorney review. What it tells you is whether this lead warrants a different conversation. A "yes" answer, combined with a large employer and a clear pay violation description, is the profile that goes to a senior intake team member or directly to an attorney on the first call.
Your CRM pipeline should have a separate stage for potential collective action candidates so intake can track them without mixing them into the individual claim queue. This is not a complex build. It is a field on the record and a conditional routing rule in your form logic.
Testing Question Order Without Tanking Conversion Rate
A qualifying page has two jobs in tension. It needs to collect enough information to screen the lead. It also needs enough people to complete the form to make the page worth running traffic to.
Every question you add creates friction. Every piece of friction reduces the completion rate. The question is not whether to accept friction. It is where to place it.
The general principle, consistent with form design research from the Baymard Institute, is that users are more likely to complete a multi-step form if early steps feel easy and low-stakes. For a wage and hour qualifying page, this means the first screen should ask about the claim itself, not about the claimant's personal information.
A practical structure:
- Screen one: claim type (unpaid overtime, misclassification, meal breaks, other) and pay structure. Low friction. The claimant is describing their situation, not handing over their data.
- Screen two: hours worked, employer size, industry, last workday. Medium friction. Still about the facts, not the person.
- Screen three: contact information, collected only after the form logic has established that the claim meets the firm's basic criteria.
This sequence means a claimant who does not pass the qualifying logic never reaches the contact screen. Your pipeline does not receive a name and phone number for a claim that will not be pursued. Your intake team does not dial a number that will not convert.
Test the order on live traffic before locking it. A/B testing question sequence on a qualifying page is a tractable experiment: run two versions, measure both completion rate and downstream signed-case rate, and evaluate both together. Completion rate alone is a vanity metric for a qualifying page. The metric that matters is the ratio of completed qualifying forms to signed cases.
Connecting the Page to Your Ad Platform and CRM
The qualifying page is part of a system, not a standalone asset. It connects upstream to your ads and downstream to your intake team and CRM.
Upstream: the optimization event.
The optimization event you send back to your ad platform should fire on a completed qualifying form, not on a raw page view or an unscreened form submission.
If you are running Meta ads for wage and hour cases, the conversion event you optimize toward determines what profile of person the platform goes to find. Optimize toward a raw form submission and the platform learns to find people who fill out forms. Optimize toward a completed qualifying form, where the claimant has passed your screening logic, and the platform learns to find people who match the profile of a viable claimant.
This requires server-side event delivery through the Meta Conversions API rather than a browser pixel alone. Browser pixels are limited by ad blockers and browser privacy settings. Server-side delivery is more reliable and supports sending the click ID, which ties the conversion back to the specific ad and audience that produced it.
For Google Ads, the same principle applies through offline conversion imports or the Google Ads API, depending on your CRM integration.
Downstream: the CRM record.
Every completed qualifying form should create a CRM record automatically. That record should carry the qualifying answers, not just the contact information. When an intake team member opens the record, they should see: pay structure, employer size, hours worked, last workday, industry, and whether the claimant indicated coworkers were paid the same way.
This information changes how the intake call opens. A team member who already knows the claimant was a salaried warehouse supervisor at a two-hundred-employee employer who last worked eight months ago is not starting from zero. They are confirming and deepening a fact pattern the form already established.
The signed case is the downstream signal that closes the loop. When a wage and hour case is signed in the CRM, that event should be sent back to the ad platform as an offline conversion. This is what teaches the platform to distinguish the creative and audience that produced signed cases from the creative and audience that produced form fills that went nowhere. RGDM's conversion tracking system is built to carry that signed-case signal from the CRM to the platform automatically.
For a deeper look at how this fits into the full acquisition system for employment law firms, see the law firms practice area page.
If you want to see how this has been built for an actual firm, the Nordanyan Law case study walks through the structure.
Frequently Asked Questions
What questions qualify a wage and hour claim online?
A qualifying page for wage and hour claims should ask about pay structure (hourly, salary, piece rate), hours worked per week, employer size, industry, and the date of the last paycheck. These questions establish whether the basic factual elements of an FLSA or state wage claim are likely present before contact information is collected. The page should also ask whether coworkers were paid the same way, which surfaces potential collective action candidates.
How do you screen unpaid overtime leads before intake?
Place qualifying questions before the contact information fields in a multi-step form. Route claimants whose answers fall outside the firm's case criteria, such as those with a last workday that falls outside the applicable statute of limitations, to a different outcome than claimants who pass the screen. Only the records that clear the qualifying logic should reach the intake team's queue.
What makes a wage and hour case worth pursuing?
From a marketing and intake-screening perspective, the signals that indicate a stronger claim include: a non-exempt worker paid a fixed salary or flat rate regardless of hours, consistent work weeks exceeding forty hours, an employer large enough to meet FLSA enterprise coverage thresholds, a last workday within the applicable statute of limitations, and a fact pattern shared by coworkers in the same role. These signals do not constitute legal advice or a prediction of case outcome. An attorney must evaluate each claim individually.
Should landing pages ask about employer size?
Yes. The FLSA's enterprise coverage standard includes a dollar volume threshold for employer coverage, and employer size is a practical proxy for that threshold in a qualifying form. A question asking for an approximate employee count helps route leads from very small employers, who may fall outside enterprise coverage, differently from leads involving large employers who are more likely to be covered. This saves intake time and improves the quality of the pipeline.
How does a qualifying page affect ad platform performance?
When the conversion event sent to Meta or Google fires on a completed qualifying form rather than a raw page visit or unscreened form submission, the platform's algorithm trains toward the profile of a person who passes the qualifying criteria. Over time, this shifts the audience the platform reaches toward claimants who match the firm's case criteria. This requires server-side event delivery through the Conversions API or equivalent to ensure reliable event matching.
What is the right number of questions for a wage and hour qualifying page?
There is no universal answer, but the practical constraint is friction. Each question reduces the probability that the claimant completes the form. The approach that tends to work best is a three-screen structure: the first screen asks about the claim itself (claim type and pay structure), the second screen asks about qualifying facts (hours, employer size, last workday), and the third screen collects contact information only for claimants who have passed the earlier screens. Test completion rate and signed-case rate together, not completion rate alone.
Do wage and hour qualifying pages need attorney-advertising disclosures?
Yes. Any page that solicits legal inquiries from the public is a communication by or on behalf of a lawyer and is subject to attorney-advertising rules in most jurisdictions. Required disclosures vary by state. Statute of limitations language on the page should be presented as general information, not legal advice, and should note that limitation periods vary and that the reader should not rely on the page to determine whether their claim is timely. Review the advertising rules of the state bar where the firm is licensed before publishing any language about case eligibility. The ABA Model Rules of Professional Conduct, Rule 7.1, prohibit false or misleading communications about a lawyer's services.
How do I connect a qualifying form to my CRM?
Most qualifying form platforms support webhook or API connections that can push a completed form submission to a CRM record automatically. The record should carry the qualifying answers as discrete fields, not as a bulk text block, so intake team members can read the claimant's situation at a glance and pipeline logic can route or prioritize records based on qualifying data. The CRM should have a pipeline stage specifically for potential collective action candidates so they are not mixed with individual claim leads.
Ready to build a qualifying page for your wage and hour practice that connects to your ad platform and CRM? Book a free Case Acquisition Review at rgdigitalmarketing.com/contact.