Inbound message routing

Each WhatsApp message that arrives through UltraMsg triggers a Beam agent to read the sender number and text, match it against your routing rules, and assign the conversation to the right queue or owner. Known contacts get their existing record updated with the new message; unknown numbers get a stub record created where permissions allow it. Messages with unclear intent, complaints, or anything your rules mark sensitive are passed to a human agent with the full thread, so a person handles the reply rather than an automated response going out unchecked.

Templated reply sending

UltraMsg sends messages on your behalf through its WhatsApp gateway. A Beam agent drafts a reply from your approved templates, fills in the contact's details, and sends it once the trigger and rule conditions are met, then writes the sent message back to the conversation log. Replies that fall outside the approved template set, or that involve pricing, refunds, or legal wording, are queued for a person to review and release. This keeps routine acknowledgements automatic while judgment-heavy answers stay under human control at all times.

Delivery status tracking

UltraMsg reports whether a message was sent, delivered, or read. A Beam agent reads these status callbacks and updates the matching conversation or campaign record so your team sees current delivery state. When a message fails repeatedly, or a number reports as invalid, the agent applies your retry rule and, if it still fails, flags the contact for a person to check. Bulk failures above a threshold you set are escalated to an operator, who decides whether to pause sending before more messages go out.