Feature 01 / 04
Solution
Automation for the work no one should have to do
Route, tag, escalate, and notify on intake, status transitions, time triggers, or webhook events. Compose conditions visually — but back the engine with the same predicates the API exposes.
Outcomes
Automate the boring half of triage
Most teams that adopt Helpdash automation rules in their first month shave 38 minutes per agent per day off mechanical work — assignment, tagging, escalation, and status transitions.
Feature 02 / 04
Time-based escalations and reminders with business-hours awareness
Feature 03 / 04
Webhook actions with retries, exponential backoff, and dead-letter queue
Feature 04 / 04
Test a rule against the last 100 tickets before you publish it
Inside the engine
Rules a junior agent can write, a CTO can audit
Feature 01 / 03
Visual composer
Drag conditions, pick actions, preview matches. No DSL to learn; every rule serialises to JSON for git review.
Feature 02 / 03
Dry-run sandbox
Run a draft rule against your last 100 tickets and see exactly which would match, what would change, and what would fire.
Feature 03 / 03
Safe retries
Webhook actions retry with exponential backoff and surface failures in a per-rule dead-letter queue you can replay manually.
FAQ
Frequently asked questions
Can I write rules in code instead?
Yes — every rule is also addressable via the REST API. Teams managing rules in version control can sync from a repo using the Helpdash CLI.
What triggers are available?
Intake (new ticket), status change, assignment change, time-based (e.g. 24h since last reply), incoming webhook, and CSAT score received. Triggers can stack with AND/OR conditions.
Is there a rate limit on actions?
Soft limit: 1,000 rule actions per minute per workspace. Above that we batch and rate-limit gracefully — you'll see a warning, not a silent drop.
Publish your first rule in five minutes
Automation is included on the Pro plan. Sandbox a rule against your live tickets before it ever fires.