Cadence Conditions
All cadence conditions are divided based on the Object they are related to. Below is the list of all Objects and Cadence Step Conditions with a short explanation for each and tips for best practice.
Customer-level Cadence Conditions
Cadence Condition | Communication is triggered |
---|---|
Customer is created | after the customer record has been created. To have the communication triggered, the customer must be created with cadence assigned automatically upon customer creation. Tip: To achieve this, select the Default Cadence. Default Cadence is automatically applied to all new customers. Without a default cadence, customers must be assigned to a cadence manually. To choose a default cadence, click the Star icon next to the cadence. |
Customer updates a payment method | when a customer updates a payment method on file. |
Customer’s balance exceeds threshold | when a customer’s outstanding balance is greater than the specified amount (set the amount threshold under the cadence condition settings). |
Oldest Invoice exceeds threshold | when a customer’s oldest invoice has a Past Due status for a specified number of days (set the number of days under cadence condition settings). |
Before Credit Card expires | before the credit card expiration date. |
After Credit Card expires | after the credit card expiration date. Tip: We consider the Credit Card expiration date as the last calendar day of the expiration month. For example, a credit card's expiration date may read as 11/26, which means the card is active until the last day of November 2026 |
After a Cadence is assigned | after the cadence is assigned to the customer. |
After Last Contacted date | after the last message sent date. You may find a field Last Contacted on the Customer Record page. Tip: The date value for Last Contacted field is used for triggering communication. |
Before the next Auto Charge | before the next Auto Payment date. You may find a field Next Auto Charge on the Customer Record page. Tip: The date value for the Next Auto Charge field is used for triggering communication. |
Auto–payment schedule is created | when an auto-payment schedule is created. |
Auto–payment schedule is cancelled | when an auto-payment schedule is cancelled. |
Invoice-level Cadence Conditions
Cadence Condition | Communication is triggered |
---|---|
Invoice is created | after the invoice has been created. |
After the Invoice Date | after the invoice date. |
Before the Due Date | before the invoice due date. |
After the Due Date | after the invoice due date. |
Before Expected Date | before the invoice expected date. |
After Expected Date | after the invoice expected date. |
Invoice is updated | when the invoice has been updated, either in AR Automation or in your accounting system. |
Invoice is fully paid | when the invoice has been fully paid. |
Cadence conditions that trigger statements
To trigger a statement to be sent out to a specific customer, you must select at least one of the following Statement Cadence Conditions as the cadence applied to your customers.
Cadence Condition | Communication triggers a statement |
---|---|
Day of month | on a specific day of the month. |
Invoices are due | when the customer has a specific number of invoices in a Past Due status. |
Invoices are created | when the customer has a specific number of invoices created. |
Tip: For the Invoices are due and Invoices are created steps, you can set the number of invoices in their respective cadence condition settings. These conditions trigger communication once a day, as long as the customer account meets cadence condition rules.
Payment Cadence Conditions
To trigger communications related to payment, you must select at least one of the following Payment Cadence Conditions as the cadence applied to your customers. If the payment cadence condition is applied to the invoice only, communication will not be triggered.
Cadence Condition | Communication is triggered |
---|---|
Payment Declined | when an auto payment with any payment method is declined. Tip: Communication is not triggered for payments attempted via the Customer Portal manually, as the shopper will see a decline response directly on the Customer Portal. |
Payment Receipt | when payment is processed successfully (when payment status is Succeeded). |
Payment Authorized | when ACH payment is successfully attempted. ACH payment has a status of Authorized. |
Before Payment Due Date | before payment due date. This is only for payments based on a Payment Plan Payment. |
After Payment Due Date | before payment due date. This is only for payments based on a Payment Plan Payment. |
Payment Plan Cadence Conditions
To trigger communications related to Payment Plan payments, you must add a Payment Plan cadence condition to the Payment Plan. If the Payment Plan cadence condition is only applied to the customer/invoice, communication will not be triggered.
Cadence Condition | Communication is triggered |
---|---|
Past Due Payment exceeds threshold | when the oldest Payment Plan payment has a status of Past Due for a specified number of days (set the number of days under cadence condition settings). |
Subscription Cadence Conditions
To trigger communications related to subscriptions, you must add at least one of the following Subscription Cadence Conditions to the cadence applied to your customers.
Cadence Condition | Communication is triggered |
---|---|
Subscription is created | after the subscription has been created. |
Subscription is updated | after the subscription has been updated. |
Subscription is cancelled | after the subscription has been cancelled. |
Subscription is paused | after the subscription has been paused. |
Before next renewal | before the subscription renewal date. |
After next renewal | after the subscription renewal date. |
Before next service period starts | before the next service period start date. |
After next service period starts | after the next service period start date. |
Before next service period ends | before the next service period end date. |
After next service period ends | after the next service period end date. |
Before subscription ends | before the subscription end date. |
After subscriptions ends | after the subscription end date. |
Quotes Cadence Conditions
To trigger communications related to quotes, you must add at least one of the following Quotes Cadence Conditions to the cadence applied to your customers.
Cadence Condition | Communication is triggered |
---|---|
Quote is created | after quote has been created. |
Quote not viewed | after quote has not been viewed for a specific number of days. |
Quote is Pending | after quote has a status of Pending for a specific number of days. |
Prospect Cadence Conditions
To trigger communications related to Prospects, you must add the following Prospect Cadence Conditions to the Cadence applied to your prospects.
Cadence Condition | Communication is triggered |
---|---|
Prospect is created | after the prospect record has been created. To have the communication triggered, prospects must be created with a cadence assigned automatically upon prospect creation. The Default Cadence is automatically applied to all new prospects. |
Other Cadence Conditions
Cadence Condition | Communication is triggered |
---|---|
Day of month | on a specific day of the month for all customers who have a cadence with this condition assigned. This is useful for bulk email dispatch, such as sending an email on the first day of every month. |
On a particular day | on a particular fixed date, such as like sending an email on November 1st, 2026. |
Updated 6 months ago