Who this article is for: Org/City Users
Overview
After communications are sent, SwiftComply tracks delivery status for each recipient. You can monitor whether emails were delivered, failed, or are still pending. This article also covers how duplicate suppression stops an automated communication from generating twice for the same assembly within a compliance cycle.
Before you begin
You must be logged in as an Org/City user with permissions to view communications
Communications must have been generated and sent (or scheduled for automated send)
Communication delivery statuses
Each individual communication log tracks its delivery status. For email communications, SwiftComply receives delivery events from the email service provider and updates the status automatically.
A letter or postcard has no automatic delivery tracking — it stays Pending until someone marks it sent after printing and mailing, which moves it to Sent. That is as far as a physical communication goes; it never reaches Delivered.
Status | What it means |
Pending | The communication has been generated but not yet sent |
Sent | The communication has been dispatched for delivery |
Delivered | The email was accepted by the recipient's mail server. Email only — there is no delivery confirmation for letters or postcards. |
Error | The email could not be delivered — it bounced or was dropped before sending (invalid address, a full mailbox, or a previous failure to that address). The reason reported by the email service is stored with the communication. |
Viewing sent communications
Where to look depends on how the communication was created. Automated (auto-generated) communications and one-time (ad hoc) communications are easiest to find on the assembly or location they were sent for. Batch communications are also grouped on their batch.
From an assembly or location record (automated and one-time communications)
The Communications tab on an assembly or location lists every communication sent for that record — automated reminders, one-time (ad hoc) communications, and any batch communications that included it.
Open the assembly or location.
Click the Communications tab.
Each communication is listed with its Communication Type, Communication Template, and Sent On date.
Click a communication to open it.
From the batch page (batch communications)
Go to Communications and open the Communication Batches report.
Click the batch you want to review.
The Communications table lists each communication in the batch with its contact, location, contact method, and sent dates.
Click a communication to open it.
From the Communications reports
On the Communications page, the Communications with Errors report lists communications across your program that are in Error, and the Unsent Communications report lists communications that have not been sent yet.
From the Communications dashboard widget
Add a Communications List table widget to your dashboard to monitor recent communications across your entire program.
Tracking email delivery
For email communications, delivery tracking happens automatically:
SwiftComply sends the email through its email provider.
Delivery events are reported back to SwiftComply automatically.
The communication log is updated with the current status — Delivered if the recipient's mail server accepted it, Error if it bounced or was dropped.
💡 If an email bounces, check the contact record for the recipient. The email address may be invalid or the mailbox may be full. Update the contact and resend if needed.
Marking letters and postcards as sent
For physical mail (letters and postcards), delivery tracking is manual:
On the batch page, click Request Download, and download the letters when the download is ready.
Print and mail the letters.
Under Download Requests, click Mark As Downloaded, then Update Comms to Sent. This moves every communication in that download to Sent.
Click Mark Completed to close the download request.
To mark every unsent letter in a batch as sent in one step, click Mark All Letters Sent on the batch page. For a batch that includes postcards, the button reads Mark All Postcards Sent.
To mark a single letter or postcard as sent, open the communication, open the contact it was sent to, and click Mark as Sent.
Duplicate communication suppression
To stop recipients receiving the same automated reminder too frequently, SwiftComply applies a suppression window to automated communications.
How it works
The rule applies only to automated communications generated during the daily system run. It does not apply to batch or one-time (ad hoc) communications.
Once an automated communication is generated for a specific assembly or location, the same Communication Type will not generate again for that record until the suppression window has elapsed. For a template that sends before a due date, the window is the template's own period: a template with a 30-day period suppresses regeneration for 30 days, and a template with a 90-day period suppresses for 90 days. Other templates use a 65-day window.
After the suppression window expires, if the record still meets the template criteria (for example, a test is still due), the system generates the communication again and a new suppression window begins.
The system checks all published templates every day.
Suppression is tracked by Communication Type name
Suppression is based on the Communication Type name, not on the individual template. 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 suppression window.
Avoid renaming an existing Communication Type. The type's name is its identifier, so renaming it rewrites that name on every historical communication that used it — those records then show the new name rather than the one they were sent under. Create a new type instead.
What happens if you change the Communication Type
Assigning a different Communication Type to a template is what breaks suppression tracking. Because the suppression records reference the old type name, the system regenerates communications for every record currently inside the active window.
Which records are inside that window depends on how the template is triggered:
Before due date (for example, "30 days before") — records with a due date 1 to 30 days from now.
After due date (for example, "7 days after") — records whose due date was 7 to 14 days ago, because a 7-day buffer is built in.
How to resend before the suppression window expires
Option | When to use | Details |
Batch communication | For a larger group of records | Create a batch targeting the specific records. Batch communications are not subject to suppression. |
One-time (ad hoc) communication | For individual records | Send directly from the assembly or location. Ad hoc communications are not subject to suppression. |
New Communication Type | When every record in the window needs a fresh communication | Create a new type, clone the template, assign the new type, publish, and unpublish the old template. |
📝 If a batch communication uses the same Communication Type as a scheduled template, sending it will reset the suppression window for those records. To avoid this, use a different Communication Type for the batch.
What happens next
Use delivery tracking to monitor your outreach and follow up on failed emails. For recurring communications, knowing how the suppression window works helps you plan your communication schedule and avoid unexpected duplicate sends.
FAQ
An automated reminder didn't send. Why?
The same Communication Type was already generated for that record inside the suppression window — the template's own period. Wait for the window to expire, or send a batch or ad hoc communication, neither of which is suppressed.
Duplicate communications were generated. What caused that?
A different Communication Type was assigned to the template, which breaks suppression tracking and regenerates communications for every record in the active window. Clean up the duplicates manually, or submit a support request for a bulk cleanup.
An email shows as Error. What does that mean?
It bounced or was dropped — usually an invalid address or a full mailbox. There is no separate "Bounced" status; a bounce is recorded as Error, with the reason from the email service stored alongside it. Open the communication to read the reported reason, update the contact's email address, and resend.
I cloned a template and it's still being suppressed.
Cloning does not change the Communication Type, and suppression is tracked by type name. Assign a new Communication Type to the clone if you need it to send immediately.
The suppression window isn't the length I expected.
For "before expiration" templates the window matches the template's configured period. For "after" templates and other trigger types, a 65-day fallback applies. Adjust the period setting on the template to change it.
Why can't I just rename a Communication Type?
The name is the type's identifier rather than a separate ID, so renaming it rewrites that name on every historical communication that used it. Those communications then show the new name instead of the one they were sent under. Create a new type instead.