Council Debate: Pop-up Form Configuration for applemobilityvehicles.com

Topic: Specify the ideal pop-up lead-capture form configuration for applemobilityvehicles.com — including trigger logic, fields, copy, success state, page-targeting, and A/B variants — that will maximize qualified-lead conversion without damaging the trust signals required for a $50–85k mobility-vehicle purchase.

Site Context: Maryland Ford Mobility Center. 27 vehicles. Buyers are wheelchair users and caregivers, sales cycle measured in weeks-to-months, often involving OT consults, insurance, and VA benefits. Existing /contact/ form already accepts name/email/phone/vehicle/message. Goal is to ADD an overlay that drives more conversions without breaking the high-trust medical-mobility tone.

Council Members

Brian Pasch (Dealer CRO Veteran — PCG Digital lineage) Voice: Practical, KPI-anchored, dealer-floor pragmatic. Speaks in cost-per-lead, lead-quality scores, BDC close rates, and VDP cannibalization risk. Bias: More fields = better lead. Overlays should serve the BDC, not the visitor. Knows the dealer-vertical benchmark numbers cold.

Peep Laja (CRO Methodologist — CXL Institute founder) Voice: Evidence-first, methodology-rigorous, allergic to folklore. Quotes friction studies, test-based field-count elasticity, and the difference between "best practice" and "actually tested on your traffic." Bias: Fewer fields, smarter triggers, multi-step over single-step when commitment is high, microcopy as a load-bearing element.

Andy Crestodina (Content Strategist — Orbit Media co-founder) Voice: Empathic, journey-aware, allergic to pop-up rudeness. Frames every form decision around "what has the user earned the right to receive, and what have we earned the right to ask?" Bias: Timing, context, and emotional resonance beat field-count optimization. A mobility purchase is life-altering — the pop-up has to feel like help, not capture.

Round 1: Initial Positions

[Pasch]: Let me start with what the dealer-vertical numbers actually say, because Apple Ford Mobility isn't a Shopify store and I don't want this council to design like it is. In our PCG dataset across Ford and import dealer pop-ups, an overlay form on a high-ticket VDP-heavy site converts 2.1%–3.4% of unique sessions when triggered correctly. That's incremental on top of whatever the static /contact/ form is doing — typically you'll see static-form leads dip by 8%–12% because the overlay cannibalizes the most motivated VDP visitors, but the net lift on total lead volume is usually +35% to +60%. So the overlay pays for itself, but only if the BDC can handle the lead quality drop, which is real.

Here's where I diverge from the CRO orthodoxy: on a $50–85k mobility purchase, more fields are not friction — they're qualification. If the BDC gets a lead with only "name + email," that rep is spending three days chasing a tire-kicker who turns out to live in Oregon and is shopping a Sienna conversion they saw on Craigslist. I want six fields minimum: First Name, Last Name, Email, Phone, Best Time to Call, and a "Who is this vehicle for?" dropdown (Myself / Spouse / Parent / Child / Veteran / Other). That last field is gold — it tells the BDC rep whether to lead the call with "tell me about your needs" or "tell me about your loved one's needs," and that single difference changes close rate by 15–20 points in our data.

Trigger logic: I want a 30-second time-on-site delay AND a scroll-depth of 50% AND must have visited at least one VDP. No exit-intent — exit-intent on mobility traffic catches the wrong people. Suppress on /contact/, /thank-you/, and on mobile (mobile gets a sticky bottom bar instead, not an overlay). The overlay copy should say "Get a Mobility Specialist on the Phone" — not "Get Pricing," not "Get a Free Quote," because mobility buyers are not coupon-hunting, they're problem-solving.

[Laja]: Brian, I respect the dealer data, but you're conflating "qualification" with "barrier" and the literature is clear on which one a six-field overlay actually is. CXL ran a meta-analysis across 47 lead-capture tests — every field above three reduces submission rate by 4%–11% depending on the field type. The "Best Time to Call" dropdown alone tanks completion by roughly 7% because it forces a decision the user hasn't made yet. You don't need it on the overlay; the BDC can ask it on the callback. The overlay is not a CRM record — it is a foot in the door.

My position: this needs to be a two-step overlay, not a single-step. Step 1 asks one question: "Are you shopping for yourself, or for a loved one?" Two giant tap targets, no typing. That's the Yes-Set — once they've clicked one, the sunk-cost of micro-commitment gets them through Step 2. Step 2 is three fields only: Name, Email, Phone. The "vehicle of interest" auto-populates from the VDP they were on (you have that data; use it). The "Who is this for" answer becomes a hidden field passed to the BDC. You get Brian's qualification without a six-field wall in the user's face.

Trigger logic: I want intent-signal-based triggering, not time-based. Time-based is 2010 thinking. Trigger on the second VDP view in a session, or on 60% scroll of a single VDP, or on returning visit within 7 days. Each of those is a real intent signal — a user reading three lines of an inventory page is not. Exit-intent: disagree with Brian, keep it but only on desktop, only after the user has spent 90+ seconds on the site. That catches the considered-but-hesitant buyer, which on a $70k mobility purchase is most of them.

Copy: headline must be specific. Not "Get More Info" — that's noise. Try "Talk to a Mobility Specialist — Most Calls Last 8 Minutes." The duration commitment is a friction-reducer; it tells the caregiver this won't eat their evening. Subhead: "We'll answer your questions about adaptive driving, financing, VA benefits, and insurance — no obligation, no sales pitch." Button: "Schedule My Call." Not "Submit." Never "Submit."

[Crestodina]: I want to take the conversation up one level before we keep arguing about field count, because both of you are optimizing the wrong variable. The right variable isn't "how many fields" or "what trigger" — it's "has this user earned the right to be asked, and have we earned the right to ask?"

A caregiver researching a Ford Transit conversion for their mother who just had a stroke is in the worst week of their life. They came to applemobilityvehicles.com because they're scared, exhausted, and trying to figure out how to keep their mom mobile. The last thing that human being needs is a 30-second overlay shoving a form in their face while they're trying to read about an EZ-Lock wheelchair docking system. That's not a conversion strategy — that's a trust violation, and on a $70k purchase that takes three months to close, trust violations are expensive.

Here's how I think about pop-up timing on this site: the form should appear only after the user has demonstrated meaningful engagement — and meaningful is not 30 seconds of scrolling. It's two-plus VDPs viewed in a session, OR five-plus minutes total dwell, OR returning visit, OR they hit the payment-calculator on a VDP. Those are earned moments. At that point, the user has been investing in your inventory; you've earned the ask.

The copy is everything. The headline should not be about getting info or scheduling a call. It should acknowledge the emotional context. Try: "Choosing a mobility vehicle is a big decision. Want to talk it through with someone who's done this hundreds of times?" That's not pop-up copy — that's a conversation opener. Subhead: "No pressure. No sales script. Just answers." The button: "Yes, let's talk." The implicit "I want to" before "talk" is the whole psychology of the click.

Page targeting: I would suppress this overlay on the /about/ and /accessibility/ pages — those are trust-building pages and an overlay there is jarring. Run it on VDPs (after earned engagement), on /inventory/, and on the payment-calculator interaction. And — this is the one I want both of you to push back on — I want a dismissed-state cookie of 30 days. Not 7. If a caregiver dismissed this overlay, they're telling you they're not ready. Asking again a week later is harassment; asking again a month later is a check-in.

Round 2: Responses & Challenges

[Pasch]: Andy, your "earn the right to ask" framing is beautiful and I'm going to steal half of it for client decks. But let me push back on the 30-day cookie because that's where good intentions kill revenue. Dealer-vertical research is unambiguous: 70% of high-ticket auto buyers visit a dealer site 5–9 times before submitting a lead. A 30-day suppression means you ask once, get dismissed, and then never get another shot during the actual decision window. 7 days is the sweet spot. I'll meet you at 14 if it makes you feel less predatory, but 30 is leaving qualified leads on the table.

Peep, the two-step overlay is smart and I will concede that the "Who is this for?" question as Step 1 is genuinely better than burying it as field 6. Conceded. But I'm not giving up Phone-as-required. You cannot run a mobility BDC on email-only — these conversations need voice, full stop. Insurance questions, VA paperwork, adaptive equipment configuration, OT involvement — none of that gets resolved over email. If the user won't give phone, they're not a lead worth closing. I'd rather have 40% fewer submissions where 100% include phone than 60% more submissions where half are email-only.

On the copy: Peep's "Most Calls Last 8 Minutes" is gold. I want that on the overlay AND on the existing /contact/ page AND on the VDP "Get More Info" button hover state. That single sentence solves the caregiver's #1 unstated objection — "I don't have time for a sales pitch right now." Andy's "Choosing a mobility vehicle is a big decision" headline I'd test against it directly. My gut says Andy's wins on first-time visitors and Peep's wins on second-visit. We'd A/B by visit count.

[Laja]: Andy, your emotional-context framing is correct and I want to be careful not to dismiss it because it's actually the load-bearing element here. But I want to challenge the implication that timing-based triggers solve the trust problem on their own. They don't. The form itself — its copy, its visual weight, its dismissibility — is what makes the difference between "this site gets me" and "this site is hunting me." You can have perfect timing and still feel intrusive if the overlay is a full-screen modal with a tiny grey X.

So here's my add to your position: design the overlay as a corner slide-in, not a center modal. Bottom-right, 380px wide on desktop, takes up no more than 30% of viewport. Always-visible close button, generous click target (44px minimum), and a "Maybe later" link below the form as an explicit dismiss. The "Maybe later" is the trust signal — it tells the user you respect their no. That single design choice is worth more than 200 words of empathic headline copy.

Brian, on phone-as-required: I'll meet you halfway. Phone is required on the BDC end but on the overlay form itself, I want to test "Phone (optional — but we respond faster by phone)" as a soft-required treatment. CXL has tested this exact pattern on healthcare and financial-services lead forms — explicit-optional with a benefit statement gets 85%–90% of users to fill it anyway, and the 10%–15% who don't are emailing because they're at work or in a hospital waiting room and can't take a call. You don't want to lose that lead.

On suppression cookie: 14 days, and I want to add a behavioral exception — if the user returns and views a third VDP, the cookie resets to zero and the overlay re-fires. That's the intent signal that overrides the dismiss. Aggressive? Yes. Justified? On a $70k purchase with a multi-month decision cycle, absolutely.

[Crestodina]: Peep, the corner slide-in versus center modal point is a great catch and I'll concede it fully — I was implicitly arguing for a less-intrusive form factor and your specificity is better than mine. Slide-in, dismissible, 380px, "Maybe later" link. All of it. Worth more than the copy debate, you're right.

Brian, on the cookie: 14 days with Peep's third-VDP override is a fair compromise and I'll take it. The override is the key — it means we're not arbitrarily nagging on a calendar; we're responding to demonstrated intent. That's the difference between marketing and stalking, and it matters on this audience.

But I want to push back on something both of you are taking for granted: the success state. Neither of you has talked about what happens after the user submits, and that's where this entire flow either earns or destroys trust. The default dealer success state is "Thanks! Someone will be in touch within 24 hours" and then a generic confirmation email. On a mobility purchase, that's malpractice. The success state should set expectations explicitly: "Marcus from our Mobility Center will call you between 10am and 12pm tomorrow at [phone]. He'll have your interest in [Vehicle Name] pulled up. If that time doesn't work, reply to this email with a better window." Named human, specific time window, specific vehicle context, easy reschedule path. That success state does more for close rate than any field-count optimization either of you would test.

And one more thing: the post-submission email needs to include a resource link, not a sales link. A PDF guide titled "5 Questions to Ask Before Buying a Mobility Vehicle" or "How VA Adaptive Equipment Grants Work." Give them something useful before the call. That's the "earn the right to ask" principle running in reverse — we're earning the right to be on their phone tomorrow.

Round 3: Synthesis Round

[Pasch]: Final position. I came in arguing six fields; I'm leaving at five (Name, Email, Phone, "Who is this for?" as Step 1, vehicle auto-populated). I conceded "Best Time to Call" — Peep's right, the BDC can ask it on the callback. I'm holding firm on phone-as-required-with-soft-optional treatment per Peep's healthcare pattern. I'm holding firm that the BDC handoff is where lead quality actually gets earned, and Andy's success-state spec is the right one — named rep, time window, vehicle context. I'll add a dealer-specific element: include the rep's photo in the confirmation email. Dealer trust research is unambiguous that face-photos in BDC follow-up raise show-up rates by 22%. Free win.

What I concede that I came in wrong on: the 30-second time trigger. Peep and Andy beat me on this — intent-signal triggers (second VDP, scroll-depth on a single VDP, calculator interaction) are objectively better than time-on-site for a high-ticket considered purchase. I was applying impulse-buy thinking to a non-impulse audience.

[Laja]: Final position. Two-step overlay, intent-signal triggered, slide-in form factor, dismissible with "Maybe later" link. Step 1: one question ("Who is this vehicle for?"). Step 2: three fields (Name, Email, Phone-with-explicit-optional-but-benefit-statement). Vehicle auto-populated from VDP context. Microcopy is load-bearing: "Most Calls Last 8 Minutes" stays on every variant. Button copy is "Schedule My Call" not "Submit."

What I concede: Andy's empathic headline framing is genuinely better than my efficiency-framed copy for first-time visitors. I want to test both head-to-head, but my prior is that Andy's wins on cold traffic and mine wins on warmer second-visit traffic — meaning we segment the copy by visit count, not pick one winner.

What I hold: methodology over folklore. Every variant gets tested before it ships to 100% traffic. Minimum 14-day test windows, minimum 200 conversions per variant for statistical confidence, and we're testing one variable at a time. No "we changed the headline and the trigger at the same time" garbage.

[Crestodina]: Final position. The pop-up exists to help a person who is in a hard moment. That frame survives every other decision. Trigger only on earned engagement (2+ VDPs, 5+ min dwell, calculator interaction, or returning visitor). Slide-in bottom-right, never center modal. Empathic copy on first-time visitors, efficiency copy on warm visitors, A/B tested. Two-step form. Success state names a human, specifies a time window, references the vehicle, and includes a useful PDF resource — not a sales follow-up.

What I concede: I was wrong on the 30-day cookie. Peep and Brian convinced me — 14 days with a third-VDP override is the right answer. That preserves trust without leaving qualified leads stranded.

What I hold: the trust frame is non-negotiable. If any single element of this design — copy, timing, form factor, success state — feels like hunting instead of helping, it gets cut. Period. Pop-up fatigue is real and on this audience, one bad experience kills the lead permanently. The bar is not "did it convert?" — the bar is "did it convert and would the user describe the interaction as helpful to a friend in the same situation?" If both are true, ship it. If only the first is true, kill it.

Council Synthesis

Areas of Convergence

1. Two-step overlay structure. Step 1 is one micro-commitment question; Step 2 is the lead fields. Pasch conceded the six-field wall; Laja and Crestodina aligned from the start.
2. Intent-signal triggers beat time-based triggers on this audience. Second VDP view, 60% scroll on a VDP, payment-calculator interaction, or returning-visitor status. No 30-second timers.
3. Slide-in form factor, bottom-right, 380px desktop / sticky bottom bar mobile, never full-screen center modal. Always-visible close + "Maybe later" link.
4. Microcopy is load-bearing. "Most Calls Last 8 Minutes" stays on every variant. Button copy is "Schedule My Call" or "Yes, let's talk" — never "Submit."
5. Success state earns the next conversation. Named rep with photo, specific time window, vehicle reference, useful PDF resource included.
6. Vehicle context auto-populates from VDP — never asked of the user.
7. 14-day suppression cookie with third-VDP override — balances respect for dismissal with response to renewed intent.

Remaining Disagreements

1. Headline copy: Crestodina's empathic frame ("Choosing a mobility vehicle is a big decision...") vs. Laja's efficiency frame ("Talk to a Mobility Specialist — Most Calls Last 8 Minutes"). Resolution: A/B test, with hypothesis that empathic wins on first-visit traffic and efficiency wins on returning traffic. Segment by visit count.
2. Phone-as-required treatment: Pasch wants hard-required; Laja wants explicit-optional with benefit statement. Resolution: ship Laja's version first ("Phone — optional, but we respond faster by phone"), measure phone-fill rate. If phone-fill drops below 80%, escalate to hard-required.
3. Exit-intent inclusion: Laja wants exit-intent as a secondary trigger on desktop after 90 seconds; Pasch and Crestodina are wary. Resolution: ship without exit-intent in v1, add as a v2 test if baseline conversion underperforms.

Buildable Spec

Trigger Logic (all must evaluate to true)

NOT on path: /contact/, /thank-you/, /about/, /accessibility/
AND (
  (VDPs_viewed_in_session >= 2)
  OR (scroll_depth >= 60% on a single VDP)
  OR (payment_calculator_interacted == true)
  OR (returning_visit_within_30_days == true)
)
AND NOT (dismissed_cookie_set within last 14 days
         UNLESS third_VDP_viewed_since_dismissal)
AND viewport_width >= 768px (else: sticky bottom bar variant on mobile)

Form Structure — Two-Step

Step 1 (large tap targets, no typing required):

Who are you shopping for? [ Myself ] [ A loved one ] [ A veteran / VA benefits ] [ Other ]

Step 2 (three fields):

Microcopy

Success State (post-submission)

On-screen confirmation:

"Thanks, [First Name]. Marcus from our Mobility Center will call you between 10:00am and 12:00pm tomorrow at [phone]. He'll have your interest in [Vehicle Name] pulled up.

If that window doesn't work, [reply to the confirmation email] with a better time.

Want to read up before the call? Here's [Five Questions to Ask Before Buying a Mobility Vehicle (PDF)]."

Confirmation email (sent within 30 seconds):

• From: Marcus Smith, Apple Ford Mobility Center
• Includes rep's photo (Pasch: +22% show-up rate)
• Restates time window, phone number, vehicle of interest
• Attaches the PDF resource
• One-click reschedule link

Page-Targeting Rules

A/B Variants for v1 Launch (run sequentially, not simultaneously)

Tracking & Telemetry

• Event popup_shown (with trigger reason, page path, visit count)
• Event popup_dismissed (which step, dismiss method)
• Event popup_step1_completed (with who_for answer)
• Event popup_step2_completed (the conversion)
• Event popup_phone_filled (boolean for the optional/required test)
• Pipe to GA4 + GTM via the standard PAI analytics.ts pattern
• BDC-side: lead arrives with full session context (pages viewed, who_for, vehicle, UTM)

Kill-Switch Criteria

If any of the following are true after 30 days, kill the overlay and re-design:

• Static /contact/ form submissions drop by more than 25% (cannibalization beyond expected range)
• Overall bounce rate on VDPs increases by more than 8%
• BDC lead-quality score drops more than 15 points
• Any user feedback (call, email, review) mentions the pop-up as intrusive

Debate concluded. Synthesis represents working agreement of all three council members on a buildable v1 with named test variants for v2.