Validate the full path: a genuinely missed incoming call, eligibility checks, a configured delay, a final check before sending, a neutral acknowledgement and an assigned owner. A reply or completed callback should stop follow-ups that are no longer useful.
1. Define the problem you want to solve
Review a few recent missed calls. Do they happen during jobs, over lunch or after closing? Who calls back today? Start with requests that have no owner rather than the number of texts you could send.
An acknowledgement can let callers explain what they need and when they can be reached. It does not confirm an appointment, technician availability or emergency service. The wording and any timing you announce must reflect how your business actually operates.
Illustrative example: a heating business receives a call during an installation. A text invites the caller to describe the request. Someone in the office reads the reply and arranges the next step. This example assumes no sales result.
2. Verify the phone system and number
Before setting up an automatic missed-call text for your business, confirm that the system can identify a completed call and its outcome. Transfers, call queues and voicemail can be classified differently across phone systems. A ringing event alone does not establish that nobody answered.
Check both the number receiving calls and the number sending texts: sending and receiving capability, displayed identity, access to replies and any provider permissions required. Ask whether your existing number can be used and whether a connection or number transfer is needed. Do not assume every existing line is compatible.
Define how withheld, invalid or SMS-ineligible numbers will be handled. An incoming call alone does not prove that a text will be delivered. If sending fails, create a review or callback action under your process instead of retrying indefinitely.
Ocliq’s current HVAC page describes missed-call text follow-up as an option depending on configuration. That confirms the proposed use case, not activation in your account or compatibility with every carrier.
3. Write the rule before enabling it
Describe the rule in plain language: “For an incoming call that ended without being handled, on an approved line, check exclusions, wait the configured interval and send only if the request has not already been addressed.” Have that rule mapped to what your system actually supports.
The delay is a setting to test with your team. It needs to allow a reliable event to arrive and account for a colleague calling back quickly. This guide does not claim a proven optimal delay. Include opening hours, the time zone and holiday exceptions.
Immediately before sending, check again whether a colleague has called back, the customer has replied elsewhere or a conversation is already active. That second check helps prevent an absence message after someone has taken care of the request.
| Situation | Intended behaviour | Check |
|---|---|---|
| Answered call or completed callback | Do not send a missed-call text | Updated status before sending |
| Eligible missed call | One acknowledgement and an owner | Line, context and permissions verified |
| Repeated event or closely spaced calls | Limit redundant messages | Call identifier and duplicate-handling rule |
| Reply received or active conversation | Hand over to a person; pause the sequence | Monitored inbox and assigned task |
| STOP, refusal or ineligible number | Exclude the relevant messages | Status shared with other follow-ups |
| Delivery failure | Flag the failure without a retry loop | Appropriate human action |
This checklist describes intended behaviour. Available conditions, event synchronization and stopping rules need to be tested in your configuration.
4. Keep the message focused on the call
Identify the business clearly and invite a simple reply. Keep discounts, promotions and long service lists out of this first message. Do not ask for card details, access codes or sensitive information by text.
CRTC guidance explains that whether a message is commercial depends in part on its content and purpose. Commercial texts are subject to applicable consent, identification and unsubscribe requirements. Do not treat a missed call as general marketing permission.
Have the context, permissions and final wording checked before activation. The templates below are acknowledgement examples, not messages certified as automatically compliant. The official CRTC reference checked on October 31, 2026 is linked in this section.
CRTC: frequently asked questions about Canada’s Anti-Spam Legislation ·
5. Templates during and after business hours
Replace every variable and use only information your team can keep current. Hours must match the actual calendar. Any stated opt-out process must work, and replies must reach a monitored inbox.
These messages promise neither an immediate callback nor a guaranteed service visit. If your business handles urgent requests, define a separate, verified procedure. Do not imply that this text inbox is monitored around the clock.
During business hours
Hello, this is [business]. We were unable to answer your call. You can briefly describe your request and let us know a suitable time to reach you. Our team will review your message during business hours. This text does not confirm an appointment. To stop receiving texts, reply STOP.
After closing
Hello, this is [business]. You called outside our business hours: [days and hours, time zone]. You can leave a brief description of your request here. Our team will review it when we next open. This inbox is not continuously monitored, and this message does not confirm a service visit. To stop receiving texts, reply STOP.
6. Assign the conversation and stop at the right time
Name a responsible person or team and a backup. A task can include the caller’s number, call time, relevant line and follow-up status. After a reply, add the stated need and next action without creating multiple records for the same person.
A reply should pause automated follow-ups related to the call so someone can read it. A completed callback, an already handled request, a refusal or STOP should also trigger the appropriate exit rule. Verify this before launch; having a CRM does not automatically provide this behaviour.
If the person reports an urgent situation, follow your business’s escalation procedure and service limitations. An automated message does not replace human assessment. If nobody can handle replies, fix ownership before adding automated sends.
7. Test exclusions and duplicate handling
Run tests on a designated line and test contacts with informed participants. Cover an answered call, a missed call, a transfer, voicemail, two closely spaced calls, a reply before the message is sent and a STOP request.
A repeated technical event for the same call should not create a second text. For several calls from the same person, define a duplicate-suppression window and re-entry rule suited to your work. Suppression must not hide a new request from the team: it limits sending, not visibility.
Also test an exceptional closure, an ineligible number, a failed send and an already active conversation. Compare expected and observed outcomes. Where a condition cannot be automated reliably, provide a human check and document the limitation.
8. Measure whether requests are handled
Separate incoming calls, genuinely missed calls, calls eligible for a text, sent messages, delivered messages where that status is available, replies and handled requests. A sent text proves neither receipt nor lead qualification.
Track requests without an owner, time to the first human action and agreed appointments. Define a qualified request for your business: an understood need, a serviceable area and a relevant next step, for example. No conversion rate is guaranteed.
In your review, also examine failures, prevented duplicates, stop requests and messages sent after a callback. These checks let you improve the process before expanding its use.
9. What to verify in an Ocliq demo
Ocliq describes centralized enquiries, SMS, tasks and follow-up depending on configuration. Bring your current phone setup and ask to see the whole path from a missed call to a customer reply and an assigned task.
Confirm the triggering signal, sending number, reply routing, business hours, duplicate handling and stopping rules after a reply or STOP. Ask about limitations, potential phone or SMS costs and required connections. Do not assume an integration is included or already active.
The right setup fits your ability to handle requests. If the phone trigger is unavailable, a callback and task process can still be useful while text-follow-up feasibility is assessed.
Organize incoming requests
Frequently asked questions
Can I keep my existing number?
That depends on the provider, SMS capabilities and connection method. Have the specific number checked before deciding on a transfer or another approach.
How long should the system wait after the call?
Choose a configurable delay that accounts for the final call outcome and your team’s process, then test it. This guide recommends no universal delay.
What if the customer calls several times?
The rule should prevent repetitive texts while keeping calls visible. Confirm the suppression window and re-entry conditions for your configuration.
Is this already enabled in Ocliq?
The site presents the use case depending on configuration. That does not establish that it is active in your account. A demo and testing should confirm the complete path.
Check the right configuration for your business
Bring your current phone setup, business hours and the name of the person handling replies. We can review the missed-call workflow and what needs to be validated for Ocliq.