Platform and texting FAQ

Short answer: A campaign defines an audience, message, sender, destination, timing, and reporting context for a group of messages.

Short answer: A sendable campaign needs a valid recipient list plus the required sender, content, destination, and scheduling data for its type. The composer identifies missing or invalid fields.

Short answer: It sends the configured message to the eligible audience once, immediately or at the scheduled time.

Short answer: It sends when configured customer or system events meet its rules, rather than launching one fixed audience once.

Short answer: The composer can exclude contacts messaged today or in the last 48 hours, 72 hours, or 7 days. The selected exclusion is applied while building the audience.

Short answer: Blackleaf stops eligible queued work and changes campaign status. Messages already handed to a carrier, in transit, or delivered cannot be recalled.

Short answer: Some data can remain editable, but changes cannot rewrite messages already submitted to carriers. Pause when appropriate, verify what remains, and test revisions.

Short answer: It sends the current rendered message to the test recipient and reports server delivery data such as status, sender, recipient, body, image, link, and cost when available. It does not launch the campaign.

Short answer: It validates content against Blackleaf’s current checks. A pass does not guarantee carrier acceptance, delivery, or legal compliance.

Short answer: Counts change when lists, exclusions, subscription state, phone validity, duplicate resolution, or source customer data changes.

Short answer: Draft is not launched; scheduled waits for send time; sending is processing; paused halts eligible queued work; completed finished processing; stopped was ended. Individual messages can have different outcomes.