1. Overview
EONS3 allows users to create email campaigns by combining a recipient/contact list with an email template. The template can contain dynamic variables (placeholders), such as customer-specific account, phone, address, work-location, or other campaign data. During campaign setup, each required placeholder must be populated either by mapping it to a column in the recipient list or by supplying a fixed/free-form value.
When a placeholder is mapped to a list column, EONS3 retrieves the corresponding value for each recipient and generates personalized content. Before a campaign is submitted, the operator should validate the recipient list, template, mapped fields, previews, test delivery, approver, and campaign settings.
2. Prerequisites
- Access to the PG&E EONS3 environment and permission to create or review campaigns.
- An approved recipient/contact list containing valid email addresses.
- An approved email template for the intended communication.
- All data required by template placeholders, either as recipient-list columns or approved free-form values.
- Approver information when the campaign workflow requires approval.
- Seed/test recipients when a seed test is requested.
3. Key Concepts
| Concept | Description |
| Recipient / Contact List | List of campaign recipients and available data columns, including email and optional personalization fields. |
| Email Template | Predefined email content containing static text and optional dynamic placeholders. |
| Dynamic Variable / Placeholder | Template token replaced with campaign or recipient-specific data. |
| List Mapping | Maps a placeholder to a column in the recipient list. |
| Free-form Value | A fixed value entered during campaign setup when a required value is not supplied by the list. |
| Seed Test | Test delivery to selected recipients before production submission. |
| Approver | Person selected to review/approve the campaign when required. |
4. End-to-End Campaign Workflow
- Open EONS3 and start a new campaign.
- Select the required recipient/contact list.
- Select the approved email template.
- Review the email preview and identify every dynamic placeholder required by the template.
- Map recipient-specific placeholders to the corresponding contact-list columns.
- Enter approved free-form values for required fields that are not available in the list.
- Review any SMS/secondary preview or target-field section displayed by the selected template and populate all required fields.
- Configure campaign settings and add the required approver.
- Perform a seed test or direct test message when requested.
- Review campaign details, supporting data, recipient list, template, mappings, and preview.
- Submit the campaign through the normal approval/sending workflow only after validation is complete.
5. Dynamic Field Mapping
Dynamic fields are the most important validation point in this workflow. The template may contain placeholders that must be replaced before the campaign can be sent. Use one of the following methods:
- Map from recipient list: use when each recipient needs a different value. Example: account number, phone number, address, or another customer-specific attribute.
- Use a free-form value: use when the required value is not present in the selected list or when the same approved value should be used for all recipients.
Example: if a template contains an Account Number placeholder and the recipient list has an Account Number column, map the placeholder to that column. Each recipient will then receive the account number from their own row.
6. Email and SMS/Target Field Preview
Review the generated preview after mapping the dynamic fields. Confirm that placeholders are resolved correctly and that the intended customer-specific information appears in the expected locations. The source document also shows an SMS/target-field section; if the selected campaign/template exposes these fields, validate and populate them as required even when the primary campaign channel is email.
| No. | Icon | Action | Description |
| 1 | View List | Opens and displays the selected recipient list. | |
| 2 | Clone Recipient List | Create an exact copy of the recipient list for reuse. | |
| 3 | Download | Download the recipient list to your device. | |
| 4 | Deeping (Number Verification) | Verifies and validates phone numbers in the recipient list. | |
| 5 | Deduplication | Removes duplicate records, such as duplicate email addresses and phone numbers. |
7. Seed Test / Test Message
Use testing before production submission when requested or when campaign content/mapping needs validation.
- Seed Test: create/select a seed list containing the required test recipients and any data needed by the template, then send the seed test.
- Direct test: where the interface provides a direct test option, send a test email/message without creating a separate seed list.
- Validate subject, body, dynamic substitutions, formatting, links, and recipient-specific values in the received test.
- Do not treat a successful test as a substitute for final campaign/list/mapping review.
Comments
0 comments
Please sign in to leave a comment.