Authentication of service requests using a communications initiation feature

Abstract

Described are computer-based methods and apparatuses, including computer program products, for facilitating communications initiated through a social networking account. A detected message communicated using a social networking account can be determined to satisfy a response criteria. Code for displaying a communications initiation feature on a customer communications apparatus associated with the social networking account can be transmitted. Selection information representing a selection of the communications initiation feature can be received and can include a parameter associated with the selection and origin information. The selection information can be validated by determining that the selection is associated with the social networking account and by comparing the parameter with a stored credential associated with the communications initiation feature. When the selection is validated, the communications can be facilitated.

Description

TECHNICAL FIELD

The technical field relates generally to computer-based methods and apparatuses, including computer program products, for authentication of service requests.

SUMMARY OF THE INVENTION

A brief summary of various exemplary embodiments is presented. Some simplifications and omissions may be made in the following summary, which is intended to highlight and introduce some aspects of the various exemplary embodiments, but not limit the scope of the invention. Detailed descriptions of a preferred exemplary embodiment adequate to allow those of ordinary skill in the art to make and use the inventive concepts will follow in the later sections.

In one aspect, a computerized method for authenticating user service requests is presented. A server transmits data that causes transmission of a service request to the server when actuated. The server receives data representing the service request and data representing a sender of the service request. The server compares (a) the data representing the service request, the data representing the sender of the service request, or both, against (b) pre-defined criteria associated with the data that causes transmission of the service request. The server processes the service request from the sender if the comparison authenticates the service request.

In other examples, any of the aspects above can include one or more of the following features. The data that causes transmission of a service request to the server when actuated comprises an HTTP link.

The techniques, which include both methods and apparatuses, described herein can provide one or more of the following advantages. Website links, such as HTTP links, can be authenticated based on the user that invoked the link, as well as pre-defined criteria for the link, such as an expiration time, a number of users that can invoke the link, and/or the like. Data received about service requests and/or the users that invoke the service requests can be used to appropriately tailor the service request for each user.

Other aspects and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating the principles of the invention by way of example only.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other aspects, features, and advantages of the present invention, as well as the invention itself, will be more fully understood from the following description of various embodiments, when read together with the accompanying drawings.

FIG. 1 is a flow chart showing an example method for processing a service request. FIGS. 2A and 2B are diagrams of an example social networking page for a social networking site according to the present invention.

DETAILED DESCRIPTION

In general, computerized systems and methods are provided for creating links (e.g., web page links, such as HTML links) that can be authenticated by a server. Data about the links and/or the user(s) that invoke the links can be used to authenticate the link based on pre-defined criteria stored for the link. The service request links can be configured based on the pre-defined criteria. For example, the service request links can expire based on the pre-defined criteria such that the links can be invoked only for a predetermined period of time, can only be invoked by a predetermined number of users, can only be invoked by particular users (e.g., based on profile data of the user), etc. This data can be used to navigate the invoking user to the proper location (e.g., to a service request (such as chat or video), or to a particular web page).

FIG. 1 is a flow chart showing an exemplary method 100 for processing a service request. At step 102, the server transmits data that causes transmission of a service request to the server when actuated. At step 104, the server receives data representing the service request and data representing a sender of the service request. At step 106, the server authenticates the service request. If the server authenticates the service request at step 106, the method proceeds to step 108, and the server processes the service request. If the server does not authenticate the service request at step 106, the method proceeds to step 110, and the server disables the service request.

Referring to step 102, the data that causes transmission of a service request to the server when actuated can be, for example, an HTTP link. For example, the link, when actuated (and authenticated as described with respect to step 106 below) can initiate any type of a service request, such as online text chat, audio chat, presentation of a support page (e.g., frequently asked questions), presentation of a coupon, video chat, and/or other types of service requests. The server can send service requests to a remote user for help with navigating a web page, to a remote user in response to a social media message (e.g., in response to a Twitter tweet or a Facebook post), to a remote user by email, a data messaging service (e.g., short messaging service (SMS)), etc. As is described further below, administrators of the server (and related components) can set pre-defined criteria for the service request (e.g., for an HTML link) that configure when the service request can be invoked (e.g., a time expiration).

Referring to step 104, the data representing the service request can include, for example, data about the service request (e.g., about an HTML link), and/or data about the user that invoked the service request (e.g., about the user that clicked the HTML link). For example, if the server transmits an HTML link to a web page, the data representing the service request can include identifying data for the service request (e.g., so the system can identify which service request was invoked), a number of times the HTML link was invoked prior to the current invocation (e.g., a number of times the link was clicked), an amount of time the HTML link has been on the web page, and/or other data about the service request.

Referring further to step 104, the data representing a sender of the service request can include data about the party that invoked the service request. For example, this data may include social networking information, as described in Appendix A (e.g., a user profile for the user from the social networking site).

Referring to step 106, the server authenticates the service request. For example, unless certain properties of the service request are satisfied (e.g., a time limit has not expired, a pre-set number of users have not already invoked the service request, the invoking user matches pre-defined criteria (e.g., the service request was sent to the user, the user is a follower of a social networking site, located in a particular geographic location, and/or the link)), then the server will not authenticate the service request.

Referring further to step 106, the server can compare the data received at step 104 with stored data for the service request. For example, in some embodiments the server compares (a) the data representing the service request, the data representing the sender of the service request, or both, against (b) pre-defined criteria associated with the data the server transmitted in step 102. For example, the pre-defined criteria can be defined by the system administrator. For example, for an HTTP link, the administrator can set a number of times the link can be clicked before the link expires (e.g., can no longer be clicked by a user to invoke the service request), an amount of time the link is active until the link expires, required social networking profile information (e.g., indicative of the originator, such as geographical location and/or other user profile information), etc.

Referring further to step 106, if the server authenticates the service request such that the pre-defined criteria are satisfied (e.g., if the time limit associated with the service request has not expired, if the maximum number of users has not invoked the service request, if the social networking data associated with the user that invoked the request matches the pre-defined criteria, etc.), the server processes the service request at step 108. The server can process the service request by setting up the service request, such as by transmitting a coupon to the sender, setting up an online chat with the sender, setting up a video chat with the sender, sending the user to a help page, and/or setting up any other type of service request.

If the server determines the service request is not authenticated (e.g., if the time limit associated with the service request expired, if the maximum number of users already invoked the service request, if the social networking data associated with the user that invoked the request does not match the pre-defined criteria, etc.), then the server disables the service request at step 110. For example, the server may transmit back to the sender an HTTP error page, a blank page, a page that indicates the link expired and therefore will not be completed, etc.

The authentication allows administrators and agents of the server to create and/or reconnect service requests (e.g., click-to-chat links) that can be limited to a number of users, time expirations, social networking attributes of the sender, etc. For example, if an agent is communicating with a user via online chat and the conversation is dropped, the server can create a link that allows the visitor to return back to the agent he was chatting with, but will only work based on pre-defined criteria associated with the link (e.g., a set number of clicks, time expiration, etc.). The link itself can be sent to the visitor as a regular HTTP link, as SMS, email, or via the original chat itself.

As an example, assume an agent is engaged in a service request with a user (e.g., online chat), and the agent needs to re-boot their computer. The agent can send the user a link so agent can be re-connected with the user after the reboot to resume their conversation. Advantageously, while the server can transmit a link that allows the user to re-engage the service request, the system can use pre-defined criteria to ensure only the same user can re-engage the service request (e.g., based on social networking data), and that the agent is still connected to the system (e.g., limit the link's active time to one hour).

As another example, assume an agent is busy but wants to talk (e.g., online chat, video chat, voice chat) with a user, and the agent determines the best time for a chat is between 4-5 PM EST. The agent (via the server) can send the user a link that is valid only from 4-5 PM (e.g., if the user clicks the link between 4-5 PM, the server will process the service request, otherwise the server will not process the service request). For example, if the user clicks the link outside of the 4-5 PM window, then the server can redirect the user to a landing page.

As another example, the server can use the links to initiate a call sequence. For example, the agent may be available for a call before 5 PM that day. The server can send the user a link that is valid only until 5 PM (e.g., if the user clicks the link any time before 5 PM that day, the server will process the service request, otherwise the server will not process the service request). If properly invoked, the server will initiate a call sequence between the user and the agent.

As another example, the server can use the links for an advertisement campaign (e.g., for marketing content). The server can send links such that the first users that click the link (e.g., the first 100 users) get a special discount (e.g., are presented with a coupon). As another example, the link can be used to keep track of a number of times people scan a bar code to keep track of how many users scan the code. The user can then be presented with a coupon related to the bar code, establish a service request (e.g., chat), and/or the like.

As another example, the validation can validate the sender that invokes the service request (e.g., to verify the sender). For example, social networking parameters (e.g., a profile page) can be used to verify the sender (e.g., if the request is transmitted from a social networking site). For example, a company may monitor tweets posted to Twitter. The company may see a tweet that states “I don't like the services of Company.” The Company can use the server (e.g., manually or automatically) to send a link to the author of the tweet to invoke a service request. For example, the link can be used to invoke a chat with a Company representative (via online chat, video chat, etc.) to discuss their dislikes of the Company, to send the user to a support page to help explain the Company's services, etc. The link, once clicked, can navigate the user to any type of service request channel (such as chat, video, a support page, etc.) based on the time the link exists, the number of clicks, and/or the social parameters of the user (e.g., who the user is, and what the user's location is, etc.). As an example, the social parameters can be used to navigate visitors from Europe to a European chat page, visitors from the US to a US chat page, etc. The social networking parameters can be used to tailor how the service request channels are invoked for each particular user.

The above-described techniques can be implemented in digital and/or analog electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The implementation can be as a computer program product, i.e., a computer program tangibly embodied in a machine-readable storage device, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, and/or multiple computers. A computer program can be written in any form of computer or programming language, including source code, compiled code, interpreted code and/or machine code, and the computer program can be deployed in any form, including as a stand-alone program or as a subroutine, element, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one or more sites.

Method steps can be performed by one or more processors executing a computer program to perform functions of the invention by operating on input data and/or generating output data. Method steps can also be performed by, and an apparatus can be implemented as, special purpose logic circuitry, e.g., a FPGA (field programmable gate array), a FPAA (field-programmable analog array), a CPLD (complex programmable logic device), a PSoC (Programmable System-on-Chip), ASIP (application-specific instruction-set processor), or an ASIC (application-specific integrated circuit). Subroutines can refer to portions of the computer program and/or the processor/special circuitry that implement one or more functions.

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital or analog computer. Generally, a processor receives instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and/or data. Memory devices, such as a cache, can be used to temporarily store data. Memory devices can also be used for long-term data storage. Generally, a computer also includes, or is operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. A computer can also be operatively coupled to a communications network in order to receive instructions and/or data from the network and/or to transfer instructions and/or data to the network. Computer-readable storage devices suitable for embodying computer program instructions and data include all forms of volatile and non-volatile memory, including by way of example semiconductor memory devices, e.g., DRAM, SRAM, EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and optical disks, e.g., CD, DVD, HD-DVD, and Blu-ray disks. The processor and the memory can be supplemented by and/or incorporated in special purpose logic circuitry.

To provide for interaction with a user, the above described techniques can be implemented on a computer in communication with a display device, e.g., a CRT (cathode ray tube), plasma, or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse, a trackball, a touchpad, or a motion sensor, by which the user can provide input to the computer (e.g., interact with a user interface element). Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, and/or tactile input. The above described techniques can also be implemented on mobile devices (e.g., a smartphone, a personal digital assistant device, a cellular telephone, a laptop).

The above described techniques can be implemented in a distributed computing system that includes a back-end component. The back-end component can, for example, be a data server, a middleware component, and/or an application server. The above described techniques can be implemented in a distributed computing system that includes a front-end component. The front-end component can, for example, be a client computer having a graphical user interface, a Web browser through which a user can interact with an example implementation, and/or other graphical user interfaces for a transmitting device. The above described techniques can be implemented in a distributed computing system that includes any combination of such back-end, middleware, or front-end components.

The computing system can include clients and servers. A client and a server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The components of the computing system can be interconnected by any form or medium of digital or analog data communication (e.g., a communication network). Examples of communication networks include circuit-based and packet-based networks. Packet-based networks can include, for example, the Internet, a carrier internet protocol (IP) network (e.g., local area network (LAN), wide area network (WAN), campus area network (CAN), metropolitan area network (MAN), home area network (HAN)), a private IP network, an IP private branch exchange (IPBX), a wireless network (e.g., radio access network (RAN), 802.11 network, 802.16 network, general packet radio service (GPRS) network, HiperLAN), and/or other packet-based networks. Circuit-based networks can include, for example, the public switched telephone network (PSTN), a private branch exchange (PBX), a wireless network (e.g., RAN, bluetooth, code-division multiple access (CDMA) network, time division multiple access (TDMA) network, global system for mobile communications (GSM) network), and/or other circuit-based networks.

Devices of the computing system and/or computing devices can include, for example, a computer, a computer with a browser device, a telephone, an IP phone, a mobile device (e.g., cellular phone, personal digital assistant (PDA) device, laptop computer, electronic mail device, iPhone available from Apple®), a server, a rack with one or more processing cards, special purpose circuitry, and/or other communication devices. The browser device includes, for example, a computer (e.g., desktop computer, laptop computer) with a world wide web browser (e.g., Microsoft® Internet Explorer® available from Microsoft Corporation, Mozilla® Firefox available from Mozilla Corporation, Chrome available from Google®, Safari available from Apple®, etc.). A mobile computing device includes, for example, a Blackberry®. IP phones include, for example, a Cisco® Unified IP Phone 7985G available from Cisco System, Inc, and/or a Cisco® Unified Wireless Phone 7920 available from Cisco System, Inc.

One skilled in the art will realize the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The foregoing embodiments are therefore to be considered in all respects illustrative rather than limiting of the invention described herein. Scope of the invention is thus indicated by the appended claims, rather than by the foregoing description, and all changes that come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

FIGS. 2A and 2B are diagrams of example social networking pages 200A and 200B, respectively, for a social networking site according to the present invention. Social networking page 200A includes posted messages 202A through 202N (collectively posted messages 202). Posted message 202A can include a logo 204, username user_one 206, content 208 (i.e., “My computer has been very slow lately”), and posting information 210 (i.e., “8 minutes ago via web”). The username user_one 206 indicates which user posted the message 202A (e.g., a user of a user device). This can be advantageous, for example, to tell users apart when multiple user devices are posting messages for a particular message thread or message board. The content 208 can include the text that the posting user user_one 206 entered for the posted message 202A. The posting information 210 can indicate how long ago user_one 206 posted the message 202A (i.e., 8 minutes ago) and how user_one 206 posted the message (i.e., via the web).

Posted message 202N can include a logo 212, username user_one 206, content 214 (i.e., “What is the best kind of computer hard drive to buy?”), and posting information 216 (i.e., “7 minutes ago via web”). Posted messages 202 are used for illustrative purposes only and are not intended to be limiting. One skilled in the art can appreciate that the information contained within the posted messages 202 can be modified without departing from the spirit of the techniques described herein.

The social media account associated with user_one 206 (where “user_one” is a screen name representative of a particular user device or of an operator of the user device) can post message 202A to the social networking server 102. One minute later user_one 206 posted the posted (using a user device 104) message 202N to the social networking server 102. User_one 206 can configure his account with the social networking site to control which other users can see posted messages 202A and 202N. There can be posted messages by other users between posted messages 202A and 202N (e.g., a different user device can post a message in response to posted message 202A). For example, all people following the posts on social networking page 200A can see posted message 202A and can choose to post a message in response. Similarly, for example, any person that user_one 206 has established a relationship within the social networking site (e.g., friends) can view the posted message 202A, and/or any user device can view posted message 202A.

The social networking page 200B in FIG. 2B includes posted messages 202A and 202N from FIG. 2A and also includes posted message 202N+1. Posted message 202N+1 includes a logo 218, username auto_reply 220, content 222 (i.e., “What do you want to know about hard drives?”), a link 224 that causes transmission of a service request to a monitoring server, and posting information 226 (i.e., “5 minutes ago via API in response to user_one”). The posting information 226 indicates that posted message 202N+1 was posted by auto_reply 220 (e.g., a user with the screen name “auto_reply,” which may correspond to an individual user or a company) five minutes ago via an API (e.g., an API to the social networking site provided by a social networking server, which allows messages to be posted in response to a user's message) in response to the posted message 202N by user_one 206. The posted message 202N+1 can be transmitted automatically (e.g., by a monitoring server based on rules stored in a database) or manually (e.g., by an operator of a monitoring server).

Claims

1. A computer-implemented method, comprising: detecting that a connection corresponding to an interaction associated with a service request has been dropped, wherein the connection is between a device associated with a remote user and a server associated with an agent;generating a link, wherein the link is associated with a set of criteria that defines when the link can be invoked in order to allow the user to be returned back to the same agent;transmitting the link, wherein when the link is actuated by the device associated with the remote user, a determination is made as to whether the set of criteria is fulfilled;receiving input corresponding to actuation of the link;determining whether the set of criteria is fulfilled, wherein when the set of criteria is fulfilled, the connection between the device associated with the remote user and the server associated with the same agent can be resumed;determining that the same agent is still connected to the server; andfacilitating resumption of the connection corresponding to the interaction associated with the service request, wherein the resumption is facilitated when the same agent is still connected to the server and as a result of the set of criteria having been fulfilled, and wherein the connection is resumed between the device associated with the remote user and the server associated with the same agent.

2. The computer-implemented method of claim 1, wherein the set of criteria defines a limitation on a number of times the link can be actuated prior to automatic expiration of the link.

3. The computer-implemented method of claim 1, wherein facilitating the resumption of the connection includes establishing an online chat session between the device associated with the remote user and the server associated with the same agent.

4. The computer-implemented method of claim 1, wherein the link is transmitted to the device associated with the remote user via a short message service (SMS) message.

5. The method of claim 1, wherein the set of criteria defines a time range during which the link can be invoked, and wherein the set of criteria is fulfilled as a result of the link having been actuated at a time within the time range.

6. The method of claim 1, wherein the set of criteria defines a time, and wherein the set of criteria is fulfilled as a result of the link having been actuated prior to the time.

7. The method of claim 1, wherein the set of criteria defines social networking data associated with the remote user, and wherein the set of criteria is fulfilled in response to the remote user being validated based on the social networking data.

8. A system, comprising: one or more processors; andmemory storing thereon instructions that, as a result of being executed by the one or more processors, cause the system to: detect that a connection corresponding to an interaction associated with a service request has been dropped, wherein the connection is between a device associated with a remote user and a server associated with an agent;generate a link, wherein the link is associated with a set of criteria that defines when the link can be invoked in order to allow the user to be returned back to the same agent;transmit the link, wherein when the link is actuated by the device associated with the remote user, a determination is made as to whether the set of criteria is fulfilled;receiving input corresponding to actuation of the link; determine whether the set of criteria is fulfilled, wherein when the set of criteria is fulfilled, the connection between the device associated with the remote user and the server associated with the same agent can be resumed;determine that the same agent is still connected to the server; andfacilitate resumption of the connection corresponding to the interaction associated with the service request, wherein the resumption is facilitated when the same agent is still connected to the server and as a result of the set of criteria having been fulfilled, and wherein the connection is resumed between the device associated with the remote user and the server associated with the same agent.

9. The system of claim 8, wherein the set of criteria defines a limitation on a number of times the link can be actuated prior to automatic expiration of the link.

10. The system of claim 8, wherein the instructions that cause the system to facilitate the resumption of the connection further cause the system to establish an online chat session between the device associated with the remote user and the server associated with the same agent.

11. The system of claim 8, wherein the link is transmitted to the device associated with the remote user via a short message service (SMS) message.

12. The system of claim 8, wherein the set of criteria defines a time range during which the link can be invoked, and wherein the set of criteria is fulfilled as a result of the link having been actuated at a time within the time range.

13. The system of claim 8, wherein the set of criteria defines a time, and wherein the set of criteria is fulfilled as a result of the link having been actuated prior to the time.

14. The system of claim 8, wherein the set of criteria defines social networking data associated with the remote user, and wherein the set of criteria is fulfilled in response to the remote user being validated based on the social networking data.

15. A non-transitory, computer-readable storage medium storing thereon executable instructions that, as a result of being executed by one or more processors of a computer system, cause the computer system to: detect that a connection corresponding to an interaction associated with a service request has been dropped, wherein the connection is between a device associated with a remote user and a server associated with an agent;generate a link, wherein the link is associated with a set of criteria that defines when the link can be invoked in order to allow the user to be returned back to the same agent;transmit the link, wherein when the link is actuated by the device associated with the remote user, a determination is made as to whether the set of criteria is fulfilled;receive input corresponding to actuation of the link;determine whether the set of criteria is fulfilled, wherein when the set of criteria is fulfilled, the connection between the device associated with the remote user and the server associated with the same agent can be resumed;determine that the same agent is still connected to the server; andfacilitating resumption of the connection corresponding to the interaction associated with the service request, wherein the resumption is facilitated when the same agent is still connected to the server and as a result of the set of criteria having been fulfilled, and wherein the connection is resumed between the device associated with the remote user and the server associated with the same agent.

16. The non-transitory, computer-readable storage medium of claim 15, wherein the set of criteria defines a limitation on a number of times the link can be actuated prior to automatic expiration of the link.

17. The non-transitory, computer-readable storage medium of claim 15, wherein the link is transmitted to the device associated with the remote user via a short message service (SMS) message.

18. The non-transitory, computer-readable storage medium of claim 15, wherein the executable instructions that cause the computer system to facilitate the resumption of the connection further cause the computer system to establish an online chat session between the device associated with the remote user and the server associated with the same agent.

19. The non-transitory, computer-readable storage medium of claim 15, wherein the set of criteria defines a time range during which the link can be invoked, and wherein the set of criteria is fulfilled as a result of the link having been actuated at a time within the time range.

20. The non-transitory, computer-readable storage medium of claim 15, wherein the set of criteria defines a time, and wherein the set of criteria is fulfilled as a result of the link having been actuated prior to the time.

21. The non-transitory, computer-readable storage medium of claim 15, wherein the set of criteria defines social networking data associated with the remote user, and wherein the set of criteria is fulfilled in response to the remote user being validated based on the social networking data.