How to Add SMS Follow-Ups to ViciDial Campaigns
Plan a ViciDial-to-messaging integration with explicit triggers, eligibility checks, reply routing, and protection against duplicate sends.
Adding an SMS follow-up to a ViciDial campaign should start with a defined event and an approved purpose. A completed call, a requested appointment confirmation, and a failed contact attempt are different events. Sending the same automatic message after all of them can create confusing or unwanted contact.
The design below is an integration pattern, not a claim that every ViciDial installation includes a ready-to-use SMS workflow. Confirm the capabilities of your installed version and existing messaging tools before choosing an approach.
Pick one useful trigger
Start with a customer-requested action, such as sending the details of an agreed callback. Specify which campaign and outcome can trigger the message, which fields are required, and when the send should be cancelled.
Do not use every unanswered call as automatic permission to text. Have the responsible team approve the audience, message purpose, contact permissions, and timing rules for the campaign.
Write the trigger in operational terms. “Send the confirmed callback time once after this call attempt” is testable. “Follow up with interested leads” leaves the timing and eligibility undefined.
Connect through supported interfaces
ViciDial publishes a Non-Agent API reference, but available functions and access depend on the installed version and configuration. Check the documentation shipped with your deployment and use supported interfaces for the data your workflow requires.
A middleware service can receive or retrieve the approved event, validate it, and request a message through the chosen provider. Avoid assuming that a generic API example can be copied into every dialer setup without authentication, field mapping, or operational review.
Keep provider credentials on the server. Give the integration only the permissions it needs and log failures without exposing secrets or unnecessary customer data.
Create a send record before contacting the provider
Store the lead identifier, call-attempt identifier, trigger, destination, template version, and planned send time. Use a stable business-event key to prevent the same event from producing two requests.
Recheck eligibility immediately before sending. A scheduled message should not go out after the person opts out, the appointment changes, or a human agent cancels the follow-up.
Handle uncertain API outcomes carefully. If a request times out, do not immediately assume that the provider rejected it and send another copy. Reconcile the result using the provider's supported tracking tools and your own send record.
Choose a sender that can support the workflow
Confirm messaging availability, target-country support, and any required registration with your provider. An existing SIP trunk or voice DID does not establish that its number can send and receive business SMS through the service you selected.
For US local-number application messaging, review A2P 10DLC requirements. Document who owns the sender account and where delivery errors will be monitored.
Route replies back to a responsible team
Configure inbound messages to reach a shared queue or case workflow. A reply such as “Can we do tomorrow instead?” must update the appointment process rather than disappear into an unattended webhook log.
Preserve enough context to identify the original request, but avoid matching solely on the customer's number when several lead records could apply. Keep messaging events separate from the final sales disposition unless the workflow explicitly authorizes a change.
Read two-way SMS handling for assignment and shift-handoff considerations.
Pilot the complete loop
Test the triggering event, successful send, customer reply, cancellation, opt-out, repeated event, and provider outage. Confirm that failure recovery cannot create a burst of duplicate messages when service returns.
Track provider acceptance and delivery separately using the available message status callbacks. Then measure whether the follow-up produces the intended customer action rather than simply counting texts sent.
Contact HiDial with your ViciDial version, current provider, and proposed trigger to discuss a limited implementation plan.