Customized Messaging Guide
Complete guide to customizing notification templates, branding, and messaging in the 24/7 system
📝 Overview
The Customized Messaging feature allows HCM administrators to personalize the content, branding, and appearance of most notifications sent from the 24/7 system. This helps you maintain consistent branding and tailor messages to your company's communication style.
Access: Admin > Communications > Customized Messaging
ℹ️ Which Messaging System Am I Using?
This guide covers Avionté's native 24/7 messaging system (Admin > Communications > Customized Messaging).
If you're using WorkN/Serveture, message templates — including the SmartLink SMS text — are managed in a different spot: WorkN's own Admin Tab > Customize Messaging, not here. See WorkN's own guide for that setup.
✅ What You Can Customize
1. Email Content & Formatting
Subject Lines
- Customize the email subject for each notification type
- Add your company name for brand recognition
- Use merge variables to personalize (e.g.,
*|MARKETPLACE_NAME|*,*|KEY_ATTRIBUTE|*) - Example: "New Shift Available at ABC Staffing" instead of generic "New Shift Available"
Email Body (HTML)
- Full control over email content and HTML formatting
- Add custom headers, footers, and legal disclaimers
- Include company policies, contact information, or helpful links
- Use rich text editor or raw HTML
- Insert merge variables for dynamic content
Important Constraints:
-
Must use exact merge variable names: The system expects specific variable names like
*|WORKER_NAME|*,*|KEY_ATTRIBUTE|*. Custom variable names won't work. - Cannot remove required information: Core notification details (job info, shift times, etc.) must remain in the message
- SMS templates must include opt-out: All SMS must contain "STOP to stop texts" for compliance
2. Sender Information
From Name
- Set a custom "From" name that appears in recipient inboxes
- Use your agency name instead of generic system name
- Example: "ABC Staffing" or "ABC Staffing Opportunities"
- Makes emails more recognizable and increases open rates
From Email Address
- Use your company's verified domain for sender email
- Example: noreply@abcstaffing.com instead of generic@avionte.com
- Requires domain verification: Contact Avionté Support to set up DKIM/SPF records for email authentication
- Improves deliverability and reduces spam filtering
3. Branding & Visual Elements
Company Logo
- Upload your company logo to appear in email headers
- Supported formats: PNG, JPG, GIF
- Recommended size: 200-300px wide, optimized for email
- Appears at the top of all customized email notifications
Color Schemes
- Customize brand colors for email templates
- Set header colors, button colors, accent colors
- Maintain consistent visual identity across all communications
Footer Content
- Add custom footer text, contact information, or social media links
- Include office hours, phone numbers, website URL
- Add unsubscribe/preference links (required for compliance)
4. Enable/Disable Individual Notifications
- Turn specific notification types on or off for your marketplace
- Example: Disable "Job Opportunity" notifications if you only use direct assignment model
- Disabled notifications won't be sent to any users
- Note: Some system-critical notifications cannot be disabled (e.g., shift cancellations, payment confirmations)
❌ What You Cannot Customize
| Element | Why It's Locked | Example |
|---|---|---|
| When notification triggers | System logic determines when events occur | Can't change when "shift cancelled" notification fires - it triggers when shift is actually cancelled in system |
| Who receives it | Recipient logic is code-controlled for accuracy | Can't manually add/remove recipients - system sends to appropriate talent based on job matching, assignments, etc. |
| Delivery channel | Email/SMS/Push associations are system-defined | Can't force a notification to send via SMS instead of email - channel is determined by notification type and user login status |
| Merge variable names | System expects exact variable names for data replacement | Must use *|WORKER_NAME|* not *|NAME|* - variables must match system definitions exactly |
| System/compliance notifications | Required for legal, financial, or system functionality | Billing reports, payment receipts, data extracts, regulatory notices cannot be customized |
🎨 How to Customize Notifications
Step 1: Access Customized Messaging
- Log into BOLD as an HCM Administrator
- Navigate to Admin > Communications > Customized Messaging
- You'll see a list of all available notification types
Step 2: Select Notification to Customize
- Click on the notification type you want to customize
- View the default template and available merge variables
- Check if the notification is customizable (some system notifications are locked)
Step 3: Edit Template
- Subject Line: Update with your preferred wording
-
Email Body: Use the rich text editor or HTML mode
- Add your company messaging and branding
- Include merge variables in
*| |*format for dynamic content - Format with headings, bullets, bold text as needed
- Add links to your website, social media, or help resources
-
SMS Template (if applicable): Keep concise (160 characters recommended)
- Must include "STOP to stop texts" for compliance
- Use merge variables sparingly due to character limits
- Focus on essential information only
Step 4: Preview & Test
- Use the preview function to see how merge variables will be replaced
- Send test messages to yourself to verify formatting
- Check both desktop and mobile email rendering
- Test SMS character count and formatting
Step 5: Save & Activate
- Save your customized template
- Enable the notification if it was previously disabled
- Changes take effect immediately for new notifications
🔤 Merge Variables Reference
Merge variables are placeholders that get replaced with actual data when the notification is sent. They must be enclosed in *| |* delimiters and use exact spelling.
⚠️ Important Variable Format:
-
Correct format:
*|variable_name|* -
Email templates: Use UPPERCASE variables (e.g.,
*|WORKER_NAME|*,*|MARKETPLACE_NAME|*) -
SMS templates: Use lowercase variables (e.g.,
*|first_name|*,*|key_attribute|*) - Variables are case-sensitive - use the exact format shown in the template editor
SMS Template Variables (lowercase):
| Variable | Description | Example Output |
|---|---|---|
*|first_name|* |
Worker's first name | John |
*|key_attribute|* |
Job title/position | Warehouse Associate |
*|start_date|* |
Work start date | Jan 15, 2025 |
*|application_name|* |
Mobile app name | WorkN |
*|short_link|* |
Smartlink URL for app navigation | https://app.link/xyz123 |
*|marketplace_name|* |
Client company name | ACME Manufacturing |
SMS Example: "*|first_name|*, Your *|key_attribute|* work starts *|start_date|*. Launch *|application_name|* *|short_link|* STOP to stop texts"
Email Template Variables (UPPERCASE):
| Variable | Description | Example Output |
|---|---|---|
*|WORKER_NAME|* |
Worker's full name | John Smith |
*|KEY_ATTRIBUTE|* |
Job title/position | Warehouse Associate |
*|MARKETPLACE_NAME|* |
Client company/marketplace name | ACME Manufacturing |
*|ENTERPRISE_NAME|* |
Enterprise/client name | ACME Corporation |
*|START_DATE_TIME|* |
Start date and time | Monday, Jan 15, 2025 8:00 AM |
*|START_DATE|* |
Start date only | Jan 15, 2025 |
*|START_TIME|* |
Start time only | 8:00 AM |
*|END_DATE|* |
End date | Jan 15, 2025 |
*|LOCATION|* |
Work location address | 123 Main St, Chicago, IL |
*|SHIFTS|* |
Shift details | Mon-Fri, 8 AM - 4 PM |
*|SESSION_LENGTH|* |
Duration of session/shift | 8 hours |
*|SMARTLINK|* |
Deep link to app/job | https://app.link/xyz123 |
*|PROVIDER_NAME|* |
Staffing provider/agency name | ABC Staffing Solutions |
*|CANCEL_DATE_TIME|* |
When cancellation occurred | Jan 10, 2025 3:30 PM |
*|CANCEL_CODE_DESCRIPTION|* |
Reason for cancellation | Client request |
Additional Email Variables:
| Variable | Description |
|---|---|
*|USERNAME|* |
User's login username |
*|COUNT_OF_INTERESTED|* |
Number of workers who showed interest |
*|APPLY_DATE_TIME|* |
When worker applied |
*|CONFIRMED_DATE_TIME|* |
When assignment was confirmed |
*|EXT_EMPLOYEE_ID|* |
External employee ID (ATS integration) |
*|EXT_ORDER_ID|* |
External order ID (ATS integration) |
*|WORKER_NAME_LIST|* |
List of worker names (multi-assignment) |
*|START_DATE_TIME_LIST|* |
List of start times (multi-shift) |
Conditional Logic (Email Only):
Email templates support conditional variable display:
Show content if variable has value:
*|IF:EXT_EMPLOYEE_ID|*
Employee ID: *|EXT_EMPLOYEE_ID|*
*|END:IF|*
Show different content based on value:
*|IF:SESSION_LENGTH|*
Duration: *|SESSION_LENGTH|*
*|ELSE:|*
Duration: See job details
*|END:IF|*
⚠️ Important: The exact merge variables available depend on the notification type. Not all variables are available for all notifications. Always check the template editor for the complete list of available variables for the specific notification you're customizing.
📋 Best Practices
Content Guidelines
- Keep it concise: Talent are often reading on mobile devices - get to the point quickly
- Use clear call-to-actions: Make it obvious what action you want them to take
- Mobile-first design: Ensure templates are responsive and readable on small screens
- Brand consistency: Use the same colors, logos, and tone across all notifications
- Test thoroughly: Send test notifications to multiple devices and email clients
SMS-Specific Best Practices
- Target 160 characters or less: Keeps message as single SMS (longer messages split into multiple parts)
- Front-load important info: Put key details first in case message is truncated
- Include clear action: "Reply YES", "Call us", "Check the app"
- Always include STOP instruction: Required for compliance ("STOP to stop texts")
- Test character count: Merge variables expand to actual data - account for realistic lengths
-
Use lowercase variables: SMS templates require
*|variable|*format in lowercase
Email Best Practices
- Scannable layout: Use headings, bullets, and white space
- Mobile-responsive: 60% of talent read emails on mobile devices
- Include app download link: Every email is an opportunity to drive app adoption
- Clear from name: Use your agency name so talent recognize the sender
- Functional links: Test all links (unsubscribe, website, phone numbers) before activating
-
Use UPPERCASE variables: Email templates require
*|VARIABLE|*format in uppercase
🚨 System Notifications (Non-Customizable)
Certain notifications cannot be customized because they're required for compliance, financial reporting, or critical system functionality:
- Billing & Financial Reports: Invoice summaries, payment receipts, billing statements
- Data Extracts & Exports: System-generated reports and data files
- Regulatory Compliance: Tax forms, I-9 notifications, background check notices (where required by law)
- System Administration: Password resets, security alerts, account lockouts
- Platform Updates: Maintenance notifications, feature announcements from Avionté
These notifications use standard templates to ensure accuracy, consistency, and legal compliance.
💡 Real Template Examples
Example 1: SMS - Assigned Job
Default Template:
*|first_name|*, Your *|key_attribute|* work starts *|start_date|*. Launch *|application_name|* *|short_link|* STOP to stop texts
Rendered Example:
John, Your Warehouse Associate work starts Jan 15. Launch WorkN https://app.link/abc123 STOP to stop texts
Example 2: Email - Job Assignment
Using Merge Variables:
Subject: New Assignment from *|PROVIDER_NAME|*
Body:
Hi *|WORKER_NAME|*,
You've been assigned to work as a *|KEY_ATTRIBUTE|* at *|ENTERPRISE_NAME|*.
Details:
Start: *|START_DATE_TIME|*
Location: *|LOCATION|*
Duration: *|SESSION_LENGTH|*
View full details: *|SMARTLINK|*
⚠️ Common Mistakes to Avoid
1. Wrong Variable Format
Problem: Using [WORKER_NAME] instead of *|WORKER_NAME|*
Result: Variable won't be replaced, notification shows literal text to recipients
Solution: Always use *| |* delimiters, not brackets or other formats
2. Wrong Variable Case
Problem: Using *|worker_name|* (lowercase) in an email template or *|FIRST_NAME|* (uppercase) in SMS
Result: Variable may not be replaced correctly
Solution: Use UPPERCASE for email templates, lowercase for SMS templates
3. Using Non-Existent Variables
Problem: Creating custom variables like *|PAY_RATE|* or *|AGENCY_PHONE|* that aren't defined in the system
Result: Variable appears as literal text, not replaced with data
Solution: Only use variables available in the template editor's variable list
4. Removing Required Information
Problem: Deleting essential shift details (time, location) to shorten email
Result: Talent can't make informed decision, may miss critical information
Solution: Keep all required fields, just reformat or rearrange for better presentation
5. Missing STOP Instruction in SMS
Problem: Forgetting to include "STOP to stop texts" in custom SMS template
Result: Template will be rejected by system (compliance requirement)
Solution: Always include opt-out instruction at the end of every SMS template
6. Not Testing Before Launch
Problem: Activating template without sending test notifications
Result: Broken links, formatting errors, or missing variables discovered after talent receive the notification
Solution: Always send test notifications to yourself and verify on multiple devices
🎯 Tips for Effective Customization
Maximize App Adoption
- Include app smartlinks (
*|SMARTLINK|*or*|short_link|*) in every email and SMS notification - Add visual download buttons (not just text links)
- Highlight app benefits: "Get instant notifications, faster responses, easier schedule management"
- Include QR codes in email footers for quick app download
Build Trust & Recognition
- Use consistent from name and logo across all communications
- Include your agency contact information in every notification
- Add office hours and support phone number in footers
- Use professional, friendly tone that matches your brand voice
- Personalize with
*|first_name|*(SMS) or*|WORKER_NAME|*(email) for better engagement
Improve Response Rates
- Use action-oriented subject lines: "New Shift - Respond by 5 PM" vs "Shift Notification"
- Make calls-to-action prominent and clear
- Include deadline or urgency when appropriate using
*|START_DATE_TIME|* - Personalize with talent's name and job-specific details
ℹ️ Need Help?
If you have questions about customizing notifications, need assistance with merge variables, or want to discuss domain verification for custom sender addresses, please contact Avionté Support.
Related Articles:
- 24/7 Notifications Overview
- 24/7 Talent Notifications
- 24/7 Agency Notifications
Last updated: 2025-11-12
Comments
0 commentsPlease sign in to leave a comment.