AUTOMATION RULES

When something changes, the right thing happens.

Your agent runs the conversation. Rules keep the record behind it — tag a new contact, set a field, start a sequence, or notify you the moment a tag, field, or date changes. Set the rule once; it fires once per contact, and never spams.

RULE · RUNS ITSELFWHEN
Tag added — abandoned-cart
DO
Add tag — warm-lead
Subscribe to sequence — Cart nudge
Notify you — a note in your Inbox
FIRES ONCE PER CONTACT · 30S THROTTLE · NO LOOPS
POSITIONING

Your agent talks. Rules keep the record.

Your agent handles the conversation — reading what a customer means, answering from your catalog, closing the sale. You would never script that. Rules handle the other half: the housekeeping every one of those conversations leaves behind. A contact gets tagged, a field changes, a renewal date comes due — and the right follow-up should just happen. That is not a conversation to design. It is a rule to set. The agent is smart on purpose; rules are exact on purpose.

The one operator both halves run for
THE OLD WAY

The old way: tag it by hand, or bury it in a flowchart.

Without rules, the housekeeping falls on you. You tag contacts by hand, try to remember which lead needs a follow-up, and export a spreadsheet to find whose trial ends this week. Or you wire it into a flow builder — where this logic gets tangled into the same canvas that runs your messaging, and one burst of updates can fire the same action over and over.

  • ✕You tag and update contacts by hand — or forget, and your segments rot.
  • ✕The follow-up that should fire on a status change waits until you remember it.
  • ✕Finding whose renewal is due this week means exporting a spreadsheet and eyeballing dates.
  • ✕In a flow builder, with no throttle, ten quick edits fire the same action ten times.
Everyday busywork — the tagging and sorting rules automate away
HOW IT WORKS

When an event happens, do these actions.

A rule is one sentence: when this happens to a contact, do these things. Pick the event you are watching for, list what should happen, and HyperDM runs it on every matching contact — in order, the moment it fires. There is no canvas to maintain and nothing to check by hand.

01

Pick the trigger

a new contact, a tag, a field, or a date.

02

List the actions

tag, set a field, start a sequence, notify you. They run in order.

03

It runs itself

every matching contact gets the actions, once each, automatically.

TRIGGERS

Five triggers. Everything that happens to a contact.

Rules listen for the events that already happen as your agent works — nothing extra to wire up. Narrow a rule to one specific tag or field, or fire on any.

01TRIGGER 01

New contact

someone messages you for the first time. Tag them by source and start a welcome sequence.

02TRIGGER 02

Tag added

a tag lands on a contact, like vip or abandoned-cart. Subscribe them to the sequence that should follow.

03TRIGGER 03

Tag removed

a tag comes off a contact. Pull them out of the sequence it was keeping them in.

04TRIGGER 04

Field changed

a custom field's value changes. Re-segment, sync a status, or notify you.

05TRIGGER 05

Date field

a date you store on the contact, like a renewal or a birthday. Fire on the day, or a set number of days before or after — checked once a day.

ACTIONS

Then it does the work — in order, automatically.

Stack as many actions as a rule needs; they run top to bottom every time it fires. The vocabulary is the same one your sequences use, so nothing is a special case.

01ACTION 01

Add a tag

create it if it is new, then tag the contact. Segment as things happen.

02ACTION 02

Remove a tag

take a tag off to move a contact out of a segment.

03ACTION 03

Set a field

write a value to any custom field, like status = churned.

04ACTION 04

Subscribe to a sequence

drop the contact into a live nurture or follow-up by name.

05ACTION 05

Unsubscribe from a sequence

pull them out the moment they should not get more.

06ACTION 06

Notify you

HyperDM leaves a note on the contact's thread in your shared inbox, so a human sees it. Not an email or a text; a note where the conversation already lives.

07ACTION 07

Start a flow

if you've built a flow, a rule can trigger it. A power-user option, not the point.

GUARDRAILS

Guardrails so it never spams a contact.

Automation that fires twice is worse than none — it messages a customer again, tags them again, and erodes the trust your agent just built. HyperDM ships the guards that keep a rule exact, so your lists stay clean and no one hears from you twice.

ONCE PER CONTACT30S THROTTLENO LOOPS
✓Fires once per contact — by default a rule runs at most once for a given contact, ever. No repeat messages, no repeat tags.
✓30-second throttle — a burst of updates on the same contact collapses into one firing, so ten quick edits don't fire the same action ten times.
✓Can't loop — a rule's own actions never trigger other rules, so rules can't chain into a spam storm.
✓Under-delivers, never double-delivers — HyperDM records the firing before it acts, so a mid-way failure won't re-run and message twice.
✓Every firing logged — you get the receipts on which rule fired, for which contact, and when.

The honest FAQ.

No. Your agent handles conversations — reading intent and answering from your catalog — and you never script that. Rules handle the record behind the conversation: the predictable housekeeping, like ‘when a contact is tagged vip, subscribe them to the vip sequence.’ You are not drawing a conversation; you are setting one ‘when this, do that’ rule that runs on every contact, once each.
No, and there are guards for exactly that. A rule fires once per contact by default, so it can't repeat. A 30-second throttle collapses a burst of updates on the same contact into a single firing. And a rule's own actions never trigger other rules, so rules can't chain into a loop. HyperDM also records a firing before it acts — so if an action fails halfway, it under-delivers instead of messaging twice. Need one to run every time? Turn off once-per-contact for that rule and the throttle still protects you.
Triggers: a new contact, a tag added or removed, a custom field changed, or a date field like a renewal or a birthday. Actions: add or remove a tag, set a field, subscribe or unsubscribe a sequence, start a flow, or notify you — a note on the contact's thread in your shared inbox, not an email or a text. You can stack several actions on one rule, and they run in order.
Date rules run on a once-a-day sweep in UTC. Point one at any date field you store — a renewal, a trial end, a birthday — and set it to fire on the day, or a set number of days before or after, say three days before a renewal. Mark it yearly and it fires once each year on that month and day. It's a daily check, so it's the right tool for reminders and follow-ups, not to-the-minute timing.

Set the rule once. Get the hour back.

Every conversation your agent closes leaves a trail worth acting on — a tag, a field, a lead to follow up. Rules turn that trail into the next action instead of a note you'll get to later. Live in under 10 minutes, free for your first 50 conversations a month, no credit card.

Get started freeNO CARD · LIVE IN 10 MIN · CANCEL ANYTIME