Custom message API

Your systems call the API to send a WhatsApp message with the exact content you supply, so alerts carry order numbers, names, or details from the source event. A Beam agent composes the message from record fields, applies your rule for when a WhatsApp is appropriate versus another channel, and issues the send once conditions match. When the content would include data your rule marks as sensitive, or a required field is missing, the agent holds the message and routes it to a person rather than sending an alert that is wrong or incomplete.

Delivery status

The API reports whether a message reached the recipient, so you know if an alert actually landed. A Beam agent reads that status, applies your rule, and updates the originating record to show the WhatsApp was delivered or failed. If a message fails, or the number looks invalid, the agent retries within the limit you set and then notifies a person to sort out the contact detail, so a customer never silently misses a notice everyone assumes went through fine.

Event driven alerts

Messages fire off business events such as a status change or a due reminder, tying each WhatsApp to something that happened in your tools. A Beam agent watches those events, reads the record, applies your approved rule about timing and recipient, and sends the matching alert. When an event is ambiguous, fires repeatedly, or targets a contact who opted out, the agent stops and hands the case to a person so the customer is not messaged in error or against their stated preference.