|Publication number||US20030195811 A1|
|Application number||US 09/876,563|
|Publication date||16 Oct 2003|
|Filing date||7 Jun 2001|
|Priority date||7 Jun 2001|
|Also published as||CA2453231A1, EP1402448A2, EP1402448A4, US7653573, US8243893, US20050165658, US20100183125, WO2002101495A2, WO2002101495A3|
|Publication number||09876563, 876563, US 2003/0195811 A1, US 2003/195811 A1, US 20030195811 A1, US 20030195811A1, US 2003195811 A1, US 2003195811A1, US-A1-20030195811, US-A1-2003195811, US2003/0195811A1, US2003/195811A1, US20030195811 A1, US20030195811A1, US2003195811 A1, US2003195811A1|
|Inventors||Marc Hayes, Sean Sweeney, Ronald Argo|
|Original Assignee||Hayes Marc F., Sweeney Sean M., Argo Ronald L.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (110), Classifications (21), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
 The invention pertains to a customer messaging and alerting service. In particular, the service provides for multi-channel communications between customers and businesses, and provides a means for businesses to create alerts for target customers that are routed via each customer's specified alert hierarchy.
 Electronic interactions between a business and its customers currently are typically reactive, responding to each customer request separately. In addition, business responses are typically rigid, tending to be seller-centric. For example, some companies offer only one or two ways for customer interaction with customer service personnel and only for specified time periods. Thus, customers must do business with their suppliers under each company's terms, and the customer support infrastructure is used only when a customer requests assistance.
 One of the most popular forms of communicating privately between persons, one-on-one, via personal computer (PC) and other devices, including personal digital assistants (PDA) and Web-enabled phones, is called instant messaging. There are various forms of instant messaging systems that do not work with one another, such as America Online's Instant Messenger and Yahoo! Messenger. But each of the instant-messaging systems allow a user to create a special list that enables the user to be informed when a “buddy” (one of the users on the special list) has come online, and that person is also informed that the user is online. The system works because a piece of client software running on each person's PC allows a connection to an Instant Messaging server to be made, and permits the user to be logged into the server by supplying the user's screen name and a password. The client software then sends a list of “buddies” to the server, which checks to see if anyone on the list is currently online, and continues checking as long as the user runs the client software.
 It is estimated that 130 million people currently use Instant Messaging software, and that about 1.5 billion instant messages are sent daily. The United States Postal Service, in comparison, handles approximately 660 million letters per day. The use of instant messaging software is thus becoming more popular as the number of people utilizing the internet continues to increase. Businesses have recognized this trend, and various instant messaging providers are developing wireless communication applications, for such devices as mobile telephones, pagers, web-enabled digital telephones, personal digital assistants and other devices.
 In view of these trends, businesses hoping to provide excellent customer service must not only be concerned about staffing call centers with knowledgeable personnel, but also must be concerned about how to locate and communicate with highly mobile and computer-savvy customers. It is clear that offering a toll-free telephone number for contacting customer representatives eight hours a day is no longer acceptable in today's fast-paced, digital environment.
 Presented is a customer messaging and alerting service (CMAS). An implementation includes enrolling a customer in a messaging and alert service, storing a list of businesses selected by the customer, storing a customer contact hierarchy list, and contacting the customer according to the customer contact hierarchy when at least one of the selected businesses has an alert for the customer.
 The CMAS may include one or more of the following features. A customer may enroll by providing information to at least one of a participating business website, a customer messaging and alert service website, and to a customer services representative. A customer contact hierarchy list may include at least one of telephone information, instant messaging information, e-mail information, pager information and wireless device information. A list of customer preferences may be stored that includes at least one of selected businesses to contact, selected businesses authorized to send alert messages, when the customer may be contacted and types of messages that require confirmation. The customer may be permitted to contact any of the selected businesses. The customer may submit a natural language query that is interpreted by the messaging and alert service.
 CMAS is a system for business service providers that provides a customer messaging and alerting service enabling real-time, interactive alerts to be delivered to customers in the customer's preferred media. These alerts are “actionable” meaning that customers can respond to those alerts providing important direction to the business enterprise. As an example, a customer may be alerted that a field service technician will be dispatched to their place of business in 30 minutes, and the customer can either accept the service dispatch time or ask for a rescheduled time. In either case, more efficient business operations are the result.
 CMAS also provides a reusable business and technical architecture to automatically respond to “natural language” requests for care from customers in message media (e.g. AOL Instant Messenger). CMAS creates a “corporate persona” in the instant messenger service (for example, a “Package Company Helper” AOL Instant Messenger helper that is always available in a customer's list of “buddies”). CMAS provides pre-built “customer intents” that are designed to respond to the most frequent customer requests.
 Furthermore, CMAS provides reusable customer profiles enabling more effective customer communications. Customers define their communications profile once and then enable their supplier's to use those profiles. The communication profile includes important attributes like devices (e.g., web phone) and services (e.g., Yahoo! Messenger) and addresses (e.g., Assistant's telephone number) and preferred order of contact. A permission-marketing model protects these customer profiles and restricts access to only those suppliers expressly authorized by the profile. This model enables a more effective, “write once, use many” approach creating greater efficiency and effectiveness from the customer's perspective and from the business' perspective.
 The CMAS engine enables businesses to shape, and in some cases reshape, many of their electronic customer interactions to keep customers happy and informed. CMAS also reduces the cost of customer service by automating many of the tasks formerly handled by customer service representatives or other human assisted means, increases customer satisfaction, and minimizes the problems associated with locating customers in today's dynamic world of increasingly transient and mobile customers. CMAS promotes customer satisfaction, retention and loyalty, which results in increased revenues because such customers tend to buy more products and services. Thus, CMAS captures some of the original electronic customer relationship management value first recognized as the internet started to develop into a viable business medium.
 Other features and advantages of the invention will be apparent from the detailed description set forth below, from the drawings and from the appended claims.
FIG. 1 is a simplified block diagram of a customer messaging and alerting service (CMAS) according to the invention.
 FIGS. 2A-2C are simplified computer screen shots illustrating an implementation of the enrollment process followed by a customer to enroll in the CMAS.
FIG. 2D is a table listing the types of customer profile data that CMAS may acquire for customers.
FIG. 3 illustrates an example of how a business uses CMAS to communicate with a customer.
 FIGS. 4A-4D illustrate an example of CMAS communications between a customer and a package delivery company.
FIG. 5A is a simplified block diagram of an implementation of a CMAS system according to the invention.
FIG. 5B is an implementation of the CMAS architecture of FIG. 5A.
FIG. 5C is a table illustrating authentication mechanisms by device type for use with a CMAS system according to the invention.
FIG. 5D is a service and delivery information table illustrating the types of services that may be supported by a CMAS system according to the invention.
FIG. 5E is a device table illustrating the types of devices that may be supported by a CMAS system according to the invention.
FIG. 6A is a simplified block diagram of an example of a customer configuration for accessing the CMAS service to communicate with one or more businesses.
FIG. 6B is a simplified block diagram of an implementation of systems that may interface with a CMAS engine according to the invention.
FIG. 7 is a simplified schematic diagram illustrating an example of how a customer may access CMAS via a wireless device.
 Like reference numbers in the drawings indicate like elements.
FIG. 1 is a simplified block diagram 10 of a customer messaging and alerting service (CMAS) 12 that connects a plurality of different types of businesses 14 a-14 g to a plurality of customers 16 a-16 n. A customer may be defined as a person, business entity or employee of a business that uses and subscribes to the CMAS services. A particular customer may have multiple devices at her disposal for communication, any or all of which may be designated for communications with chosen businesses. In an implementation, the customer may wish to request information from one or more of the businesses affiliated with the CMAS. For example, customer 16 a may use a computer running instant-messaging software, an e-mail program and a website chat program, while customer 16 b may also utilize a computer, a wireless phone and a personal digital assistant with wireless communications capability. As long as both customer 16 a and 16 b are enrolled, which is explained below, both can use any of their devices to communicate with one or more businesses of their choice.
 A feature of the CMAS system is the capability for a customer to use instant messaging as a communications tool to request information. The customer generates a “special list” of “buddies” that include chosen businesses so that conversational, humanistic customer care can be delivered to that customer. If instant messaging is used, then conversational, humanistic customer care may be delivered by what some consider to be the most natural and personal electronic interface medium. Further, the CMAS system may include natural language processing (NLP) that permits a customer to form natural language queries that can be interpreted and answered based on industry-specific and enterprise-specific customer intention models. Each company may develop its own proprietary, industry-specific business processes codified in the natural language processing linguistics and intent-response models used for their field. Some examples of how such natural language queries may be formed, interpreted and answered will be given below.
 Another feature of the CMAS system is that an enterprise or company may create business-specific alert messages, and target customers to receive such alerts via customer-specified alert hierarchies until the alert is delivered. The CMAS system is therefore “customer-centric” in that each customer must grant permission to be contacted by one or more chosen companies. The customer thus controls who, how and when their suppliers may contact them.
 A customer may sign up for the CMAS services in a number of ways, may specify or control which businesses and what type of communications will be acceptable, and may define a hierarchy of contact means for receiving alerts. The CMAS service maintains the customer profiles, may specify employment groups that certain sets of customers belong to, and may periodically send bulk e-mail notices to customers to ensure that profile data is accurate and current. The system permits a customer to communicate with a plurality of different suppliers in the same manner.
 FIGS. 2A-2C are simplified computer screen shots showing how a customer, “Marc Smith”, enrolls himself by using a personal computer and accessing the CMAS website. In FIG. 2A, the customer enters various contact information 20 a to 20 f or alerting media, including various instant-messenger accounts 20 b to 20 d. Next, in FIG. 2B the customer indicates company preferences to control which businesses 22 may use the alert infrastructure (the businesses are all CMAS subscribers or CMAS affiliated enterprises in this example). Lastly, the customer enters his contact preferences hierarchy 24 a to 24 c, and whether or not confirmation 26 a to 26 c is required for each of the notification channels. In particular, when one of the information providers 22 (FIG. 2B) issues an alert, then an attempt to contact Marc Smith will be made first via AOL Instant Messenger™ 24 a, then via a text pager 24 b, and lastly via a mobile phone 24 c. The first two preferred notification channels require confirmation 26 a, 26 b, but if communication via these channels is unsuccessful, then mobile phone 24 c communications will be attempted which does not require confirmation 26 c.
 Once a customer is enrolled, CMAS monitors for relevant alert events from that customer's preselected companies and provides alert messages as they occur. FIG. 2D is a list of the types of customer profile information that a CMAS system may include. Each customer has full access to their profile settings and subscriptions and may modify the setup at any time. This “permission marketing” orientation permits customers to shape interactions to their preferences, and results in a “cockpit” for the customer for all suppliers. That is, the customer has a means for grouping all of her business contacts together in one integrated system. In addition, the customer may be able to subscribe for personal service messages or other options provided by businesses, which may be provided on a scheduled basis. Customers could also receive event reminders regarding scheduled tasks or required responses.
 CMAS may share some relevant profile data with subscribing companies that is centrally maintained. Such data is typically identification and demographic data that may be used for marketing or personalization purposes. For example, a business may use the customer's name in an automatically-generated greeting when first contacted, and may use other customer data such as the customer's preferences to generate alert messages. For example, customers who are “Gold” frequent flyers may receive different or fewer alert messages than customers who are “Platinum” frequent flyers.
 A customer using a personal computer may also be viewing a business website and notice a CMAS option. The customer may navigate to that section and decide to enroll in the service. The CMAS site may be “deep linked” inside many companies web sites (Frame or redirected URL). The customer feels as though she is on the originating company's web site, but is really on a co-branded version of the CMAS site. The enrollment process is similar to that described above. In particular, during the process the customer is introduced to CMAS and the services that are available. The customer may be educated about the other companies that utilize the CMAS service for alerting, and may include then when enrolling. If, for example, the customer happens to be at the website of a parcel delivery company when enrolling, then the CMAS is preconfigured to at least include delivery company enabled alerting for this customer. The customer receives an enrollment confirmation e-mail, which may include an invitation to enroll for alerting services from other companies. A link to the CMAS web site may also be included in the e-mail. CMAS then begins to ‘monitor’ for relevant alerts for the enrolled customer.
 A customer may also enroll to use CMAS by using other communication devices. For example, the customer may use a telephone to call a customer service center and orally give the required information to a customer service representative who enters the data into the system.
FIG. 3 illustrates an example of how CMAS works for an enrolled customer, Marc Smith. In this example, a package requiring a signature is scheduled to be delivered, and thus CMAS notifies Mr. Smith according to his stated preferences to ensure that he will be available for signature. The package delivery company initiates a customer alert to Marc Smith via CMAS identifying the requirement for him to confirm that he will be available to sign for the package. Such messages may be automatically generated by the CMAS engine according to customer preferences and the CMAS engine suggested protocols. CMAS attempts to notify on Mr. Smith's first media preference 30 (Yahoo! Instant Messenger) but determines that he is unavailable on that media. Next, CMAS automatically escalates to his second media preference, and Marc Smith is successfully alerted on the second preference, which is by short message system 32 (SMS) on his cell phone. The message requires a response, so Marc Smith can reply using any of the communication devices that he indicated upon enrollment in CMAS. For example, Marc Smith may respond via e-mail that he will be unavailable at the scheduled delivery time, and suggest a delivery time of 3:00 p.m. He may also request to continue the present communication by e-mail, or else the package delivery company will continue it by using the “originating media”, which was SMS in this example. On some occasions, CMAS recommends a media change when it detects human assistance may be required. This may occur, for example, when CMAS cannot identify a natural language query after three tries, and then will suggest and then initiate a call to the customer from a customer service representative. Otherwise, the communication remains in the originating media unless the customer requests a change to another media. Returning to the present example, the delivery company, utilizing the CMAS engine, responds and offers alternate delivery times and requests that Marc Smith choose one of the offered selections. Once the customer responds by picking a delivery time the delivery company may transmit a confirmation communication such as a confirmation e-mail.
 The CMAS engine, when operable to send an alert to a customer, will follow the customer hierarchy list of communication types until the list is exhausted. In some implementations, the string of communication types is followed once, and is not repeated once exhausted. However, CMAS may be configured to try the string of communication types two or more times if needed, and to report such activity to the alerting business.
 In another example, a customer wishes to obtain tracking information from his package delivery company. FIGS. 4A to 4D illustrate how CMAS can be used to perform such tasks. In particular, the customer uses the Yahoo! Messenger® instant messaging system to request the location and status 40 of his order from his package delivery company.
 CMAS identifies and authenticates the customer, interprets the natural language request, automatically extracts the tracking number, and retrieves the status information from the delivery company. CMAS then formats the response appropriately based on the customer's message service and returns a response 42 to the customer. The customer, as shown in FIG. 4B, then indicates that he is interested in package number one, and the CMAS engine obtains detailed tracking information 46. In the example of FIGS. 4C and 4D, the customer wishes to be notified of the status of his package delivery bound for Atlanta. The package delivery company sends alerts 48, 50, 52 and 54 as the package is received and transported from various locations enroute to its final destination of Atlanta. In this example, the package was received in Dallas on February 12th and shipped to Jackson, Miss., then to Montgomery, Ala., and lastly arrived in Atlanta on February 14th. A final estimated destination time of arrival is also communicated. In the example shown in FIGS. 4A to 4D, the message responses were automatically generated by the package delivery company using the CMAS engine.
 It should be understood that CMAS could be used in many different situations to both communicate customer requests to different companies, and to communicate alerts or other information from different companies to customers. For example, a customer could request to be alerted whenever a stock market event occurs based on his predefined preferences. The customer would then be able to act upon that information by contacting a customer service representative such as a stock broker, or access a financial website, for example. In another example, a customer may send an instant message requesting shipment status of a critical component needed for an upcoming production run. CMAS first interprets the natural language request for routing to the appropriate business unit and then identifies the requester, identifies his employer, and then authorizes a response to the inquiry. The supplier company then utilizes the CMAS engine to complete the response by automatically generating a reply message based on a predefined list of company-specific and business appropriate language replies. In yet another example, a frequent traveler preparing for a business trip could request flight status information including the departure gate in a natural language inquiry. The CMAS engine interprets the natural language request, routes it to the appropriate airline, and responds with the information. The customer then may ask if she has been upgraded, and the CMAS engine again interprets the request, routes it to the airline and sends an appropriate response. An alert could also be sent by the airline to the frequent traveler in the event that her flight has been delayed or cancelled.
 As described above, a customer may enter a natural language request and the CMAS engine will attempt to interpret the request. The CMAS engine will use the “corporate persona” the customer selected (e.g., an “Airline company Helper” in AOL Instant Messenger) to identify the business to which the request may be directed. The CMAS engine will identify the customer initiating the request by translating their service identity (e.g., their “screen name” in AOL Instant Messenger) into a specific customer identity. The CMAS engine will extract data from the natural language request and use that data to complete the business transaction. The status of such requests may be tracked, and an audit history reported to the business concerning the number of successes or failures, and the type of failures that occurred.
 The interpretation of a customer's natural language request may involve using a customer intent processor that is asynchronous, customer media independent, that includes a timeout and/or aging mechanism, and that includes an interface to a content management engine to retrieve approved alert text for an outbound alert. Several common customer intents may be accessible from every enterprise version of CMAS, such as a help request, a provider inquiry, a profile update request and a human escalation request (i.e. instead of a machine generated response, the customer will be directed to speak to a human representative).
 The customer intent data may be provided by companies affiliated with the CMAS service, and may be modified or expanded depending on the audit history of its customers. For example, a package delivery company may recognize various natural language queries phrased as “what is the status of my package?” or “when will my package be received?” or “when will I receive my order?” to all pertain to a request for shipment tracking associated with that customer. A list of possible shipments could be supplied so that the customer can select the package information of interest. Other inbound customer requests for information that would be recognized by a package company may include: shipment tracking by tracking number, shipment tracking by info/notice, shipment tracking by reference number, schedule shipment delivery, shipment cost inquiry, schedule parcel pickup, waive signature requirement, transit time inquiry, drop off location inquiry, hold mail request, postal code lookup, and change of address request. Outbound messages or alerts that may be automatically generated by the package delivery company may include: delayed shipment notification, driver en route notification, and shipment tracking information.
 The customer “intents” are business-specific, and may be somewhat different or totally different from one business to another. For example, a financial services company may recognize inbound customer natural language requests for such information as balance inquiries, stock price inquiries, brokerage orders, rate inquiries, and payment/transfer orders. Outbound messages or alerts that may be automatically generated and transmitted to customers may include equity portfolio notice, suspicious (credit card) transaction notices, check overdraft/overlimit warnings, and special offer/rate notices.
FIG. 5A is a simplified block diagram of an implementation of a CMAS system 100. Customers 102 a to 102 n each sign-up or enroll for the CMAS services as described above, each indicating which businesses, what types of messages they wish to receive, and how each customer wishes to receive communications. A device interface gateway 104 is capable of receiving and passing messages from customers 102 a-102 n onto a CMAS application architecture service 106. The device interface gateway is configured to translate each received message from a customer into data that the CMAS application architecture package 106 can utilize. The CMAS application architecture bundle 106 is also connected to message-oriented middleware 108 which is connected to a plurality of business services databases 110. In addition, the CMAS application architecture bundle 106 may be connected to a contact center 114 via a contact center integration service 112. The CMAS engine is therefore a collection of software, hardware and communication infrastructure required to maintain CMAS services.
FIG. 5B shows an implementation of the CMAS architecture 106. A customer may utilize any of a plurality of user interfaces 103 to communicate with the CMAS engine through the device interface gateway 104. In this example, the device interface gateway 104 is configured to receive analog or digital telephone messages, digital instant messages, web-based requests and data, e-mail, kiosk-based data, wireless data from many different types of devices (pagers, cell phones, etc.), data from handheld personal digital assistant devices, and the like. The CMAS application architecture 106 may be a bundle of hardware devices and software modules configured to perform session management, perform state management, perform connections management (session timeouts and session termination, etc.), authenticate customers, determine entitlement of customers to receive certain information if required, conduct natural language processing, conduct workflow management, handle customer personalization processes, perform content management, perform alert management (detect presence of an alert, send alert using message hierarchy of each customer to which the alert pertains, and obtain delivery confirmation if required), perform customer profile management, handle customer profile syndication, handle transaction management, handle agent queue management, handle networking protocols (VPN or private network) and perform operations management functions (reporting, monitoring, logging and auditing operations). Some of these operations may be performed by vendor software running on various computer platforms, while other operations may consist of proprietary software code that has been developed and maintained by one or more of the affiliated businesses. The CMAS application architecture 106 is also connected to business services databases 110 through message oriented middleware 108. The business services databases 110 may include information from multiple companies concerning business-specific data. Such databases may include, for example, order status reports, account balances, payment and/or transaction histories, and shipment status for a delivery company; product configurations, commerce systems and product specifications for a consumer product company; travel reservation data for airfare, flight status, hotel accommodations, and car and/or limousine rental for a travel agency; news data, weather conditions and other data from content providers; and other business services databases. Customer-care data, such as customer history data and sales data, may also be included. The CMAS application architecture 106 may also be connected to a contact center 114 through contact center middleware 112. The contact center 114 may include customer service representatives that are familiar with one or more of the affiliated businesses and are available to communicate directly with customers. Functions performed by software of the contact center integration service 112 may include agent queue management, context management and computer telephony integration. It should be understood that the device interface gateway 104, the CMAS application architecture 106, the message oriented middleware 108 and the contact center integration service 112 may include software and hardware developed by many different vendors or software companies for performing the various tasks required to achieve the various customer care goals of the customer messaging service.
 The CMAS application architecture 106 may be configured to remotely support customer profile management of customer profile data maintained by affiliated businesses. Thus, customer profile data need not be stored in a centralized location.
 The CMAS application architecture 106 may also be configured to authenticate customers and identify which accounts that customer is entitled to access, by validating a password, for example. Authentication may be at an individual level (single customer) or at a group level (business entity). FIG. 5C is a table 125 illustrating examples of “native” authentication mechanisms available in column 127 depending on the communication device or communication media used in column 126. Column 128 illustrates the secondary or CMAS managed authentication mechanism, column 129 indicates if a cookie computer file is generated (customer data file), and column 130 generally indicates if another measure is provided, such as security measures. For example, if a customer uses a cell phone to access the CMAS service, a password may be required, a CMAS user ID/Password is required, she can then access a business based on her user profile, no cookies will issue, and security is that provided by the cell phone service provider.
FIG. 5D is a service and delivery information table 135 illustrating the types of services and devices that may be supported by CMAS. Service providers listed in column 136 may support the devices listed in column 138 and may provide presence detection (column 140), delivery confirmation (column 142), guarantee delivery (column 144) and provide receipt acknowledgement (column 146). Receipt acknowledgment may be native, meaning automatically generated by the service (sub-column 147) or manual (column 149), meaning that a customer would have to respond by performing some type of action such as sending a reply e-mail. For example, referring to column 136 a customer may use the service provided by either AOL, Yahoo! Or Microsoft and a device supporting that company's version of instant messaging, and would be detected if on-line (check mark in column 140), but delivery confirmation (column 142) or guaranteed delivery (column 144) of a message could not be promised, and the customer would have to reply manually (check mark in column 149) if a receipt acknowledgement was requested. Thus, the presence detection, delivery confirmation, guaranteed delivery and receipt acknowledgement features depend upon the service and the device used by a customer.
FIG. 5E is a device table 160 illustrating the types of devices (column 162) that may be supported by CMAS, and the services supported on those devices that CMAS may use. In particular, short message system (column 164) may be supported by web phones and mobile phones and used by CMAS; e-mail (column 166) may be supported by all the listed devices, except for a touch-tone phone and a pulse dial phone, and used by CMAS; IVR which stands for “interactive voice response” (column 168) may be supported by Web Phones, mobile phones and touch tone phones and used by CMAS; voice mail (column 170) may be supported by web phones, mobile phones, touch tone phones and pulse dial phones and used by CMAS; and instant messenger (column 172) may be supported by all listed devices except for touch tone and pulse dial phones, and used by CMAS.
 The CMAS application architecture may also be capable of providing predefined reports to businesses to support operations. For example, reports concerning completed transaction summaries by enterprise, peak number of transactions by channel by enterprise, transaction failure by channel by enterprise, transaction frequency by channel and customer intent, transaction summary by customer intent and channel, and transaction failure by customer intent by enterprise may be provided to each business for analysis. Each business can use such information to improve its customer services.
 The CMAS application architecture 106 includes contact management features that are driven by the need to manage message content and format, both from customers and from businesses. Message templates may be provided for use in formatting responses to customer messages and to format customer alert messages. Message management includes the ability to define message content templates for each target platform, the ability to preview message content in each target platform, and the ability to stage message templates for scheduled promotion to the production environment. For example, depending on who the customer may be, a business may use a particular font color scheme and letter sizes to present certain messages. Each business defines its own content and presentation parameters while the CMAS architecture provides a means to deliver the messages to customers.
FIG. 6A is a simplified block diagram 200 of a business configuration wherein a customer uses a personal computer 202 to access the CMAS website provided by the CMAS server 204 over the internet 206. The customer may use her personal computer (PC) to enroll in the CMAS service, to request information from affiliated companies, and to receive alerts from the companies. For example, the customer may log on to the CMAS website by using a Microsoft Passport™ identification, and if the customer does not have an identification then she will be presented with a sign-in menu. (Microsoft Passport™ software provides a single sign-in service that enables businesses to provide a fast and convenient way for customers to sign-in and communicate securely.) Once the customer has signed-up or enrolled, CMAS begins monitoring for relevant alert messages and also permits the customer to request information of affiliated companies. In the example shown in FIG. 6, the CMAS server 204 is connected to a delivery service corporate server 208 and associated database 210, and to an airline corporate server 212 and associated database 214. Many other companies or enterprises could also be connected, either via the internet or dedicated lines or by other means, to the CMAS server. In this manner, the customer PC can communicate with businesses specified by the customer, and the businesses may communicate by various other means, such as by transmitting messages to another customer device, as explained above.
FIG. 6B is a simplified block diagram 220 of an implementation illustrating how a business enterprise system may interface with the CMAS engine 222. As explained above and as shown in FIG. 6B, CMAS supports multiple interfaces with diverse systems. The core CMAS engine communicates with a business through an enterprise system 224 that may include a transaction server 226 and active server pages (ASP's) 228, 229 which may be connected to an enterprise business system 230 for generating alerts. For example, if the business enterprise is an airline, then the system 230 may generate alerts for customers that are scheduled to fly on certain flights that have been delayed due to bad weather conditions. The CMAS engine may also be connected to an enterprise business system 232 through an ASP 234 and an intent processor 236 for interpreting customer natural language queries. Channel product interfaces 250 (channel provider 252, channel product API 254 and channel product 256) are used by the CMAS engine to define communications with different services and customer devices. Lastly, the CMAS engine is configured to communicate with databases 240 that may include a profile database 242, security database 244 and session database 246.
 The CMAS inbound interface may handle communications through an e-mail, a HTTP request, a request through an Instant Messenger, or query from one or more databases. Use of an XML interface ensures that these requests through the inbound interfaces are transformed into system inputs. The transaction server 226 ensures that such requests are interpreted by CMAS. CMAS may handle any outbound requests through vendor software.
FIG. 7 is a simplified schematic diagram 300 illustrating an example of how a customer could access CMAS via a wireless device 302. The system 300 bridges the customer voice channel to the data channel of various businesses. Today's web-phone technology can operate in either a voice mode or a web-browser mode, but cannot operate in both mediums simultaneously. In this example the customer pushes “call CSR” (call customer service representative) on a wireless application protocol (WAP) telephone 302, which connects via a WAP gateway 304 to a mobile internet network 306 which retrieves customer information from a wireless server 308 and associated database 310. The wireless server then writes information about the caller and web context to a database server 312 based on a database lookup of the phone number of the user, and based on a database search of the CSR phone number. The database server 312 may obtain data such as context information of the user, the name of the user, the business function-(Order, Service Request, etc.) and the business item (order number). In this case, a confirmation page is then displayed on the WAP telephone 302 instructing the customer to call a customer service representative. The customer accepts this advice and the WAP telephone 302 then disconnects from the internet and places a call via a mobile network 314. The call is routed to an Automatic Call Distributor (ACD) 316 which recognizes that the customer is a WAP user via the Dialed Number Identification Service (DNIS) and identifies the specific customer via Automatic Number Identification (ANI) service 318. The ANI service 318 then retrieves user data from the database server 312, and sends the data to a contact server 320 for processing. The contact server 320 may process such data as the customer name, WAP user by DNI, business function and business item and then route the call to an agent at a desktop computer 322. The contact server 320 then transmits a “screen pop”, which is an information display that comes up on the agent's computer screen which provides customer information to the agent such as the customer's name, business function and history of prior questions asked during such sessions. The agent or customer service representative may have, for example, information including a description of any problem from the beginning (for example, a recurring problem with a particular product may have been called in several times in the past by the customer) without having to ask the customer to reiterate the problem. The information permits a customer to bypass the conventional “voice response menu” designed to route calls to the correct contact person at the call center. Such a system alleviates customer frustration by helping to solve problems in a timely manner. The system 300 therefore logically bridges the data channel to the voice channel, and is useful to a customer because it can be used to bypass the typical voice response menu typically used by customer service telephone centers.
 A number of implementations of the invention have been described. Nonetheless, it should be understood that various modifications could be made without departing from the spirit and scope of the invention. Accordingly, other implementations are within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US2151733||4 May 1936||28 Mar 1939||American Box Board Co||Container|
|CH283612A *||Title not available|
|FR1392029A *||Title not available|
|FR2166276A1 *||Title not available|
|GB533718A||Title not available|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6993554 *||21 Mar 2002||31 Jan 2006||The Boeing Company||Ground-based travel portal|
|US7016855 *||31 May 2002||21 Mar 2006||Motorola, Inc.||Method and apparatus for managing a task list using location based filtering|
|US7085774 *||30 Aug 2001||1 Aug 2006||Infonox On The Web||Active profiling system for tracking and quantifying customer conversion efficiency|
|US7092778 *||6 Dec 2004||15 Aug 2006||Taiwan Semiconductor Manufacturing Co., Ltd.||Fabrication management systems and methods|
|US7269793 *||18 Oct 2002||11 Sep 2007||Ebs Group Limited||Conversational dealing system|
|US7281201 *||26 Nov 2003||9 Oct 2007||Sap Aktiengesellschaft||Common message area for a customer interaction center user interface|
|US7376902||13 Feb 2003||20 May 2008||Sap Ag||User interface for alerts|
|US7376957 *||16 Dec 2002||20 May 2008||At&T Delaware Intellectual Property, Inc.||Method and system for recovering stranded outbound messages|
|US7587474||19 Jul 2005||8 Sep 2009||The Boeing Company||Ground-based travel portal|
|US7656885 *||25 May 2004||2 Feb 2010||Sybase 365, Inc.||Intermediary content gateway system and method|
|US7697677 *||12 Mar 2002||13 Apr 2010||Siemens Aktiengesellschaft||Method for call distribution in a call center and associated call distribution apparatus|
|US7716128||30 Nov 2007||11 May 2010||The Western Union Company||Electronic indentifier payment systems and methods|
|US7753267||22 May 2008||13 Jul 2010||The Western Union Company||In-lane money transfer systems and methods|
|US7765489 *||14 Sep 2009||27 Jul 2010||Shah Shalin N||Presenting notifications related to a medical study on a toolbar|
|US7769154||26 Jun 2008||3 Aug 2010||Avaya Inc.||Aggregated perceived presence|
|US7783571||31 May 2007||24 Aug 2010||First Data Corporation||ATM system for receiving cash deposits from non-networked clients|
|US7801760||30 Sep 2005||21 Sep 2010||Rearden Commerce, Inc.||Method and system for capturing and calculating complex consumer ratings of goods and services|
|US7805444 *||12 Jan 2007||28 Sep 2010||Sas Institute Inc.||Method and system for responding to user-input based on semantic evaluations of user-provided resources|
|US7809639 *||29 Mar 2002||5 Oct 2010||Checkfree Services Corporation||System and method to provide interoperable service across multiple clients|
|US7809724 *||12 Jan 2007||5 Oct 2010||Sas Institute Inc.||Method and system for responding to user-input based on semantic evaluations of user-provided expressions|
|US7844494 *||26 Sep 2001||30 Nov 2010||First Data Corporation||Electronic acknowledgment of receipt of inventory|
|US7873657 *||12 Jan 2007||18 Jan 2011||Sas Institute, Inc.||Method and system for processing, by an information retrieval system, user input modifying the information retrieval system|
|US7908179||1 Aug 2007||15 Mar 2011||The Western Union Company||Electronic gift linking|
|US7925540 *||15 Oct 2004||12 Apr 2011||Rearden Commerce, Inc.||Method and system for an automated trip planner|
|US7930216||29 Sep 2006||19 Apr 2011||The Western Union Company||Method for making an online payment through a payment enabler system|
|US7933835||17 Jan 2007||26 Apr 2011||The Western Union Company||Secure money transfer systems and methods using biometric keys associated therewith|
|US7936865||30 Sep 2008||3 May 2011||Avaya Inc.||Messaging advise in presence-aware networks|
|US7937292||30 Sep 2008||3 May 2011||The Western Union Company||Wide area network person-to-person payment|
|US7941342||30 Sep 2008||10 May 2011||The Western Union Company||Wide area network person-to-person payment|
|US7941346||30 Sep 2008||10 May 2011||The Western Union Company||Wide area network person-to-person payment|
|US7945252||27 Mar 2008||17 May 2011||At&T Mobility Ii Llc||Customer service messaging, such as on mobile devices|
|US7995742||9 Jan 2007||9 Aug 2011||Avaya Inc.||Outbound dialing decision criteria based|
|US8014497||13 Oct 2006||6 Sep 2011||Avaya Inc.||Messaging advise in presence-aware networks|
|US8024229||30 Sep 2008||20 Sep 2011||The Western Union Company||Wide area network person-to-person payment|
|US8050388||30 Sep 2008||1 Nov 2011||Avaya Inc.||Messaging advise in presence-aware networks|
|US8064574||30 Sep 2008||22 Nov 2011||Avaya Inc.||Messaging advise in presence-aware networks|
|US8098799||1 Oct 2008||17 Jan 2012||Avaya Inc.||Messaging advise in presence-aware networks|
|US8107597||30 Sep 2008||31 Jan 2012||Avaya Inc.||Messaging advise in presence-aware networks|
|US8108231||20 Jan 2005||31 Jan 2012||The Crawford Group, Inc.||Method and apparatus for improved customer direct on-line reservation of rental vehicles|
|US8108516||30 Sep 2008||31 Jan 2012||Avaya Inc.||Presence tracking and name space interconnection techniques|
|US8117073 *||17 Sep 2004||14 Feb 2012||Rearden Commerce, Inc.||Method and system for delegation of travel arrangements by a temporary agent|
|US8135811 *||3 Sep 2008||13 Mar 2012||International Business Machines Corporation||Client device configuration with configuration services providers|
|US8140096 *||27 Mar 2008||20 Mar 2012||At&T Mobility Ii Llc||Customer service messaging, such as on mobile devices|
|US8145275 *||27 Mar 2008||27 Mar 2012||At&T Mobility Ii Llc||Customer service messaging, such as on mobile devices|
|US8150003||23 Jan 2007||3 Apr 2012||Avaya Inc.||Caller initiated undivert from voicemail|
|US8150763||1 Aug 2006||3 Apr 2012||The Western Union Company||Systems and methods for staging transactions, payments and collections|
|US8218735 *||10 Dec 2007||10 Jul 2012||Avaya Inc.||Messaging advise in presence-aware networks|
|US8230048||25 Jun 2007||24 Jul 2012||International Business Machines Corporation||Client device configuration with hooks|
|US8234134 *||13 Jun 2003||31 Jul 2012||The Crawford Group, Inc.||Method and apparatus for customer direct on-line reservation of rental vehicles including deep-linking|
|US8244632||2 Jan 2003||14 Aug 2012||First Data Corporation||Automated transfer with stored value|
|US8264345 *||30 Nov 2009||11 Sep 2012||Baron Services, Inc.||System and method of providing real-time site specific information|
|US8271309||16 Mar 2006||18 Sep 2012||The Crawford Group, Inc.||Method and system for providing and administering online rental vehicle reservation booking services|
|US8301581||24 Sep 2009||30 Oct 2012||Avaya Inc.||Group compositing algorithms for presence|
|US8355960 *||22 Mar 2005||15 Jan 2013||The Western Union Company||Electronic acknowledgement of receipt of inventory|
|US8362927||23 May 2012||29 Jan 2013||Eclipse Ip, Llc||Advertisement systems and methods for notification systems|
|US8368562||23 May 2012||5 Feb 2013||Eclipse Ip, Llc||Systems and methods for a notification system that enable user changes to stop location for delivery and/or pickup of good and/or service|
|US8374962||2 Jan 2003||12 Feb 2013||First Data Corporation||Stored value payouts|
|US8396728||30 Jan 2012||12 Mar 2013||The Crawford Group, Inc.||Method and apparatus for improved customer direct on-line reservation of rental vehicles|
|US8401009||19 Mar 2013||Twitter, Inc.||Device independent message distribution platform|
|US8407307 *||9 Nov 2007||26 Mar 2013||Flightview, Inc.||Flight information sending system and method|
|US8427308 *||16 Aug 2012||23 Apr 2013||Baron Services, Inc.||Method and system of providing real-time site specific information|
|US8484088 *||6 Oct 2004||9 Jul 2013||Rearden Commerce Inc.||Customer satisfaction in booking process|
|US8489473 *||24 May 2012||16 Jul 2013||The Western Union Company||Electronic acknowledgement of receipt of inventory|
|US8504473||28 Mar 2007||6 Aug 2013||The Western Union Company||Money transfer system and messaging system|
|US8515874||24 Aug 2006||20 Aug 2013||The Western Union Company||Airline ticket payment and reservation system and methods|
|US8531317||2 Jan 2013||10 Sep 2013||Eclipse Ip, Llc||Notification systems and methods enabling selection of arrival or departure times of tracked mobile things in relation to locations|
|US8564459||2 Jan 2013||22 Oct 2013||Eclipse Ip, Llc||Systems and methods for a notification system that enable user changes to purchase order information for delivery and/or pickup of goods and/or services|
|US8639784||13 Jun 2012||28 Jan 2014||International Business Machines Corporation||Client device configuration with hooks|
|US8672220||30 Sep 2005||18 Mar 2014||The Western Union Company||Money transfer system and method|
|US8695016||25 Jul 2012||8 Apr 2014||At&T Intellectual Property I, L.P.||Method and system for recovering stranded outbound messages|
|US8706534||30 Jul 2012||22 Apr 2014||The Crawford Group, Inc.||Method and apparatus for customer direct on-line reservation of rental vehicles including deep-linking|
|US8706640||17 Jul 2006||22 Apr 2014||The Western Union Company||Systems and methods for enrolling consumers in goods and services|
|US8711010||2 Jan 2013||29 Apr 2014||Eclipse Ip, Llc||Notification systems and methods that consider traffic flow predicament data|
|US8738739||20 Oct 2011||27 May 2014||The Delfin Project, Inc.||Automatic message selection with a chatbot|
|US8762267||19 Jun 2013||24 Jun 2014||The Western Union Company||Money transfer system and messaging system|
|US8818904||17 Jan 2007||26 Aug 2014||The Western Union Company||Generation systems and methods for transaction identifiers having biometric keys associated therewith|
|US8851371||17 May 2013||7 Oct 2014||The Western Union Company||In-lane money transfer systems and methods|
|US8862487||17 Sep 2012||14 Oct 2014||The Crawford Group, Inc.||Method and system for providing and administering online rental vehicle reservation booking services|
|US8862488||17 Sep 2012||14 Oct 2014||The Crawford Group, Inc.||Method and system for providing and administering online rental vehicle reservation booking services|
|US8937546||2 Jan 2014||20 Jan 2015||Baron Services, Inc.||Method and system of providing real-time site specific information|
|US8949283||23 Dec 2013||3 Feb 2015||Google Inc.||Systems and methods for clustering electronic messages|
|US8949377 *||11 Apr 2011||3 Feb 2015||The Delfin Project, Inc.||Management system for a conversational system|
|US8960537||21 Nov 2012||24 Feb 2015||The Western Union Company||Money transfer systems and methods|
|US9013334||5 Mar 2014||21 Apr 2015||Eclipse, LLC||Notification systems and methods that permit change of quantity for delivery and/or pickup of goods and/or services|
|US9015192||19 Mar 2014||21 Apr 2015||Google Inc.||Systems and methods for improved processing of personalized message queries|
|US9019130||5 Mar 2014||28 Apr 2015||Eclipse Ip, Llc||Notification systems and methods that permit change of time information for delivery and/or pickup of goods and/or services|
|US9088532||18 Jan 2013||21 Jul 2015||Twitter, Inc.||Device independent message distribution platform|
|US9123044||29 Jun 2014||1 Sep 2015||The Western Union Company||Generation systems and methods for transaction identifiers having biometric keys associated therewith|
|US9124546 *||31 Dec 2013||1 Sep 2015||Google Inc.||Systems and methods for throttling display of electronic messages|
|US9129464||1 Aug 2006||8 Sep 2015||The Western Union Company||Staged transactions systems and methods|
|US20020154757 *||12 Mar 2002||24 Oct 2002||Andreas Hack||Method for call distribution in a call center and associated call distribution apparatus|
|US20040081310 *||13 Feb 2003||29 Apr 2004||Hermann Lueckhoff||Alert modeling|
|US20040141594 *||20 Jan 2003||22 Jul 2004||Brunson Gordon R.||Messaging advise in presence-aware networks|
|US20050060218 *||30 Aug 2004||17 Mar 2005||Ncr Corporation||Targeted messaging system|
|US20050076076 *||9 Aug 2004||7 Apr 2005||Liberty Logistics Inc.||Collaborative logistics information exchange method and apparatus|
|US20050114753 *||26 Nov 2003||26 May 2005||Janaki Kumar||Common message area for a customer interaction center user interface|
|US20050132298 *||16 Dec 2003||16 Jun 2005||Hermann Lueckhoff||Displaying interactive chat sessions|
|US20050187835 *||22 Mar 2005||25 Aug 2005||First Data Corporation||Electronic acknowledgement of receipt of inventory|
|US20050197848 *||23 Mar 2004||8 Sep 2005||Chou Y. H.||Airport customer support dispatch system and method for operation for the same|
|US20050201392 *||25 May 2004||15 Sep 2005||Tam Derek H.K.||Intermediary content gateway system and method|
|US20050256751 *||19 Jul 2005||17 Nov 2005||O'donnell Mary E||Ground-based travel portal|
|US20060031124 *||16 Feb 2005||9 Feb 2006||Liberty Logistics Inc.||Collaborative logistics information exchange method and apparatus|
|US20060122722 *||6 Dec 2004||8 Jun 2006||Chen-Chu Huang||Fabrication management systems and methods|
|US20060156063 *||20 Dec 2005||13 Jul 2006||Travel Sciences, Inc.||Instant messaging transaction integration|
|US20060167699 *||27 Mar 2002||27 Jul 2006||Mikko Rontynen||System and method for managing messaging services|
|US20060190961 *||30 Sep 2005||24 Aug 2006||Sean Handel||Method and system for capturing and calculating complex consumer ratings of goods and services|
|US20070027842 *||27 Jul 2005||1 Feb 2007||Sbc Knowledge Ventures L.P.||Information-paging delivery|
|US20110213642 *||1 Sep 2011||The Delfin Project, Inc.||Management system for a conversational system|
|US20140358799 *||31 May 2013||4 Dec 2014||Bank Of America Corporation||Alert packaging and bundle system|
|WO2007106602A2 *||15 Mar 2007||20 Sep 2007||Global Information Res And Tec||Information repository and answering system|
|U.S. Classification||705/26.41, 705/26.62|
|International Classification||G06Q30/06, G06Q10/10, G06Q30/02|
|Cooperative Classification||G06Q30/0641, G06Q30/02, G06Q30/0633, G06Q30/0623, G06Q10/10, G06Q30/0617, G06Q30/0625, G06Q30/0613|
|European Classification||G06Q30/02, G06Q10/10, G06Q30/0613, G06Q30/0633, G06Q30/0617, G06Q30/0625, G06Q30/0623, G06Q30/0641|
|7 Jun 2001||AS||Assignment|
Owner name: ACCENTURE, LLP, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HAYES, MARC F., JR.;SWEENEY, SEAN M.;ARGO, RONALD L.;REEL/FRAME:011888/0088
Effective date: 20010605