Skip to main content

SMS

Quick Links

Overview · Who This Is For · Navigation · SMS Logs · Check Status · Sending SMS · Permissions · Troubleshooting

Screenshots & Videos

Place real assets under /images and /videos using root paths.

📌 Why SMS?

Time-sensitive outreach when email is missed: confirmations, gate changes, and urgent notices with delivery checks and audit trails.

The SMS module lets you send one-off or bulk messages to guests and review delivery outcomes. Use the built-in status checker to refresh delivery state from your provider. No code is required.

Overview​

  • Send SMS messages to guests
  • Monitor delivery and failure logs
  • Refresh status from your provider

Who This Is For​

  • Event Admins / Managers: Monitor and audit SMS activity
  • Operators (with permission): Check delivery status on demand
  • Event > SMS > Logs (SMS Logs)

Tip: Page labels may vary slightly depending on your theme; look for “SMS Logs”.

Screenshot: SMS Logs

SMS Logs​

A paginated table showing messages sent for the event.

Columns:

  • Phone: Recipient’s number
  • Message: Text body sent
  • Created At: When SMS was created/sent (shown in user timezone; hover shows timezone)
  • Status: Last known provider status (JSON or human-readable)
  • Action: Check Status button to refresh delivery info

Behavior:

  • Pagination: 4 items per page (Next/Previous)
  • Sorting: newest first
  • Timezone: uses user preference

Check Status (Refresh Delivery)​

Click the cloud-arrow icon in the Action column.

Flow:

  1. Click Check Status on a row
  2. System queries the SMS provider using the transaction ID
  3. Feedback appears: success or error message

Possible Messages:

  • Success: “SMS status checked successfully.”
  • Error: “SMS status check failed.”
  • Error: “Transaction ID is required.”

Validation:

  • Transaction ID must exist
  • Only users with proper permission can perform the action

Sending SMS (If Enabled)​

The platform provides a simple form for sending SMS. Exact fields may vary.

Fields and Constraints:

  • Phone (required):
    • Must be valid; international format recommended (+974…)
    • No letters; only digits and "+"
  • Message (required):
    • Non-empty, concise
    • Long texts may split into multiple segments

User Feedback:

  • Inline validation errors displayed next to fields
  • On submit, log entry is created and queued for delivery

Best Practices:

  • Keep messages concise; avoid URL shorteners flagged by carriers
  • Test on small groups first
  • Respect local opt-out and SMS regulations

Permissions​

  • View SMS Logs: sms.sms-logs
  • Check Status: sms.sms-logs (button hidden if lacking permission)

Tip: If access is denied, ask an admin to adjust your role.

Troubleshooting​

ProblemLikely causeAction
“Check Status” not availableMissing permissionRequest sms.sms-logs access
Status doesn’t changeProvider hasn’t updated yetTry again later; check provider dashboard
Created At shows wrong timeTimezone preferenceSet your timezone in Preferences
“Transaction ID is required.”No transaction ID on rowVerify the message was sent via platform
Long message billed as multipleCarrier segmentationKeep messages short or accept multi-segment billing

Replace Placeholders​

  • Add real screenshots of your SMS Logs page to public/docs/images and update paths
  • Record a short video showing opening SMS Logs, clicking Check Status, reading results, and navigating pagination

Last updated: 2025-11-10