Campaigns & Communications
Run time-bound member campaigns and send structured communications with forms and signatures.
Campaigns
Create time-bound member campaigns with ordered steps and uploaded assets, then publish updates to the member portal. Campaigns can also include key messages, ownership details, linked agreements, participating suppliers, and audience scope.
A campaign has a required start date and an optional end date. Its member-facing state is derived from those dates.
Campaign fields
| Field | What it does |
|---|---|
| Title | Names the campaign members see. |
| Slug | Provides the campaign's URL-friendly identifier. |
| Summary | Gives members a short description of the campaign. |
| Long description | Provides the full campaign context and details. |
| Start date | Determines when the campaign becomes active. |
| End date | Determines when the campaign moves past its active period. This field is optional. |
| Campaign code | Identifies the campaign for internal reference or member workflows. |
| Key message | Highlights the primary message members should understand. |
| Owner contact | Identifies the person or team responsible for the campaign. |
| Linked agreements | Connects the campaign to relevant agreements. |
| Participating suppliers | Lists the suppliers involved in the campaign. |
Campaigns can also define an audience by region or company ID. Use the audience scope to control which member companies can see the campaign.
Campaign steps
Add steps to present the campaign in a defined order. Each step can include supporting campaign assets such as documents or images.
Campaign assets support up to 10 files, with a maximum size of 50 MB per file.
Campaign states
| State | When it applies |
|---|---|
UPCOMING | Before the start date. |
ACTIVE | On or after the start date and before the end date, when an end date exists. |
PAST | After the end date. |
Publishing and notifications
Campaigns move through a publication lifecycle:
- Draft: The campaign is being prepared and is not published.
- Scheduled: The campaign is set to publish at a defined time.
- Published: Members can access the campaign according to its audience scope.
- Archived: The campaign is no longer active for member use.
Members can subscribe to campaign updates and unsubscribe when they no longer want notifications. When you update a published campaign, subscribed members receive a notification. The person who makes the edit is excluded from that notification.
Use notify-preview to review the notification before sending it. Use notify to send the campaign update to subscribers through the available notification channels.
Review the campaign audience, ordered steps, and assets before publishing. Members see the published content according to the campaign's configured audience scope.
Communications
Send structured messages from HQ to members when you need acknowledgements, choices, signatures, or tracked responses. A communication includes a message body, an audience, optional form fields, and response status for each member.
Communication fields
| Field | What it does |
|---|---|
| Title | Names the communication members receive. |
| HTML body | Defines the formatted message content. |
| Due date | Sets the date by which members should respond. |
| Target companies | Selects the member companies that receive the communication. |
| Notified roles | Selects the roles within the target companies that receive the communication. |
Communications also preserve the audience and brand context used for delivery. This information is frozen when you send the communication.
Form fields
Add form fields when you need members to provide structured responses. Communications support these field types:
- Text: Collects a written response.
- Choice or options: Lets members select from defined options.
- Signature: Collects a member signature.
A communication can contain a maximum of one signature field. Assign a unique ID to every form field so responses can be tracked reliably.
Attachments
Add one attachment to a communication when members need supporting material. Attachments can be PDF, image, or office files and must not exceed 10 MB.
| Feature | Limit |
|---|---|
| Campaign assets | Up to 10 files, 50 MB per file |
| Communication attachment | 10 MB |
Sending and freezing
Use send-preview to review the communication and its audience before sending. Preview the message, form fields, attachment, target companies, and notified roles before you confirm delivery.
Confirm the audience, notified roles, form fields, and brand presentation before sending. Sending freezes the audience, target companies, roles, and brand snapshot, and you cannot edit the communication afterward.
After sending, members see whether their response is pending or answered. Use the pending status to identify members who still need to respond.
Responses and export
After delivery, you can:
- Re-notify members who have not responded.
- View individual sends and delivery records.
- View submitted responses.
- Export responses as a CSV file.
- Render a branded response PDF for each member company.
Use response exports for analysis or follow-up workflows. Use the member-company PDF when you need a formatted record of an individual company's response.
Duplicate and archive
Duplicate a communication when you need to reuse its structure, form fields, or message content for a new audience or event. Review the copied audience and due date before sending the duplicate.
Archive communications that no longer need active management. Archiving preserves the communication record without leaving it in the active working set.