System and method for automating customer relations in a communications environment

Abstract

A method includes receiving performance data associated with a service provided by at least one component of a communication network to one or more subscribers. The performance data may be gathered by one or more passive listening devices that monitor a performance characteristic of the at least one component of the communication network. The method further includes identifying the at least one component that provides a particular service to a particular subscriber based on a subscriber inquiry received from the particular subscriber. The method further includes identifying particular performance data within the received performance data. The particular performance data may be associated with the particular service provided by the at least one component. The method further includes determining a performance status of the at least one component, based on the particular performance data.

Description

FIELD OF THE DISCLOSURE

The present disclosure relates generally to automating customer support.

BACKGROUND

In today's competitive communications market, service providers strive to improve system performance. Although near perfect reliability and extraordinary speeds are goals of service providers, often unplanned and unexpected phenomena degrade system performance. When a customer feels that performance of their communications system is less than average, they often call a service center to request information, determine if there is an outage, or see if there is work in process to solve their problem. Often customer equipment fails, yet the customer will blame the service provider and inquire whether the service provider is having problems.

Communication service providers seek to efficiently address these concerned subscribers. However, service providers often lack the available resources to identify problems that are specific to subscribers. A single subscriber may be provided with physical connections and signal processing from many different providers within a network.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that, for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:

FIG. 1 presents a block diagram of a communication system that incorporates teachings of the present disclosure; and

FIG. 2 shows a flow diagram of a method for providing customer service for a communication service provider in accordance with the teachings disclosed herein.

DETAILED DESCRIPTION

A system and method are disclosed for automating network performance reporting. In some cases, the reporting may be provided to a customer and/or to a customer support department. Depending upon implementation detail, a system incorporating the present teachings may include a passive listening device configured to monitor portions of a communication network. A performance database may be coupled directly and/or indirectly to the passive listening device and configured to store network performance data.

A customer relations module may be set up to receive a subscriber inquiry and to identify at least one component of a communication network that affects the subscriber. The module may retrieve relevant performance data on identified components of the communication network to provide customer-specific communication performance data to the subscriber and/or an agent assisting the subscriber. In one configuration, the passive listening device can be configured to monitor at least one performance characteristic of a communications network component and to output a plurality of signals representing the performance characteristic. A customer relations management module may be configured to manage customer connection data, to create a list of components used by a given subscriber, and to identify and provide a status of components that have or continue to affect the service provided to the given subscriber.

Referring to FIG. 1 an illustrated system 100 for detecting network performance and providing customer specific performance data to a customer via a customer relationship management module 124 is provided. As depicted, system 100 may help support subscribers and include client interaction interfaces such as e-mail interface 104, telephone interface 106, mobile/wireless interface 102, utilizing antennae 103, and/or Internet interface 108.

System 100 may be implemented by and/or in connection with a communications network-like wide area network (WAN) 110 that facilitates the coupling together of a plurality of service providers such as Internet Service Provider (ISP) 114, power company 116, local Telco provider 118, wireless service provider 112, and messaging service provider 122. System 100 may also include a service bureau offering that assists in near real time tracking of network performance for individual subscribers. As depicted, this service bureau may include a local area network (LAN) 128 interconnecting several components such as customer relationship management module 124, passive listening device interrogator 120, activity database 126, and agent 130.

In an illustrated embodiment, passive listening device interrogator 120 may include a specialized server for locating, addressing, and receiving information from various passive listening devices (PLDs) such as stand-alone PLD 150 located within WAN 110. As depicted, WAN 110 could take several forms including the Public Internet. Depending upon how a designer elects to implement system 100, various components of WAN 110 may have PLDs installed within them. For example, each of the depicted service providers and each of the subscriber interface mechanisms could contain at least one PLD. Stand-alone PLDs may also be installed at pre-defined critical locations. These PLDs may be configured to periodically transmit status information over WAN 110, and/or the PLDs may be responsive to interrogation by PLD interrogator 120.

When a subscriber experiences perceived problems in communicating via WAN 110 and/or some other network, the subscriber may call a customer service department and be placed in contact with customer relationship management module (CRMM) 124. CRMM 124 may be designed to include an auto-response system and a database maintaining customer information such as customer account information. In operation, CRMM 124 may receive a call and based on “call data” received with the call such as CallerID, a CRMM 124 database may be accessed to determine additional information about the subscriber. The additional information can include, for example, subscriber location, the services provided to the subscriber, the communication path servicing the subscriber, and/or a list of PLD monitored components providing service to the subscriber.

Utilizing the customer/subscriber specific information, activity database 126 may be accessed over LAN 128. In some implementations, CRMM 124 may request activity data specific to one or more of the monitored components, which may be components of WAN 110 that supply/support the subject subscriber. Activity database 126 may respond to the request by providing information reflecting the performance of monitored components. The information may be updateable. For example, passive listening device interrogator 120 may send queries to distributed PLDs, receive data from component-based PLDs throughout WAN 110, and write some portion of the received data to activity database 126.

In one instance, PLD interrogator 120 may send periodic queries to PLDs throughout WAN 110. PLD interrogator 120 may also send near-real-time queries to implicated PLDs throughout WAN 110 in response to a particular subscriber inquiry. PLD interrogator 120 can operate on the received data and communicate the network status and/or component status to CRMM 124. Thus, when CRMM 124 requests information specific to a customer/subscriber, activity database 126 may provide historical customer-specific performance data to CRMM 124. In addition, CRMM 124 may also gather additional real-time data. This may not be the only way information is input into activity database 126. For example, outside plant personnel, network status organizations, and/or others may also provide or key-in information to activity database 126.

If CRMM 124 can identify a component in WAN 110 that is under-performing and/or has a significant degradation, the news of this network problem may be sent to the subscriber making the inquiry utilizing an auto-response system. System or component degradation may be hierarchically ordered by CRMM 124 in order of occurrence (date and time), probability of causing a problem, and/or severity. Subject matter in a subscriber query may be linked to an occurrence utilizing a failure analysis, and CRMM 124 may automatically reply to the subscriber request via a communication interface linked to or with WAN 110.

In some cases, the reply to a subscriber may be customer-specific system performance status even when the system is operating within its specified limits. An auto response that provides system performance may be provided to the subscriber based on real-time actual performance, a derived performance characteristic, or a high probability that a component within a communication system has caused unacceptable performance, and/or some other metric or data. In the event that a subscriber inquiry is relatively complicated, the inquiry may be sent from CRMM 124 to agent 130. As such, agent 130 may have access to activity database 126 via LAN 128, and CRMM 124 may automatically provide agent 130 with a list of system performance characteristics that come from distributed PLDs and are subscriber-specific. Although only one agent is illustrated, CRMM 124 may be configured to supply hundreds of agents.

In practice, CRMM 124 may store historic communication responses to subscriber inquiries. As such, in some cases CRMM 124 may determine with a high probability what the problem is for a given subscriber circumstance and provide an inquiring subscriber with a “canned” response. In practice, responses may be assigned confidence levels based on how likely the response is to cover the subscriber inquiry. When the confidence level is low, the inquiry can be routed to agent 130 for manual processing; when the confidence level is high the auto response system can automatically respond.

The system disclosed may utilize many different methods to monitor the communication network 110. A stand-alone PLD 150 or any PLD may use monitoring technologies based on, for example, anomaly detection, heuristics, traffic pattern analysis, application analysis, payload analysis, code violations, as well as passive listening and/or active listening. In some embodiments, an appliance or stand-alone PLD 150 may provide for near-real-time analysis of usage, availability, and performance for applications and services running across public and private networks. For example, stand-alone PLD 150 may measure response times for Internet Protocol applications, network applications, and/or other Web applications. Depending upon implementation detail, stand-alone PLD 150 may be coupled to a port on a data center switch. In some applications, stand-alone PLD 150 may be located behind a corporate firewall, it may track and analyze network activity and usage, and generated information may be stored in a repository or database.

Utilizing stand-alone PLD 150 in combination with activity database 126 may allow agents 130 and technicians to more quickly identify and resolve network problems. In operation, localizing a problem may be accomplished by considering, for example, the interdependencies of a larger network. In effect, such a solution may narrow down the search for customer-specific performance data to a particular component or platform. When a subscriber calls for service, they may be asked questions about their problem. Utilizing an interactive-voice-response system (IVR) the system may be able to learn more about the subscriber's problem and pinpoint a malfunctioning device. Moreover, call-center support personnel may be informed of the problem and made aware of customers who could be impacted by the problem—allowing call center personnel to proactively notify potentially affected customers.

Referring now to FIG. 2 a method of operation that may be used in connection with system 100 of FIG. 1 is illustrated. The method starts at 202 and proceeds to 204 where a subscriber submits an inquiry to a service provider. Data can be gathered regarding the inquiry such as a CallerID telephone number, an e-mail address, and account number, or a MAC address of the subscriber. Additional data may be gathered from prompting the caller and storing caller responses. Additional data can include details about the phenomena surrounding the caller's problem such as slow speed, inoperability, intermittency or whether the problem is reoccurring. This information can be utilized to help diagnose and isolate the cause of the problem.

The subscriber information may be stored at step 206; at decision step 208 it may be determined whether the subscriber can be accurately identified. If the subscriber cannot be accurately identified, then a failure may be recorded at step 212 and additional information may be requested at 210. The method may then proceed back to step 206. If the subscriber can be identified, the monitored components that supply the subscriber with communication services may be identified at step 214. At step 216, the monitored network components that are linked to the subscriber may be queried for past performance and possibly current performance problems. A reply to the subscriber may be created from a library of replies based on component performance at step 218. A confidence level may be assigned to each reply at step 220 based on the likelihood that a reply provides useful information. If the confidence level for a given reply is above a predetermined value, the method may proceed to reply at step 226 where the reply is sent. If the confidence level of the reply is less than a predetermined level, the inquiry may be routed to an agent at step 224 and the process ends at step 228.

The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

1. A method comprising: receiving performance data associated with a service provided by at least one component of a communication network to one or more subscribers, wherein the performance data is gathered by one or more passive listening devices that monitor a performance characteristic of the at least one component of the communication network;identifying a particular component that provides a particular service to a particular subscriber based on a subscriber inquiry received from the particular subscriber;identifying particular performance data within the received performance data, the particular performance data associated with the particular service provided by the particular component; andbased on the particular performance data, determining a performance status of the particular component.

2. The method of claim 1, further comprising: generating one or more responses to the subscriber inquiry based on the performance status;assigning a confidence level to each of the one or more responses based on relevance to the subscriber inquiry; andautomatically sending the one or more responses to the particular subscriber, the one or more responses having a corresponding assigned confidence level that satisfies a threshold level.

3. The method of claim 2, further comprising automatically sending the subscriber inquiry to an agent station in response to determining that the assigned confidence level corresponding to each of the one or more responses does not satisfy the threshold level.

4. The method of claim 3, further comprising sending information identifying the particular component to the agent station.

5. The method of claim 2, wherein the one or more responses are generated based on information obtained from a database.

6. The method of claim 1, further comprising: receiving network status data associated with the particular component of the communication network, wherein the network status data is generated by the one or more passive listening devices that monitor a network status of the particular component;determining a particular network status of the particular component that provides the particular service to the particular subscriber, wherein the particular network status is determined based on the received network status data; andin response to determining that the particular network status indicates a network problem, generating one or more status-specific responses to the subscriber inquiry, the one or more status-specific responses indicating the network problem.

7. The method of claim 6, wherein the network status data includes network status information, component network status information, or a combination thereof.

8. The method of claim 6, wherein the one or more status-specific responses indicate a severity of the network problem and include occurrence information associated with one or more occurrences of the network problem.

9. The method of claim 1, wherein the performance data is received from a performance database.

10. An apparatus comprising: a database interface to request performance data from a performance database, wherein the performance data is associated with a service provided by at least one component of a communication network to one or more subscribers, and wherein the performance data is gathered by a plurality of passive listening devices that monitor a performance characteristic of the at least one component;a customer relationship management component configured to: identify a particular component based on a subscriber inquiry received from a particular subscriber;identify particular performance data within the performance data obtained from the performance database; anddetermine a performance status of the particular component based on the particular performance data; anda communication component to send one or more responses to the particular subscriber, the one or more responses based on the performance status.

11. The apparatus of claim 10, wherein the customer relations management component is further configured to classify the subscriber inquiry as a network performance issue, and wherein the particular component is identified based of whether the particular performance data indicates network degradation.

12. The apparatus of claim 10, wherein the customer relations management component is further configured to: determine, based on the particular performance data, whether the particular component has unacceptable performance; anddetermine a ranking for the at least one component based on a level associated with the unacceptable performance.

13. The apparatus of claim 10, wherein at least one of the plurality of passive listening devices is located behind a firewall of the communication network.

14. The apparatus of claim 10, wherein at least one of the plurality of passive listening devices is located within a network appliance of the communication network.

15. The apparatus of claim 10, wherein each of the plurality of passive listening devices is coupled to a data center switch.

16. The apparatus of claim 10, wherein the performance data in the performance database is associated with the particular subscriber based on a geographic location associated with the particular subscriber, subscriber connection data, one or more services provided to the particular subscriber, or a combination thereof.

17. The apparatus of claim 10, wherein each of the plurality of passive listening devices is configured to monitor the performance characteristic based on anomaly detection, heuristics, traffic pattern analysis, application analysis, payload analysis, code violations, or a combination thereof.

18. The apparatus of claim 10, wherein at least one of the plurality of passive listening devices is a stand alone device that is not disposed within another network component.

19. The apparatus of claim 10, wherein the performance data is stored in the performance database by a server that periodically queries the plurality of passive listening devices to obtain the performance data.

20. An apparatus comprising: means for requesting performance data from a performance database, wherein the performance data is associated with a service provided by at least one component of a communication network to one or more subscribers, and wherein the performance data is gathered by one or more passive listening devices that monitor a performance characteristic of the at least one component;means for identifying a particular component that provides a particular service to a particular subscriber based on a subscriber inquiry received from the particular subscriber;means for identifying particular performance data within the performance data obtained from the performance database, the particular performance data associated with the particular service provided by the particular component;means for determining a performance status of the particular component based on the particular performance data; andmeans for sending one or more responses to the particular subscriber, the one or more responses based on the performance status.