Bulk SMS campaigns

Campaigns in Textlocal push one message to many recipients. A Beam agent builds the recipient set from your rule, prepares the message, and queues the campaign where account permissions allow it. It respects opt-out lists and sending windows before anything goes out. Routine campaigns to a known, approved segment can proceed on their own. New audiences, changed wording, or unusually large sends are held for a human to sign off, so no mass message leaves until someone has checked both the list and the copy against your approved standards first.

Contact list segments

Textlocal organizes recipients into lists and groups. A Beam agent reads incoming replies and delivery signals, applies your rule, and moves contacts between segments, adding a new opt-in or retiring a dead number. Clean, unambiguous updates happen automatically. Where a number looks invalid or a contact appears on conflicting lists, the agent flags it for a human to resolve rather than guessing. It keeps a note of every change so the team can audit how a list was built, which matters when campaign reach and compliance are both on the line.

Reply handling and opt-outs

Inbound replies and opt-out keywords come back through Textlocal. A Beam agent reads each reply, applies your rule to classify it, and acts, recording an opt-out, tagging interest, or drafting a response for a follow-up. Stop requests are honored at once and the contact is suppressed from future sends. Simple replies are handled without review. Messages that read as complaints, questions, or anything ambiguous are routed to a human with the thread attached. This keeps the marketing list clean and compliant while a person handles the rest.