• Skip to main content
  • Skip to navigation
  • Skip to search
    Petunia™
    FeaturesPricingIntegrationsAboutContact
    Log inStart free trialSign up
    Loading
    Petunia™

    Reimagining customer communication for the modern business.

    Product

    • Features
    • Pricing
    • Integrations
    • Roadmap
    • What's New

    Resources

    • Help Center
    • Documentation
    • Guides
    • API Reference
    • Community
    • Support

    Company

    • About Us
    • Careers
    • Blog
    • Press
    • Contact

    © 2026 Gray Group International LLC. All rights reserved.·
    Made by gardenpatch 🌱

    Privacy PolicyTerms of ServiceCookie Policy

    Petunia™ is a trademark of Gray Group International LLC. The Petunia name, brand, product design, and content are proprietary. Unauthorized use, imitation, or copying is prohibited.

    BlogJul 15, 2026

    In this article

    • Define the clock
    • Staff the first mile
    • Copy-paste scripts
    • Metrics worth tracking every week
    • Honest limitations: when a human must take over
    • Implementation checklist
    • Operator FAQ
    • Alert design
    • Proving it with buckets
    • Form and call parity
    In this article
    • Define the clock
    • Staff the first mile
    • Copy-paste scripts
    • Metrics worth tracking every week
    • Honest limitations: when a human must take over
    • Implementation checklist
    • Operator FAQ
    • Alert design
    • Proving it with buckets
    • Form and call parity

    The Five-Minute Rule: Speed-to-Lead for Home Service Dispatch

    Web leads and missed calls decay in minutes. Build a five-minute response standard your CSRs can hit on busy days.

    A web form hits at 10:04 a.m. Nobody calls until 11:40. The homeowner already booked with the company that texted at 10:06.

    Classic speed-to-lead research (including widely cited Lead Response Management studies) shows contact odds collapse as minutes turn into hours. Home-service call tracking vendors echo the same shape. Your standard should be measured in minutes, not "same day."

    Here is how to make five minutes real on a loud dispatch floor.

    Define the clock

    Clock starts at form submit, missed call, or chat handoff. Clock stops at first human or qualified AI contact attempt that can book.

    Staff the first mile

    • Live alert to on-duty CSR
    • Backup alert at minute three
    • AI or SMS bridge if phones are slammed
    • Visible timer on the board

    Copy-paste scripts

    Copy these, then edit bracketed fields so they sound like your shop.

    Web lead SMS

    Hi {Name}, {Company} here. Got your request for {Service}. Reply 1 for a call now or 2 to pick a window.

    CSR opener

    Hi {Name}, this is {Rep} with {Company}. I saw you requested help with {Issue}. Are you looking for today or a scheduled visit?

    Minute-three backup

    Backup: lead {Name} waiting {Minutes}m on {Source}. Claiming now.

    Metrics worth tracking every week

    Fifteen minutes every Monday. Same numbers. Same owners.

    MetricHow to count itTarget
    Median speed-to-leadMinutes to first contactUnder 5
    Contact rateReached / leadsTrend up
    Book rate by speed bucketCompare <5m vs >30mProve the rule
    Abandoned leadsNo attempt / totalNear zero

    Honest limitations: when a human must take over

    Speed without competence just annoys people faster. Scripts and capacity still matter.

    • Do not auto-dial illegally
    • Honor quiet hours
    • Prioritize emergencies over estimate spam
    • Humans for angry VIP leads

    Implementation checklist

    1. Instrument timestamps
    2. Set 5-minute SLA
    3. Create backup alert
    4. Write first-touch scripts
    5. Review slow leads daily
    6. Publish weekly speed histogram

    Operator FAQ

    Is five minutes realistic?

    Yes with alerts and a backup. No if leads sit in email only.

    AI first touch count?

    Yes if it can gather intent and book or schedule a real callback.

    Nights?

    Use after-hours rules; morning batch is not five minutes.

    Petunia is built for fast first touches across voice and SMS. Features · Book.

    Related pages: Missed calls, After-hours, Pricing.

    Alert design

    If nobody hears the lead, the SLA is theater.

    1. Loud alerts

    Loud alerts. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    2. Mobile backup

    Mobile backup. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    3. Escalation at minute three

    Escalation at minute three. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    4. Quiet-hour variants

    Quiet-hour variants. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    5. Spam filters that do not hide real leads

    Spam filters that do not hide real leads. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    Proving it with buckets

    Show book rate by response speed.

    1. Weekly histogram

    Weekly histogram. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    2. Share with marketing

    Share with marketing. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    3. Coach slow CSRs

    Coach slow CSRs. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    4. Celebrate fast books

    Celebrate fast books. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    5. Fix capacity before blaming people

    Fix capacity before blaming people. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    Form and call parity

    Web and phone leads deserve the same clock.

    1. Same SLA

    Same SLA. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    2. Same dispositions

    Same dispositions. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    3. Same scripts family

    Same scripts family. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    4. Same owner

    Same owner. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    5. Same Monday review

    Same Monday review. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

    Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

    Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

    Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

    Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

    Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

    When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

    More from the blog

    • Speed to Lead Benchmarks for HVAC and Plumbing

      Aug 2, 2026

    • AI Receptionist ROI for Home Service Companies

      Aug 2, 2026

    • Missed Call Text-back Scripts That Book Jobs: Text Back

      Aug 2, 2026

    • Confirm Bookings Across Phone, SMS, and Web Without Chaos

      Jul 21, 2026

    • Ask for Reviews Without Feeling Sleazy: Post-Job Timing

      Jul 20, 2026

    Running a home-service shop and tired of missed calls?

    Petunia is your Growth Partner for voice, SMS, social selling, reviews, and booking. See features, pricing, or book a walkthrough.

    More from the blog

    • Speed to Lead Benchmarks for HVAC and Plumbing

      Aug 2, 2026

    • AI Receptionist ROI for Home Service Companies

      Aug 2, 2026

    • Missed Call Text-back Scripts That Book Jobs: Text Back

      Aug 2, 2026

    • Confirm Bookings Across Phone, SMS, and Web Without Chaos

      Jul 21, 2026

    • Ask for Reviews Without Feeling Sleazy: Post-Job Timing

      Jul 20, 2026

    Running a home-service shop and tired of missed calls?

    Petunia is your Growth Partner for voice, SMS, social selling, reviews, and booking. See features, pricing, or book a walkthrough.