Feature · Workflow automation
Compose workflows from real building blocks: signal triggers, approval-gated emails, tasks, durable waits, branches that check live data, A/B splits, and a goal that ends the workflow the moment it succeeds. Every step logged, every outcome provable.
Quick answer
Exeechain workflow automation lets CS teams build custom workflows that start from real signals (failed payments, new customers, renewals, churn risk), hold every customer-facing email for human approval, branch on live account data, and complete themselves when a defined goal is met. Conditional and reply-aware workflows start at $999/mo; Command ($2,999/mo) increases capacity. Every step reports entered / through / dropped from the run log.
Last updated · Pricing and feature claims reviewed against publicly listed sources.
What it is
Most workflow tools were designed for marketing: maximize sends, measure opens. Retention work is the opposite. The customer is already paying you; every touch is a withdrawal from a trust account. So Exeechain's workflows are opinionated in four ways that matter to CS teams: every customer-facing email is held for your approval before it sends; branches evaluate the account's live status, not a snapshot from enrollment; autonomous sends respect quiet hours in your workspace timezone; and every journey can carry a goal condition that completes it the moment the outcome is achieved, so nobody gets a “checking in!” email three days after they already renewed.
Under the hood the runtime is durable: waits survive restarts and deploys, retried webhooks never double-enroll a customer, and each step executes exactly once with an idempotency key. Those three properties are what a workflow needs when it is touching real paying customers over days and weeks: a restart must not lose a wait, a retry must not enrol somebody twice, and a step must not run twice.
How it works
Step 01
Start from the starter library, build in the visual builder, or tell the Copilot 'win back customers whose renewal is 60 days out' and review its draft. Blocks: signal and segment triggers, approval-gated emails, tasks, Slack alerts, durable waits, branches (nestable), deterministic A/B splits, and a goal exit. Dry-run the whole graph on a real customer before enabling.
Step 02
Payment failed, customer created (with a backfill guard for imports), NPS detractor, champion departure - or continuous segment enrollment like 'renewal within 90 days' anchored to the actual renewal date. Enrollment dedupes automatically: a retried webhook or re-run sweep never starts a second journey for the same customer.
Step 03
Drafted emails wait in your queue; approved sends go out, autonomous ones respect quiet hours. Every step shows entered / through / failed from the run log, goal-met runs count as conversions, and recovered revenue is only booked when your billing provider confirms it.
Why it matters for NRR
The most damaging automation is the one that keeps messaging after the problem is solved. Goal-aware workflows complete themselves on recovery, so your best save never turns into an annoyance.
Renewal runway, onboarding, payment rescue and win-back workflows run for every matching customer simultaneously - the coverage a CS team of ten would provide, operated by one person approving drafts.
56 entered, 41 through, 6 booked a call: per-step counts turn 'we have a renewal play' into 'here is exactly where accounts drop out of it'. You fix the step, not the vibe.
Frequently asked
Customer success workflow automation means multi-step workflows that run without manual effort: a real signal (a failed payment, a new customer, a renewal approaching, churn risk crossing a threshold) enrolls the customer, and the workflow then executes a sequence of emails, tasks, waits, and branches. In Exeechain, workflows are goal-aware: you define the outcome (payment recovered, risk back under 40) and the workflow completes itself the moment it's true, so nobody keeps receiving messages after they've already converted.
Marketing automation optimizes for volume of sends; customer success workflows optimize for retained revenue, which changes the design. Exeechain's workflows hold every customer-facing email for your approval by default, check live account status at each branch (not a snapshot from when the workflow started), respect quiet hours so no customer is emailed at 3am, and stop the moment their goal is met. Outcomes are counted against billing data, not opens and clicks.
By default, no. Emails drafted by a workflow are held in your approval queue; you review and click send, or veto. The draft is written from the account's own data (name, plan, champion, the signal that fired) rather than a static template. Internal actions like tasks, Slack alerts, and score refreshes run without approval since they never touch the customer.
Real-time signals: payment failed, customer created (with a backfill guard so importing 2,000 existing customers never fires 2,000 welcome emails), NPS detractor, champion departure, cancel intent. Plus segment triggers that continuously enroll customers matching a filter: plan, MRR band, churn-score band, or renewal within N days anchored to the actual renewal date. Manual enrollment is always available.
Yes. Every run gets a stable 0–99 split value, so a single branch step (for example, split under 50) routes half your runs down each path. The assignment is deterministic per customer: a crash, retry, or restart never flips which arm someone is in mid-journey. The per-step funnel then shows each arm's volume and drop-off so you can compare outcomes.
Three layers. Each workflow can carry a goal condition, and runs that meet it are counted as conversions with the exit reason recorded. Every step shows its funnel (entered, through, failed) straight from the durable run log. And revenue outcomes follow Exeechain's verification rule: a save is only booked when it's confirmed against your billing provider, never estimated from activity.
Multiplier ($999/mo) includes up to 10 workflows with 12 steps each, branches and reply waits. Command ($2,999/mo) includes up to 100 workflows with 50 steps each. Drafts count toward capacity. Enterprise supports custom capacity with bounded execution and retries. Preview a journey before enabling it; Free previews use the sample book.
Related features
Churn prediction
0–100 score, daily refresh, ranked by revenue
Customer health score
AI score with the three drivers explained
QBR automation
A quarter's deck, in about a minute
Retention playbooks
3 prebuilt, plus your own - AI-drafted per customer
Copilot
Plain-English Q&A grounded in your data
Revenue forecast
A 90-day number you can defend
First scores in 15 minutes. Every connected signal read within 24 hours. Branches and reply waits on Multiplier ($999/mo); higher workflow capacity on Command ($2,999/mo).
Not ready to switch? Size your leak from your MRR and churn rate, with no billing access at all.