Individual & Bulk messaging : User Story ( UX02US02)
1. Problem Statement
Core Problem
Utility company staff (Customer Service Executives, CSO call center agents, Utility Admin, Meter managers, and Billing managers) lack a unified messaging interface to efficiently communicate with customers through their preferred channels. The platform aims to solve this by providing:
- An individual messaging interface for sending targeted communications to specific customers
- A bulk messaging capability for sending the same message to multiple recipients simultaneously
Pain Points for Individual Messaging:
- Users must switch between multiple communication platforms when sending messages to individual recipients
- No unified interface for selecting appropriate communication channels based on recipient preferences
- Inability to easily schedule follow-up messages from the same interface
- Time-consuming process of composing similar messages multiple times for different recipients
Pain Points for Bulk Messaging:
- Inefficient process for sending messages to multiple recipients simultaneously
- Limited ability to personalize mass communications with recipient-specific details
- Inability to efficiently target specific recipient segments or geographic areas
- Challenges in scheduling important announcements in advance
- No streamlined process for creating reusable templates for recurring communications
- Time-consuming process of sending individual messages for widespread issues or announcements
- Limited capabilities for managing and organizing recipient lists for different communication purposes
2. Who Are the Users Facing the Problem?
CSO Manager/Customer Service Executive: Responsible for overseeing all customer touchpoints and ensuring high-quality customer service. Needs to communicate with customers about service issues, account changes, and general inquiries.
Call Center Representative: Handles incoming customer calls and needs to follow up with customers regarding service requests, account updates, and issue resolutions.
Utility Administrator: Manages system settings and configurations, including communication channels, templates, and recipient lists. Oversees messaging standards and compliance.
Billing Manager: Responsible for billing operations and needs to communicate with customers about bills, payment issues, and collection activities.
Meter Manager: Oversees metering operations and needs to notify customers about meter reading schedules, usage patterns, and potential issues.
3. Jobs To Be Done
For CSO Manager/Customer Service Executive: When I need to respond to a customer inquiry, But I have to switch between multiple systems to find the customer's preferred contact method, Help me send messages through a unified interface that shows customer preferences, So that I can provide timely and consistent customer service through their preferred channels.
For Call Center Representative: When I need to follow up with a customer after a call over messages, But I don't have an efficient way to send and track these communications, Help me quickly send and schedule messages from within my main work interface, So that I can ensure proper messaging without extending call handling time.
For Utility Administrator: When I need to establish and manage effective customer communication capabilities across the organization, But I struggle with fragmented channel configurations, inconsistent templates, and scattered recipient lists, Help me administer all messaging components (channels, templates, recipient lists, and user permissions) from a centralized interface, So that I can ensure regulatory compliance, standardize communications, and optimize customer engagement across all departments.
For Billing Manager: When I need to notify customers about billing issues or updates, But I can't easily send personalized messages to multiple customers at once, Help me create bulk messages with personalization fields for specific customer segments, So that I can efficiently address billing matters with relevant customer groups.
For Meter Manager: When I need to inform customers about meter-related activities, But I have no efficient way to communicate with specific service areas, Help me send targeted messages to predefined lists of customers by area, So that I can keep customers informed about meter readings and maintenance activities.
4. Solution
The UtilityConnect Messaging feature provides a comprehensive communication platform that allows utility staff to send both individual and bulk messages to customers through their preferred channels, from a single unified interface.
Key Capability Areas:
1. Unified Messaging Interface
- Tabbed interface for individual and bulk messaging
- Integration with existing customer information systems
2. Multi-Channel Support
- Support for email, SMS, push notifications, and other communication channels
- Channel preference management by customer
- Channel-specific message formatting and limitations
3. Individual Messaging
- Channel selection based on customer preferences
- Message composition with formatting options of schedule delievry
- Subject line management for applicable channels
4. Bulk Messaging
- Recipient selection by audience type (consumers, technicians,businesses)
- Predefined recipient list selection from the lists
- Message configuration for bulk delivery
5. Scheduling and Delivery Options
- Schedule messages for future delivery
- Delivery time optimization based on customer preferences
- Estimated delivery time information for bulk
5. Major Steps Involved
For Individual Messaging :
For Bulk Messaging:
6. Flow Diagram
7. Business Rules
General Messaging Rules
- Messages can be sent to individual recipients or multiple recipients
- All messages must be sent through a selected communication channel
- Every message must have a channel selected before it can be sent
- Message subject is required for individual messages
- Message content is mandatory for all message types
- Users can schedule messages for later delivery
Channel Selection Rules
- Users must select a communication channel before sending any message
- Available channels are displayed in a dropdown menu
- Channel selection determines message delivery method
- Channel options are consistent across individual and bulk messaging
- Channel-specific formatting rules:
- Email:
- Requires subject line
- Supports rich text formatting
- Can include placeholders for personalization
- SMS:
- Plain text only, no formatting
- WhatsApp:
- Plain text only, no formatting
- Email:
Individual Message Rules
- Individual messages require recipient selection, channel, subject, and message content
- Subject field must be filled with relevant information about the message purpose
- Message content must be provided in the message body
- User can choose to schedule the message for later delivery
Bulk Messaging Rules
- Bulk messages can be sent to multiple recipients by selecting a predefined list
- An audience type must be selected before sending bulk messages
- A recipient list must be selected or uploaded for bulk messages
- Bulk messages require channel selection and message content and relative requirements related to whatsapp/sms & email.
- Personalization placeholders like [name], [email] can be used to customize bulk messages
- Estimated delivery time is displayed when scheduling bulk messages (within 15 minutes)
Recipient Selection Rules
- Individual messaging allows selection of a single recipient
- Bulk messaging requires either:
- Selection of a predefined recipient list, or
- Uploading a file containing recipient information
- Audience type must be selected for bulk messages (e.g., Consumers)
Delivery Options Rules
- Users can choose immediate delivery or scheduled delivery
- Scheduled messages display a date/time selector when "Schedule for later" is checked
- Bulk messages display estimated delivery time
- Once sent, messages cannot be recalled
User Interface Rules
- Messaging interface has two main tabs: Individual Message and Bulk Messaging
- Each tab displays relevant fields and options for that message type
- Error messages appear when required fields are not completed
- "Send Message" button is enabled only when all required fields are completed
Message Composition Rules
- Recipient Email = Must be in valid email format (name@domain.com)
- Subject Line = Required for email messages, optional for other channels
- Message Content = Required for all message types
- System must retain draft messages if user navigates away without sending
Scheduling Rules
- Schedule for later = Optional toggle for delayed message delivery
- Scheduled time must be in the future (cannot schedule for past dates/times)
- Time zone for scheduling is based on system default or user preference settings
Error Handling
- Invalid email format must display "Please enter a valid email address" error
- Empty required fields must prevent message sending and highlight missing fields
- Delivery failures must be logged and shown in history
- Critical errors must be highlighted with distinct visual indicators ( red )
8. Sample Data
Recipient Email Samples:
- consumer1@gmail.com
- fieldtech@utilityco.com
- billing_manager@waterdistrict.org
- john.smith@cityelectric.net
- service_alerts@gasutility.com
Subject Line Samples:
- Upcoming Maintenance in Your Area
- Your April 2025 Billing Statement
- Service Appointment Confirmation
- Outage Update: Power Restoration Timeline
- Important: Water Service Interruption Notice
Message Content Samples:
Service Appointment Confirmation:
Dear Customer,
This is to confirm your service appointment scheduled for April 21, 2025, between 9:00 AM and 12:00 PM.
Our technician will need access to your meter located on the south side of your property. Please ensure the area is accessible.
If you need to reschedule, please contact our customer service team at 555-123-4567.
Thank you,
UtilityConnect Service Team
Payment Reminder:
Dear John Smith,
This is a friendly reminder that your utility payment of $127.35 is due on April 25, 2025.
You can make your payment online at www.utilityconnect.com or through our mobile app.
Please disregard this message if you have already made your payment.
Regards,
UtilityConnect Billing Department
Outage Notification:
IMPORTANT: We are currently experiencing an outage in your service area affecting approximately 200 customers. Our crews are working to restore service, with an estimated restoration time of 7:30 PM today.
For updates, visit our outage map at www.utilityconnect.com/outages or reply to this message for assistance.
We apologize for the inconvenience.
Channel Options:
- SMS
- In-App Notification
Schedule Options:
- Send immediately
- Schedule for April 18, 2025 at 8:00 AM
- Schedule for April 20, 2025 at 6:00 PM
- Schedule for April 22, 2025 at 9:00 AM
These sample data points would allow users to test the full functionality of the Compose Message page, including input validation, different message types across various channels, and scheduling options.
9. Acceptance Criteria
Individual Messaging Acceptance Criteria
- The system must provide an "Individual Message" tab in the messaging interface
- The system must require selection of a communication channel before sending an individual message
- The system must provide a field for entering a subject when the selected channel is email
- The system must show mobile number tab for both sms and whatsapp
- The system must validate that the message content field is not empty before sending
- The system must validate that the subject field is not empty before sending
- The system must validate that the channel field and subtype(subject/ number) is not empty before sending
- The system must allow scheduling individual messages for later delivery with date/time selection
- The system must display a confirmation when an individual message is successfully sent.(as shown in ui)
- The system must record all individual messages in the message history with timestamp and sender details(----)
- The system must display delivery status for individual messages (sent, delivered, read, failed) in history(----)
Bulk Messaging Acceptance Criteria
- The system must provide a "Bulk Messaging" tab in the messaging interface
- The system must support audience type selection (e.g., Consumers, techinician ,Business users) for segmentation
- The system must allow users to select from predefined recipient lists
- The system must support recipient lists from the lists page.
- The system must display the estimated number of recipients for the selected audience/list
- The system must support placeholders (e.g., [name], [email]) for message personalization
- The system must display estimated delivery time for bulk messages (e.g., "Within 15 minutes")
- The system must handle partial failures in bulk messaging (e.g., some recipients are invalid)--(---)
10. Process Changes
Reduces time spent switching between systems and ensures consistent messaging across channels |
Improves compliance with customer preferences and reduces incorrect channel usage |
Provides complete visibility into customer communications and reduces missed follow-ups |
Ensures messaging consistency and reduces time spent composing messages |
Reduces missed follow-ups and improves timely communications with customers |
Enables efficient communication to customer segments while maintaining personalization |
Reduces duplicate efforts and ensures consistent targeting across departments |
Allows for proactive management of failed communications and better service recovery |
11. Impact from Solving This Problem
Communications are faster and more efficient using a unified interface and templates |
Messages are timely, consistent, and aligned with customer preferences |
Better follow-up communications reduce interaction gaps and improve resolution on the first contact |
Staff can focus on higher-value tasks with less time spent on manual processes |
Preferences are applied automatically and consistently, improving compliance |
Communication flows are more streamlined, allowing faster customer responses |
Engagement improves with personalized and well-timed messages across preferred channels |
Costs are lower through consolidation and process automation |
12. User Behavior Tracking
User Behavior Tracking for Messaging Pages
Event | Description | Key Properties | Metrics To Track |
---|---|---|---|
Viewed_Messaging_Page | When a user visits the messaging page. |
,
,
| DAU/WAU of Messaging Page Users |
Selected_Individual_Message_Tab | User clicked on the "Individual Message" tab. |
,
| Tab selection frequency |
Selected_Bulk_Messaging_Tab | User clicked on the "Bulk Messaging" tab. |
,
| Tab selection frequency |
Selected_Communication_Channel | Selected a communication channel from dropdown (email, SMS, WhatsApp, etc.). |
,
| Channel preference distribution |
Entered_Message_Subject | User entered text in the message subject field. |
,
| Subject field completion rate |
Composed_Message | User typed message content in the message body field. |
,
,
| Average message length, placeholder usage |
Toggled_Schedule_Option | User toggled the "Schedule for later" checkbox. |
,
| Scheduled message frequency |
Set_Schedule_Time | Set a specific time for message delivery. |
,
,
| Average schedule lead time |
Sent_Individual_Message | Clicked the "Send Message" button for individual recipient. |
,
,
| Message send completion rate |
Selected_Audience_Type | Selected an audience type from dropdown (Consumers, Technicians, Business). |
,
| Audience type distribution |
Selected_Recipient_List | Selected a specific recipient list from dropdown. |
,
,
,
| List usage frequency |
Used_Message_Placeholder | Added a placeholder tag to personalize message (like {name}, {email}). |
,
,
| Personalization usage rate |
Viewed_Delivery_Options | Expanded or viewed the delivery options section. |
,
| Engagement with delivery options |
Viewed_Estimated_Delivery | Viewed the estimated delivery time for bulk messages. |
,
| Delivery time awareness |
Saved_Message_Draft | Clicked "Save as Draft" for a bulk message. |
,
,
| Draft save frequency |
Sent_Bulk_Message | Clicked the "Send Message" button for multiple recipients. |
,
,
,
| Bulk message send rate |
Returned_To_Dashboard | Clicked "View Dashboard" to navigate back to dashboard. |
,
| Average time on messaging page |
Messaging_Error_Encountered | User encountered an error when trying to send a message. |
,
,
| Error frequency by type |
Added_Attachment | User added an attachment to message (if supported). |
,
,
| Attachment usage rate |
Cancelled_Message_Composition | User navigated away without sending or saving message. |
,
,
| Abandonment rate |
Questions Answered By Tracking
- Which communication channels yield the highest customer engagement?
- What types of messages most effectively drive desired customer actions?
- How does message personalization impact response rates?
- What is the optimal timing for different types of communications?
- Which templates and message formats are most effective?
- How do communication patterns correlate with customer satisfaction metrics?
- What is the ROI of different messaging approaches for different departments?
- How effectively are staff utilizing the unified messaging platform?
3 Comments
recipient email address: is this a drop down or input field
Mention how this is done and which user have access to which list