Give Shinobi an outcome, not a campaign
A mission is a goal in your words, a moment that matters from your real order history, and guardrails that protect the relationship. Today missions plan in dry run: you see exactly who would be engaged and who was protected, before anything sends. Autonomous sending ships next.
Moments computed from real order history
Missions do not guess who to talk to. They watch the order data your store connection already imports and surface the moments worth acting on.
The reorder moment
Customers whose order was fulfilled about N days ago, and you pick N. The follow-up, the review ask, the reorder nudge, timed to the delivery instead of the calendar.
The gone-quiet moment
Customers whose last order is older than N days. The win-back moment, caught while there is still a relationship to win back.
Rules that protect the relationship
Proactive outreach is only welcome when it is considerate. Every mission carries guardrails that are checked per person, on the day.
Never mid-problem
Anyone with an open or pending case is held back automatically. Nobody gets a reorder nudge while they are waiting on support.
Never right after a conversation
Anyone who talked to your team in the last N days is held back. You pick the cooldown, up to 90 days.
Every name has a why
Every planned engagement carries the signal that matched it, and every suppression names the guardrail that held it back.
See the plan before anything sends
Arm a mission and the control panel audits it live: who Shinobi would engage today and why, and who its guardrails protected and why. Computed live from real data, never stored, never sent.
What is live and what is next
Missions ship in the open, and this page updates the day the next piece does, not before.
Live today: missions with goals, signals and guardrails, audited in dry run against your real customers and orders.
Ships as its own wave: armed missions start sending, exactly where the dry-run audit shows. Nothing sends from a mission today, and the console says so.