Abstract:
A device may receive an indication to generate a link associated with accessing a message. The message may be intended for a shared device identifier of a receiver device identified by a receiver device identifier, where the shared device identifier is shared by multiple receiver devices. The device may store information associating the message with the receiver device identifier. The device may generate the link using information associated with the message. The device may provide the link to the receiver device after generating the link. The device may receive a request, from a requesting device, to access the message, the request including a device identifier associated with the requesting device. The device may selectively permit or prevent access to the message, by the requesting device, based on the stored information and the device identifier associated with the requesting device.
Abstract:
Systems and methods described herein enable call center managers to identify behavioral drivers for improving call agents' performance. A computing device obtains call data for multiple calls received at a call center and plots individual calls of the multiple calls, based on the call data, against three behavioral measures related to agent activities. The computing device identifies an optimal zone, among the plotted individual calls, for a selected performance metric value over the three behavioral measures. The computing device also plots a particular agent's calls, based on the call data, against the three behavioral measures and identifies an agent's zone, among the plotted agent's calls, for the selected performance metric value. The computing device generates a visual model of the optimal zone and the agent's zone within the context of the three behavioral measures.
Abstract:
Systems, methods, devices, and non-transitory storage media provide a web-based graphical user interface to allow a user to control a softphone of a user device. A context handler operates on the user device and manages a page context of the web-based graphical user interface. A call manager operates as a RESTful web service on the user device. The context handler and the call manager communicate using JavaScript Object Notation with Padding (JSONP) messages. The call manager includes a finite state machine that indicates a current state of the softphone. The call manager generates application programming interface calls to the softphone in response to receiving JSONP messages. The user interface is updated to reflect the current state of the softphone based on execution of user selections by the softphone. The context handler chunks data into multiple JSONP messages if data exceeds a data size limitation of the JSONP.
Abstract:
A method may include receiving a call from a caller and determining whether the call has been queued for at least a predetermined period of time. The method may also include interacting with the customer via an interactive voice response unit, in response to determining that the call has been queued for at least the predetermined period of time, to offer a call back service to the customer. The call back service may include a scheduled call back or an immediate type call back when an agent is available. The method may further include receiving, from the customer and via the interactive voice response unit, an indication that the customer would like a call back and queuing the call back.
Abstract:
A network device receives credentials of a user of a client device, and receives an enrollment request from the client device, wherein the enrollment request includes a network address of the client device. The network device generates a token comprising the network address and an identifier of the user, encrypts the token, and sends the encrypted token to the client device. The network device receives, when the client device attempts to access a protected resource or a network service, the encrypted token from the client device for authenticating the client device without further requiring the credentials of the user.
Abstract:
A device can establish an identity for an individual by communicating with a first set of devices. The first set of devices can include a user device, a first server device associated with a certificate authority, or a second server device associated with an identity provider. The device can authenticate the identity of the individual by communicating with a second set of devices. The second set of devices can include the user device, or a third server device associated with a first service provider. The device can authorize the identity of the individual to be used by one or more service providers by communicating with a third set of devices. The third set of devices can include the user device, the third server device, or a fourth server device associated with a second service provider.
Abstract:
A device may receive an authentication request generated based on a request to access a service. The authentication request may include a user identifier. The device may identify a mobile device associated with the user identifier. The device may authenticate the mobile device, and may generate an access notification based on authenticating the mobile device. The access notification may include information relating to the request to access the service. The device may provide the access notification to the mobile device, and may receive an access response from the mobile device. The access response may indicate whether to permit access to the service. The device may cause access to the service to be permitted when the access response indicates to permit access to the service, or may cause access to the service to be denied when the access response indicates to deny access to the service.
Abstract:
A method may include identifying diverse applications associated with supervision of agent work stations. The method may include generating a unified view interface based on supervisory communications associated with the diverse applications and receiving a request for the unified view interface from a supervisory interface device. The method may include exporting the unified view interface to the supervisory interface device. The method may further include receiving notifications associated with the diverse applications, and sending the notifications to the supervisory interface device.
Abstract:
A device generates parameters identifying selectively revealed un-obfuscated information associated with administering and assessing a Turing test. The device provides, to a client device, a challenge based on the parameters. The challenge directs the client device to selectively reveal the un-obfuscated information for presentation to a user associated with the client device. The device receives a response, to the challenge, from the client device and determines, based on the response and the parameters, whether the user associated with the client device is human. The device selectively performs an action based on determining whether the user associated with the client device is human.
Abstract:
A method, a device, and a non-transitory storage medium to receive a referral request from a customer of a service provider; generate a referral code based on a receipt of the referral request; receive a message from the customer to a non-customer, wherein the message includes the referral code; store referral information included in the message, wherein the referral information includes a communication address of the non-customer, the referral code, and a communication address of the customer; receive a request from the non-customer to subscribe to a service offered by the service provider; request the referral code or a referent of the referral code from the non-customer; and use the referral code or the referent to assign a reward to the customer.