Draft first, then eligibility
The team drafts message content, and VehicleDesk checks that the customer, shop, channel, workflow, and provider are all ready before the message sends.
Eligibility is deterministic
Consent, suppression, shop and channel flags, feature approval, provider readiness, and workflow rules run as application checks on every send.
Tests stay separate from customer sends
Draft and internal test states verify content and rendering. Provider acceptance and final delivery record as later, separate states.
Blocked means visible
A blocked send shows its reason without exposing credentials or customer secrets. The Compliance workspace keeps consent, suppression, contact-point, and policy evidence in view.
Worked example: a blocked send
A staff member drafts an SMS to a customer. Before it sends, the eligibility checks run against that contact point.
The channel is suppressed for that customer, so VehicleDesk blocks the send and shows the reason without exposing credentials or customer secrets.
The team records the outcome and, where the customer allows it, reaches them another way that is eligible.
Checklist: message-safety essentials
These four checks prevent most compliance surprises.
- Consent and suppression are checked on the contact point, not only the customer
- Draft, internal test, provider acceptance, and delivery are separate states
- A blocked send shows a reason the team can act on
- Opt-outs propagate to the contact point immediately
Common questions
No. Eligibility is deterministic. If a contact point fails consent, suppression, channel, provider, or workflow checks, the message does not send, and the reason is shown on the record.
More guides
Other safety guides
Review contact compliance before every send
Read consent, suppression, contact-point, policy, provider, and manual-call evidence on the record before a customer hears from the shop.