Topics:
What Is Duplicate Communication Suppression?
To prevent property owners and testers from receiving repeated reminders too close together, SwiftComply automatically limits how often the same automated communication can be sent.
Once an automated reminder is generated for a specific assembly or location, the system will wait 65 days before generating that same type of reminder again.
This is called the 65 day suppression window.
How the 65 Day Rule Works
The rule applies only to automated communications generated during SwiftComply’s daily system run.
Once a reminder is generated, that same Communication Type will not generate again for that assembly or location for 65 days.
After 65 days:
If the record still meets the criteria (for example, a test is still due),
The system will generate the reminder again,
And a new 65 day window begins.
The system re-checks all published templates every day.
Example
You have a reminder set to generate 90 days before a test due date.
An assembly enters the 90 day window.
The reminder is generated.
For the next 65 days, the system will not generate that same reminder again.
After 65 days, if the test is still due and qualifies, the reminder will generate again.
Suppression Is Based on Communication Type
Suppression is tracked by Communication Type, not by individual templates.
This means:
If multiple templates share the same Communication Type, they share the same suppression tracking.
Cloning a template without changing the Communication Type will NOT bypass the 65 day rule.
How to Send a Reminder Again Before 65 Days
If you need to resend a communication before the suppression window expires, you have two options:
Option 1: Create a New Communication Type (for automated regeneration)
Create a new Communication Type with a unique name.
Note: Only one template per Communication Type with matching targeting can be published at a time.
If you publish a new template, any existing published template with the same type and identical targeting will be automatically unpublished. However, two templates of the same Communication Type with different targeting can both be published simultaneously.
Unpublish the current template.
Assign the template to the new Communication Type.
Republish the template.
This resets suppression tracking because the system treats it as a new type.
Option 2: Use Batch or Ad Hoc Communications
If you only need to resend for specific records:
Use an Ad Hoc communication (for individual records), or
Use a Batch communication (for larger groups)
Batch and ad hoc communications are not affected by the 65 day suppression rule.
Note: If a batch communication uses the same communication type as a scheduled template, sending it will reset the 65 day window for those records. To avoid this, use a different Communication Type for batch communications.
Editing a Published Template
If a template has already sent communications and you need to change the subject line or message content, you must create a new template (cloning is recommended).
This keeps your historical communication records accurate and intact.
Things to Note
The 65 day suppression window is a system wide setting and cannot be customized.
Avoid renaming Communication Types. Renaming will update historical records and logs.
If you need a new version, create a new type instead (for example: “First Notice v2”).The suppression rule applies only to automated communications generated during the daily run.
FAQ: Duplicate Communication Suppression
Why didn’t my automated reminder send again?
If the same Communication Type was generated within the last 65 days for that assembly or location, the system will suppress it until the 65 day window expires.
Does cloning a template bypass suppression?
No. Suppression is tracked by Communication Type. If the cloned template uses the same Communication Type, it will still be suppressed.
How can I resend a reminder before 65 days?
You can:
Create a new Communication Type and republish the template, or
Send a batch or ad hoc communication (these are not suppressed).
Does the 65 day rule apply to batch communications?
No. The rule only applies to automated communications generated during the daily system run.
Can the 65 day window be changed?
No. The 65 day suppression window is a system wide setting and cannot be modified.