Reference · The Veto

When BHASM says no.

1 in 6 messages BHASM drafts are stopped, not delayed. The veto is the mechanism behind BHASM's central belief: the relationship is worth more than the message.

What the veto is

A held message is not a queued message. It is not a delayed message. It is a stopped message. The system decided that sending this customer this message right now would do more harm than the value of any potential response.

The veto operates after the engine has drafted a message and selected a channel and a send window. Every law and every signal layer that affects the customer is consulted one final time. Any single failure stops the send.

The hold is logged. The reason is logged. The law cited is logged. The founder can review every held message in the decision log — there is no hidden suppression.

The four veto categories

1Governance violation

If any layer of the governance stack fires, the send is blocked. No overrides. Not even by the founder — the dashboard surfaces the held card so the founder can see it, but the Send button is gone.

Example. Customer has an open complaint logged in your CRM. BHASM drafts a re-engagement message. The sentiment safeguard fires — complaint + promotional outreach is always wrong. Message held.
Example. Recent BHASM messages received no response. The frequency limit fires. The relationship needs quiet; another message would deepen the imbalance.
2Sentiment veto

BHASM reads the last customer-facing interaction for negative sentiment. A reply that said “please stop messaging me” — even without a formal opt-out — triggers an extended silence hold across all channels.

The system reads tone, not just flags. Phrases like “not interested”, “leave me alone”, “wrong number”, “take me off the list” all trip the veto even when the customer never clicked an unsubscribe link.

Why it matters. Compliance unsubscribe is a legal floor. Sentiment veto is the ethical ceiling. Most retention tools treat them as the same. BHASM does not.
3World signal suppression

A disruption event in the customer's geography suppresses sends. Floods, riots, political events, market shocks — BHASM consults the world intelligence layer before every send.

Example. A pre-holiday gifting message scheduled to a city where a major natural-disaster event hits the day before — flood, wildfire, hurricane, earthquake, regional shutdown. BHASM holds every send to that city until the disruption signal clears. Sending into a crisis is brand damage that no campaign can recover.
Example. A SaaS renewal nudge to a B2B customer in a quarter where their industry just had a major regulation announcement. World signal: industry shock. Send held until context clears.
4Relationship debt

BHASM tracks the running balance of messages sent versus responses received per customer. Where outreach has exceeded responses — the system has reached out repeatedly without a reply — more messages are held, not fewer.

This is counter to what every other retention tool does. Most tools accelerate when there is no response. BHASM slows down. Silence becomes the action.

How it works. As the imbalance between outreach and response grows, urgency is progressively reduced and silence floors lengthen. The system requires more time to pass before attempting contact again — not less.

What a held message looks like

The founder sees every held message on the dashboard, with the reason and the layer cited.

Kim Linh Nguyen
Held · reengagement candidate
Held. Recent outreach received no response. Frequency limit triggered. Re-evaluate after the silence floor clears.
Layer cited: Frequency limitCycle: overdueChannel: WhatsAppWait: silence hold

The Send button is absent. The Edit button is absent. Only Why? and Disagree (Scale+) remain. The founder can see exactly what BHASM saw and decided not to do.

Why the veto is the product

Every other retention tool optimises for the same thing: more sends.

More sends = more engagement (their assumption). The metric is volume. The unit is the message.

BHASM optimises for the opposite: relationships preserved. Fewer wrong sends. Stronger long-term retention. The metric is dignity. The unit is the customer.

The veto is the mechanism by which this difference becomes structural rather than aspirational. Anyone can promise “intelligent send timing.” Only BHASM commits to not sending.

The product claim
Every competitor sends. BHASM sometimes does not. That is the product.

The hold record

Every held message is logged in the decision log with full citation.

Available on the dashboard under Decisions — every hold shows the customer, the message that was drafted, the reason for the hold, the law cited, and the recommended wait period.

The transparency is the trust signal. BHASM never silently suppresses. It tells you exactly what it decided not to do and why — so you can either agree (most of the time) or override (Scale tier and above, with logged justification).

No black box. No surprise. Just discipline, made auditable.