The Service Operator
Checklist

Restore One‑Tap Calls in 48 Hours: Sticky “Call Now” + LSA Ramp (with Caps)

Step‑by‑step 48‑hour checklist to restore one‑tap calls: add a sticky mobile Call button, route it through call tracking, and ramp LSAs with Max‑per‑lead caps and a starter weekly budget. Includes copy‑paste HTML, plugin options, exact LSA screen labels, a dispute workflow, and a 10‑minute QA script plus an 80/20 answer‑time SLA.

Use this when mobile calls from Google’s Map Pack dip. In two workdays, you’ll recreate one‑tap calling on your site, cap LSA lead costs, and tighten answer time so more calls turn into booked jobs.

  1. 1

    Day 1 AM — Pick the number and routing you’ll protect

    Confirm your main inbound line [YOUR_MAIN_NUMBER], who it rings (simultaneous vs. round‑robin), and your after‑hours fallback (answering service/IVR). Set an 80/20 answer‑time SLA (answer 80% within 20 seconds) and name an owner for it.

  2. 2

    Add a sticky “Call now” button to every mobile page (code option)

    Paste this at the end of your site’s <body> or in a global HTML block; swap [YOUR_MAIN_NUMBER] for your main line (DNI will replace it later).

    &lt;a class=&quot;call-now&quot; href=&quot;tel:[YOUR_MAIN_NUMBER]&quot; aria-label=&quot;Call now&quot;&gt;Call now&lt;/a&gt;
&lt;style&gt;
  .call-now{position:fixed;bottom:0;left:0;right:0;background:#0D1B2A;color:#B7FF00;text-align:center;padding:14px 16px;font-weight:700;z-index:9999;}
  @media(min-width:768px){.call-now{display:none}}
&lt;/style&gt;
  3. 3

    Or use a plugin (WordPress)

    Install “Call Now Button” or “WP Call Button.” Set: Button label = “Call now,” Phone number = [YOUR_MAIN_NUMBER], Visibility = Mobile only, Position = Bottom fixed. Make sure it doesn’t cover chat widgets or cookie banners.

  4. 4

    Route the button through call tracking (DNI)

    In your call‑tracking tool (e.g., CallRail), create a new tracking number named “Website — Mobile Call Button,” forward it to [YOUR_MAIN_NUMBER], enable call recording, and install the DNI script. Set swap targets to any visible phone number and the tel: link in the sticky button.

  5. 5

    QA the sticky button on iPhone and Android

    On LTE (not office Wi‑Fi), load your homepage and one service page; confirm the bar shows on mobile only. Tap to call; verify the call appears in tracking with the correct source (“Website — Mobile Call Button”) and that the recording plays back.

  6. 6

    Prep or refresh your Local Services Ads (LSA) profile

    If new, start/verify your LSA profile (license, insurance, background checks). If existing, review Service Areas, Job Types, and Business Hours so only the high‑intent work you want is enabled.

  7. 7

    Set bidding to Max per lead with starter caps and a weekly budget

    In LSA: Settings → Budget & Bidding → Bidding mode = [Max per lead]. Set starting caps: HVAC ~$65, Plumbing ~$55, Pest ~$40 (adjust to your market). Set Weekly budget = [Target leads/week] × [Max per lead] (e.g., 10 × $55 = $550).

  8. 8

    Tighten job types and hours to avoid junk

    Enable only urgent, profitable jobs (e.g., “water heater repair,” “AC repair”) and disable vague/low‑value ones. Limit service radius/ZIPs you’ll actually roll; match LSA Business Hours to times you can answer within 20 seconds.

  9. 9

    Turn on recordings/alerts and connect LSA to tracking

    In LSA, enable call recordings and notifications (email/SMS). In your tracking tool, connect the Google LSA integration so LSA calls and recordings flow into one inbox with source tags.

  10. 10

    Stand up a dispute + QA workflow

    Assign one person to review all LSA calls daily, tag junk, and submit disputes within Google’s window (typically 30 days). Create canned reasons (e.g., sales/solicitation, wrong number, outside service area) and block repeat offenders.

  11. 11

    Launch LSAs and watch caps for 72 hours

    Turn your ads on. Check daily: Leads, Cost per lead, and Job Types. If capped too low to spend, raise Max per lead by 10–15%; if CPL or quality drifts up, drop cap 10% and trim ZIPs/job types.

  12. 12

    Install answer‑time monitoring and alerts

    In your phone or tracking system, create an alert when Time to Answer > 20s or calls roll to voicemail. Post a simple scoreboard (Today: calls answered, avg answer time, missed calls) where CSRs see it; escalate if >3 missed calls/day.

  13. 13

    Run the 10‑minute QA call test

    Do 4 fast calls: (1) Tap the sticky site button, (2) Tap the phone icon from your LSA unit, (3) Tap to call from your GBP profile, (4) Let one ring out and return the missed call in <5 minutes. For each: time to human answer, confirm routing, confirm recording saved, confirm the source tag (Website/LSA/GBP) is correct, and note any dead air or IVR loops.

  14. 14

    Week‑1 tune‑ups and guardrails

    If quality is off, narrow ZIPs/hours and remove low‑intent job types; if CPL climbs, lower Max per lead 10% and add a daily dispute block. Keep the sticky bar simple (one button, mobile only) and ensure it never hides navigation or chat.