Skip to content
Help Center
Submit a request Sign in

Send useful SMS notifications from a case workflow

An SMS notification can draw attention to a time-sensitive support event when the right person needs a short, actionable alert. Use it for a defined operational purpose, such as notifying the approved on-call contact that a high-impact case needs review. The message should explain what to do next and point to the normal support record; it should not become a second, incomplete case history.

At a glance

For: support operations administrators coordinating approved mobile alerts. Applies to: Supportbench Core.

Start here: Settings → Configuration → Workflows → Actions

Check readiness and the alerting agreement  ·  Understand the recipient and sender controls  ·  Configure a narrow case alert  ·  Write an alert that leads to the right action  ·  Verify delivery and negative cases  ·  Example: an approved on-call escalation alert  ·  Troubleshoot missing or repeated SMS

Check readiness and the alerting agreement

The SMS action depends on a configured, ready SMS client. Relevant integration fields may be hidden when that capability is unavailable, and execution also checks readiness. If the fields are absent, have the administrator responsible for SMS configuration verify availability; creating a workflow does not provision a provider or a sending number.

Agree the recipient population, the situations that justify an interruption and who follows up if nobody responds. Use customer mobile details only for the support purpose and consent/contact practices your organization has established. Confirm the actual number rather than copying an unrelated telephone field.

  • Identify the event and conditions that make the alert useful.
  • Choose approved recipients and a controlled test number.
  • Confirm the provider sender and delivery arrangement with its owner.
  • Check the current provider/account pricing and delivery limitations separately; this guide does not establish a per-message price.
  • Keep private diagnostic detail, credentials and unnecessary personal information out of the message.

Understand the recipient and sender controls

Control or behaviorWhat it means
Send to the Case contactIncludes the case Contact only when selected and that Contact has a mobile number. It does not automatically notify every contact at the Company.
Additional mobile numbersExplicit extra numbers, entered as a comma-separated list. They are trimmed and deduplicated during sending.
SMS messageThe nonblank message to send. A configured notification requires message text and an intended recipient selection/number.
SMS senderA compatibility field may appear in the workflow editor, but the current workflow delivery path uses the configured host/provider sender. Do not rely on this field to override the sending number.

The Case contact and additional-number list solve different problems. A customer status alert may use the intended Case contact; an internal on-call alert may use an approved explicit recipient. Review them together so the same rule does not accidentally send internal wording to the customer. Duplicate-number handling is not a substitute for reviewing the recipient list.

Configure a narrow case alert

  1. Open Settings → Configuration → Workflows with workflow administration permission. Open or create the intended rule.
  2. In Details and Trigger, choose a clear purpose, active state, priority, Case scope and the appropriate event.
  3. Use Requirements, Conditionals and any necessary Exclusions to define when interruption is justified. Avoid a rule that alerts on every ordinary case update.
  4. In Actions, review the SMS notification controls. Select Send to the Case contact only when the customer contact is an intended recipient.
  5. Enter any approved Additional mobile numbers as a comma-separated list. Confirm each destination outside the workflow editor before testing.
  6. Write the SMS message. State the purpose and next action briefly. Use only variables verified for the selected notification context, and inspect the actual expanded result.
  7. Review the configured provider sender with its owner, then save and reopen the workflow. Perform a controlled delivery test before relying on it.

Write an alert that leads to the right action

A useful internal alert identifies the support event and where the recipient should review it. For example: “Priority support review needed. Open the linked case, confirm ownership and record the next customer update.” Include a verified case reference using the supported workflow variable mechanism where applicable.

Avoid declaring a root cause or promising a resolution time that has not been verified. A text message should not contain a long transcript or a credential. The intended recipient should use their own authorized access to the case for the full record.

An alert is not a completed handoff

Sending a message does not prove that someone received it, read it or accepted ownership. Your team still needs an acknowledgement and follow-up process. Keep the case owner and next action explicit.

Verify delivery and negative cases

  1. Use an approved test case and controlled recipients. Confirm the selected event and conditions match.
  2. Trigger the actual event and check that the intended recipient receives the expected message from the configured provider sender. Inspect substituted text and any case link.
  3. Test a case without a Contact mobile number. The Case-contact option alone cannot supply a missing destination.
  4. Test a nonmatching case and confirm it does not generate the alert.
  5. Inspect whether other workflows or repeated updates generate additional messages. Stop processing applies to the current matching pass; it does not prevent every later event.
  6. Record the workflow, test event, non-secret outcome and delivery verification. If delivery is uncertain, inspect the case and available provider diagnostics before repeating the event.

Example: an approved on-call escalation alert

A B2B support team has a defined specialist escalation process and an approved on-call contact. A narrowly scoped Case workflow sends an internal SMS when the relevant event and conditions match. The wording asks the recipient to review the case and acknowledge the handoff through the normal support process.

The duty lead verifies ownership and the next customer update rather than assuming the SMS completed both tasks. Review false alarms and missed acknowledgements after the shift. The operational benefit is timely attention with a clear next step; it is not a guarantee of delivery, response or resolution.

Troubleshoot missing or repeated SMS

ProblemWhat to check
SMS controls are missingConfirm the configured SMS client is ready and the selected scope/action supports the feature.
The customer did not receive a messageCheck the recipient toggle, saved Contact mobile number, matching event/conditions and provider delivery result.
The sending number differs from the editor fieldCurrent workflow delivery uses the configured host/provider sender. The workflow SMS sender field does not override it.
Several messages arriveInspect multiple matching rules and later Updated events. Refine the event and conditions.
A field value appears literallyThe placeholder may not be supported in this context. Use the current variable reference and test expanded output.
The provider reports failureGive the configuration owner the non-secret event/time and delivery diagnostics. Do not paste provider credentials into the case.

Was this article helpful?