# Laddr - full content corpus

> Every public Laddr docs article and blog post as one markdown file. Canonical HTML lives at https://useladdr.com. The index with descriptions is at https://useladdr.com/llms.txt.

---

# Switching plans without losing data

Source: https://useladdr.com/docs/billing/switching-plans
Category: Billing
Last updated: Apr 12, 2026

> Upgrades happen mid-month, downgrades take effect next cycle. Either way, your phone numbers, knowledge, cadences, and call history stay where they are.

## What's kept across plan changes

Switching plans never deletes data. Specifically, all of these survive any plan change:

- Phone numbers (LARA)
- Call history and transcripts
- Pulse knowledge sources, sessions, and chunks
- Boost cadences, review requests, and reviews
- Team members, roles, and notification settings
- Any integrations you've connected (your calendar, Slack, and others)

<Callout tone="info" title="Limits, not data">
Downgrading might cap how much new data you can add (e.g. fewer phone numbers), but Laddr never deletes existing records to fit you into the new plan.
</Callout>

## Upgrade

1. Open /organization/billing.
2. Click Change plan → pick the higher tier.
3. Confirm. The upgrade is immediate; new features unlock on the spot.
4. Stripe charges a prorated amount for the rest of the billing period.

## Downgrade

Downgrades take effect at the next renewal: you keep paid features until then so you don't lose access mid-cycle.

1. Open /organization/billing.
2. Click Change plan → pick the lower tier.
3. Confirm. You'll see the date the change takes effect.
4. Cancel the scheduled change anytime before that date if you change your mind.

<Callout tone="warn" title="Heads up on phone numbers">
If your new plan allows fewer phone numbers, Laddr asks you which to keep before the downgrade lands. The unselected numbers stay reachable through your renewal date, then release on the next billing cycle.
</Callout>

## Hitting plan limits

Every plan includes monthly allowances. For example, **1,500 LARA call minutes**, **5,000 Pulse chat sessions**, **5,000 Boost review sends**, and **25 to 100 knowledge sources** depending on plan. See the [pricing page](/pricing) for the full matrix.

- **At 80%:** Laddr shows an amber banner on `/organization/billing` and records an internal audit event so our team can reach out if you need headroom.
- **At 100%:** New usage that would exceed the cap is paused until you upgrade or the next billing period starts. **Calls already in progress are not cut off.** Existing transcripts, knowledge sources, and review history stay put.
- **Pulse widget:** When session limits are hit, visitors see a short message to contact the business directly (HTTP 429).
- **Upgrade path:** Switch plans from `/organization/billing`; proration follows the rules in the sections above.

## Annual to monthly (and back)

- Monthly → Annual: discount applies immediately, prorated against your monthly charge.
- Annual → Monthly: takes effect at the end of your annual term, no refunds for unused months.
- Annual term refunds: only within 14 days of the original purchase, and only if no usage credit has been consumed.

<Callout tone="success" title="Stuck mid-change">
If your plan change does not show up right away, refresh the page and check again in a minute or two. If it still has not updated after 5 minutes, contact support and we will fix it for you.
</Callout>

---

# Track your usage and plan limits

Source: https://useladdr.com/docs/billing/usage-and-limits
Category: Billing
Last updated: Jun 9, 2026

> Where to see how much of your plan you've used this month, what each meter measures, and what happens when you get close to the cap.

Every plan comes with a monthly allowance. You can see exactly where you stand at any time, and Laddr warns you before you run out rather than cutting you off by surprise.

## Where to check usage

Open Organization → Billing. Alongside your plan and invoices you'll find usage meters: each one shows what you've used this billing period against what your plan includes. They reset at the start of each cycle.

## What each meter measures

Depending on your products, you'll see meters for:

- **LARA call minutes**: total minutes of calls this month. LARA and Bundle plans include **1,500 minutes**.
- **Pulse chat sessions**: distinct visitor conversations. Pulse and Bundle plans include **5,000 sessions**.
- **Boost review sends**: review requests sent. Boost and Bundle plans include **5,000 sends**.
- **Knowledge sources**: websites, documents, and manual answers Pulse draws from. Pulse includes **25**; the Bundle includes **100**.
- **Team seats**: people on your account. Single-product plans include **1**; the Bundle includes **10**.

Custom plans run on the allowances in your contract rather than these defaults.

## At 80%: a heads-up

When a meter crosses 80%, Laddr shows an amber banner on Organization → Billing and flags it internally so we can reach out if you're trending toward a cap. Nothing changes about how the product works: it's just a warning so you can decide whether to upgrade.

## At 100%: a soft stop

When you hit a cap, new usage that would go over it pauses until the next cycle or until you upgrade. The stop is deliberately gentle:

- **Calls already in progress are never cut off.**
- When Pulse hits its session cap, new visitors see a short note to contact you directly instead of getting a broken widget.
- **Nothing is deleted.** Your transcripts, knowledge, reviews, and history all stay exactly where they are.

<Callout tone="info" title="Limits cap new usage, never your data">
Hitting a cap only slows down adding more this month. Everything you've already built stays in place, and it all comes back the moment the next cycle starts or you move up a plan.
</Callout>

## Need more headroom

If you're regularly near a cap, the fix is a bigger plan. Upgrades take effect immediately and the new allowance applies right away, see [Switching plans without losing data](/docs/billing/switching-plans) for how proration works.

<Callout tone="success" title="No surprises">
Between the 80% banner and the soft stop at 100%, you'll always know before a limit affects a customer. Check Organization → Billing whenever you want the current numbers.
</Callout>

---

# Build a 3-message review request cadence

Source: https://useladdr.com/docs/boost/build-cadence
Category: Boost
Last updated: Apr 28, 2026

> The shape of the cadence matters more than the words. Three sends, the right intervals, and a way out for the customers who aren't going to leave one anyway.

## The shape we recommend

The math: a 3-touch cadence converts at roughly 2.5x a single send for our customer base. Stop at one and you leave money on the table; push to four and you start hurting the relationship.

1. Send 1: SMS, 2 hours after job complete. The customer still feels the relief.
2. Send 2: Email, next morning. Different channel, different format, different inbox.
3. Send 3: SMS, 3 days later. Soft nudge, a one-liner with the same link.

## Message 1: same-day SMS

Short, warm, named. The customer should be able to read it, smile, and tap the link in 8 seconds.

```text
Hey {{first_name}}, {{tech_name}} here from Acme Plumbing. 
If today went smoothly, would you mind dropping us a quick review? 
It genuinely helps a small shop like ours.

{{review_link}}

- Acme
```

## Message 2: next-day email

Use email for the customers who don't open texts but live in their inbox. Keep it short: long emails feel like marketing.

```text
Subject: Quick favor, {{first_name}}

Hey {{first_name}},

Thanks again for trusting Acme with the {{job_short}} yesterday. 
If we earned it, a 30-second review on Google means the world for a small shop. 
Here's the direct link, no login, no form: {{review_link}}

If we missed something, hit reply instead and I'll fix it.

- Max
Acme Plumbing
```

## Message 3: 3-day SMS

Last touch. One line. No ask for forgiveness. Same link.

```text
Hey {{first_name}}, Max here. Just one more nudge if you have 30 seconds: {{review_link}}. Truly appreciated either way.
```

<Callout tone="warn" title="Don't four-touch">
We've tested 4- and 5-touch cadences. Beyond touch 3, conversion barely moves and unsubscribe rate climbs. Stop at three.
</Callout>

## Channels and connecting platforms

Open Boost → Settings → Channels and connect at least SMS + email. Then connect the platforms you actually want reviews on:

- Google Business Profile: first priority for almost everyone.
- Facebook Page: second priority for B2C shops.
- BBB / Angi: only if it actually drives leads in your market.

## Personalization that works

Use first name, tech name, and short job description. Skip dollar amounts, skip job IDs. Boost merges these from your CRM connection, so make sure the names sync.

<Callout tone="success" title="Ship it">
Open /boost/cadences → New cadence, paste the three templates above, set the timing, and turn it on. Watch the first 50 jobs go through and tweak from real conversion data.
</Callout>

---

# Personalize review requests with merge variables

Source: https://useladdr.com/docs/boost/personalize-messages
Category: Boost
Last updated: Jun 9, 2026

> A review request that uses the customer's name and your business name gets answered. Here's how to set up the message and the sender.

A review request that reads like a form letter gets ignored. One that opens with the customer's first name and names the job you just did for them feels like it came from a person. Boost lets you write the personal version once and send it to everyone.

## Where the message lives

Open Boost → Cadences and pick a cadence, then open the step you want to edit. Each step has its own message, so a three-step cadence can open warm, follow up gently, and close with a direct ask.

## Use merge variables

Inside a step's message you can drop in merge variables that fill in per recipient when the message sends: the customer's name, your business name, and the tracked review link. Write the sentence once with the variable in place and every send comes out personalized.

- Lead with the customer's first name so it reads as one-to-one.
- Name your business so it's obvious who's asking.
- Use the review link variable rather than pasting a raw URL, so clicks stay tracked. See [Tracked redirects](/docs/boost/tracked-redirects).

<Callout tone="info" title="Keep it short">
The best-performing requests are two or three sentences: thank them, ask for the review, give them the link. Long messages lower response rates. The variables do the warmth; you don't need paragraphs.
</Callout>

## Set your sender identity

Open Boost → Settings to set the name and email your requests come from, plus the reply-to address. Send as a real person at your business, not a no-reply: customers are far more likely to open and respond when the sender looks human and replies go somewhere a person reads.

## Test before you send

Send a test of the cadence to yourself (test sends go to an owner or admin) and read it the way a customer would. Check that every variable filled in correctly, the link works, and the tone sounds like you. Fix it in the step editor and test again until it's right.

<Callout tone="success" title="Personal at scale">
Once the message and sender are dialed in, every customer gets a note that feels handwritten, and you wrote it exactly once.
</Callout>

---

# Tracked redirect URLs for review requests

Source: https://useladdr.com/docs/boost/tracked-redirects
Category: Boost
Last updated: Apr 22, 2026

> Send the customer to one short link and let Boost route them: to Google, Facebook, or a private feedback form depending on rating intent.

## What a tracked redirect is

A tracked redirect is a short Laddr URL like useladdr.com/r/abc123 that customers tap from your review-request message. Behind the scenes, Boost asks for an intent rating, then sends the customer to the right destination: public review platform if they're happy, private feedback form if they're not.

## Create one

1. Open /boost/sources and add at least one review destination by pasting its review link (your Google Business Profile review URL is the usual first one).
2. Open /boost → Tracked redirects → New.
3. Set the destination platforms in priority order (Google, then Facebook).
4. Pick a slug, keep it short. `/r/acme` or `/r/{{job_id}}` both work.

```json
{
  "slug": "acme",
  "intentPrompt": "How was your visit today?",
  "destinations": {
    "high": ["google", "facebook"],
    "low": "private-feedback"
  },
  "threshold": 4
}
```

## Routing logic

Each tap on the link follows the same flow:

1. Customer taps useladdr.com/r/acme.
2. Boost shows a tiny intent screen: "How did we do?" with a 1-5 picker.
3. If they pick 4 or 5, Boost redirects to your highest-priority public platform with a write-review link.
4. If they pick 1-3, Boost shows a private feedback form. The submission goes to your inbox, never the public listing.

## Use it in cadences

Replace `{{review_link}}` in any cadence template with the tracked redirect. Boost auto-substitutes the right URL per customer.

```text
Hey {{first_name}}, quick favor: {{review_link}}

// Renders as: useladdr.com/r/acme?j=84219
```

## What's allowed

<Callout tone="warn" title="Don't gate Google reviews">
Google's policy says you can't redirect only positive reviewers to Google while diverting negative ones elsewhere. Boost defaults to compliant: every customer can leave a public review on any platform you've connected. The tracked redirect's job is to surface the platform they're most likely to use, not to gatekeep.
</Callout>

If you want stricter compliance, set the threshold to 1: every customer goes straight to the public picker, no intent screen. Conversion drops about 15%, but you sleep better.

<Callout tone="success" title="Done">
Your tracked redirect is live. Watch /boost/reviews over the next 14 days: taps, intent ratings, and where customers actually completed the review all surface there.
</Callout>

---

# Get Laddr live in 30 minutes

Source: https://useladdr.com/docs/getting-started/30-minute-setup
Category: Getting started
Last updated: May 1, 2026

> The fastest path from sign-up to a working AI front desk. Phone connected, knowledge loaded, widget embedded, first review request sent.

## What you'll have at the end

- A LARA phone number that takes after-hours and overflow calls.
- Pulse answering visitor questions on your website 24/7.
- An automated 3-message review-request cadence for completed jobs.
- All of it captured in one shared inbox you can assign and follow up from.

<Callout tone="info" title="Stay in this tab">
Each step opens a deeper guide in a new tab if you want detail. The 30-minute path stays here. Don't worry about perfection: you'll tune everything in the first 30 days.
</Callout>

## Step 1: Connect a phone (5 min)

1. Open Settings → LARA → Phone numbers.
2. Click Add number → Buy a new number, pick an area code that matches your service region.
3. Place a test call from your cell. LARA answers: you're live.

Already have a number you want LARA on? See port-existing or conditional-forwarding instead.

## Step 2: Add knowledge (10 min)

1. Open /knowledge → Add source → Website.
2. Paste your homepage URL. Pulse auto-discovers your sitemap and crawls the right pages.
3. While that's running (~3 minutes for most sites), upload your top-3 PDFs: pricing sheet, service-area map, common-FAQ doc.
4. Mark any critical pages as Priority: Pulse weighs them more in retrieval.

## Step 3: Embed Pulse (5 min)

1. Open /pulse/install. Copy your snippet (it includes your tenant ID).
2. Paste it just before `</body>` in your site's footer template.
3. Refresh your homepage. The Pulse launcher appears bottom-right within 2 seconds.

```html
<script async
  src="https://cdn.useladdr.com/pulse.js"
  data-tenant="YOUR_TENANT_ID"></script>
```

## Step 4: Turn on review requests (10 min)

1. Open /boost/sources → New source, then paste your Google Business Profile review link. Boost sends customers to that URL; there is no account to authorize yet.
2. Open /boost/cadences → New cadence → pick the "Standard 3-touch" template.
3. Edit the `{{tech_name}}` and `{{business_name}}` merge fields if needed.
4. Connect your CRM (or, if you don't have one yet, you can mark jobs complete manually).

<Callout tone="success" title="Done, you're live">
From the next missed call, the next visitor question, and the next completed job, Laddr is doing the work. Watch /overview for the next 48 hours and let real activity show you where to tune.
</Callout>

## What to do next week

- Read your first 20 LARA transcripts. Tune the system prompt where you see drift.
- Read 20 Pulse sessions. Add a Manual Q&A for any low-confidence answer.
- Watch /boost/reviews: review-request open rates and conversion show within 5 to 7 days.

---

# Invite your team and set roles

Source: https://useladdr.com/docs/getting-started/invite-your-team
Category: Getting started
Last updated: Jun 9, 2026

> Add the people who run your business with you, give them the right level of access, and know exactly who can change what.

Most accounts are run by more than one person: an owner who pays the bill, a manager who tunes LARA and reads calls, a front-desk lead who works the inbox. Laddr has three roles so each of them gets exactly the access they need and nothing they don't.

## The three roles

- **Owner**: full control, including billing and deleting the organization. There is always at least one owner. Owners can invite anyone, including other owners.
- **Admin**: runs the product day to day: phone numbers, knowledge, cadences, integrations, team. Admins can invite admins and members, but not owners.
- **Member**: works inside Laddr (inbox, leads, contacts, calls) but can't change org settings, add Pulse domains, or touch billing. Member surfaces that they can't edit show up read-only rather than hidden, so they still see what's configured.

## Who can invite

Inviting is limited to owners and admins. A member who opens the team page sees the roster but no invite button. If a member tries to invite someone through the API, it's rejected.

## Send an invite

1. Open Organization → Team.
2. Click Invite teammate.
3. Enter their work email and pick a role.
4. Send. They get an email with a link that's good for 7 days.

Until they accept, the invite shows as pending on the team page. You can resend or revoke it from there.

<Callout tone="info" title="Invites expire after 7 days">
If someone doesn't accept in time, the link stops working. Resend it from Organization → Team and they get a fresh 7-day window.
</Callout>

## Manage people already on the team

From Organization → Team you can change anyone's role or remove them. Changing a role takes effect immediately, the next time they load a page. Removing someone revokes their access right away.

<Callout tone="warn" title="Seats depend on your plan">
Single-product plans (LARA, Pulse, or Boost on their own) include one seat. The Bundle includes ten. If you hit your seat limit when inviting, you'll need the Bundle or a custom plan. See [Track your usage and plan limits](/docs/billing/usage-and-limits).
</Callout>

---

# Find your way around Laddr

Source: https://useladdr.com/docs/getting-started/navigate-laddr
Category: Getting started
Last updated: Jun 9, 2026

> A quick tour of the sidebar so you know where calls, chats, reviews, and settings live before you go looking for them.

Everything in Laddr hangs off the left sidebar. It's grouped so each product has its own section, and the work that flows out of all of them (leads, contacts, the inbox) sits up top in Main.

## Start with Overview

Overview is your home screen: the headline numbers for the day and a feed of what just happened across LARA, Pulse, and Boost. When you sign in and want a pulse check, start here.

## The Main group

Main is the shared workspace, not tied to any one product:

- **Inbox**: every conversation in one place.
- **Leads** and **Rescue**: new opportunities, with Rescue surfacing the ones that need a fast human touch.
- **Contacts**: your people, with tags and history.
- **Appointments** and **Scheduling**: what's booked and the rules behind it.
- **Knowledge**: the answers LARA and Pulse draw from.
- **Activity**: a running log of changes.

## The product groups

Each product has its own section so its dashboard, settings, and history stay together:

- **Pulse**: the website chat widget: Install, Configure, Coverage, and Sessions.
- **LARA**: the phone agent: Phone Numbers, Calls, Usage, and Settings.
- **Boost**: review requests: Requests, Cadences, Reviews, and Sources.

You'll only see the groups for products on your plan.

## The Organization group

This is where account-level setup lives: Team, Integrations, Tags, Settings, Billing, Notifications, and the Weekly digest. Most of it is owner and admin territory.

<Callout tone="info" title="Begin at Setup">
Organization → Setup is a checklist of the steps every new account works through. If you're not sure what to do next, open it: it tells you what's done and what's still waiting on you.
</Callout>

---

# Connect Outlook Calendar to LARA

Source: https://useladdr.com/docs/integrations/connect-outlook-calendar
Category: Integrations
Last updated: Jun 9, 2026

> Give LARA your Microsoft 365 calendar so it can see when you're free and book jobs straight onto it during a call.

LARA can only book a job if it knows when you're open. Connect your Microsoft 365 (Outlook) calendar and LARA reads your availability live and writes confirmed bookings right onto it, so the schedule a caller hears is the real one.

## What LARA does with your calendar

- **Reads availability** so it only offers times you're actually free.
- **Writes the booking** as an event on your calendar when a caller confirms, so it's on your schedule the second the call ends.

## Before you start

- A **Microsoft 365 / Outlook** calendar.
- A **LARA** or **Bundle** plan: calendar booking is part of LARA.
- Owner or admin access in Laddr to connect integrations.

## Connect Outlook Calendar

1. Open Organization → Integrations.
2. Find Microsoft / Outlook Calendar and click Connect.
3. Sign in to Microsoft and approve the calendar access Laddr requests.
4. You're returned to Laddr with the calendar showing as connected.

It's a one-click authorization through Microsoft: no keys to copy.

<Callout tone="info" title="Keep your calendar honest">
LARA trusts your calendar to decide what's free. Block out the time you don't want booked (drive time, lunch, personal appointments) so callers are never offered a slot you can't actually take.
</Callout>

## Disconnect

Open Organization → Integrations, find Microsoft / Outlook Calendar, and disconnect. LARA stops reading and writing to your calendar immediately.

<Callout tone="info" title="On Google Calendar?">
Google Calendar is not connectable yet. It is listed in **Organization → Integrations** as coming soon, and it turns on once Google finishes reviewing our app. Until then, LARA books on Microsoft 365 / Outlook.
</Callout>

---

# Connect Slack

Source: https://useladdr.com/docs/integrations/connect-slack
Category: Integrations
Last updated: Jun 15, 2026

> Push LARA, Pulse, and Boost business alerts into a Slack channel your team already watches.

If your team lives in Slack, that's where new business should show up. Connect Slack once and Laddr posts alerts from **LARA**, **Pulse**, and **Boost** into the channel you choose — no dashboard babysitting.

## What the connection does

Once connected, Laddr posts to your chosen Slack channel when:

- **LARA** books or requests an appointment, or captures a lead from a phone call
- **Pulse** captures a lead from your website chat widget
- **Boost** syncs a new customer review into your inbox

Your team reacts in the place they're already paying attention to.

## Before you start

- A Slack workspace where you can authorize an app.
- An active **LARA**, **Pulse**, **Boost**, or **Bundle** plan.
- Owner or admin access in Laddr to connect integrations.

## Connect Slack

1. Open **Organization → Integrations**.
2. Find **Slack** and click **Connect**.
3. Slack asks you to authorize Laddr and choose the channel to post to. Approve it.
4. You're returned to Laddr with Slack showing as **Connected**.

It's a one-click authorization: there are no keys or webhooks to paste.

<Callout tone="info" title="Pick a channel people read">
Post to a channel your team actually watches during business hours, like a shared "leads" or "ops" channel. An alert nobody sees isn't much better than no notification at all.
</Callout>

## What you'll see in Slack

Example alert shapes (wording varies by event):

- `LARA booked: HVAC tune-up on Tuesday at 2:00 PM.`
- `LARA captured a lead from Jane Doe: needs same-day service.`
- `Pulse captured a lead from a website visitor: asking about pricing.`
- `Boost: 5★ review from Alex — Great work`

## Disconnect

To stop the posts, open **Organization → Integrations**, find Slack, and **Disconnect**. Laddr drops the connection and stops sending to your channel right away.

<Callout tone="success" title="Live where your team is">
With Slack connected, LARA bookings, Pulse chat leads, and new Boost reviews are one glance away for the whole team.
</Callout>

---

# ServiceTitan integration (coming soon)

Source: https://useladdr.com/docs/integrations/servicetitan
Category: Integrations
Last updated: Jun 9, 2026

> ServiceTitan support is on the way. Here's what it will do when it lands and how to get set up the moment it's ready.

<Callout tone="info" title="Not live yet">
The ServiceTitan integration is in development, not available to connect today. It shows as "Coming soon" on your Integrations page. This article describes what it will do so you can plan for it. We'll update it with the full setup steps when it ships.
</Callout>

## What it will do

When ServiceTitan support lands, it will connect LARA to your ServiceTitan account so the phone agent works against your real customer and job data:

- **Look up callers.** When someone calls, LARA can recognize an existing ServiceTitan customer instead of treating every call as new.
- **Book jobs.** LARA can create a job in ServiceTitan from a booking it takes on a call, so it lands in the system your team already runs on.

The exact set of synced fields and directions will be documented here when the integration is released.

## What you'll need

- A **LARA** or **Bundle** plan. The ServiceTitan connection is part of LARA.
- A ServiceTitan account with an admin who can authorize the connection.

## How setup will work

ServiceTitan is an **assisted** connection: rather than a one-click button, our team will help you wire it up correctly the first time, since field-service data mapping is worth getting right. When it's available, you'll start from Organization → Integrations, and we'll take it from there with you.

<Callout tone="success" title="Want it sooner?">
If ServiceTitan is a must-have for your shop, tell us. We prioritize connectors by how many customers are waiting on them, so letting support know moves it up the list.
</Callout>

## In the meantime

LARA works fully without ServiceTitan. You can connect your calendar so LARA books against real availability ([Outlook Calendar](/docs/integrations/connect-outlook-calendar)) and push LARA, Pulse, and Boost business alerts to your team in [Slack](/docs/integrations/connect-slack) today.

---

# Configure after-hours rules and on-call rotation

Source: https://useladdr.com/docs/lara/after-hours
Category: LARA
Last updated: Apr 26, 2026

> Decide what LARA does when the office is closed: triage, schedule, transfer to on-call, or take a message. Set it once and stop second-guessing the night shift.

Most home-service shops lose more revenue to nights and weekends than to busy signals. After-hours rules let LARA triage urgency, schedule low-priority jobs for morning, and only wake your on-call tech for the calls that warrant it.

## What counts as after-hours

By default, after-hours is everything outside the business hours you set. You can also flag certain weekday hours (lunch, training) as after-hours without redefining your full schedule.

## Set your business hours

1. Open Settings → LARA → Business hours.
2. Pick your time zone first: every rule is evaluated against this.
3. Set open and close times per weekday. Use the copy-day shortcut for typical 8-to-5 schedules.
4. Mark Saturdays/Sundays as open if you cover weekends. Otherwise leave them closed.

<Callout tone="info" title="Multiple service regions">
If you operate across time zones, set hours per region under Settings → LARA → Regions. LARA evaluates the caller's number against the region map and uses the matching schedule.
</Callout>

## Pick the after-hours rule

There are four rule shapes. You can compose them, for example, triage urgent + schedule the rest.

1. Triage urgent: LARA asks 2 to 3 qualifying questions. If urgency keywords hit, transfer to on-call. Otherwise, schedule.
2. Schedule for morning: LARA offers the next-day morning window and books it. No transfer.
3. Transfer to on-call: every after-hours call rings the on-call tech directly.
4. Take a message: LARA captures name, number, and reason, then sends a notification.

## On-call rotation

If a rule transfers, LARA uses the rotation to decide who to ring.

1. Open Settings → LARA → On-call rotation.
2. Add team members with their personal cell numbers.
3. Set the rotation cadence: daily handoff at 6pm is the most common.
4. Add a fallback (usually the owner) for the case where the on-call tech doesn't pick up after 3 rings.

```json
// Rotation example: weekly Mon to Fri
{
  "cadence": "weekly",
  "handoffAt": "06:00",
  "members": [
    { "id": "u_01", "phone": "+17165550101" },
    { "id": "u_02", "phone": "+17165550102" }
  ],
  "fallback": { "id": "u_owner", "phone": "+17165550100" }
}
```

## Holidays and exceptions

Add date-range exceptions for holidays, training days, or full-shop closures. LARA falls back to the after-hours rule for the entire range, regardless of weekday.

<Callout tone="warn" title="Watch the time zone">
Holiday ranges are evaluated in the region's time zone, not the caller's. If you cover Eastern + Central, set the holiday once per region or accept that the boundary shifts by an hour.
</Callout>

## Test it

Use Settings → LARA → Simulate to send a test call as if the clock were 10pm. Verify the rule fires, the transfer reaches the right cell, and the call shows up tagged as after-hours in /lara/calls.

<Callout tone="success" title="Done">
Your after-hours rule is live. Revisit it after the first 30 days. Most shops adjust the urgency threshold once they see what LARA actually transfers.
</Callout>

---

# Conditional call forwarding from your carrier

Source: https://useladdr.com/docs/lara/conditional-forwarding
Category: LARA
Last updated: Apr 22, 2026

> Send only the calls your team didn't pick up to LARA. Your real number stays the one customers see. LARA just catches the drops.

## Why conditional forwarding

Conditional forwarding sends calls to LARA only when (a) you don't answer after N rings, (b) your line is busy, or (c) the phone is unreachable. Your team still answers everything they pick up. LARA only sees the drops.

<Callout tone="info" title="Beats unconditional">
Don't use Call Forwarding (Always). It routes everything to LARA and your team never gets a chance to pick up. Always pick conditional or No-Answer forwarding.
</Callout>

## Get your LARA number

1. Open Settings → LARA → Phone numbers.
2. Buy a fresh number you'll forward to. Pick any area code: the number stays hidden from callers.
3. Copy the number. You'll need it for the carrier codes below.

## Carrier-specific codes

Each carrier uses a slightly different dial code. The pattern is consistent: a star or pound prefix, the LARA number, and a confirmation tone.

```text
Verizon Wireless
  No-answer forward:  *71<LARA-NUMBER>
  Cancel:             *73

AT&T Wireless
  No-answer forward:  *61*<LARA-NUMBER>#
  Cancel:             ##61#

T-Mobile
  No-answer forward:  **61*<LARA-NUMBER>**30#  (30 = ring time in seconds)
  Cancel:             ##61#

Most VoIP / business lines
  Configure in your provider's web admin under "Call Routing" → "No Answer".
```

<Callout tone="warn" title="Ring count matters">
Set the ring count to 4 (≈20 seconds). Less than that and your team won't have time to grab the phone. More than that and callers hang up before LARA gets the call.
</Callout>

## Test the forward

1. From a different phone, call your real business number.
2. Let it ring 5+ times without picking up.
3. LARA should answer. If it doesn't, the forwarding rule didn't take.
4. Check /lara/calls: the call should appear with the original caller's number, not LARA's.

## Troubleshooting

- Carrier doesn't honor the code: call your carrier's business support; some prepaid plans block forwarding entirely.
- Calls forward immediately: you set unconditional forwarding by mistake. Cancel and re-set with the no-answer code.
- Caller ID shows your own number: LARA is configured correctly; the carrier is rewriting CLI. Switch your LARA number's CLI mode to "original caller" in Settings → LARA → Phone numbers.

---

# Connect your first phone number to LARA

Source: https://useladdr.com/docs/lara/connect-phone-number
Category: LARA
Last updated: Jun 9, 2026

> Use a fresh Laddr number, port your existing one, or forward your current line. Here's how each path works and how to pick.

<Callout tone="info" title="We set this up with you">
Connecting a number is part of LARA setup, and we handle the provisioning side with you rather than leaving you to wire up a carrier alone. You decide which of the three approaches below fits, and we get the number live. Until it's provisioned, your LARA dashboard shows a setup-in-progress panel.
</Callout>

## Before you start

Decide whether you want LARA on a brand-new number, your existing main line, or as a fallback when your team can't pick up. Most businesses start with option 3 (forward) so nothing changes for callers, then graduate to option 1 or 2 once they trust LARA.

You'll need one of:

- Your business address and service region, for a fresh number, or
- A US or Canadian phone line you own, to port, or
- Forwarding access on your current carrier, to forward.

## Three ways to connect

Each option has trade-offs. Pick the one that matches your risk tolerance:

1. A fresh Laddr number: quickest, lowest risk. LARA owns the number outright, nothing on your existing line changes.
2. Port your existing number: keeps your printed marketing intact. Takes 5 to 10 business days.
3. Forward to LARA: zero changes for callers. LARA only picks up when you don't.

## Option 1: A fresh Laddr number

Best for new locations or trying LARA without touching your main line. Tell us the area code you want (we recommend matching your service region) and we provision the number on your account. Once it's live, it shows up under LARA → Phone Numbers and starts taking calls.

## Option 2: Port your existing number

Keeps your printed marketing intact. Porting takes 5 to 10 business days because your current carrier has to release the number.

<Callout tone="warn" title="Don't cancel first">
Do NOT cancel service with your current carrier before the port completes. If they release the number first, it goes back to the pool and you may lose it permanently.
</Callout>

## Option 3: Forward to LARA

Use your carrier's conditional forwarding to send calls to LARA only when your team doesn't pick up after a few rings. Your real number stays your number: callers never see LARA's. See [Conditional forwarding](/docs/lara/conditional-forwarding) for the carrier-by-carrier setup.

## Test the connection

Once your number is connected, place a test call from your personal phone:

1. Dial your LARA number.
2. LARA should answer in 1 to 2 rings with your greeting.
3. Ask a question your business knows the answer to.
4. Hang up and open LARA → Calls. The test call should appear within a minute, with a transcript.

<Callout tone="success" title="Looking good">
If the test call shows up with a transcript, you're done. From here, every missed call becomes a tracked, transcribed, follow-up-ready opportunity. See [Review your call transcripts](/docs/lara/review-calls).
</Callout>

## Troubleshooting

If LARA isn't picking up:

- Open LARA → Phone Numbers: the number's status pill should be green.
- If you're forwarding, confirm your carrier's forwarding rule is active. Not all carriers honor conditional forwarding.
- Re-run the test call after a minute. Routing can take a moment to settle.
- Still stuck? Contact support and we'll check the provisioning from our side.

---

# Port an existing phone number to LARA

Source: https://useladdr.com/docs/lara/port-number
Category: LARA
Last updated: Apr 14, 2026

> Move your existing main line to Laddr without breaking your printed marketing. Plan for 5 to 10 business days and a few easily-avoided pitfalls.

## Should you port

Port if your existing number is on every truck, every business card, and every Google listing. Don't port if you're testing LARA: buy a fresh number for that, then port later when you're ready to commit.

<Callout tone="warn" title="One-way move">
Porting back to your old carrier is possible but slow. Treat the port as a deliberate move, not an experiment.
</Callout>

## Before you submit

Gather these from your current carrier. Laddr can't pull them for you:

- Account number with current carrier
- Account PIN (some carriers call this the transfer PIN)
- The exact business name and service address on file with that carrier
- A current bill (PDF, less than 30 days old)

<Callout tone="warn" title="Match exactly">
Carrier port departments reject mismatched names by default. If your carrier has the address as "100 Main St" but Laddr has "100 Main Street," the port fails and resets the clock. Match the carrier's records exactly, even if it looks wrong.
</Callout>

## Submit the port

1. Open Settings → LARA → Phone numbers → Add number → Port existing.
2. Enter the number, account info, and upload the recent bill.
3. Pick a target port date: Laddr defaults to 7 business days out.
4. Submit. You'll get a confirmation email and a status pill in the dashboard.

## During the port window

- Don't cancel service with your old carrier. They'll release the number prematurely.
- Don't change the address or business name on either side.
- If the carrier disputes, you'll get an email with the reason and what to fix.

<Callout tone="info" title="Cutover is brief">
Most ports complete in a 30-minute window during business hours on the target date. Expect a few minutes of "call goes to voicemail" while DNS propagates. Schedule the cutover on a day you'll be at the desk.
</Callout>

## After it lands

1. Place a test call. The number now rings LARA (or your conditional forward, if configured).
2. Verify your old carrier closed the line: log in and confirm the account is closed.
3. Update Google Business Profile if you changed phone display preferences.
4. Send a one-time announcement to your customer list. Most don't notice, but a heads-up reduces "is this still you" calls.

---

# Review your call transcripts

Source: https://useladdr.com/docs/lara/review-calls
Category: LARA
Last updated: Jun 9, 2026

> Every call LARA takes is logged, transcribed, and tied to a contact. Here's how to read them and turn a missed call into a follow-up.

The point of LARA isn't just answering the phone, it's that nothing said on the phone disappears. Every call is recorded, transcribed, and filed against a contact, so you can pick up exactly where the caller left off.

## Where calls live

Open LARA → Calls. You get a list of every call, inbound and outbound, with the caller, the time, the length, and the result. Click any row to open the full call.

## Read a single call

The call detail page is the whole conversation in one view:

- **Transcript**: the full back-and-forth, so you can see precisely what was asked and what LARA said.
- **Caller**: matched to an existing contact when there is one, or captured as a new one.
- **Result**: what came out of the call: a booking, a qualified lead, a question answered.
- **Linked records**: the lead or contact the call belongs to, so you can jump straight into follow-up.

## Turn it into a follow-up

When a call needs a human, you've got everything you need to respond well: the transcript tells you what they want, and the linked contact gives you their details. No "let me pull up your account": you already have it.

<Callout tone="info" title="Read the misses, not just the wins">
The most useful calls to review are the ones where LARA wasn't sure. Reading those tells you what to add to your knowledge or fix in the [system prompt](/docs/lara/system-prompt) so the next caller gets a clean answer.
</Callout>

## Search and filter

As call volume grows, use the filters on LARA → Calls to narrow by date or result, or search by caller, instead of scrolling. It's the fastest way to find a specific conversation or pull every call that turned into a booking last week.

## Flag or remove a recording

From a call's detail page you can flag a call for follow-up or delete a recording you don't want to keep. Deleting removes the recording; the rest of the call record stays so your history and counts stay intact.

<Callout tone="success" title="Every call is an asset">
Once you're in the habit of skimming LARA → Calls, the phone stops being a black hole. Every missed call becomes a tracked, transcribed, follow-up-ready opportunity.
</Callout>

---

# Write a system prompt LARA actually follows

Source: https://useladdr.com/docs/lara/system-prompt
Category: LARA
Last updated: Apr 18, 2026

> The difference between a generic AI receptionist and one that books your jobs is the system prompt. Here's the structure that holds up across thousands of calls.

Most teams write their first system prompt as a mood: "be friendly, be professional, book the call." That works for the first 50 calls, then drifts. The prompts that hold up are structured: identity, guardrails, playbook, and tone, in that order.

## Anatomy of a good prompt

1. Identity: who LARA is, who they work for, what they're not allowed to claim to be.
2. Guardrails: pricing, scope, policy. The non-negotiables.
3. Playbook: the qualifying questions and the order to ask them.
4. Tone: voice and pacing. Last because the model defaults to neutral if absent.

## Identity and voice

Be specific. "You are the front desk at Acme Plumbing" beats "You are a helpful assistant" by a wide margin. Give the business name, the service area, and the operating hours.

<Callout tone="warn" title="Don't claim to be human">
If a caller asks if they're talking to a person, LARA must say no. Most states require this disclosure. Add it to the prompt explicitly: "If asked whether you are a person, say you are an AI assistant for [business]."
</Callout>

## Guardrails

Guardrails are the rules LARA must follow even when a caller pushes. Common ones:

- Never quote a price. Always say a tech will provide an estimate on-site.
- Don't book outside service area: list ZIP codes covered.
- Don't promise emergency response if not staffed.
- Don't take payment over the phone.

## Service-call playbook

Order matters. The most common LARA failure mode is asking for the appointment time before confirming the address is in service area. Order: scope → service area → urgency → schedule → contact info.

```text
1. Greet, identify business.
2. "What can we help you with today?" (capture scope).
3. "What ZIP code is the property in?" (confirm service area).
4. "Is this a leak/no-heat/etc that needs same-day, or are you flexible?" (urgency).
5. Offer 2 windows. Book the one they pick.
6. Confirm name, callback number, and address.
7. Read the booking back and end the call.
```

## Full example

```text
You are the front desk at Acme Plumbing in Buffalo, NY. You answer the phone for callers who couldn't reach a human.

IDENTITY
- Acme Plumbing has been serving Erie County since 1998.
- Service area: ZIP codes 14201-14228, 14260, 14261.
- Hours: 7am-6pm M-F. After-hours emergency line for no-water and gas leaks.
- If asked whether you are a person, say you are an AI assistant for Acme.

GUARDRAILS
- Never quote a price.
- Don't book outside service area. Politely refer them to call back during hours for a referral.
- Don't promise emergency response unless caller is in service area AND issue is no-water, no-heat (winter), or gas leak.

PLAYBOOK
1. Greet, identify yourself as Acme.
2. Capture scope: leak, no-hot-water, install, drain, other.
3. Confirm service area by ZIP.
4. Assess urgency: same-day vs flexible.
5. Offer two windows. Book one.
6. Read back name, callback number, address.

TONE
- Warm, brisk, never chatty. Owners pay for time saved.
- Mirror the caller's energy. Calm callers: calm voice. Stressed callers: direct, reassuring.
```

## Tune from real calls

Read the first 20 transcripts in /lara/calls. Look for: callers asking the same off-script question (add it to guardrails), LARA hesitating on a routine question (clarify the playbook), or LARA over-explaining (tighten the tone).

<Callout tone="success" title="Iterate weekly">
The best LARA prompts get edited weekly for the first month. After that, monthly is enough. Save versions: Settings → LARA → Prompt history shows the diff and call performance per version.
</Callout>

---

# Control which sites can load Pulse

Source: https://useladdr.com/docs/pulse/allowed-domains
Category: Pulse
Last updated: Jun 9, 2026

> Pulse only runs on domains you've approved. Here's how the allow-list works and how to add your sites to it.

Your Pulse snippet carries your tenant ID, which means anyone who copies it could try to run your widget on their own site. The allow-list is the guardrail: Pulse only answers on domains you've explicitly approved.

## Why the allow-list exists

The widget loads from a public script, so the snippet itself can't be a secret. Instead of trusting the snippet, Pulse checks the domain the request comes from against your approved list on every call. An approved domain gets answers; anything else gets turned away. That keeps your knowledge, your session quota, and your branding tied to your sites.

## Add an allowed domain

1. Open Pulse → Install.
2. Find the domain allow-list.
3. Add the exact domain Pulse should run on (for example, `yourbusiness.com`).
4. Save. The widget starts answering on that domain right away.

Add each site you run separately if you have more than one.

<Callout tone="warn" title="Owners and admins only">
Adding a domain is restricted to owners and admins. Members can see the embed snippet and the current list, but the add control is hidden for them, and the server rejects the change if it's attempted anyway. If you can't add a domain, ask an owner or admin on your team. See [Invite your team and set roles](/docs/getting-started/invite-your-team).
</Callout>

## What happens on other domains

If the widget is loaded from a domain that isn't on your list, Pulse refuses to answer there. So even if your snippet ends up on someone else's page, it won't serve your knowledge or burn your session quota.

<Callout tone="info" title="Widget loaded but silent?">
The most common cause is a domain that isn't approved, often a `www` vs. bare-domain mismatch or a staging URL. Confirm the exact host you're testing on is in the allow-list under Pulse → Install.
</Callout>

---

# Capture leads from Pulse chats

Source: https://useladdr.com/docs/pulse/capture-leads
Category: Pulse
Last updated: Jun 9, 2026

> Every chat is a potential customer. Here's how Pulse turns a website conversation into a lead you can follow up on.

Answering questions is half of what Pulse does. The other half is catching the visitor's details before they leave, so a late-night chat becomes a lead waiting for you in the morning.

## How a chat becomes a lead

When a visitor shares their name and email in the widget, Pulse creates a lead and attaches the whole conversation to it. You don't wire anything up: capture is built into the widget. The visitor keeps chatting; you get the contact.

## Where leads land

New leads show up in Leads (the Main group in your sidebar). Open one and you get the full picture: who they are, how they reached you, and the chat that produced them. Leads that need a quick human response surface in Rescue so they don't sit.

## Read the session behind a lead

Every captured lead links back to its chat. Open Pulse → Sessions to read the full transcript: the questions asked, what Pulse answered, and where the visitor left off. That context tells you what the person actually wants before you reply.

<Callout tone="info" title="The transcript is your script">
Skim the session before you follow up. If they asked about weekend availability, lead with weekend availability. You already know what they came for.
</Callout>

## Follow up fast

Speed is the whole game with inbound leads. Work them straight from the Leads list: the contact details and the conversation are already there, so you can reply with context instead of starting cold.

<Callout tone="success" title="Nothing slips">
With capture on, a question you'd have missed at 11pm is a named lead with a transcript by the time you're at your desk. That's the difference between a chat widget and a salesperson.
</Callout>

---

# Pulse confidence threshold tuning

Source: https://useladdr.com/docs/pulse/confidence
Category: Pulse
Last updated: Apr 18, 2026

> When Pulse isn't sure, it should hand off, not guess. The confidence threshold decides where that line sits. Here's how to set it without over- or under-handing-off.

## What confidence is

Every Pulse answer comes with a confidence score between 0 and 1. The score blends retrieval similarity (how close the source matched the question) with answer coherence (how much of the answer is grounded in the source). Below the threshold, Pulse hands off: to a lead form, a callback request, or a transfer to LARA.

## The default threshold

The default is 0.62. We landed on it after looking at thousands of sessions. It hands off about 8 to 12% of questions for a typical home-services site.

<Callout tone="info" title="Don't push it too high">
Tempting move: "only answer when you're really sure." The result is Pulse handing off 30%+ and visitors bouncing. Confident-sounding wrong answers are rare; over-handoff is common.
</Callout>

## How to tune it

Tune from data, not vibes. Open /pulse/sessions and filter by Confidence < 0.7. Read 20 of them and answer two questions:

1. Of the answers Pulse gave at 0.5 to 0.7, how many would you have wanted handed off?
2. Of the handoffs Pulse triggered at 0.4 to 0.6, were they real questions worth a human, or just visitors typing nonsense?

If most 0.5 to 0.7 answers were fine, lower the threshold to 0.55. If a chunk of them were misleading, raise to 0.7.

## Pick the right fallback

What Pulse does below the threshold matters more than the threshold itself. Three options:

- Lead form: "I'm not 100% sure on that one. Want a tech to call you back? Drop your number." Best for service inquiries.
- Live transfer to LARA: opens a voice call straight from the chat. Best for urgent questions during business hours.
- FAQ deflect: Pulse offers the 3 most-related FAQ links. Best for high-volume info questions.

## Monitor the rate

Track two metrics in /pulse: handoff rate and answered-with-confidence rate. Healthy ranges:

- Handoff rate: 8 to 15%. Below 5% suggests Pulse is over-confident; above 20% suggests under-served knowledge.
- Answered-with-confidence rate: 75%+. Lower than that, add knowledge sources before tweaking the threshold.

<Callout tone="success" title="Threshold isn't the first lever">
If your handoff rate is high, the fix is usually "add the missing FAQ to the knowledge source," not "lower the threshold." Threshold tuning is for the last 10%: the questions you can't answer in writing.
</Callout>

---

# Customize how the Pulse widget looks and greets visitors

Source: https://useladdr.com/docs/pulse/customize-widget
Category: Pulse
Last updated: Jun 9, 2026

> Match the widget to your brand and set the first thing it says, so it feels like part of your site instead of a bolt-on.

The default Pulse widget works the moment you install it, but a minute of styling makes it feel native to your site. Appearance lives in one place and updates everywhere without touching the snippet.

## Where appearance lives

Open Pulse → Configure. You set the widget's name, accent color, and greeting here. Changes apply to the live widget after they save: you don't re-paste the embed snippet or redeploy your site.

## Name and color

- **Name** is what shows in the widget header. Use your business name or a friendly persona, whatever matches how you talk to customers.
- **Accent color** drives the launcher button and the header. Set it to your brand color so the widget reads as yours.

## The opening message

The greeting is the first line a visitor sees when they open the widget. Keep it short and specific to what you do: "Ask us about scheduling, pricing, or service areas" beats a generic "How can I help?" because it tells people the widget actually knows your business.

<Callout tone="info" title="Write the greeting like a prompt">
A greeting that names the topics you answer well nudges visitors toward questions your knowledge sources can handle. That means cleaner answers and fewer dead ends. Revisit it after you've read a week of sessions.
</Callout>

## Decide where it appears

By default Pulse loads on every page that has the snippet. To hide it on pages where a chat bubble gets in the way (checkout, careers, a landing page), open Pulse → Configure → Page rules and add a path pattern with the action Hide. Full snippet and install detail is in [Embed the Pulse widget](/docs/pulse/embed-widget).

## Preview before you ship

Open your site in a fresh tab and confirm the launcher shows your name, your color, and your greeting. If it still looks like the default, hard-refresh: your browser may be holding an old copy of the widget assets.

<Callout tone="success" title="Looks like you">
Once the widget carries your name and color, visitors treat it as part of your site instead of a third-party pop-up, and they're far more likely to actually ask a question.
</Callout>

---

# Embed the Pulse widget on your website

Source: https://useladdr.com/docs/pulse/embed-widget
Category: Pulse
Last updated: Apr 30, 2026

> One snippet on your footer template gets Pulse on every page. Visitors can ask anything 24/7. Pulse answers from your knowledge or captures the lead.

Pulse ships as a single async script. Drop it once in the footer of your site template and every page picks it up: no per-page wiring.

## Get your snippet

1. Open Pulse → Install.
2. Add your domain (or domains, if you have multiple sites).
3. Copy the snippet. It includes your tenant ID, so don't share it across customers.

```html
<!-- Laddr Pulse - paste before </body> -->
<script async
  src="https://cdn.useladdr.com/pulse.js"
  data-tenant="YOUR_TENANT_ID"></script>
```

## Install on your site

Add the snippet immediately before the closing `</body>` tag in your site template. The async attribute ensures it never blocks page rendering.

<Callout tone="info" title="Once is enough">
Don't paste the snippet on every page. Put it in the global template (footer.html, _layout.tsx, theme footer, etc.) so it loads everywhere automatically.
</Callout>

## Platform-specific install

- WordPress: Appearance → Theme File Editor → footer.php (or use the Insert Headers and Footers plugin).
- Squarespace: Settings → Advanced → Code Injection → Footer.
- Wix: Settings → Custom Code → Add Custom Code → Body, end.
- Webflow: Project Settings → Custom Code → Footer Code.
- Shopify: Online Store → Themes → Edit code → theme.liquid → just before `</body>`.
- Next.js / React: paste in your root layout.tsx or _app.tsx.

```tsx
// Next.js App Router - app/layout.tsx
import Script from 'next/script'

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Script
          async
          src="https://cdn.useladdr.com/pulse.js"
          data-tenant="YOUR_TENANT_ID"
        />
      </body>
    </html>
  )
}
```

## Verify the install

1. Open your site in a fresh browser tab.
2. The Pulse launcher should appear bottom-right within 2 seconds.
3. Click it, ask any question. The first message also tells the dashboard you're live.
4. Open Pulse → Install. The install status should flip to "Live" with a green pill.

## Configure on/off pages

By default Pulse appears on every page. To hide it on specific pages (cart, checkout, careers), open Pulse → Configure → Page rules and add a path pattern with the action "Hide."

<Callout tone="success" title="Live">
Pulse is now answering visitor questions 24/7. From here, your weekly job is reading sessions in /pulse/sessions and tightening the knowledge sources for any question that didn't get a clean answer.
</Callout>

---

# Add a website as a Pulse knowledge source

Source: https://useladdr.com/docs/pulse/knowledge-sources
Category: Pulse
Last updated: Apr 24, 2026

> Crawl your own site once, and Pulse answers visitor questions from the pages you already wrote. Refresh on a schedule so the bot stays in sync with what's actually published.

## Source types

Pulse pulls from four kinds of source. Mix and match: most shops use website + a few PDFs.

- Website: crawled on a schedule, respects robots.txt and sitemaps.
- PDF / DOCX upload: manuals, warranties, internal SOPs.
- Manual entry: quick Q&A pairs you write directly.
- URL list: a flat list of pages to fetch (great for help-center articles).

## Add a website

1. Open /knowledge.
2. Click Add source → Website.
3. Paste the root URL (e.g. https://acmeplumbing.com).
4. Pulse auto-discovers your sitemap.xml. If you don't have one, it crawls links from the homepage.

<Callout tone="info" title="Sitemap helps">
If your site has /sitemap.xml, Pulse uses it directly: faster, more complete, and respects your priority hints. If you don't have one, generating one is a 10-minute SEO win.
</Callout>

## Scope the crawl

Limit what Pulse indexes so visitor answers stay focused:

- Include patterns: /services/*, /faq/*, /pricing. Only crawl pages that match.
- Exclude patterns: /admin/*, /careers/*, /tag/*. Skip noisy or private sections.
- Max depth: 3. Avoid crawling pagination tails on blogs.

```yaml
include:
  - /services/*
  - /service-area/*
  - /faq/*
exclude:
  - /admin/*
  - /careers/*
  - /blog/tag/*
maxDepth: 3
```

## Refresh schedule

Pick a refresh cadence based on how often the site actually changes:

- Daily: high-traffic sites with constant updates.
- Weekly: most service shops. The default.
- Manual: set-it-and-forget-it pages, or you trigger from a CMS webhook.

## Review what was indexed

1. Open /knowledge → click your source.
2. The page list shows everything indexed with last-fetched timestamps.
3. Click any page to see the chunks Pulse extracted.
4. If a page is missing important content, mark it Priority. Pulse weighs it more in retrieval.

<Callout tone="success" title="Pro tip">
After your first 50 Pulse sessions, scan /pulse/sessions for low-confidence answers. Most of them point to a page that exists on your site but wasn't worded the way visitors asked. Add a Manual Q&A entry and the next person gets a clean answer.
</Callout>

---

# Why the Most Valuable Home-Service Calls Often Happen After Hours

Source: https://useladdr.com/blog/most-valuable-home-service-calls-after-hours
Category: Operations
Author: Max Svejda
Published: May 4, 2026

> High-intent HVAC, plumbing, and electrical demand does not stop at closing time. The urgent, expensive, low-patience calls often arrive when the office is dark.

A homeowner rarely discovers the real problem at a convenient time. The basement starts taking on water after dinner. The furnace quits when the temperature drops overnight. The outlet smells hot on a Sunday. The panel starts buzzing when everyone is finally home.

That is why after-hours coverage is not just a convenience feature for HVAC, plumbing, and electrical shops. It is a demand-capture system for some of the highest-intent calls a local service business will ever receive.

<Callout tone="info" label="The practical claim">
The best-supported argument is not that most emergencies happen at night. It is that many valuable, urgent, low-patience calls happen when the office is closed.
</Callout>

## The Bottom Line

Public evidence supports the core thesis: high-intent home-service demand keeps moving after 5 p.m. Housecall Pro reports that 41% of jobs booked online come in after hours, with real activity even between 1 a.m. and 4 a.m. Scorpion found that 56% of homeowners want 24/7 scheduling or a way to communicate after hours.

Plumbing shows the holiday version of the same pattern. ServiceTitan says call volume spikes around Thanksgiving, and Roto-Rooter has long described the day after Thanksgiving as its busiest day. Weather sharpens HVAC demand too: heat waves, cold snaps, and deferred maintenance can turn comfort complaints into urgent calls.

> After-hours calls are valuable because they pair high urgency with low patience and, often, larger service tickets.

There is an important caveat. Official U.S. agencies publish strong safety guidance for gas leaks, carbon monoxide, sewage exposure, heat, cold, electrical warning signs, fatigue, and working alone. They do not publish one national, regulator-grade dataset that breaks homeowner HVAC, plumbing, and electrical contacts down by hour. Exact timing percentages should be treated as directional unless they come from your own call logs.

## When Homeowners Reach Out

The most convincing framing is not just that people call at night. It is that problems become undeniable when people are home, when guests are in the house, when weather is extreme, or when a system fails outside office hours.

That makes early mornings, evenings, weekends, and holidays matter disproportionately. The homeowner is either noticing the problem in real time or finally has enough context to act on it. A slow drain becomes a holiday kitchen crisis. A weak furnace becomes a no-heat call. A flicker becomes a safety question when it is paired with heat, odor, or repeated breaker trips.

The operational takeaway is simple: your call log should be split by hour and day. If you only measure total missed calls, you will miss the difference between a Tuesday vendor call and a Saturday night burst-pipe opportunity.

## What the Caller Is Really Asking

In HVAC, the caller is often asking whether the home is still habitable. No heat during dangerous cold, no cooling during dangerous heat, gas odor, or carbon-monoxide alarm symptoms are not ordinary scheduling issues. They are safety and escalation issues first.

In plumbing, the first job is usually containment. Is water actively flowing? Can the main valve be shut off safely? Is sewage backing up? Is there standing water near electrical equipment? The customer wants the damage stopped before they care about the final diagnosis.

In electrical, the caller is often asking whether the house is safe to occupy. Burning smells, active sparking, hot outlets or panels, repeated breaker trips, tingling shocks, and damaged wires all need a more careful path than standard next-available booking.

<Callout tone="warn" label="Do not diagnose by phone">
A good after-hours flow identifies risk and routes the call. It should not pretend to inspect the home, clear a hazard, or replace emergency services.
</Callout>

A practical urgency model has three lanes: life-safety escalation now, urgent on-call review, and next-business-day booking. The trick is asking enough to choose the right lane without trapping the customer in a long interrogation.

## Why These Calls Are Worth More

Emergency trade calls can be expensive even before replacement work enters the picture. Public homeowner price guides put many urgent HVAC repairs in the hundreds and some component repairs above $1,000. Plumbing has an even wider spread because emergency work can involve trip fees, premium hourly rates, burst pipes, sewer backups, remediation, excavation, and restoration.

Electrical urgent work also skews above routine jobs when panels, breakers, hot outlets, repeated faults, or immediate service are involved. Even when the final repair is modest, the intent is valuable because the homeowner is not browsing casually. They want the problem assessed and made safe.

The safest revenue statement is this: after-hours urgent tickets are often worth high hundreds of dollars when contained, and can move into low or mid four figures when access, parts, contamination, water damage, sewer work, panel work, or major HVAC components are involved.

<Figure caption="After-hours demand is less about the clock and more about urgency, safety, and low patience." gradient="from-rose-700 via-slate-900 to-teal-700" />

## What Happens When Nobody Answers

Voicemail is not much of an after-hours strategy. CallRail has reported that 78% of surveyed consumers have abandoned a business after an unanswered call. Moneypenny found that many callers who reach voicemail do not leave a message. Scorpion's homeowner research says many homeowners decide on a provider quickly and often choose the first company that responds.

That matters because a missed after-hours call is not always recoverable in the morning. A callback from an unfamiliar number has to compete against the contractor who answered last night, booked the job, or at least gave the homeowner a credible next step.

> When someone with a flooded basement, a dead furnace, or a hot breaker panel hears voicemail, they do not become patient. They become available to the next company that answers.

The cost is not only lost revenue. It is also wasted acquisition spend. If the call came from paid search, local services ads, SEO, or a review-driven search result, the shop already paid to create the opportunity. No-answer turns that investment into a handoff.

## What Good After-Hours Triage Sounds Like

After-hours intake should start with risk, not calendar availability. Ask what is happening now, whether anyone is in danger, whether there is smoke, gas odor, sewage, sparking, standing water, or a CO alarm, and whether the customer can shut off water or power safely.

Then ask about vulnerable occupants and operating constraints: infants, older adults, medically vulnerable people, no secondary bathroom, no alternate heat, no alternate cooling, or loss of power to critical home functions. These details help an on-call tech or dispatcher distinguish inconvenience from immediate risk.

1. Life-safety escalation now: gas smell, CO alarm or symptoms, smoke, active sparking, hot panel, downed or damaged wires, flooding near energized equipment, severe sewage exposure, or unsafe temperatures for vulnerable occupants.
2. Urgent on-call review: burst pipe after the water is shut off, sewer backup, no heat in freezing conditions, no cooling during dangerous heat with vulnerable occupants, repeated breaker trips, or loss of power to critical home functions.
3. Next-business-day booking: isolated fixture issues, one dead outlet, no hot water without leakage or health risk, and comfort complaints that are frustrating but not unsafe.

The service promise should be bounded. Say, "I am flagging this for immediate on-call review," or "an on-call technician will review the severity and contact you as soon as possible." Do not promise guaranteed emergency service tonight unless your staffing, geography, weather exposure, and technician availability can actually support that promise.

<Callout tone="warn" label="Worker safety matters too">
On-call work creates fatigue and lone-worker risk. A responsible after-hours system routes urgent calls without turning every nervous customer into an unsafe dispatch.
</Callout>

## The Coverage Math Owners Should Run

The cleanest payback formula is simple: required booked jobs to justify after-hours coverage = monthly after-hours coverage cost divided by average gross profit per urgent job. If evening and weekend coverage costs $2,000 per month and the average gross profit per urgent job is $400, five extra booked jobs cover the program.

You can also model leakage. If 25 after-hours callers hit no answer in a month and a large share abandon after unanswered calls, the opportunity loss can easily exceed the cost of basic coverage before you even count wasted ad spend. If 20 urgent callers reach voicemail and most do not leave a message, those callers disappear before your team can try to recover them.

Do not use public averages as final truth. Pull your own 90-day call log, classify after-hours contacts by trade and urgency, separate spam and existing-customer noise, track which calls booked, and compare recovered gross profit against the cost of coverage.

The goal is not to promise everything to everyone. The goal is to answer, assess, route urgent work safely, and give real demand a credible path before the homeowner starts calling the next shop.

## Sources Used

- Housecall Pro: after-hours online booking benchmarks and homeowner scheduling behavior.
- Scorpion: homeowner response expectations, fast decision windows, and preference for 24/7 scheduling or after-hours communication.
- ServiceTitan and Roto-Rooter: Thanksgiving and holiday-adjacent plumbing demand patterns.
- CallRail, Moneypenny, and MIT/InsideSales: unanswered-call abandonment, voicemail behavior, and speed-to-lead context.
- Angi, Thumbtack, and This Old House: homeowner-facing HVAC, plumbing, and electrical urgent-service price ranges.
- CDC, CPSC, EPA, ESFI, NFPA, OSHA, and NIOSH: safety guidance for heat, cold, gas, carbon monoxide, sewage, electrical warning signs, fatigue, and working alone.

---

# RAG for Contractors: Why Freshness, Guardrails, and Citations Matter

Source: https://useladdr.com/blog/rag-for-contractors-freshness-guardrails-citations
Category: Technical
Author: Colin Lawless
Published: May 4, 2026

> A safe website chatbot for trades businesses is not a generic model trained on a site. It is a domain-locked retrieval system that answers from current business evidence and knows when not to answer.

A generic website chatbot can sound confident while being wrong about the exact thing a contractor cannot afford to get wrong: current business truth.

For trades businesses, the risky facts are operational and time-sensitive. Service areas change. Hours change. Emergency coverage changes. Promotions expire. Financing terms update. Dispatch policies vary by location. A model that sounds helpful but guesses on those facts is not a product advantage. It is a liability with a friendly voice.

<Callout tone="info" label="The practical takeaway">
Pulse should not be framed as a chatbot trained on your business. It should be a retrieval system that only answers from your current business evidence.
</Callout>

## The Bottom Line

The safe architecture is not loose training in the consumer sense. It is a production retrieval system that continuously ingests the business's current website, PDFs, FAQs, and approved internal notes; tags that content with metadata like tenant, location, effective dates, and document status; retrieves only relevant evidence at runtime; reranks it; and generates an answer grounded in those retrieved sources.

That is the difference between a demo and an operating system. The chatbot should be domain-locked, tenant-isolated, freshness-aware, citation-backed, and explicitly allowed to say it does not know when the business has not published the answer.

> On a trades website, correctness comes from source selection, freshness, and guardrails more than from model eloquence.

The practical split is simple: use RAG for changing textual knowledge, structured tools for live operational facts, and fine-tuning only for behavior, tone, extraction, or tool-use reliability after evals prove it is worth the extra complexity.

## The Core Architecture

A good website-copilot architecture has seven stages: source discovery, ingestion, normalization, chunking, retrieval, reranking, and constrained generation. The knowledge base stays outside the model. Retrieval becomes a first-class system. Evaluation decides when extra complexity is justified.

The ingest layer should crawl the canonical site, sitemap pages, landing pages, service pages, FAQ sections, policy pages, financing pages, and downloadable PDFs. It should also support approved non-web sources such as office policy notes, dispatch scripts, or exported documents.

Chunking should be structure-aware, not just character-count based. On a trades site, that usually means heading-bounded chunks for service pages, question-answer chunks for FAQs, and paragraph-or-table-row chunks for pricing or policy documents, with parent-document context restored when the answer is synthesized.

Retrieval should be hybrid by default. Dense semantic retrieval catches paraphrase. Keyword retrieval catches exact-match intent like ZIP codes, discount codes, model numbers, brand names, service names, and policy terminology. Contractor visitors mix both modes constantly.

Reranking should sit between first-stage retrieval and generation. Retrieve a larger candidate set, rerank it, then pass the best evidence to the model. That keeps the answer grounded without dumping the whole website into context.

<Callout tone="info" label="Generation rule">
Hours, pricing, service areas, discounts, warranties, policy terms, and emergency procedures should only be stated when present in retrieved business sources.
</Callout>

## How to Model Business Knowledge

Different source types need different handling. Website HTML should be stripped of chrome, navigation, cookie text, and duplicate footer content. Service pages should preserve headings. FAQ pages should preserve question-answer pairing. Policy pages should preserve section boundaries and effective-date language.

PDF handling matters more than people expect. Financing sheets, warranty PDFs, permit checklists, seasonal price books, and safety instructions often contain the actual business truth. Those documents should be parsed into a layout-aware representation so tables, lists, and headings survive ingestion.

Each source should become a versioned document object with chunk-level metadata. At minimum, that metadata should include tenant, source type, canonical URL or file ID, document title, service category, document status, source revision, published date, effective date, expiration date, crawl time, host domain, geography, and whether the content is emergency-approved.

For local contractors, local-search metadata is not just SEO exhaust. Service areas, business hours, location pages, and structured business details are operational truth. They should be normalized into the same evidence system rather than left as disconnected frontend decorations.

1. Public content: service pages, FAQs, location pages, pricing pages, warranties, and published emergency policy.
2. Customer-visible private content: approved office notes, dispatch scripts, and policy clarifications safe to quote to prospects.
3. Internal-only content: escalation instructions, employee phone trees, sales notes, and other material the public chatbot should never retrieve.

## Freshness, Versioning, and Tenant Isolation

Freshness is a correctness property. Hours, promotions, service areas, and emergency coverage may change quickly. Evergreen pages may change slowly. A crawler should support hot, warm, and cold freshness classes instead of one universal recrawl interval.

Versioning should be immutable. Every crawl or upload should create a new source revision, every chunk should point back to that revision, and the live index should switch through an active-version pointer rather than in-place mutation. That makes rollback possible when a crawl goes bad, a PDF parser misreads a table, or draft pricing accidentally publishes.

Tenant isolation must be hard, not advisory. A multi-business chatbot should use one namespace, shard, or equivalent hard partition per business, with every write and query scoped to that business. If Pulse is embedded on a contractor's domain, the request should already carry the resolved tenant and allowed hostnames before retrieval begins.

Domain-locked deployment is the application-layer companion to tenant isolation. The widget should be host-bound, the backend should map host to tenant, and the retriever should refuse to search outside that tenant unless an explicitly allowed cross-tenant corpus exists.

<Figure caption="Safe RAG for trades websites starts with tenant boundaries, current sources, and source-backed generation." gradient="from-emerald-700 via-slate-900 to-sky-700" />

## Failure Modes and Guardrails

The biggest failure mode is not a weird answer about trivia. It is a plausible business fact the company never authorized: stale hours, wrong service area, unsupported capability claim, hallucinated discount, invented financing offer, or improvised emergency advice.

Stale hours and service-area errors are freshness and filtering bugs, not model-style bugs. The fix is to tag documents with effective dates and geography, retrieve with date and region filters, and bias toward current sources. A bot should not say yes to a ZIP code unless it retrieved tenant-scoped geography evidence.

Unsupported claims happen when the model is rewarded for helpfulness more than faithfulness. The generator needs hard invariants: do not invent prices, discounts, warranties, license status, availability windows, or financing terms; cite each such claim; and if evidence is absent, say so and offer escalation.

Emergency advice needs its own guardrail tier. A trades chatbot should not improvise safety instructions from general world knowledge. It should quote an approved emergency policy, route to the business's authorized emergency flow, or escalate when the situation appears dangerous or outside the published guidance.

<Callout tone="warn" label="No evidence, no answer">
A polished but unsupported answer is worse than a clear no-answer fallback. The product should be rewarded for knowing when not to answer.
</Callout>

## How to Evaluate It

Evaluation should be built around contractor website risks, not generic chatbot vibes. Every business should have a golden set of expert-verified questions before launch, and that set should keep growing from production failures.

The dataset should include answerable questions, deliberately unanswerable questions, ambiguous questions, stale-content traps, policy exceptions, multi-page reasoning, and high-risk prompts about emergencies, prices, and service areas.

Retrieval and generation should be scored separately. On retrieval, measure hit rate, recall at k, MRR, context relevance, and citation coverage. On answers, measure faithfulness, relevance, correctness, and guideline adherence.

No-answer behavior needs its own tests. A contractor chatbot that refuses to answer an unsupported pricing or emergency question is doing better than one that fabricates a confident answer. Abstention quality is part of product quality.

After launch, human review loops should stay in the system. Low-confidence and high-risk traces should go into an annotation queue. False positives and false refusals should be reviewed weekly and promoted into the golden set before changing prompts, models, chunking, or retrieval settings.

## RAG, Tools, and Fine-Tuning

RAG is the right source-of-truth mechanism for changing business knowledge: service descriptions, hours pages, service-area pages, pricing sheets, financing PDFs, FAQs, warranties, and customer-visible policies.

Fine-tuning is a behavior tool, not a live-knowledge database. It can help with tone, refusal style, citation style, extraction behavior, dispatch-summary formatting, or tool selection. It should not be used to memorize current emergency dispatch fees or service-area rules.

Structured tools should handle live operational state: scheduling availability, dispatch status, customer-specific entitlements, finance pre-qualification, coupon eligibility, and exact ZIP coverage. If the answer must come from an authoritative live system, it should not come from text search.

The best production system uses all three, but for different jobs: RAG for current business knowledge, tools for live state and actions, and optional fine-tuning for consistency once evaluation proves the basic stack is strong.

## Sources Used

- OpenAI: retrieval, file search, citations, prompt guidance, function calling, model optimization, and eval-driven development.
- Anthropic: contextual retrieval, reranking, agent guardrails, and evaluation-driven tool design.
- LangChain, LangSmith, and LlamaIndex: retrieval architecture, chunking, evaluation, human review, and knowledge-base design.
- Pinecone, Weaviate, Elastic, Qdrant, Chroma, BEIR, and pgvector: hybrid retrieval, namespaces, multitenancy, reranking, chunking, and filtered vector-search behavior.
- Google Business Profile and LocalBusiness documentation: service areas, hours, local business details, and structured operational facts.

---

# Why Home-Service Websites Don't Convert

Source: https://useladdr.com/blog/why-home-service-websites-dont-convert
Category: Growth
Author: Colin Lawless
Published: May 4, 2026

> Contractor websites do not mainly lose leads because traffic is bad. They lose leads because homeowners still have basic, high-intent questions when they are ready to call or book.

A lot of home-service websites have the same quiet problem. They attract high-intent local visitors, then make those visitors keep guessing.

The homeowner wants to know whether you serve their address, whether you are open or available now, what problem you solve, roughly what it may cost, and whether you are trustworthy enough to invite into the home. The website answers with a hero headline, a phone button, three stock-ish service cards, and a form.

<Callout tone="info" label="The practical takeaway">
Contractor websites do not mainly lose leads because homeowners dislike websites. They lose leads because homeowners still have unanswered questions when they are ready to act.
</Callout>

## The Bottom Line

The strongest through-line in the research is simple: conversion depends on practical confidence. Homeowners need availability, fit, price context, trust, and a low-friction next step. When those answers are missing, slow to find, or inconsistent across the site and local listings, trust drops and leads leak away.

BrightLocal's local consumer research found that contact information and opening hours are among the most important things people look for when researching a local business. It also found that many consumers would avoid a business if they found incorrect information online. Google's business-profile guidance points in the same direction: complete, accurate details help users and search systems match a business to local intent.

> Your website is often the last trust check before the call. It is not just a brochure.

For HVAC, plumbing, and electrical shops, this matters even more because the category sits close to right-now intent. A visitor with no cooling, a sewer backup, or a hot breaker panel is not reading in browse mode. They are trying to decide whether your company is the safe next step.

## Where Contractor Websites Lose Leads

The first leak is thin service pages. A generic AC repair or emergency plumber page with one paragraph and a call button may technically exist, but it often fails the usefulness test for search and the reassurance test for homeowners. If the page does not explain symptoms, next steps, service area, emergency policy, pricing context, and what happens after the call, the highest-intent visitor still has homework to do.

The second leak is unclear service area and business facts. Google says local results are shaped by relevance, distance, and prominence, and it tells businesses to keep phone numbers, hours, and service-area details complete and accurate. If your site says you serve the metro, your profile says something else, and edge-city coverage is vague, both ranking confidence and customer confidence suffer.

The third leak is no pricing guidance at all. Homeowners do not necessarily need a binding price list, but they do need enough to judge fit: diagnostic fee, emergency surcharge, what drives cost, whether financing exists, whether estimates are written, and what warranty language usually applies.

The fourth leak is weak emergency information. For trades categories, can you help now is a conversion question. Vague language like call anytime without actual hours, dispatch coverage, after-hours policy, or area restrictions forces the visitor to gamble.

The fifth leak is poor mobile UX and slow pages. Google has reported that mobile bounce probability rises sharply as load time grows, and that many users leave pages that take more than a few seconds to load. On a contractor site, a slow page means the visitor may never reach the FAQ, financing explanation, emergency policy, or booking form.

The sixth leak is slow response. A site can capture a form and still lose the job if nobody responds while the homeowner is still in decision mode. Live chat and AI chat only help when they answer quickly, accurately, and pass context cleanly to the person who can book or dispatch.

## What Homeowners Need Answered Before They Call

At the broadest level, homeowners want five answers before they contact a contractor: Are you available? Are you the right fit? What might this cost? Can I trust you? What is the next step?

Trust is not abstract in home services. The FTC advises consumers to verify licensing and insurance, check complaints, and research reputation before hiring a contractor. BrightLocal's review research shows tradespeople are one of the categories where reviews matter most. A contractor site has to answer not only can you do the job, but should I trust you with my home.

Price confidence is nuanced. Consumers often need a bounded answer, not a fixed quote: diagnostic fee or no fee, what changes the price, whether emergency service costs extra, whether financing exists, whether estimates are written, and what a warranty covers.

<Callout tone="info" label="Channel reality">
Phone still matters for urgent and advice-heavy situations. The better model is phone plus fast digital answers plus human escalation, not replacing the phone number with a widget.
</Callout>

## The Questions Change by Trade

### HVAC

HVAC visitors want to know whether the system should be repaired or replaced, what the rough cost range will be, what changes the price, whether financing is available, whether same-day or emergency service costs more, and whether the contractor will size the system correctly instead of guessing. ACCA's consumer guidance around Manual J load calculation is a good example of the kind of trust-building detail serious HVAC buyers care about.

### Plumbing

Plumbing visitors skew toward urgency, damage control, and money clarity. Is this a real emergency? Do you charge extra at night or on weekends? Will you give upfront pricing or a detailed breakdown? Are you licensed and insured? Do you warranty the work? Do you offer financing for unexpected repairs?

### Electrical

Electrical visitors are especially trust-heavy because the category carries obvious safety risk. They want to know whether you are licensed and insured, whether permits are required, whether you handle permits, whether written estimates are available, whether warranties apply, whether emergency service is real, and whether their panel, wiring, or home may need code-related work.

<Figure caption="The best contractor pages are built around the questions homeowners ask before they feel safe enough to call." gradient="from-indigo-700 via-slate-900 to-emerald-700" />

## What a Website Chatbot Needs to Know

A chatbot is only useful if it has grounded answers. A marketing-only FAQ library is not enough. Zendesk has reported that customers would use a knowledge base if it met their needs, and Microsoft guidance on reducing hallucinations emphasizes curated data, topic organization, recency metadata, source reliability, chunking, and explicit escalation behavior.

For a home-service chatbot, the knowledge base should start with business facts: canonical phone numbers, business hours, holiday hours, office address if applicable, service areas, emergency coverage, booking methods, financing availability, warranty summaries, and escalation contacts.

Then it needs service answers: one source page per service and subservice, written around homeowner questions. Include common symptoms, what the service includes, exclusions, diagnostic-fee rules, likely next steps, repair-versus-replace heuristics, and permit-related notes.

Pricing guidance should be governed. Not every number has to be exact, but ranges, starting points, emergency surcharges, financing options, and cost drivers should carry effective dates, owners, and last-reviewed timestamps so the assistant does not repeat stale information.

1. Business facts: phone, hours, service area, coverage rules, financing, warranties, and escalation contacts.
2. Service answers: symptoms, inclusions, exclusions, next steps, diagnostic rules, and permit notes.
3. Pricing guidance: ranges, cost drivers, fees, surcharges, financing, and last-reviewed dates.
4. Geo logic: ZIP, city, neighborhood, travel-fee, dispatch, and emergency-coverage rules.
5. Trust content: licenses, insurance, guarantees, certifications, reviews, photos, and what-to-expect pages.
6. Handoff rules: required lead fields, routing rules, urgency labels, summaries, and disposition categories.

## The Risks That Matter

The biggest risk is hallucination: a plausible but false answer. For a trades chatbot, that means no free-form guesses about pricing, availability, permits, rebates, service area, or safety. If the source material does not support the answer, the assistant should say it is not sure and route the conversation.

The second risk is outdated facts. Hours, after-hours coverage, seasonal service offerings, promotions, and service areas change. Every answerable fact should trace back to an owned source with an effective date and review cadence.

The third risk is service-area mistakes. If a chatbot says yes to a ZIP code outside the dispatch radius, that is not a harmless typo. It is a trust failure that can waste the homeowner's time and poison the lead before the office ever calls back.

The fourth risk is bad handoff. Customers dislike repeating themselves. The minimum viable handoff for a contractor is name, contact information, address or ZIP, problem summary, urgency, equipment type if known, preferred time window, and a concise transcript summary.

<Callout tone="warn" label="The widget is not the strategy">
Chat does not fix a thin website. It exposes it faster. The answers have to exist somewhere reliable before automation can serve them well.
</Callout>

## What to Fix First

Start with the pages closest to money: emergency service, top repair categories, replacement or install pages, financing, service area, reviews, contact, and after-hours coverage. Each page should answer the practical questions a homeowner asks before calling.

Next, reconcile the facts across the website, Google Business Profile, booking links, chat, call scripts, and internal dispatch rules. The best conversion copy in the world cannot overcome conflicting hours, vague coverage, or a bot that promises service in cities the shop does not serve.

Then measure the funnel honestly: calls, chats, forms, booked jobs, missed contacts, response time, service-area disqualifications, and unanswered questions. The conversion problem is not always traffic. Very often, it is the gap between what the homeowner needed answered and what your site made obvious.

## Sources Used

- BrightLocal: local consumer trust, reviews, contact information, opening hours, and incorrect business information.
- Google Business Profile and Search Central: local ranking factors, service areas, business details, and people-first content guidance.
- HubSpot, Zendesk, LiveChat, and speed-to-lead research: response expectations, chat behavior, knowledge-base usefulness, and follow-up speed.
- FTC consumer guidance: licensing, insurance, reputation checks, complaints, and contractor trust basics.
- ACCA, Carrier, plumbing FAQ patterns, and electrician FAQ patterns: common pre-sale questions by trade.
- OpenAI and Microsoft: hallucination risk, grounded source material, recency metadata, and escalation when uncertain.

---

# Will Customers Trust an AI Receptionist at Your Plumbing, HVAC, or Electrical Company?

Source: https://useladdr.com/blog/will-customers-trust-ai-receptionist-home-services
Category: Technical
Author: Colin Lawless
Published: May 4, 2026

> Yes, when it acts like a fast, honest, well-trained front desk. No, when it pretends to be human, traps callers in a script, or guesses its way through real service problems.

Most owners asking about AI receptionists are not really asking a technology question. They are asking a trust question: will a homeowner with a backed-up drain, a cold house, a sparking outlet, or a noisy unit hang up the second they realize a machine answered?

The honest answer is conditional. Consumers do not broadly trust AI in customer service by default. But they also do not broadly love voicemail, hold music, generic IVR menus, or waiting until tomorrow for a callback.

<Callout tone="info" label="The practical takeaway">
Customers trust AI answering when it behaves like a fast, accurate, clearly bounded front desk. They punish it when it behaves like a fake human or a dead end.
</Callout>

## The Bottom Line

The strongest current evidence does not support the claim that consumers broadly trust AI service by default. Gartner reported that 64% of customers would prefer companies not use AI for customer service, and 53% would consider switching to a competitor if they learned a company planned to use AI in service. Pew Research Center found that the U.S. public is more concerned than excited about AI in daily life, and only a minority of AI chatbot users describe chatbots as extremely or very helpful.

That sounds grim until you look at what people actually want from support. ServiceNow reported that phone remains a preferred support channel for most customers, while customers are more willing to use technology for simple tasks than for advice, relationship-building, or complex inquiries. Verint found that many AI-chatbot users cite at least one benefit, especially saving time and resolving issues faster.

> The question is not whether homeowners love AI in the abstract. The question is whether they prefer a competent first response over no response.

For trades businesses, the right question is narrow: will callers trust an automated assistant that answers immediately, knows the business, books correctly, discloses what it is, and gets a human involved fast when needed? The evidence suggests many will. It also suggests they will not forgive slow, generic, misleading, or inescapable experiences.

## What the Evidence Says About Consumer Comfort

Consumers are uneasy about AI in service, but that unease is not uniform. The consistent pattern across the research is that people are more willing to use automation for low-stakes, well-defined tasks and much less willing to rely on it for high-stakes, emotionally charged, or ambiguous situations.

ServiceNow found that customers still prefer humans for client relationships, advice, recommendations, and more complex inquiries. It also reported that lack of empathy and poor understanding are major frustrations with AI service. The Consumer Financial Protection Bureau reached a similar conclusion in its chatbot report: automation can help with basic inquiries, but trust erodes when people cannot get tailored support or timely human intervention.

Verint's data adds the operational detail. Bad chatbot experiences are usually about the bot failing to answer, failing to understand, taking too long to realize it cannot help, or refusing to offer a path to a human. Bad IVR experiences follow the same pattern: too many prompts, irrelevant information, no completion, and no real person.

Those are not anti-AI complaints in the abstract. They are anti-bad-service-design complaints. For home services, where intent and urgency are often high, speed gets you into the conversation and competence keeps you there.

## Where AI Answering Works

AI answering works best when it improves the part callers already value most: speed to help. A good assistant answers on the first ring, identifies the job, captures the address, confirms the caller's intent, and moves the call toward the next safe step.

The strongest use cases are narrow and operational: booking a repair, checking service area, collecting emergency context, answering approved business questions, routing existing customers, taking after-hours details, and transferring complex or sensitive calls with a clean summary.

It also works when the assistant is grounded in the actual business. Home Depot's public rollout of AI voice agents is aimed at defined store-call tasks, business-specific answers, multiple languages, and a path to associates. Contractors need the same pattern at a smaller scale: real service areas, approved dispatch rules, schedule windows, emergency policy, warranty language, financing basics, and escalation rules.

<Callout tone="info" label="A better benchmark">
Do not compare AI answering to a perfect live CSR available 24/7. Compare it to the real fallback: missed calls, rushed field calls, voicemail, and next-day callbacks.
</Callout>

The escape hatch matters. Gartner's guidance emphasizes that AI should guide customers to a person when needed. Verint found that easy switching to a live person is one of the benefits users value. A caller may accept an automated first stop if they believe it is not the last stop.

## Where AI Answering Fails

AI answering fails when it blocks human help, answers outside its competence, or makes callers feel manipulated. The CFPB report documents the classic failure modes: endless loops, scripted responses, policy-page detours, and poor access to individualized support. In a trades context, those failures show up as wrong service-area answers, missed urgency, bad schedule promises, or unsafe advice.

Speed is also fragile. Customers expect AI to be faster and more efficient. Long pauses, awkward turn-taking, meandering scripts, and filler language burn the one advantage automation is supposed to bring.

Pretending to be human is another failure mode. There may be isolated contexts where concealment improves short-term engagement, especially in outbound settings, but the regulatory and reputational direction is moving against AI-enabled deception and impersonation. For inbound service calls, early disclosure paired with clear utility is the better long-term trust strategy.

Generic scripts are risky too. Homeowners care about zip codes, appointment windows, weather, emergency status, warranties, permit realities, equipment type, financing, and whether your company actually handles their problem. A generic voice can survive a store-hours question. It usually will not survive, "my furnace is out and I have a newborn at home."

<Figure caption="AI answering earns trust when it is specific enough to help and humble enough to hand off." gradient="from-cyan-700 via-slate-900 to-lime-700" />

## Legal and Ethical Guardrails

There is not one broad federal rule that says every inbound customer-service AI call in the U.S. must begin with a specific AI disclosure. But the safer direction is obvious: do not mislead callers about who or what they are interacting with.

Utah's 2024 AI law requires prominent disclosure in certain regulated-services contexts and requires oral disclosure at the start of covered voice exchanges. California's bot law is narrower and focused on online interactions, but it reflects the same anti-deception logic. The FTC has also been explicit that AI tools cannot be used to trick, mislead, or defraud people.

Outbound calls are stricter. In 2024, the FCC ruled that AI-generated or AI-simulated voices fall within TCPA restrictions on artificial or prerecorded voice. That matters if a contractor uses AI for lead reactivation, appointment reminders with marketing content, financing follow-up, review solicitation by voice, or other outbound campaigns.

<Callout tone="warn" label="Compliance note">
Call recording, AI disclosure, outbound consent, and state-specific rules should be reviewed with counsel before launch, especially for multistate operators.
</Callout>

Ethically, the operating rule is simple: do not hide the machine, do not overclaim its competence, do not collect more information than needed, and do not let it improvise where a trained dispatcher or technician would use judgment.

## Best-Practice Scripts for Trades

The right script is not human-sounding theater. It is role clarity, fast triage, business-specific answers, and a visible human handoff. A useful greeting can be short: "Thanks for calling [Business Name]. I am Laddr, the automated assistant for [Business Name]. I can help schedule service, answer common questions, or get your call to our team. If you want a person at any time, just say representative. What can I help you with today?"

Qualification should stay practical: ask whether the caller is new or existing, what issue they are dealing with, what service address or ZIP code applies, whether the problem is happening now, and whether anything unsafe is happening, such as gas smell, smoke, sparking, flooding near electrical equipment, or no heat for a vulnerable person.

Safety escalation should be direct and humble: "This may be a safety issue. If there is active fire, heavy smoke, a strong gas odor, or immediate electrical danger, please hang up and call 911 or the relevant utility emergency line now. I can also alert our emergency on-call team. Would you like me to transfer you immediately?"

Booking should confirm details before commitment: issue summary, address, time window, name, callback number, and email. Transfer should include a concise recap so the caller does not have to repeat everything.

1. Answer immediately and keep the first 20 seconds free of brand fluff.
2. Ground every answer in business-approved knowledge, not generic model memory.
3. Escalate safety, angry callers, billing disputes, legal threats, repeated misunderstanding, and unclear scope.
4. Review failed calls as quality events, not just uncontained calls.
5. Measure booked jobs, save rate, transfer quality, and customer complaints instead of containment alone.

## The Owner Objections Are Real

### My customers will hate talking to AI

Some will dislike it in the abstract. The data supports that skepticism. But the service evidence is more nuanced: people accept automation more readily when it is fast, routine, useful, and easy to escape.

### Disclosure will scare people off

Disclosure can carry an engagement cost in some contexts, especially outbound. But concealment creates larger trust and legal problems. For inbound service calls, early disclosure plus immediate usefulness is the stronger play.

### It will sound generic and hurt our brand

That concern is well-founded if the deployment is generic. The fix is not to make the assistant more human at all costs. The fix is to make it more business-specific and less ambitious.

### What about emergencies?

AI should triage emergencies, not handle them end to end. Safety-related cues need immediate escalation logic, stop-rules, and clear instructions that emergency services or utility emergency lines come first when there is immediate danger.

### Can this replace my office staff?

The evidence points to augmentation, not full replacement. Human roles remain central for exceptions, empathy, dispute resolution, complex scheduling, judgment calls, and quality review.

## Sources Used

- Gartner: 2024 customer-service AI survey and trust guidance.
- Pew Research Center: 2025 U.S. public-attitudes research on AI and chatbot usefulness.
- ServiceNow: CX Shift research on customer preferences, AI comfort, and human-versus-technology tasks.
- Verint: 2024 customer-experience research on chatbot and IVR benefits and failure modes.
- Consumer Financial Protection Bureau: chatbot risks, failures, and trust erosion in consumer finance.
- Federal Trade Commission and Federal Communications Commission: AI deception, impersonation, and AI voice-call enforcement context.
- Utah and California AI disclosure laws: state-level disclosure and anti-deception context.
- Home Depot: 2026 AI voice-agent rollout as an example of bounded, business-specific voice automation.

---

# The Best Time to Ask for a Review After a Service Job

Source: https://useladdr.com/blog/best-time-to-ask-for-review-after-service-job
Category: Reviews
Author: Max Svejda
Published: May 3, 2026

> There is no universal 24-48 hour rule. Review asks work best when they arrive right after the customer has actually experienced the result, on the channel they already use to talk to your shop.

Most owners want a single answer: send the review request 24 hours after the job, or 48, or right before the truck pulls away. Pick a number, automate it, move on.

The honest answer is more useful than that. Public research does not support a universal 24 to 48 hour rule. It supports a different rule: review asks work best when they arrive right after the customer has genuinely experienced the result, on a channel they already use to talk to your shop.

<Callout tone="info" label="The practical takeaway">
Trigger review asks from the job, not from the clock. Same day or next morning for repairs and maintenance. 24 to 48 hours after sign-off for installs, replacements, and other higher-involvement work.
</Callout>

## The Bottom Line

Two streams of public evidence point in slightly different directions, and the honest answer for trades is the synthesis of both. A peer-reviewed Journal of Marketing study found that very early review reminders can actually reduce posting likelihood in some categories, because the ask feels controlling. A 2024 working paper from Paderborn University, using 22.3 million review requests and 2.3 million reviews, found that response probability generally falls as the delay grows, but that higher-involvement and experience-oriented purchases should wait longer before the ask.

Read together, those findings give a clean operating rule. For repairs, maintenance visits, and same-day problem resolution, the result is obvious quickly, so the ask works within hours or by the next morning. For replacements, installs, repipes, panel upgrades, and jobs the homeowner needs to live with for a beat, a 24 to 48 hour window after sign-off is a better fit.

> The right time to ask is not measured in hours since dispatch. It is measured in whether the homeowner can fairly evaluate what you did.

## What the Research Actually Says

The cleanest academic timing evidence comes from the Journal of Marketing paper Ask for Reviews at the Right Time, summarized by Arizona State University and Baylor University. In two randomized field experiments, immediate review reminders reduced posting likelihood, while delayed reminders increased it. In one travel experiment, the group nudged the day after the experience posted fewer reviews than the no-reminder control, and later reminders performed better.

The authors explain it as psychological reactance. An ask that arrives too early can crowd out the customer's own motivation. They feel prompted instead of moved.

The Paderborn working paper complicates the picture in a useful way. Across 22.3 million requests, the probability of getting a review decreased as the time between the purchase and the ask increased. But within that overall trend, businesses selling high-involvement, experience, or hedonic goods should wait longer than businesses selling low-involvement search goods. Delay usually costs response. Some experiences need breathing room first.

<Callout tone="info" label="Translate it for trades">
Repair calls behave like fast feedback. Installs behave like experience goods. The same shop should not use one timer for both.
</Callout>

There is a caveat worth keeping. There is not yet a strong public body of controlled research specifically on HVAC, plumbing, or electrical businesses comparing 24 to 48 hour asks against longer waits by channel and job type. The research is cross-category. The synthesis is evidence-based, not law.

## SMS vs Email for Review Requests

On channel performance, the strongest direct comparisons come from vendor datasets, not peer-reviewed trials. They consistently point in the same direction. GatherUp reports that businesses using SMS only generated about 20 reviews per 100 requests, while those using both SMS and email generated about 26 per 100. Birdeye reports SMS follow-ups drive higher response rates than email, and that multi-channel follow-ups outperform either channel alone.

Independent survey-methodology research is more cautious. A paper in the Journal of Survey Statistics and Methodology found that adding SMS invitations in mixed-mode survey designs often has little effect on total response rate compared with email alone, but does reduce time-to-response. The clear win for SMS is speed, not necessarily total volume.

For home services, that synthesis is a clean operating rule. Default to SMS first when the customer has consented to text and already expects text from your shop. The customer is mobile, the ask is simple, and faster response is genuinely valuable. Default to email first when the customer relationship has been office-led, the job was consultative or higher-ticket, or the brand needs more context than an SMS comfortably carries. Use the other channel as the follow-up so you widen reach without sounding repetitive.

<Callout tone="warn" label="Label the data honestly">
When you cite SMS-vs-email numbers, label vendor datasets as vendor data. Treat them as directional, not regulator-grade.
</Callout>

## The Cadence That Works for Trades

The most defensible cadence for HVAC, plumbing, and electrical shops is job-triggered, channel-aware, and short. The trigger is not the calendar. The trigger is the job state.

1. Repairs and maintenance: send the first ask by SMS a few hours after completion, or the next morning if the job ended late.
2. Replacements, installs, and higher-involvement jobs: send the first ask 24 to 48 hours after completion, after commissioning, walkthrough, or final sign-off.
3. Any job with an unresolved punch list, callback risk, or uncertain result: do not ask until the issue is fully resolved.
4. First follow-up: 3 to 5 days later on the other channel, only if the customer has not opted out.
5. Optional final follow-up: 7 to 14 days later, only if the brand wants slightly more persistence.

Older Birdeye guidance recommends one to three reminder emails. Housecall Pro recommends a first reminder after 2 to 4 days and notes it often takes two or three reminders to catch a customer at the right moment. Birdeye's newer aggregate report says many businesses now send a very high number of reminders per review converted, but that figure describes platform behavior, not what a trades brand should copy if it cares about perception and complaint risk.

> Enough persistence to lift conversion. Not so much that the request starts to feel needy, spammy, or manipulative.

Skip Yelp from any automated public-review ask. More on that in the policy section.

## What Reviews Mean for Google Business Profile

Google's official local-ranking documentation is direct. Local results are driven by relevance, distance, and prominence, and Google explicitly says that more reviews and positive ratings can help a business's local ranking. Google also includes responding to reviews in its ranking-improvement tips, stating that replies show customers you value feedback and that positive reviews plus helpful replies can help your business stand out.

The consumer side matters as much as the ranking side. BrightLocal's 2026 Local Consumer Review Survey found that 47% of consumers won't use a business with fewer than 20 reviews, 74% only care about reviews written in the last three months, 31% only use businesses with 4.5 stars or higher, and owner responses are a meaningful trust signal. People look for consistency across multiple reviews, not one glowing testimonial.

<Callout tone="info" label="Steady velocity beats spikes">
Recency, count, rating, and owner responses all influence trust. Treat review generation as an operating system, not a quarterly campaign.
</Callout>

Keywords inside reviews are the shakiest of the review-signal claims. Practitioner sources like Whitespark argue that review text mentioning services and locations can help a profile compete for relevant local queries. Google does not explicitly confirm keywords in reviews as a discrete ranking factor in its public documentation. The safe stance is that natural service-specific language in genuine reviews is helpful for persuasion and may help relevance, but it is not a guaranteed ranking lever.

Owner responses help trust and are recommended by Google, but Google does not publish a precise ranking weight for replies. A workable standard for trades is to reply to new reviews the same day or next business day whenever possible, especially to negative feedback that signals a live service issue.

<Figure caption="Recency, count, rating, and owner responses all shape the trust signal a homeowner reads in the first 10 seconds." gradient="from-amber-600 via-slate-900 to-violet-700" />

## The Rules That Can Get Shops in Trouble

Platform policy matters as much as conversion optimization. The compliant lane looks different on every platform, and the FTC has tightened the legal stakes.

### Google

Google allows businesses to ask for genuine reviews and even provides review links and QR codes for that purpose. It bans incentives, review gating, discouraging negative reviews, and asking for specific content. It also says merchants should not require or pressure users to leave reviews while on the premises. For a home-service workflow, that means sending the ask after the technician leaves and the job is marked complete, not by handing over a phone at the doorstep or coaching the homeowner on what to write.

### Trustpilot

Trustpilot allows invitations, but only if they are fair, neutral, unbiased, and non-incentivized. Businesses should invite everyone in the same way, use one invite per experience, and give customers time to experience the service before asking. Trustpilot also requires using its supported invitation methods, which matters for any third-party review tool.

### Facebook recommendations and Meta

Meta's public policy listing says community feedback must not be directly or indirectly incentivized unless properly disclosed. That is enough to support a neutral, no-incentive approach, but it is less granular than Google's or Trustpilot's business-facing guidance.

### The FTC

The 2024 Consumer Reviews and Testimonials Rule prohibits fake reviews, sentiment-conditioned incentives, and certain review-suppression tactics. The rule explicitly says generalized solicitations to purchasers are allowed, but compensation or incentives conditioned on positive or negative sentiment are not. It also prohibits materially misleading claims that displayed reviews represent most or all submitted reviews when negative ones are being suppressed by rating or sentiment.

<Callout tone="warn" label="No happy-only funnels">
Filtering dissatisfied customers away from the public review link, while pushing happy ones toward it, is the exact pattern Google bans and the FTC's rule targets. Ask everyone the same way.
</Callout>

On the channel-compliance side, the FCC says texts to mobile phones using an autodialer generally require prior consent, and the FTC's CAN-SPAM rules apply to commercial email and give recipients the right to stop future messages. A conservative review-request flow preserves consent records, clear sender identity, and easy opt-outs. This is marketing research, not legal advice.

## Wording That Sounds Professional, Not Needy

The copy should be neutral, specific, and easy to act on. Reference the actual job, ask for an honest review rather than a positive one, include a direct link, and keep the ask optional. That mirrors Google's instruction to value all reviews and Trustpilot's requirement for fair and unbiased invitations. It also reduces the psychological reactance risk identified in the academic timing research.

- Use the customer's first name and the actual service performed, not a generic "thanks for your business."
- Ask for honest feedback, not 5 stars. "Leave us a 5-star review" language drifts toward Google's prohibited specific-content rule.
- Include a direct review link or QR code. Do not ask the customer to search for you.
- Keep one ask per experience. Do not stack a survey, an NPS prompt, and a Google review ask into one message.
- Keep an opt-out path that actually works on the channel you used to send the message.

## Templates Trades Shops Can Copy

These examples are intentionally neutral, ask for honest feedback, avoid ratings language, and work best with a direct Google review link. They align with Google's and Trustpilot's public guidance better than "leave us a 5-star review" language.

### SMS for a completed repair call

> Hi [First Name], thanks for choosing [Company Name] today for your [repair/service]. If you have a minute, would you share your experience here? [Review Link] Your feedback helps other homeowners know what to expect.

### SMS for an install or replacement, sent the next day

> Hi [First Name], thank you for having [Company Name] out for your [install/service]. Hope everything is running smoothly. If you'd like to leave an honest review, here's the link: [Review Link]

### SMS follow-up

> Hi [First Name], just a quick follow-up from [Company Name]. If you haven't had a chance yet and would like to share your experience, here's the review link: [Review Link] Thanks again.

### Email for a same-day service visit

> Subject: Thanks for choosing [Company Name]. Hi [First Name], thank you for having us out today for your [service]. If you have a minute, we'd appreciate your honest feedback about the experience. Here's the review link: [Review Link]. Thank you, [Dispatcher/Owner Name], [Company Name].

### Email for a higher-involvement install

> Subject: How is your new [system/service] working? Hi [First Name], thank you again for choosing [Company Name] for your [install/project]. Now that you've had a little time with the new system, we'd love to hear how the experience went. If you'd like to leave a review, here's the link: [Review Link]. Thanks, [Name], [Company Name].

The wording is unglamorous on purpose. Honest, specific, optional. That is the version platforms reward and homeowners actually act on.

## Sources Used

- Journal of Marketing: Ask for Reviews at the Right Time (Arizona State University and Baylor University), randomized field experiments on review-reminder timing.
- Paderborn University 2024 working paper: empirical analysis of online review-request timing across 22.3 million requests and 2.3 million reviews.
- Journal of Survey Statistics and Methodology: SMS, email, and web invitations in mixed-mode survey designs.
- GatherUp: SMS vs email review-request data (vendor data).
- Birdeye: SMS vs email and follow-up trends, plus review-request cadence guidance (vendor data).
- Housecall Pro: field-service review reminder cadence guidance.
- Google Business Profile Help: local ranking factors, review-request tips, and Maps prohibited and restricted content policy.
- Yelp: official Don't Ask for Reviews business guidance.
- Trustpilot: Guidelines for businesses on fair, non-incentivized invitations.
- Meta: Community Feedback Policy listing.
- Federal Trade Commission: Consumer Reviews and Testimonials Rule and Q&A.
- Federal Communications Commission: unwanted-text and autodialer guidance, plus FTC CAN-SPAM guidance for commercial email.
- BrightLocal: 2026 Local Consumer Review Survey on review recency, count, rating, and owner-response trust signals.
- Whitespark: practitioner guidance on keywords in reviews and local relevance.

---

# The True Cost of Missed Inbound Calls for Home Service Shops

Source: https://useladdr.com/blog/true-cost-missed-inbound-calls-home-service-shops
Category: Operations
Author: Max Svejda
Published: May 2, 2026

> Missed calls are not automatically lost jobs. The real cost is narrower, more measurable, and often more dangerous: qualified demand that moves to the next shop when nobody answers.

For a small-to-mid-sized HVAC, plumbing, or electrical shop, the most defensible claim is not that every missed call equals a lost job. That sounds good in an ad, but it is too blunt to be useful.

The stronger claim is simpler: a meaningful share of inbound calls go unanswered, customers move on quickly when they cannot reach a business, and missed calls that happen after hours or during urgent windows tend to be worth more than the average daytime call.

<Callout tone="info" label="The practical takeaway">
Missed-call loss should be modeled from qualified missed opportunities, not from every raw ring in the call log.
</Callout>

## The Bottom Line

Recent public benchmarks put the problem in a real range instead of at one magic number. One business-calling benchmark says 28% of calls go unanswered overall. A home-services-specific analysis of 1.1 million calls found a 14% missed-call rate. Another home-services source says unanswered rates rise from 18% on weekdays to 41% on weekends.

The customer behavior data is what turns that operating issue into a revenue issue. A recent consumer survey found that 78% of consumers have taken their business elsewhere after failing to reach a company by phone. In the same survey, 42% said they would leave a voicemail, 24% would switch to chat, and 21% would immediately call another business.

> For an owner-operator, a missed call is often not unfinished admin. It is active demand reallocating to the next shop that answers.

A second reality check comes from booking-rate data. ServiceTitan's trade benchmark found that the typical shop booked only 42% of calls into jobs. For companies with 5 to 14 technicians, it estimated that a five-point improvement in booking rate was worth about $100,000 in annual revenue.

## Benchmarks You Can Trust

The cleanest way to talk about missed calls is to separate related but different metrics. Missed call, unanswered call, abandoned call, voicemail, and unbooked call are not interchangeable. When sources disagree, it is usually because they are measuring different things.

- Missed or unanswered calls: public benchmarks range from 14% in a home-services dataset to 28% across businesses, with weekend unanswered rates reported as high as 41%.
- Booking rate: ServiceTitan reported a typical trade-shop booking rate of 42%, with plumbing at 43%, electrical at 41%, and HVAC at 38%.
- Shop-size gap: the same benchmark found shops with more than 25 techs booked 59% of calls, while shops with fewer than five booked 24%.
- Customer defection: CallRail's consumer survey found that 78% of consumers have taken business elsewhere after an unanswered call.
- Lead response: Jobber's 2026 report says only 20% of home service businesses respond to new leads within an hour.

The safest summary is this: expect meaningful leakage even during normal hours, and much worse leakage on weekends and off-hours.

## A Conservative Way to Calculate the Loss

The least exaggerated model starts by removing noise. Do not multiply every spam call, vendor call, duplicate ring, existing-customer status check, and recruiter call by your average ticket. That will inflate the number and make the exercise easy to dismiss.

<Callout tone="info" label="Use this formula">
Missed-call revenue loss = missed qualified opportunity calls x booking rate x realized average completed revenue for that call type.
</Callout>

For replacement-dominated calls, use a different model: missed qualified replacement calls x appointment-set rate x sold rate x realized install ticket. The distinction matters because replacement leads can be worth thousands in expected revenue, but only when the missed call was actually replacement-classified.

### Service and repair calls are still expensive enough

- HVAC service or repair: a 38% booking rate multiplied by common service-ticket proxies produces roughly $95 to $143 in expected completed revenue per missed qualified call.
- Plumbing service or repair: a 43% booking rate multiplied by common repair-ticket proxies produces roughly $104 to $215 per missed qualified call, with water-heater repair calls higher still.
- Electrical service or repair: a 41% booking rate multiplied by small-task and service-tech ticket proxies produces roughly $94 to $236 per missed qualified call.

If a shop lets 20 qualified service calls a month slip away, conservative public-data math suggests roughly $1,900 to $2,900 per month in missed HVAC service revenue, $2,100 to $4,300 per month in plumbing service revenue, and $1,900 to $4,700 per month in electrical service revenue depending on the job mix.

Those are not sensational numbers. They are deliberately conservative because they use service and repair ticket sizes instead of applying replacement-ticket math to the whole call log.

## Why After-Hours Missed Calls Hurt More

After-hours missed calls are not just more frequent. They are often more valuable. Invoca's home-services numbers show unanswered calls rising from 18% on weekdays to 41% on weekends. ServiceTitan's booking-rate study found booking performance falls sharply after 6 p.m. Housecall Pro says 41% of jobs booked online come in after hours.

Put those together and the pattern is clear: when the office closes or the owner is buried in field work, customer intent does not stop. It simply becomes harder to catch.

The ticket economics can also worsen at the wrong time. Emergency plumbing and electrical calls often carry premium rates. The same unanswered call is not equally expensive at 11 a.m. and 11 p.m.; the after-hours version is often both more urgent and more monetizable.

<Figure caption="The missed-call problem gets sharper when higher-intent calls arrive outside the hours a small shop can comfortably staff." gradient="from-slate-900 via-blue-800 to-emerald-700" />

## Safe Claims and Shaky Claims

The safest claims stay close to what the sources actually show. You can say unanswered calls are a measurable revenue leak, consumers defect quickly after unanswered calls, voicemail is a weak recovery mechanism, after-hours and weekend windows are riskier, and conservative loss math should use qualified missed calls instead of total inbound calls.

You can also say small and growing shops are more exposed than larger operators. The benchmark gap between under-five-tech shops and 25-plus-tech shops is large, and faster lead response is more common among more structured businesses.

<Callout tone="warn" label="Avoid the hype">
Do not claim every missed call is a lost customer, every missed call costs your average install ticket, or missed calls directly hurt Google rankings unless you can support the exact claim.
</Callout>

## What to Do Next

1. Pull the last 90 days of calls and classify missed calls by qualified opportunity, existing customer, vendor, duplicate, spam, and other.
2. Split qualified missed calls by intent: repair, emergency, estimate, replacement, maintenance, and unknown.
3. Break the misses by hour and day so you can see whether the problem is weekday lunch, after 6 p.m., weekends, or all of the above.
4. Use your own average completed revenue by job class wherever possible. Use public proxies only when you do not have clean internal numbers.
5. Compare the recovered revenue opportunity against the cost of coverage: CSR staffing, call overflow, AI answering, booking links, chat, or after-hours routing.

The point is not to scare yourself with the largest possible number. The point is to find the portion of demand you are already paying to generate, then make sure it has a path to book even when nobody is sitting at a desk.

## Sources Used

- CallRail: unanswered-call consumer behavior, voicemail behavior, hold-time patience, and home-services call-answering benchmarks.
- Invoca: weekday versus weekend unanswered-call benchmarks for home services.
- ServiceTitan: trade call-booking benchmarks by trade, shop size, and time of day.
- Jobber: 2026 home-service lead-response benchmarks.
- Housecall Pro: after-hours online booking benchmark.
- Angi and HomeAdvisor: consumer-facing repair and emergency-service ticket proxies.
- Google Business Profile Help and BrightLocal: business-hours, contact-path, and local trust context.