Skip to content

How to Customize Automation Timing and Cooldowns

Open a trigger under Texty > Notifications > Automations to change its rules. These may include a wait, reminder limit, cooldown, threshold, or product choice. Save the change and create a matching test event. Then check the send time in Texty > SMS Logs.

Texty Order recovery automation showing the Failed or pending payment recovery trigger with Delay before sending and Maximum reminders fields

Each rule controls a different part of the send process.

RuleWhat it controls
DelayHow long Texty waits after the event before sending
Maximum remindersHow many messages the same order can receive
CooldownHow long Texty waits before sending the trigger again to the same person
ThresholdThe minimum value an event must meet before it can send
Product choiceWhich item Texty names when an order has several products

Not every trigger has all these rules. Use only the fields shown inside the trigger you are editing.

  1. Go to Texty > Notifications > Automations.
  2. Find the trigger you want to change.
  3. Select the trigger row to open its settings.
  4. Change the delay, limit, cooldown, or other rule.
  5. Check the unit, such as minutes, hours, or days.
  6. Save your changes.
  7. Create a matching test event.
  8. Check the result in Texty > SMS Logs.

What are the default timing and control settings?

Section titled “What are the default timing and control settings?”
TriggerFieldDefaultWhat it controls
Failed or pending payment recoveryDelay before sending10 minutesWait after a failed or pending payment
Failed or pending payment recoveryMaximum reminders1Messages allowed for the same order
On-hold payment reminderDelay before sending24 hoursWait after an order goes on hold
On-hold payment reminderMaximum reminders1Messages allowed for the same order
Price dropMinimum drop to notify1%Smallest price cut that can send an alert
Review requestDelay before sending5 daysWait after the order is complete
Review requestProduct to ask aboutHighest-value itemProduct named in a multi-item order
Customer note addedMaximum note length280 charactersPoint where Texty cuts a longer note
License or download expiryDays before expiry7 daysHow early the first reminder sends
License or download expiryAlso notify on expiry dayOffWhether a second alert sends on the expiry date
Win-back or lapsed customerDays since last order90 daysGap before a customer becomes eligible
Win-back or lapsed customerCooldown between win-backs180 daysWait before another win-back to that person
Replenishment or reorderCooldown between nudges30 daysWait before another nudge for the same person and product
Low or out of stockSend to store numbersEmptyStore phone numbers that receive stock alerts
Low or out of stockAlso alert on out of stockOffWhether Texty sends a separate zero-stock message

Back in stockFirst-order welcome, and Security alert have no timing field. They send when their event happens.

Some fields do not set a wait. The note length caps long text. The price rule checks if the price cut is large enough.

Start with the defaults. Change a rule only when your store needs a new value.

  • Give payment systems enough time to finish before sending a recovery SMS.
  • Ask for a review after customers have had time to use the product.
  • Use longer cooldowns when products are bought less often.
  • Set a price threshold that reflects a real change, not a rounding update.
  • Keep reminder limits low until your tests show a clear need for more.

Change one rule at a time. This makes the result easier to check.

Use a test order, product, customer, and phone number that you control.

  1. Save the new rule.
  2. Record the time when you create the event.
  3. Wait until the saved delay has passed.
  4. Open Texty > SMS Logs.
  5. Check the log time and final message.
  6. Repeat the event if you need to test a limit or cooldown.
  7. Confirm that Texty skips the extra send when the rule blocks it.

For a long delay, test on a staging site or with a safe test account. Do not shorten a live rule if real customers may meet it during the test.

Success check: The first SMS sends at the expected time, and Texty blocks extra messages after the saved limit or during the cooldown.

What happenedWhat to check
It sent too soonCheck the saved delay and its time unit.
It has not sent yetConfirm that the full delay passed and the trigger is on.
A price alert did not sendMake sure the price cut met the minimum percentage.
A review request names the wrong itemReview the product choice setting.
A repeat message is missingCheck the maximum reminders or cooldown.
Too many messages were sentLower the limit, raise the cooldown, and test again.
A stock alert went to the wrong phoneReview each number in the store phone list.

No. A delay appears only on triggers that support one. Other triggers run when their event or threshold is met.

What is the difference between a cooldown and a reminder limit?

Section titled “What is the difference between a cooldown and a reminder limit?”

A cooldown controls the gap between messages. A reminder limit controls the total number allowed for the same event or order.

Does changing a delay affect messages already sent?

Section titled “Does changing a delay affect messages already sent?”

No. It changes future sends. Test the saved rule with a new event so the result is clear.

Why is the store phone list inside the timing reference?

Section titled “Why is the store phone list inside the timing reference?”

It sits with the low-stock trigger’s control fields. The list chooses store recipients, while the other toggle controls zero-stock alerts.

Please follow the remaining guides to make the most out of Texty.