Outbound SMS Delivery

Plivo sends text messages through its SMS API to numbers you provide. A Beam agent triggers a message when your workflow calls for it, an order ships, an appointment nears, reads the recipient and the approved template, personalizes the allowed fields, and dispatches it within your rate and consent rules. It writes the delivery result back to the contact record. Numbers that are unverified, opted out, or in regions your policy restricts are skipped and flagged to a person, and any message outside the approved templates waits for human approval before it goes out.

Inbound Reply Handling

Replies to a Plivo number arrive as inbound messages tied to a contact. A Beam agent reads each one, classifies its intent against your rules, and acts: it updates the contact status, logs an opt-out, or answers a common question from your approved responses. It writes the exchange to the record so the thread stays whole. Messages that are angry, ambiguous, or ask something outside the agent's approved answers are routed to a teammate with the conversation attached, so a person replies where judgment or a policy call is needed.

Voice Call Triggers

Plivo's Voice API can place or receive calls and capture their outcome. A Beam agent starts a call flow when an event fits your rules, a payment fails, a lead requests a callback, then reads the result Plivo returns, answered, missed, or voicemail, and updates the record with the disposition and next step. It can schedule a retry within your limits. Calls that connect to a person needing a real conversation, repeated failed attempts, or anything touching a sensitive account are handed to a human, who takes the call rather than leaving it to automation.