Claim before calling
Reserve the message in a persisted state before the external action begins.
✓ Concurrent workers and restarts see the same delivery authority.DELIVERY RECONCILIATION
A timeout is uncertainty—not permission to send again.
The most dangerous send failure is not a clear rejection. It is a lost response after the provider may already have acted. Nolina fails closed until the outcome is known.
THE OPERATING FAILURE
Automatic retry turns provider ambiguity into duplicate outreach.
Network timeouts, rate limits, and 5xx responses do not prove that no action occurred. Nolina separates proven non-delivery from an unknown outcome.
PRODUCT CONTRACT
One model, enforced at every decision boundary.
The controls below are product behavior, not a checklist an operator must remember to rebuild in every campaign.
Classify the response
Separate confirmed success, proven pre-action failure, and ambiguous outcome.
✓ Only proven non-delivery can return to an eligible state.Reconcile with the provider
Ask what actually happened instead of inferring from a lost response.
✓ Unknown outcomes remain visible and auditable.Escalate when proof is unavailable
Move irreducible uncertainty to human review.
✓ The system prefers a missed touch to a duplicate touch.Suppressed → stopUnknown send → reconcileAmbiguous reply → review
WHAT TO MEASURE
Judge the workflow by outcomes and guardrails.
- ✓At-most-once dispatch policy
- ✓Visible uncertain delivery state
- ✓Provider-specific reconciliation
- ✓Human review for irreducible ambiguity
A STRONG FIT WHEN
Your outbound motion has something valuable to protect.
- The sending provider does not guarantee idempotency
- A duplicated invite or email damages trust
- Workers can restart during active delivery
- RevOps needs evidence of what actually happened
RUN A REAL SEGMENT
See how this operating model behaves on your market.
Define the target segment, evidence rules, channel, exclusions, and success measure before execution begins.
Request a pilot scope