Decide what a second call should do

For a home-service business, the first useful response identifies the company, offers a next step, and leaves someone responsible for replying. The harder question is what happens when the same person calls three times while your team is busy.

HighLevel’s native text-back can send after every missed call, including repeated attempts. Choose that mode when this behavior fits your business. Use a workflow when you need a repeat-call window or a more specific handoff. Keep one system responsible for the initial message. Native feature documentation.

Option 1: turn on native text-back

In your sub-account, go to Settings → Phone System → Voice → Voicemail & Missed Call Text Back → Missed Call Text Back. Enable it, choose Customize, write the acknowledgement, preview it, and save. Review the ring timeout alongside voicemail routing.

A preview checks the copy; an actual unanswered test call checks the trigger. HighLevel may use another eligible sending number when the dialed number cannot send SMS. Check the sender and delivery record in Conversations. DND preferences apply, and these texts count toward messaging usage. Setup and sender selection.

Option 2: test a workflow with a repeat-call window

Write the intended behavior first. For example: “Send one acknowledgement and notify the team, then suppress further acknowledgements for 20 minutes.” The duration is a planning choice to validate with your team.

In Automation → Workflows, create a workflow and add the Call Details trigger. Filter for Incoming calls and the missed-call outcomes your routing actually produces, such as busy, no-answer, or voicemail. Scope it to the intended number if needed. Check call logs before choosing statuses; staff-entered dispositions are a separate filter. Call Details filters.

Proposed acknowledgement workflow
  1. Check that this contact is eligible for SMS and has not opted out.
  2. Send one acknowledgement.
  3. Notify the assigned person or create a callback task.
  4. Wait 20 minutes, then end. Send no further customer messages in this workflow.

Enable Allow Re-entry for later calls after completion. HighLevel documents that an already-active contact cannot re-enter a call-based workflow. Our design uses the final wait to hold that active state. Test rapid repeated calls before relying on it. Workflow entry settings.

For this acknowledgement-only design, leave Stop on Response off. There are no later customer messages to cancel. Ending the workflow on a reply could end the proposed waiting window early; manual removal could do the same. This is a design inference from the documented entry and exit rules, not an observed result in our account.

Make the message useful without overpromising

Hypothetical copy for a fictional service company:

“Thanks for calling Northstar Repairs. We couldn’t answer. Reply with what you need help with, and our team will follow up during business hours. Reply STOP to opt out.”

Replace the company name and state hours the team can meet. If callers should choose a callback slot, add your actual booking link after checking its mobile experience. Avoid promising an immediate response when no one is available. Confirm applicable messaging permissions and account registration requirements before sending.

Keep later reminders separate

If you add a reminder sequence, define separate exits for a reply, booking, and opt-out. Stop on Response applies to replies to messages from that particular workflow; it is not a universal stop switch. A reply to the initial acknowledgement must also prevent entry into, or remove the contact from, any separate reminder sequence. Test that path explicitly. Response settings.

Customer Booked Appointment covers the customer booking independently through a link; it excludes staff-created and recurring appointments. Evaluate Appointment Status for the relevant staff-booking path and calendar. Remove the contact from the specific reminder workflow, preserving the acknowledgement wait when appropriate. Customer booking trigger · Appointment Status trigger · Remove from Workflow action.

A small acceptance test before rollout

Use a phone and contact you control. Record the expected outcome, actual message count, sender, call status, and person responsible for the next action.

Keep the call, conversation, and workflow records together. Message delivery, a booked appointment, and a paid job are different outcomes; count them separately.