Transactional SMS sending

BulkGate sends SMS messages such as order confirmations, appointment reminders, or one-time codes to a phone number anywhere it has coverage. A Beam agent sends a message when a trigger fires, such as an order status change or a scheduled reminder, filling in the approved message template with the relevant details. It reads the send result to confirm the message reached the carrier. Numbers that are invalid, unreachable, or in a country the account is not set up to send to are routed to a person instead of retried repeatedly.

Delivery status tracking

BulkGate reports whether a message was delivered, failed, or is still pending with the carrier. A Beam agent reads that delivery status after sending and updates the related record, such as marking an order notification as confirmed sent or flagging a failed delivery for a fallback channel. Where delivery fails for a reason the agent recognizes, like an invalid number format, it can apply the agreed rule, such as trying an alternate contact method. Repeated or unexplained failures for the same contact are routed to a person to check the underlying contact record.

Contact list management

BulkGate stores contact lists used for sending campaigns, and a Beam agent can read and update these lists as records change elsewhere, adding a new contact when a customer opts in or removing one when they unsubscribe. It applies the rule the customer has approved for keeping lists current, such as syncing opt-out requests from a support system into the SMS contact list within a set time. Contacts with incomplete numbers or conflicting opt-in status are held back and sent to a person before any message goes out to them.