revsetHVAC missed-call text-back sends an approved SMS after an eligible unanswered call, inviting the caller to continue the request or arrange a callback. A complete setup also checks messaging permission, suppresses repeat texts, records the reply and gives the next action to someone. A delivered text is the beginning of recovery, not proof of a booked job.
Start with the missed-call problem you actually have
Listen to how calls move through your current phone system. Does the office miss calls while already speaking to someone? Does a forwarded call reach the owner’s personal voicemail? Are weekend inquiries invisible until Monday? A text-back workflow needs a reliable unanswered-call event from that route. It cannot recover a call that never reaches the connected system.
Separate new inquiries from existing appointments, suppliers, wrong numbers and spam. A customer calling twice about an arrival window should not be treated as two new leads. The first message should make it easy to explain the reason for calling. The next step may be a dispatcher task rather than a sales booking.
Choose a callback process before activating messages. Name the responsible person, coverage hours and backup. If nobody is available until the next business day, make that clear in approved wording. Do not let an automatic reply imply that the office is currently reviewing the request when it is closed.
What you need before turning it on
| Requirement | Decision to record |
|---|---|
| Phone route | Which business numbers produce reliable call events, including forwarded and tracking numbers? |
| Sending number | Which approved number sends SMS and receives replies? Can the office monitor that inbox? |
| Messaging permission | Where is the relevant permission recorded, and which message purpose does it cover? |
| Repeat-call policy | How will repeat attempts update one request without repeatedly texting the caller? |
| Owner and hours | Who owns the reply now, after closing and during an absence? |
| Record destination | Where do call, message, callback and appointment status live together? |
For a Twilio-backed implementation, follow its messaging policy on consent, sender identity and opt-out handling. Do not treat a phone number captured from an unanswered voice call as blanket permission for recurring promotional texts. A registration or a functioning send button does not replace the required permission. Confirm the proposed use case with your provider. Twilio messaging policy ↗
The complete missed-call recovery workflow
1. Receive and classify the event
Wait for the final call outcome. Distinguish answered, busy, unanswered and failed events according to your phone provider’s definitions. Exclude outbound calls and events generated by your own transfer legs. Preserve the original caller and called business number so the right office identity is used.
2. Check whether a message is eligible
Look for an existing request, messaging permission, opt-out status, a usable destination and recent text-back activity. If a condition is unknown, route for review rather than guessing. Use the call event identifier to prevent a retried event from producing the same message twice.
3. Send one useful first reply
Identify the business and ask one simple question. Record the provider message identifier and delivery state. “Queued,” “sent” and “delivered” are different states; none means the customer has read the message.
4. Make the reply actionable
Link the incoming response to the service request. Collect the missing service and location context, or alert the office if it concerns an existing visit. A request for a call should become an assigned callback, not just an unread text.
5. Complete or escalate the next step
If a callback is scheduled, save its time zone, owner and status. If delivery fails or a handoff is unclaimed, create a visible exception. Keep an eligible human callback path for callers who cannot or do not want to use SMS.
Four message templates to adapt
These are fictional operational templates, not a universal consent solution. Use them only for the approved message purpose and channel. Replace placeholders with validated business facts; the example opt-out wording is included for the initial text.
During staffed hours
“Hi, this is [Business]. We missed your call. What service do you need, and what ZIP code is the property in? Reply STOP to unsubscribe.”
After the office closes
“Hi, this is [Business]. Our office is closed until [verified opening time and time zone]. What were you calling about? We can arrange the next step when the office reopens. Reply STOP to unsubscribe.”
When the customer wants a callback
“Would [verified available callback time and time zone] work for a call with our office? This would be a phone call to discuss your request, not a confirmed service visit.”
After the callback is actually confirmed
“Your callback with [Business] is confirmed for [day, time and time zone] on [confirmed number]. Reply here if that needs to change.”
Avoid “a technician is on the way,” “we will call in five minutes” or an unsupported fixed repair price. A person who replies with a potential urgent hazard needs the company’s approved escalation response, not the standard qualification sequence. The message should never encourage someone to wait for a sales callback in place of an appropriate urgent response.
How to approach setup in HighLevel
HighLevel’s current support instructions place the feature under Settings → Phone System → Voice → Voicemail & Missed Call Text Back. Open Missed Call Text Back, configure the approved message and follow the account’s save and test process. Review number selection and voicemail behavior on the same route. Interface labels and account availability can change. Current HighLevel setup instructions ↗
The same documentation warns that the basic feature can trigger for every missed call, including repeat attempts from one caller. If your acceptance criteria require suppression, build and test an appropriate workflow rather than assuming the toggle does it. Disable the overlapping basic sender when the custom path owns the message; otherwise both may fire.
For a custom workflow, define the call-status trigger, inbound filter, permission and opt-out checks, recent-contact condition, approved send action and owner task. Treat this as a specification to verify in your account. Do not copy a generic recipe without checking which conditions and event fields it actually supports.
How do you prevent duplicate texts?
Three call attempts, one recovery message
At 2:01 PM a fictional customer calls and gets no answer. At 2:02 PM they try again. At 2:04 PM they call a second office number that reaches the same team. The system should retain the three call activities while keeping one customer request and one recovery conversation.
A sample policy might suppress additional initial text-backs for 30 minutes while the same request remains open. That duration is an operator-selected starting rule, not a carrier requirement or a proven optimum. Repeated attempts can still increase the priority of the office task. If the caller has already replied, route to the conversation owner.
Handle two different duplication problems: repeated delivery of the same event, and genuinely different calls from the same person. The first needs an event-level uniqueness check; the second needs a recent-conversation policy. A simple wait step does not necessarily protect against simultaneous workflow runs.
Also account for shared household numbers. A phone number can be a useful matching signal, but it does not prove that two inquiries concern the same property or job. Preserve the new message and let the owner separate requests when the context differs.
Budget for recovery, not just the SMS
Include the software plan, business number, messaging usage, applicable registration and carrier charges, setup and staff response time. Ask whether billing uses messages or segments, whether incoming replies are charged and whether forwarding adds cost. Use your provider’s current quote; there is no single HVAC text-back rate.
A sample volume calculation
Suppose a business has 120 missed-call events. After repeated attempts, spam and ineligible messages are removed, 70 distinct requests qualify for a text. If each receives one initial text and 30 of those conversations produce two additional outbound messages, the model contains 130 outbound messages before segmentation or retries. Those are assumptions for budgeting, not an expected reply rate.
At an assumed all-in incremental usage cost of $0.02 per segment, 130 single-segment messages would cost $2.60. Your actual rate and segment count can differ. The platform fee, configuration and office handling may exceed the message cost by far. Replace the assumed rate with your provider’s price.
Test the failures before real callers encounter them
- Answered call: no missed-call text is sent.
- Same event delivered twice: exactly one initial message is recorded.
- Repeat caller: the agreed suppression policy holds and the office still sees the repeat attempt.
- Caller replies STOP: the messaging suppression state updates and no scheduled promotional or follow-up text bypasses it.
- Landline or failed delivery: failure is visible; no fake “customer contacted” status is added.
- Reply about an existing appointment: the service owner gets the message; a duplicate sales opportunity is not automatically created.
- Closed office: the text uses correct hours and the callback task belongs to the next staffed queue.
- Sender or integration outage: the team can identify affected requests and recover without blindly resending everything.
Run controlled tests from permissioned test numbers and inspect the call record, SMS record, inbox and task. Name the owner who signs off each scenario. Keep a way to pause the sending workflow while preserving inbound calls and office access.
What should the owner review each week?
Count unique eligible missed-call requests, attempted texts, delivered texts, customer replies, completed callbacks, confirmed appointments and completed jobs. Use each stage’s appropriate denominator. Reply rate among delivered messages answers a different question from completed jobs among all missed calls.
Inspect unresolved requests and office response time as well as totals. If customers reply promptly but nobody answers them, the bottleneck has moved rather than disappeared. Review opt-outs, delivery failures and repeated messages so efficiency does not come at the cost of an irritating customer experience.
Does text-back replace an answering service?
No. It follows an unanswered call; it does not provide a live voice conversation. A business may use both, with one coordinated set of triggers.
Can I send repeated offers to everyone who called?
Do not assume that permission for one conversation covers ongoing marketing. Keep promotional campaigns separate and verify their permission requirements.
When should I hire help?
Use a native feature when it meets your routing and messaging requirements. Get implementation help when multiple numbers, overlapping automations, repeat-call behavior or CRM handoffs cannot be reliably tested by your team.
MAKE IT PRACTICAL
Turn the guide into a project brief.
See the implementation scope and interactive preview ↗
Use the worksheet to record your current tools, decisions, costs and pass/fail checks. Bring a redacted example and the workflow you want to improve.
Download the implementation worksheet ↗
RevSet reviews the process, scopes the build, configures the agreed connections, tests the handoffs and documents ownership. Implementation fees and ongoing support are agreed separately after the review.
Book an HVAC systems consultation ↗What the 30-minute review covers · Evaluate our implementation evidence
Sources and editorial approach
Product documentation checked October 5, 2026. Product availability, interface labels and prices can change. The workflows and buying criteria are RevSet’s editorial recommendations, supported by illustrative examples.