Questions you probably have.

Only for playbooks you've explicitly marked autopilot. Every other action lands in your briefing as a draft to approve. The default everywhere is copilot.

A few foundational ones: signup, activation moment, key feature use, session return, subscription events. ChurnLoop will tell you on day one which ones it wants more of — most setups take an hour.

No. Global hard caps: max 2 messages per user per week, quiet hours per timezone. Every email includes a one-click unsubscribe, and opted-out users are permanently excluded from all future outreach. You can tighten the caps further.

ChurnLoop is opinionated about SaaS lifecycle work — trial, activation, expansion, churn. If you're shipping subscription software with an event stream and email, you're the target. Marketplaces and e-com are a roadmap item, not a fit today.

Yes — always, in copilot mode (the default). Every draft lands in your morning briefing for review. Read it, edit if needed, then tap approve. Nothing sends without your sign-off. In autopilot mode you've pre-approved the approach for that playbook, but you can review or undo any recent send from the audit trail.

On Scale, yes — bring an Anthropic or OpenAI key and we'll route completions through it. On Growth, we manage the inference for you with no usage caps.

Every decision is in the audit trail. You can rewind, undo recent actions per user, and report any specific reasoning that was off — that example feeds your workspace's tuning, not the underlying model.

Not today — ChurnLoop is a managed service. On Scale plans, we offer a continuous Postgres + S3 mirror so you always have your own copy of your data.