Gentle reminder cadence
Send a branded reminder (email and SMS) a set number of days before due, or when a client hasn't opened the pack in 48 hours. Reminders stop the instant the pack completes.
Product · Automations
Rules that run the chase for you
Reminder cadences, exception routing, review SLAs and auto-drafted next months — every automation is visible, editable, and logged with inputs and outcome.
Gentle reminder cadence
- WhenPack issued and incomplete
- If3 days before dueClient has not opened in 48h
- ThenSend branded reminder (email + SMS)Stop when pack completes
Last run 14 min ago · every run is logged with inputs and outcome
Four rule recipes, ready to use
Start from a recipe, adjust the conditions
Every rule below ships as a starting point. Edit the trigger, conditions or actions to match how your firm actually works.
Route exceptions to the right reviewer
When a mismatch is flagged on a payroll or bank requirement for a priority client, assign it to the client's owner and post to a Slack or Teams channel automatically.
Review SLAs
If an item sits unreviewed for a set number of business days, escalate to the firm admin and log the SLA breach to the audit trail — nothing ages silently in a queue.
Auto-draft next month
When a month closes, draft the next engagement from the same template and push the signed manifest to QuickBooks Online or Xero without anyone lifting a finger.
Nothing runs invisibly
Every automation run is logged, start to finish
Automations act with the same accountability as a person: each run records what triggered it, which conditions matched, what actions fired, and when. Review SLA breaches escalate to a named admin instead of aging quietly in a queue.
- Run history is visible per rule, not buried in a generic activity feed
- Pausing a rule preserves its history — nothing is lost
- SLA breaches write directly to the immutable audit trail
FAQ
Automations, plans and logging
Automations are included on Team and Scale. Workspace covers the core workflow — intake, collection, review, handoff — without rule-based automation.
Yes. Every rule has an enabled/paused toggle, and pausing keeps its configuration and run history intact so you can turn it back on later.
Yes. Each run records the trigger, the conditions that matched, the actions taken, and a timestamp — visible in the rule's run history and included in the audit trail.
Yes, through Zapier, Make, or the REST API and webhooks on the Scale plan — trigger on engagement issued, pack complete, exception raised or month closed, and take it from there.
Beyond the built-ins
Wire automations into the rest of your stack
Zapier, Make and the REST API let you trigger on engagement issued, pack complete, exception raised and month closed — and take it anywhere from there.
See every trigger and event name on the integrations page.
Put the chase on autopilot
Start your free 7-day trial of the Team plan — automations included, no credit card required.