Voice SMS campaigns: a recorded call with a defined purpose
Voice SMS is commonly used to describe outbound dialling that plays a recorded message when a call is answered. It is a call workflow, not a text message delivered to the SMS inbox. Brainguru scopes voice campaigns around the message purpose, authorised audience, recording, retry policy and the action the recipient can take.
A useful campaign might communicate an approved reminder or invite a permitted response. The correct setup depends on the use case and access provider. This page explains the brief and acceptance checks; it does not promise unrestricted calling, universal network reach or a fixed completion rate. See cloud telephony for the wider communications system.
Select voice when the next action suits a call
Voice can be considered where a spoken message helps the audience understand a short instruction and the contact is eligible for that communication. For a message someone needs to keep and read later, a suitable SMS alert may be preferable. For a person initiating a keyword enquiry, short code messaging is a different task. Do not combine all channels into one campaign without explaining their separate purposes.
Define the action: listen to an announcement, request a callback, respond with a keypad input where supported, or reach an available team. If no next action is required, reporting should reflect that. A keypad response should not be labelled a purchase or completed service request unless the downstream process actually confirms it.
Prepare the audience and permission record
Document why each recipient is eligible for the message, its category and the applicable permission or preference record. An existing relationship should not be treated as unlimited permission for every promotion. Keep suppression and opt-out handling current and avoid purchased or unverified lists that the sender cannot justify.
Confirm the applicable number resources, registration, calling conditions and automated-call requirements with the access provider before launch. TRAI’s commercial communication guidance describes unsolicited calls and messages, consent and customer preferences. An auto-dialler or prerecorded voice does not remove those requirements.
Approve the recording as a user journey
- Identify the sender and explain the reason for the call early.
- Use a short message with an unambiguous action; keep detailed terms available through the approved follow-up route.
- Check pronunciation, numbers and names in each language with competent reviewers.
- Match the stated keypad action to the actual routing configuration, where keypad response is supported.
- Check the recording on a representative phone connection, not only through studio headphones.
Do not place sensitive account or health information in a recording that could be heard by someone else answering the phone. If personalised content is required, agree the authentication and disclosure boundary first. A language label should come from appropriate recipient information, not a guess based solely on the city being called.
Illustrative reminder: an appointment needs confirmation
An eligible recipient receives an approved appointment reminder. If the configured service supports a keypad request for staff contact, the campaign records that response and sends it to the assigned queue. The staff team confirms the appointment or resolves a change request. The campaign should stop redundant retries after the relevant outcome, subject to the agreed provider behaviour.
This example is a proposed workflow, not a customer result. A connected call may reach voicemail, the wrong person or someone who hangs up immediately. The report should preserve those limitations instead of calling every connection a successful confirmation.
Retries and handoffs need an operating plan
Set a bounded retry policy with the provider, including when to stop and which outcomes permit another attempt. A missed call is not always evidence of a busy recipient. Record opt-outs and staff-completed actions before the next run to avoid repeating a message after the request has been resolved.
A transfer or callback option should have an available owner, queue capacity and an outside-hours route. Agree what happens if the receiving team is unavailable. CRM and automation can preserve the campaign, response and staff outcome; API integration may be needed for approved event-triggered reminders.
Read the report without confusing technical delivery and business results
- Attempted: the dialler initiated an attempt; repeated attempts should be visible.
- Answered or connected: the provider reported a connection, which does not necessarily identify the intended person.
- Listen duration: useful operational evidence where supported, not proof of comprehension.
- Response: a keypad action or callback request recorded by the configured system.
- Confirmed outcome: the responsible team completed the intended appointment, service or sales step.
Compare campaigns using consistent denominators and account for duplicate numbers and retries. Report failed and abandoned interactions, opt-outs and unresolved staff handoffs. A longer recording or more retry attempts can increase usage charges without improving the recipient’s experience.
Checks before a wider run
Test a correct answer, no answer, immediate hang-up, duplicate number, unsupported keypad response, unavailable staff queue and a revoked permission. Verify the caller identity and recording version, supported coverage and billing interpretation. Confirm that the run can be paused and that the team can trace an individual response without exposing the whole contact list.
Bring the approved recording, audience eligibility basis, desired response, language requirements and receiving team to a voice campaign consultation. Costs depend on provider terms, call duration, attempts, routing and integration. Review promotional messaging and two-way SMS when a different channel fits the action better.
Frequently Asked Questions
Is voice SMS a text message?
No. The term commonly describes an automated outbound call that plays a recorded message. SMS text messaging and inbound keyword messaging are separate channels.
Does a connected call mean the intended person heard the message?
Not necessarily. A connection can reach voicemail, another person or an immediate hang-up. Separate connection, listen evidence, responses and confirmed staff outcomes.
Can every existing customer be called for any promotion?
No. Review the message purpose, recipient eligibility, applicable consent or preferences, suppression and provider requirements. A customer relationship is not blanket permission for unrelated campaigns.
What should a callback or keypad option include?
Confirm provider support, the actual routing configuration, queue ownership, operating hours and the fallback when staff are unavailable. Record the resulting staff action separately from the keypad response.
What determines the campaign cost?
Provider rates, duration, attempts and retries, number resources, supported response options, integration and support. Request a scope that explains how technical call outcomes are billed.