Unified Messaging Escalation via Acknowledgement Flags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In call centers using a unified messaging platform, customers experience poor quality of service due to delayed responses when customer service representatives are unavailable, as messages are not timely retrieved or escalated to alternative representatives.
Innovation Solution
An automatic message escalation system that attaches an acknowledgement flag to messages, checks for retrieval after a specified time, and sends escalation notifications to other CSR recipients based on configured schedules, allowing authorized CSRs to access and change message status, ensuring timely handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If messages are deposited in the mailbox of a single customer service representative, then message routing is simplified, but customer service quality deteriorates when the representative is unavailable for a significant period
Solution Approach 1:
The system pre-configures escalation recipient sets and schedules before messages arrive. When a message is deposited, the escalation path is already established, allowing automatic escalation to occur without complex real-time routing decisions. This preliminary setup maintains simple routing while ensuring reliable service through pre-planned escalation paths.
Solution Approach 2:
The unified messaging platform acts as an intermediary between the customer service representative and the message. It monitors message retrieval status and automatically escalates messages to alternative representatives when the original recipient does not retrieve the message within the specified time period, thereby maintaining service reliability without requiring complex direct routing between multiple representatives.
2Reliability
If messages are automatically escalated to multiple recipients, then customer service quality improves, but system complexity increases
Solution Approach 1:
The escalation system is segmented into distinct components: message deposit, time period monitoring, retrieval status checking, and automatic escalation. Each component performs a specific function, making the overall system manageable despite its complexity. The escalation recipient set is also segmented into primary and alternative recipients with defined escalation paths.
Solution Approach 2:
The system uses periodic time periods to determine when escalation should occur. A specified time period is established when the message is deposited, and the system periodically checks whether the message has been retrieved by the end of this period. This periodic action simplifies the escalation logic compared to continuous monitoring, reducing system complexity while maintaining reliability.
3Loss of time
If the system continuously checks message retrieval status, then timely response is ensured, but processing overhead increases
Solution Approach 1:
Instead of continuous monitoring, the system implements periodic checking at predetermined time periods. When a message is deposited, a time period is established, and the system checks retrieval status only at the end of this period. This periodic approach ensures timely response by catching unretreived messages at appropriate intervals while significantly reducing processing overhead compared to continuous monitoring.
Solution Approach 2:
The system uses the passage of time itself as the trigger for status checking. Rather than actively and continuously polling for message retrieval, the system waits for the predetermined time period to elapse and then checks status. This self-service approach leverages the natural progression of time to minimize processing overhead while still ensuring timely detection of unretreived messages.
Data Source
AI summary
An automatic message escalation system includes attaching an acknowledgement flag to a message after it is received in the message mailbox of an identified message recipient. The status of the acknowledgement flag indicates whether or not the message has been retrieved. After a given or specified period of time, the acknowledgement flag is checked to see if the message was retrieved. If the message was retrieved, the message will not be escalated. If the message was not retrieved, the message will be sent to the next message recipient on an escalation list.