Abstract: Techniques are described for automatically creating resolution scripts. When a user contacts an agent with an issue, intent parameters associated with the user and/or the user's electronic device are collected. As the agent resolves the issue, a script engine monitors the actions taken by the agent. The script engine also locates content related to the issue which may be used to train agents about the issue. Actions taken by the agent and the located content is used to create a resolution script, which is stored and associated with the intent parameters. When a similar issue arises in the future, intent parameters from that issue can be used to match a resolution script created for the issue by matching intent parameters from the issue with intent parameters associated with the resolution script. Thus, an agent can use the resolution script to assist the agent in resolving the issue.

Abstract: Techniques are described for estimating capacity need in a service network and for dynamically adjusting resources to meet the estimated capacity. When an enterprise is contacted by a user with an issue, a service system determines an intent of the contact. The service system then determines if the issue is something that may arise with a significant number of users in the foreseeable future. Once the service system knows how many users with a similar issue may be contacting the enterprise, the service system makes a determination as to the capacity the service system has to handle the specific issue and the number of user communications. This is accomplished by searches of agent profiles to determine which agents have the ability to resolve the intent. Agents so identified are added to the capacity until the capacity is great enough to handle the expected user communications.

Abstract: Techniques are described for estimating capacity need in a service network and for dynamically adjusting resources to meet the estimated capacity. When an enterprise is contacted by a user with an issue, a service system determines an intent of the contact. The service system then determines if the issue is something that may arise with a significant number of users in the foreseeable future. Once the service system knows how many users with a similar issue may be contacting the enterprise, the service system makes a determination as to the capacity the service system has to handle the specific issue and the number of user communications. This is accomplished by searches of agent profiles to determine which agents have the ability to resolve the intent. Agents so identified are added to the capacity until the capacity is great enough to handle the expected user communications.

Abstract: Techniques are described for automatically creating resolution scripts. When a user contacts an agent with an issue, intent parameters associated with the user and/or the user's electronic device are collected. As the agent resolves the issue, a script engine monitors the actions taken by the agent. The script engine also locates content related to the issue which may be used to train agents about the issue. Actions taken by the agent and the located content is used to create a resolution script, which is stored and associated with the intent parameters. When a similar issue arises in the future, intent parameters from that issue can be used to match a resolution script created for the issue by matching intent parameters from the issue with intent parameters associated with the resolution script. Thus, an agent can use the resolution script to assist the agent in resolving the issue.

Abstract: Techniques for identifying a likely subject of a user contact with a user support network and routing the user contact to an agent or an application that is determined to have relevant experience with the subject or issue the user is experiencing. To identify a likely subject of the user contact, data is gathered from a user device as well as from secondary user devices located near the user device. Also, data related to network resources the user device is using, history data of a user's previous contacts with the user support network, and account data associated with the user device is also collected. As a result, the user contact is routed to a knowledgeable agent who is likely to resolve the user's issue without further routing or consultation, thus saving network bandwidth, user device resources, agent time, user time, etc.

Abstract: Techniques for identifying a likely subject of a user contact with a user support network and routing the user contact to an agent or an application that is determined to have relevant experience with the subject or issue the user is experiencing. To identify a likely subject of the user contact, data is gathered from a user device as well as from secondary user devices located near the user device. Also, data related to network resources the user device is using, history data of a user's previous contacts with the user support network, and account data associated with the user device is also collected. As a result, the user contact is routed to a knowledgeable agent who is likely to resolve the user's issue without further routing or consultation, thus saving network bandwidth, user device resources, agent time, user time, etc.

Abstract: A user identifier of a customer may be obtained from a customer identification database of a wireless telecommunication carrier in response to receiving a support request to resolve a service issue for the customer. Subsequently, a determination may be made based on the user identifier as to whether the customer satisfies one or more conditions. The one or more conditions may include that the customer is previously assigned to a customer support team of the wireless telecommunication carrier for a prior support session, a service account associated with the user identifier is already assigned to the customer support team, or the customer was formerly assigned to the customer support team while using a former service account that is now expired. Accordingly, the customer support team may be designated to assist the customer with the service issue when the customer satisfies a condition of the one or more conditions.

Abstract: A user identifier of a customer may be obtained from a customer identification database of a wireless telecommunication carrier in response to receiving a support request to resolve a service issue for the customer. Subsequently, a determination may be made based on the user identifier as to whether the customer satisfies one or more conditions. The one or more conditions may include that the customer is previously assigned to a customer support team of the wireless telecommunication carrier for a prior support session, a service account associated with the user identifier is already assigned to the customer support team, or the customer was formerly assigned to the customer support team while using a former service account that is now expired. Accordingly, the customer support team may be designated to assist the customer with the service issue when the customer satisfies a condition of the one or more conditions.