How to Set Up Missed-Call Text-Back When Your Techs Are Under a Door

A tech is under a door with a drill in one hand. The office line rings, nobody answers it in time, and the caller either tries again later or, more often, moves to the next search result. A missed-call text-back does not answer the phone. It sends a text the moment that call goes unanswered, so the caller has something to respond to before they dial the next shop. Calling back later helps too, but Hiya’s State of the Call report, as cited on CallRail’s blog, found 86 percent of consumers do not answer calls from numbers they do not recognize, which is exactly what a returned call from your shop looks like on a stranger’s phone. A text lands regardless. This guide gets that text sending from one of three tools a garage door company is likely to already be paying for, and it flags the one compliance step that breaks it silently if you skip it.

One disclosure up front: Garage Door Lead Engine sells missed-call text-back as part of our platform, so we are not a neutral reviewer here. What follows is the same setup logic we use internally, written so you can build it yourself in whatever tool you already have.

Which one you should probably pick

If you already have a GoHighLevel account, and plenty of door shops do because an agency put them there, build the workflow inside it. You already own the subscription, and GoHighLevel’s automation builder can do more than send a text: it can also create a contact record and notify staff in the same trigger.

If you do not already have a CRM and just need a phone system that texts, OpenPhone (Quo) is the faster path. Its A2P registration is a guided in-app step rather than something buried in a broader platform, and it ships native desktop apps for Mac and Windows alongside the phone app.

If you already run Housecall Pro for scheduling, dispatch, and invoicing, check its automation settings before buying anything else. A tool you are already paying for that can do this job does not need a second subscription stacked on top of it.

What each one actually costs

Prices below are as published on each vendor’s own pricing page, checked August 28, 2026. None of these figures include per-message carrier surcharges, which have reportedly moved at more than one major US carrier through 2026 and are not published on a single confirmed fee schedule as of this writing.

Tool	Published price (checked 2026-08-28)	Best at	Where it gets hard
GoHighLevel	Starter $97/month (3 sub-accounts, unlimited contacts and users); Unlimited $297/month; phone and SMS usage metered as Twilio-based pass-through on top of the subscription	A single workflow that texts the caller, creates a contact, and notifies staff in one trigger	A2P 10DLC brand and campaign registration is mandatory before any automated text sends, and approval takes 1 to 5 business days with no error shown if you skip it
OpenPhone (Quo)	Starter $15/user/month annual ($19 monthly); Business $23/user/month annual ($33 monthly); A2P registration $19.50 one-time plus $1.50 to $3/month maintenance; extra numbers $5/month; automated/API SMS $0.01 per message	Fastest self-serve setup, guided A2P flow inside the app, native Mac and Windows desktop apps	It is a phone system, not a CRM. The text-back sends, but it does not automatically build a lead record the way GoHighLevel’s workflow does, unless you also pay to connect HubSpot or Salesforce
Housecall Pro	Basic $59/month annual (1 user); Essentials $149/month annual (5 users included, then $100/month per extra user); Max $299/month annual (8 users included, then $75/month per extra user)	Already bundled into a plan you may be paying for if you use it for scheduling and invoicing	Housecall Pro’s own pricing page does not spell out missed-call text-back as its own line item or confirm which tier it lives on. Confirm it is actually available and enabled in your specific plan before assuming it is there

Before you start

Gather these before you touch a workflow builder. Missing one of them is the most common reason a shop builds the automation, tests it once, and then discovers weeks later it never actually went live for real customers.

• A phone number that already routes into the tool you are using. If your main line forwards to a separate answering service or a personal cell, confirm the missed-call event actually reaches GoHighLevel, OpenPhone, or Housecall Pro before you build anything downstream of it.
• A2P 10DLC registration started, or already complete. This is the single most common reason a correctly built text-back never sends. See the section below for what it involves and how long it takes.
• Your business legal name, address, and EIN, if you are registering a Standard brand. A Sole Proprietor tier is available without one, but it caps how many messages you can send per day, which matters once texting volume includes review requests and follow-up, not just missed-call replies.
• A decision on what the text should say, and who gets notified when it fires. Write the message before you build the trigger, not while you are inside the workflow builder.
• A stop condition. Decide what ends the sequence: a returned call, a reply, or a lead manually marked handled. Build it in the same setup session as the trigger itself.

Setting up missed-call text-back in GoHighLevel

GoHighLevel is genuinely the most capable of the three for this specific job, because the same workflow that sends the text can also create a contact and alert a staff member. It is also the one where a missed compliance step produces the most confusing failure, so read the registration piece before you build the trigger.

1. Inside your GoHighLevel sub-account, confirm the phone number that will receive calls is connected under the Phone Numbers settings. Use an existing number or provision one through GoHighLevel’s built-in LC Phone (Twilio-backed) service.
2. Before building anything else, complete A2P 10DLC registration: a Business Profile, then a Brand, then a Campaign, selecting a use case that matches what you are actually sending (a missed-call reply and a review request typically fall under customer care or low-volume conversational, not marketing). GoHighLevel’s own support documentation walks through the current menu path, since sub-account interfaces get revised over time. Budget 1 to 5 business days for approval before you plan a launch date.
3. Once the campaign is approved and your number is attached to it, open the Workflow builder and create a new automation.
4. Set the trigger to a missed or unanswered call event on your business number. Confirm the trigger does not also fire on an internal call transfer between staff, which will send a customer-facing text to your own tech by mistake if left unfiltered.
5. Add an action to send a templated SMS to the caller. Keep the message short and specific (see the templates below).
6. Add a second action to create or update a contact record, tagging it so it shows up as a new lead rather than getting buried in an existing customer’s history.
7. Add a third action that notifies a real person, by internal SMS, email, or a task assignment, so the text-back is not the last thing that happens.
8. Build the stop condition into the same workflow: an exit branch triggered by a returned call, a reply from the customer, or the lead being manually marked handled.
9. Test it. Call from a phone not already in your CRM, let it go unanswered, and confirm the text lands, the contact record is created, and the staff notification fires.

Setting up missed-call text-back in OpenPhone (Quo)

OpenPhone, rebranded to Quo in September 2025 though still widely searched under its old name, is the faster path if you do not already have a CRM and just want a business phone system that texts reliably.

1. Sign up and either port your existing business number or provision a new local or toll-free number.
2. Complete A2P 10DLC registration inside the app: a $19.50 one-time fee plus $1.50 to $3 per month in ongoing maintenance, as published on OpenPhone’s own pricing page. This is a guided flow, not a form buried in a broader console, but it is still a separate step you have to finish before automated texting works reliably.
3. Invite your team and assign them to the shared number and inbox that will handle missed calls.
4. Look for the automated-response or missed-call setting inside the app’s automation or workflow area (the exact menu label can shift as the product evolves under its new Quo branding, so look for language like “auto-reply” or “missed call text” rather than a specific screenshot).
5. Configure the missed-call condition, meaning how many rings or how many seconds of no answer counts as missed, and set the templated reply text.
6. If you want the missed call to also create a record in an outside CRM, connect HubSpot or Salesforce (available on the Business plan and up) or route it through Zapier.
7. Test with a call from an outside number and confirm the text lands, then check that the number shows up correctly in your shared inbox for a human to follow up.

Setting up missed-call text-back in Housecall Pro

If Housecall Pro is already running your scheduling, price book, and invoicing, this is worth checking before adding anything else to the stack.

1. Inside your Housecall Pro account, look under Settings for an Automations or Messaging area. Housecall Pro’s own pricing page does not itemize missed-call text-back as a named feature or state which tier includes it, so confirm directly in your dashboard, or with a support rep, whether it exists on your current plan (Basic, Essentials, or Max) before assuming it is there.
2. If the feature exists, set the trigger condition (an unanswered inbound call) and the templated reply text the same way you would in a dedicated phone tool.
3. Confirm whether the resulting text-back automatically creates a job or lead record inside Housecall Pro, or whether it only sends the text and still requires someone to manually add the caller as a lead.
4. Test with a call from an outside number, the same way as the other two tools, and check both that the text lands and that whatever record it is supposed to create actually appears.

If the feature is not available on your tier, or not available at all, the honest next step is either upgrading, or running the trigger in GoHighLevel or OpenPhone instead and keeping Housecall Pro for scheduling and invoicing. Paying for two tools that both claim to do the same thing is a common way shops end up with an automation nobody remembers which system actually owns.

Writing the text itself

“Sorry we missed you” is the default text most tools ship with, and it is the weakest option available. It tells the caller you know you missed them, but it gives them nothing to do next.

A text that asks a direct question performs better in practice, because it gives the caller something to reply to instead of a dead end:

• General inquiry: “Hi, this is [Shop Name]. Sorry we missed your call, our techs are out on jobs right now. What’s going on with your door, and what’s the best number to reach you?”
• Likely emergency (spring, opener failure): “Hi, this is [Shop Name]. We missed your call. If your door won’t open or close, reply URGENT and we’ll call you back first.”
• Seasonal or high-volume period (storm season, spring): “Hi, this is [Shop Name]. We’re getting a lot of calls right now. Reply with what’s happening and we’ll call you back in order.”

What usually goes wrong

• A2P 10DLC is skipped or still pending when the workflow goes live. This is the single most common failure across all three tools. The dashboard shows the automation as active, the text shows as sent, and it simply never arrives, because an unregistered or under-registered number gets filtered by the carrier before it reaches the customer’s phone.
• The trigger fires on internal transfers, not just true missed calls. A call routed from the front desk to a tech’s cell that goes unanswered for a ring or two can trigger the same automation meant for outside callers, sending a customer-facing text to your own employee.
• No stop rule, so the customer gets texted twice. The office calls the customer back, then the automated sequence fires again later because nothing told it the lead was already handled.
• Nobody is watching the inbox the reply lands in. The text-back captures the lead, but a reply sitting in a shared inbox nobody checks buys you nothing but a faster-looking non-response.
• The default text is left as-is. A generic “sorry we missed you” gives the caller nothing to respond to, and a caller who does not reply looks identical, from inside the dashboard, to one who was never going to book anyway.

How to tell it is working

In week one, call your own business line from a phone number that is not already in your CRM or contact list, let it ring through to missed, and time how long the text takes to arrive. Check that it lands as an actual text message on the receiving phone, not just as a “sent” status inside the dashboard, since a carrier can silently filter a message that shows as sent on your end. Confirm the lead record that gets created, if your tool builds one, has an owner assigned and a visible next action rather than just sitting in a list.

In month one, look at how many missed calls actually resulted in a reply from the caller, and how many of those replies turned into a booked estimate. If replies are landing but nobody is following up on them within the same day, the text-back is working and your follow-up process is the gap, which is a different problem with a different fix (our guide on automated lead follow-up sequences covers that piece separately: automated lead follow-up sequence setup). If texts are not landing at all weeks after setup, go back to your A2P registration status first: our full walkthrough on that step is here: A2P 10DLC registration for garage door companies. And if you are still deciding whether a lightweight call-tracking layer or a full phone-system swap makes more sense for your shop before you build any of this, that comparison is covered in business phone system vs call tracking.

Missed-call text-back is a reasonable first automation to build, because it is cheap and fast to set up in a tool you may already be paying for. It is also the clearest test of whether your texting is actually reaching customers, since a call you make yourself and a text you can watch arrive on your own phone is about as close to a controlled test as this gets.