Skip to content
Verbatik

Test and monitor

Fix Flows, campaigns and undelivered SMS

Check activation, scheduling, consent, calling gates and carrier outcomes.

A lead did not receive a call

Start with the specific Flow run or Dialer campaign, rather than importing the contact again.

  1. Confirm the Flow is published/active or the campaign has been started. A saved draft does not enroll a contact or dial.
  2. Check the trigger and segment rules, contact phone number, selected published voice agent and source phone number.
  3. Review the schedule, timezone, calling window, wait step and next run time. A ten-second delay is a scheduling instruction, not a delivery guarantee during a blocked or paused state.
  4. Check recipient permission, consent, do-not-call and suppression state.
  5. Inspect the recorded step/run error and calling limits.

Outbound calling requires platform activation, an eligible account and a configured source number. A saved SIP connection must be ready for calling; a number pending release cannot be used. If a disabled-calling or billing error is displayed, ask Verbatik to review account activation. Do not remove consent safeguards to make a run progress.

SMS is blocked or not delivered

A voice number or SIP trunk is not automatically an SMS sender. Use a messaging-capable customer Twilio number with the required messaging configuration, permissions and registration. SMS must also be enabled for the platform/account.

Check the selected recipient and sender, opt-out state and a fully resolved message body. A placeholder left as {{variable}} can block a Flow text. A carrier opt-out rejection stops the text; do not resend it from another sender to bypass the recipient's choice.

Distinguish the application submission from the carrier's final delivery result. Sent is not necessarily Delivered. Review failure or undelivered status and the carrier error. If the outcome is uncertain, inspect the existing message record before making a new attempt. The system intentionally avoids automatically resending a possibly completed Flow text.

A later branch did not run

Inspect the actual call outcome, branch condition and completed steps. A paused/cancelled Flow, changed permission, redacted call or a caller's request to stop can prevent follow-up. Correct a draft and publish deliberately; do not assume an existing run silently adopts a new graph.

Frequently asked questions

Can I force a “busy” result to send SMS? Only if the configured branch matches that outcome and all sender, account and recipient checks pass.

Can forwarding my clinic number enable SMS? No. Voice forwarding and SIP routing do not establish messaging capability.

Continue with Deploy Flows, Dialer campaigns and SMS setup.

Verbatik documentation · Updated November 5, 2026