JP6993712B2 - Information processing equipment, information processing methods and programs - Google Patents

Description

The present invention relates to an information processing apparatus, an information processing method and a program.

With the spread of Web search engines and SNS (Social Networking Service), it is important for business to take measures against word-of-mouth posted by general users on the network. For example, Patent Document 1 discloses a word-of-mouth information management system that collects word-of-mouth information from a plurality of Web pages, outputs a word-of-mouth information list, and accepts and replies to input of reply writing for each word-of-mouth information.

Japanese Unexamined Patent Publication No. 2014-38647

However, the invention according to Patent Document 1 only replies to the word-of-mouth, and does not encourage the user to post the word-of-mouth.

One aspect is to provide an information processing device or the like that can promote the posting of word-of-mouth.

The information processing device according to one aspect requests a user to post a word-of-mouth related to a search target that can be searched on the Web search site, a storage unit that stores the URL of a posting page that can be posted on the Web search site, and a storage unit that stores the word-of-mouth. A generation unit that generates a shortened URL that is a request page for making a transition to the posting page and shortens the URL of the request page according to the search target, and an output unit that outputs the shortened URL. When an access based on the shortened URL is received from the user terminal , the generation unit includes a transfer unit that transfers to the request page and a reception unit that accepts the input of the information of the user who requests the posting of the word-of-mouth . The shortened URL corresponding to the search target and the user is generated, and the output unit is a message requesting the posting of the word-of-mouth, and the message including the shortened URL is transmitted to the user terminal, and the storage unit. Is request information indicating the content of the request to the user, stores the request information indicating the search target related to the shortened URL and the information of the user, and the word-of-mouth for the search target is the Web search site. Further includes a collecting unit for collecting from the above and a second receiving unit for receiving the selection input of the word-of-mouth corresponding to the request information, and the storage unit stores the selected word-of-mouth and the request information in association with each other. It is characterized by that.

On one side, it can encourage the posting of reviews.

It is a schematic diagram which shows the configuration example of the word-of-mouth request system. It is a block diagram which shows the configuration example of a server. It is explanatory drawing which shows an example of the record layout of a facility DB, a person in charge DB, a word-of-mouth DB, a request DB, and a session DB. It is a block diagram which shows the configuration example of a user terminal. It is explanatory drawing which shows an example of the word-of-mouth communication list screen. It is explanatory drawing which shows an example of the request form. It is explanatory drawing which illustrates an example of a message. It is explanatory drawing which shows the display screen example in a user terminal. It is explanatory drawing which shows an example of the word-of-mouth detail screen. It is explanatory drawing which shows an example of the transmission history screen. It is explanatory drawing which shows an example of the request detail screen. It is explanatory drawing which shows an example of a report screen. It is a flowchart which shows an example of the processing procedure which a server executes. It is a flowchart which shows an example of the processing procedure which a user terminal executes.

Hereinafter, the present invention will be described in detail with reference to the drawings showing the embodiments thereof.
(Embodiment)
FIG. 1 is a schematic diagram showing a configuration example of a word-of-mouth request system. In this embodiment, a word-of-mouth request system for requesting a user to post a word-of-mouth will be described. The word-of-mouth request system includes an information processing device 1, a user terminal 2, a person in charge terminal 3, and a search engine server 4. Each device is communicatively connected to a network N such as the Internet.

The search engine server 4 is a server computer that functions as a web search engine, and is a server computer that provides a search site that searches a website by receiving an input of a search query. In the present embodiment, the search engine server 4 provides a map search service (for example, Google Map (registered trademark)) as one function of the search site, and performs a map search (search based on area name, terminal location information, keywords, etc.). ) Allows you to search for facilities (for example, stores). Furthermore, on the search site, when a certain facility is searched by a map search, the user can post a review of the facility. For example, when a map search is performed by inputting "Tokyo hospital", hospitals located in Tokyo are output as search results, and the user can arbitrarily post a review for each searched hospital. Other users can view the reviews posted by the user on the search site.

In this embodiment, for the target facility (for example, a commercial facility), the word-of-mouth of the target facility (search target) is posted on the search site in order to improve the search ranking in the map search, that is, to take measures against MEO (Map Engine Optimization). Ask the user.

In this embodiment, word-of-mouth requests are made on the premise of MEO measures, but this system may be applied to SEO (Search Engine Optimization). That is, it suffices if the user can be requested to post a review of some search target (preferably a facility that can search a map) that can be searched on a Web search site.

The information processing device 1 is an information processing device capable of transmitting and receiving various types of information processing and information, and is, for example, a server computer, a personal computer, or the like. In the present embodiment, it is assumed that the information processing apparatus 1 is a server computer, and in the following, it will be read as server 1 for the sake of brevity. As will be described later, the server 1 provides a word-of-mouth request tool for requesting a user to post a word-of-mouth on a search site for a facility operator who takes MEO measures using this system. Specifically, the server 1 converts the URL of the request page for requesting the posting of word-of-mouth into a shortened URL (Uniform Resource Locator) that differs depending on the target facility, etc., and outputs the URL, and outputs the URL via the request page. To guide the user to the posting page of the search site. The process will be described in detail later.

The user terminal 2 is a terminal device owned by a user who posts a word of mouth, and is, for example, a smartphone, a tablet terminal, a personal computer, or the like. When the server 1 receives the access based on the shortened URL from the user terminal 2, it redirects (forwards) to the request page and requests the user to post a word of mouth.

The person in charge terminal 3 is a terminal device used by a person in charge of a facility that takes MEO measures, and is, for example, a personal computer, a smartphone, a tablet terminal, or the like. In the present embodiment, the server 1 receives a request from the person in charge terminal 3, outputs a shortened URL of the request page, and guides the user to the posting page. Further, the server 1 outputs a list of word-of-mouth requests made in the past, a list of word-of-mouth posted on the search site, and the like to the person in charge terminal 3 and presents them to the person in charge.

FIG. 2 is a block diagram showing a configuration example of the server 1. The server 1 includes a control unit 11, a main storage unit 12, a communication unit 13, and an auxiliary storage unit 14.
The control unit 11 has an arithmetic processing unit such as one or a plurality of CPUs (Central Processing Units), MPUs (Micro-Processing Units), GPUs (Graphics Processing Units), and stores the program P stored in the auxiliary storage unit 14. By reading and executing, various information processing, control processing, etc. are performed. The main storage unit 12 is a temporary storage area for SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), flash memory, etc., and temporarily stores data necessary for the control unit 11 to execute arithmetic processing. Remember. The communication unit 13 is a communication module for performing processing related to communication, and transmits / receives information to / from the outside.

The auxiliary storage unit 14 is a non-volatile storage area such as a large-capacity memory or a hard disk, and stores a program P and other data necessary for the control unit 11 to execute processing. Further, the auxiliary storage unit 14 stores the facility DB 141, the person in charge DB 142, the word-of-mouth DB 143, the request DB 144, and the session DB 145. The facility DB 141 is a database that stores information on each facility that is the requester of word-of-mouth posting. The person in charge DB 142 is a database that stores information on the person in charge of requesting word-of-mouth posting at each facility. The word-of-mouth DB 143 is a database that stores information on word-of-mouth posted on the search site. The request DB 144 is a database that stores the contents of the request (request information) made to the user by the person in charge of the facility. The session DB 145 is a database that stores session data on the request page.

The auxiliary storage unit 14 may be an external storage device connected to the server 1. Further, the server 1 may be a multi-computer composed of a plurality of computers, or may be a virtual machine virtually constructed by software.

Further, in the present embodiment, the server 1 is not limited to the above configuration, and may include, for example, an input unit that accepts operation input, a display unit that displays an image, and the like. Further, the server 1 includes a reading unit for reading a portable storage medium 1a such as a CD (Compact Disk) -ROM, a DVD (Digital Versatile Disc) -ROM, and reads and executes a program P from the portable storage medium 1a. You can do it. Alternatively, the server 1 may read the program P from the semiconductor memory 1b.

FIG. 3 is an explanatory diagram showing an example of the record layout of the facility DB 141, the person in charge DB 142, the word-of-mouth DB 143, the request DB 144, and the session DB 145.
The facility DB 141 includes a facility ID column, a facility name column, and a posting page column. The facility ID column stores the facility ID for identifying each facility targeted by this system. The facility name column and the posting page column are associated with the facility ID, respectively, and store the facility name and the URL of the posting page on which the review of the facility can be posted on the search site.

The person in charge DB 142 includes a person in charge ID column, a name column, and a facility column. The person in charge ID column stores the person in charge ID for identifying each person in charge of the facility. Each of the name column and the facility column stores the name of the person in charge and the facility name to which the person in charge belongs in association with the person in charge ID.

The word-of-mouth DB 143 includes a word-of-mouth ID column, a posting page column, a word-of-mouth column, and a reply column. The word-of-mouth ID column stores word-of-mouth IDs for identifying each word-of-mouth posted on the search site. The post page column, word-of-mouth column, and reply column correspond to the word-of-mouth ID, respectively, and memorize the post page where the word-of-mouth was posted, the content of the word-of-mouth, and the content of the message replied by the person in charge to the word-of-mouth. There is. In the word-of-mouth column, for example, the name of the user who made the word-of-mouth, the evaluation of the facility by the user (for example, a numerical value of 1 to 5), the comment posted by the user, the posting date and time, and the like are stored. In the reply column, for example, the name of the person in charge who made the reply, the comment replied by the person in charge, the date and time of reply, and the like are stored.

The request DB 144 includes a request ID column, a facility column, a request column, an evaluation column, a shortened URL column, and a related word-of-mouth column. The request ID column stores a request ID for identifying a posting request made to the user by the person in charge. The facility column, request column, evaluation column, shortened URL column, and related word-of-mouth column are associated with the request ID, respectively, when making an evaluation or request for the facility name, request content (request information), posting request, and posting request. It stores the shortened URL generated in and the word-of-mouth ID of the word-of-mouth posted by the request. In the request column, for example, the type of request described later (whether the shortened URL was output by SMS (Short Mail Message), e-mail, or QR code (registered trademark)), the date and time of the request (sending), and the request are made. Information such as the person in charge, the evaluation type described later, and the user who received (received) the request is stored. As will be described later, the evaluation column stores the evaluation of the facility (“Yes” or “No”) entered by the user on the request page, and the evaluation (score and comment) to the person in charge.

The session DB 145 includes a session ID column, a date / time column, a facility column, a user column, and a session column. The session ID column stores the session ID numbered for each session on the request page. The date / time column, facility column, user column, and session column are associated with the session ID to store the date and time when the session occurred, the name of the facility that requested the posting of the review, the requested user name, and the content of the session. ing.

FIG. 4 is a block diagram showing a configuration example of the user terminal 2. The user terminal 2 includes a control unit 21, a main storage unit 22, an auxiliary storage unit 23, a communication unit 24, a display unit 25, an input unit 26, and an image pickup unit 27.
The control unit 21 has an arithmetic processing unit such as a CPU, and performs various information processing, control processing, and the like by reading and executing a program stored in the auxiliary storage unit 23. The main storage unit 22 is a temporary storage area such as a RAM, and temporarily stores data necessary for the control unit 21 to execute arithmetic processing. The auxiliary storage unit 23 is a non-volatile storage area such as a ROM (Read-Only Memory), and stores programs and other data necessary for the control unit 21 to execute processing. The communication unit 24 is a communication module for performing processing related to communication, and transmits / receives information to / from the outside.

The display unit 25 is a display screen such as a liquid crystal display, and displays an image given by the control unit 21. The input unit 26 is an operation interface for a touch panel, mechanical keys, etc., and receives operation input. The image pickup unit 27 is a camera provided with an image pickup element such as a CMOS (Complementary MOS) sensor, and captures an image.

FIG. 5 is an explanatory diagram showing an example of the word-of-mouth list screen. FIG. 5 is an example of a screen displayed by the person in charge terminal 3, and shows an example of a screen of the word-of-mouth request tool provided by the server 1. For example, the person in charge terminal 3 displays a menu bar on the left side of the screen of the tool as shown in FIG. The person in charge terminal 3 displays the word-of-mouth list screen of FIG. 5 when the word-of-mouth list 52 is operated, and operates the transmission history screen (see FIG. 10) when the transmission history 51 is operated and the report 53 is operated. If so, the report screen (see FIG. 12) is displayed. The outline of the present embodiment will be described below.

Before explaining the word-of-mouth list screen of FIG. 5, the processing contents when requesting the user to post a word-of-mouth will be described. The person in charge terminal 3 displays the request button 50 on the upper right of the word-of-mouth list screen (and other screens) of FIG. When the operation input to the request button 50 is accepted, the person in charge terminal 3 pops up the screen of FIG.

FIG. 6 is an explanatory diagram showing an example of the request form. When the operation input to the request button 50 is accepted, the person in charge terminal 3 pops up the request form shown in FIG. FIG. 6A illustrates a screen example of a request form when requesting a post by SMS. FIG. 6B illustrates a screen example of a request form when requesting a post using a QR code. When the operation input to the request button 50 is accepted, the person in charge terminal 3 first displays the request form of FIG. 6A.

The request form includes an SMS tab 61, an email tab 62, and a QR code tab 63. The person in charge terminal 3 switches the display of the request form of FIGS. 6A and 6B according to the operation input to each tab. The display screen of the request form related to the e-mail tab 62 is almost the same as the SMS tab 61, so the illustration is omitted.

When the SMS tab 61 is active, the person in charge terminal 3 displays the request form of FIG. 6A. In the request form, the person in charge terminal 3 accepts input of various information necessary for transmitting a posting request message (SMS) to the user. Specifically, the person in charge terminal 3 accepts the input of the person in charge name, the evaluation type, the telephone number of the user, the user name (recipient name), and the comment to the user. The evaluation type will be described later.

The server 1 sends a message of a word-of-mouth posting request to the user terminal 2 based on the input contents in the request form. FIG. 7 is an explanatory diagram illustrating an example of a message. In addition to the user name, comment, etc. entered above, the message includes a shortened URL 71 that shortens the URL of the request page (see FIG. 8) for requesting the user to post.

The server 1 does not transmit the URL of the request page as it is, but transmits the shortened URL 71. There are multiple reasons for using a shortened URL, but the main reasons are that the number of characters that can be described in SMS, QR code, etc. is limited, and that the URL of the original request page is masked. Further, the server 1 transmits a shortened URL in order to record the operation history from the request for posting the word-of-mouth to the user posting the word-of-mouth (or postponing the post).

The method of generating the shortened URL is not particularly limited, but for example, the server 1 generates a random character string of several characters (6 characters of "e1MMhb" in FIG. 7) as the file name of the HTML file, and redirects to the file. Store the URL of the request page as the destination. When the access based on the shortened URL is received from the user terminal 2, the server 1 redirects (transitions) to the request page stored in the file.

When generating the above shortened URL, the server 1 generates an individual shortened URL for each message, at least based on the target facility (facility requesting word-of-mouth communication). Specifically, the server 1 generates a shortened URL based on the target facility, the user who receives the word-of-mouth request, the person in charge of making the request, and the evaluation type described later. The server 1 generates a unique shortened URL based on the person in charge who entered the information in the request form of FIG. 6, the facility to which the person in charge belongs, the user entered in the request form, and the evaluation type, and sends a message to the user terminal 2. Send to.

In the above, shortened URLs are generated according to four types of information: target facility (search target), user, person in charge, and evaluation type. For example, server 1 is based on information of three or less types or five or more types. You may generate a shortened URL. That is, the information associated with the shortened URL may at least include the target facility, and other information is not particularly limited.

FIG. 8 is an explanatory diagram showing an example of a display screen on the user terminal 2. When the operation input to the shortened URL is accepted, the user terminal 2 performs a redirect based on the shortened URL and transitions to the request page on the left side of FIG. After that, the user terminal 2 sequentially switches the screen according to the operation input on the request page, and transitions to the word-of-mouth posting page of the search site.

The request page is a Web page for requesting the posting of word-of-mouth information about the target facility, and is a page for guiding (transitioning) the user to the word-of-mouth posting page on the search site. The server 1 requests the user to post a word-of-mouth via the request page, and transitions to the posting page.

In the present embodiment, the server 1 first receives the facility evaluation input from the user on the request page on the left side of FIG. For example, as shown in FIG. 8, the user terminal 2 displays a question "Can you recommend XX?", Accepts selection input from "Yes" or "No" options, and accepts evaluation input. In addition, instead of the alternative of "yes" or "no", for example, a score evaluation of 1 to 5 points may be accepted.

In this embodiment, the facility evaluation input is accepted on the request page, but the configuration for evaluating the facility on the request page is not essential, and the user may be guided to the posting page as it is without performing the evaluation. ..

Here, when "facility and person in charge" is selected as the evaluation type in the request form of FIG. 6, the server 1 is a page for inputting the evaluation of the person in charge after the evaluation input of the facility is completed (not shown). ), And the person in charge who sent the message also accepts the evaluation input. For example, the server 1 accepts a score evaluation of 1 to 5 points and input of a comment. In this way, by enabling the evaluation of the person in charge on the request page, for example, when an employee of the facility requests the user (customer) to post a review, the customer service of the employee (person in charge) It is possible to record attitudes and the like.

After completing the evaluation input of the facility (and the person in charge), the user terminal 2 transitions to the request page in the center of FIG. In addition, in the present embodiment, in order to avoid posting negative reviews, the server 1 transitions to the page in the center of FIG. 8 only when the evaluation of the facility is "yes", that is, when the evaluation is positive. do. If "No", the process ends.

The user terminal 2 asks the user whether or not there is a predetermined e-mail address (address of the free mail service provided by the search site) for the user to log in to the search site on the page in the center of FIG. 8, and "Yes" or "Yes". Accepts selection input from "No". When "Yes" is selected, the user terminal 2 transitions to a login screen (not shown) for the user to log in to the search site, and accepts input of an e-mail address or the like. If "No" is selected, the server 1 ends the process.

After the login is completed, the user terminal 2 transitions to the word-of-mouth posting page on the right side of FIG. The posting page is a Web page for the search engine server 4 to accept the posting of reviews of the target facility, and is a page in the search site. For example, the user terminal 2 accepts input of word-of-mouth such as score evaluation and comment on the posting page and transmits it to the search engine server 4. The transmitted word-of-mouth is uploaded by the search engine server 4.

As described above, the server 1 sends a message including a shortened URL to the user terminal 2, accepts the redirect, and transitions to the request page. Then, after accepting the evaluation input of the facility (and the person in charge) on the request page, the server 1 transitions to the posting page of the search site and prompts the posting of the word-of-mouth. The shortened URL is associated with the facility, the user, etc., and the server 1 stores the operation history from the transmission of the message to the transition to the posting page as session data in the session DB 145.

In the above, the case of requesting the posting of word-of-mouth by sending an electronic message (SMS or e-mail) to the user terminal 2 has been described, but in the present embodiment, a QR code (bar code) is used. It is also possible to request posting of reviews. A one-dimensional barcode may be used instead of the QR code. For example, as shown in FIG. 6B, when the QR code tab 63 is activated, the person in charge terminal 3 displays the QR code describing the shortened URL. Specifically, the person in charge terminal 3 displays a QR code whose evaluation type is "facility only" and a QR code of "facility and person in charge", respectively.

The server 1 generates a shortened URL according to the target facility (and the person in charge, evaluation type), converts it into a QR code, and outputs it to the person in charge terminal 3. In this case, the shortened URL is fixed for each facility, unlike the above-mentioned message transmission. For example, the person in charge prints out the QR code and presents it to a user who visits the facility. Alternatively, the person in charge may present the QR code display screen to the user as it is. The user terminal 2 reads the QR code according to the user's operation input, performs a redirect based on the shortened URL, and accesses the request page.

The user terminal 2 accepts the facility evaluation input on the request page in the same manner as when the message is transmitted, and transitions to the word-of-mouth posting page. In this case, the user terminal 2 first accepts the input of the user name on the request page because the shortened URL of the QR code is not associated with each user. When managing the session data on the request page, the server 1 stores the session data (operation history) in the session DB 145 in association with the input user name.

The explanation will be continued by returning to FIG. In the following, the request for posting the reviews made above and the management of the posted reviews will be described. The server 1 collects reviews posted about the target facility from a predetermined API (Application Programmable Interface) provided by the search site, and stores them in the word-of-mouth DB 143. Then, the server 1 displays the word-of-mouth list screen of FIG. 5 in accordance with the request from the person in charge terminal 3.

The word-of-mouth list screen is a display screen that displays a list of comments posted by each user about the target facility. For example, the person in charge terminal 3 displays the overall evaluation of word-of-mouth of the target facility (average value of word-of-mouth, total number of word-of-mouth, etc.) in the upper part of the screen, and displays a list of individual word-of-mouth in the lower part of the screen. For example, the person in charge terminal 3 displays the user name (handle name), the score, the comment, etc. that posted the word-of-mouth for each word-of-mouth. In addition, the person in charge terminal 3 displays the browse button 54 for each word of mouth.

FIG. 9 is an explanatory diagram showing an example of the word-of-mouth detail screen. When the person in charge terminal 3 accepts the operation input to the browse button 54 on the word-of-mouth list screen, the person-in-charge terminal 3 displays the word-of-mouth detail screen of FIG. The word-of-mouth detail screen is a display screen that displays information on word-of-mouth information posted on the search site. The person in charge terminal 3 displays the word-of-mouth posted on the search site in the upper part of the screen.

In addition, the person in charge terminal 3 displays a reply form for the person in charge to reply to the word-of-mouth at the lower part of the screen. The person in charge terminal 3 accepts the input of the comment in the reply form, and sends the input comment to the search engine server 4 via the server 1. As a result, a reply is made to the word-of-mouth posted by the user, and for example, a thank-you word-of-mouth can be collectively performed on this tool.

The server 1 may not only accept a reply to the word-of-mouth from the person in charge, but may also notify the person in charge or the facility manager to reply to the word-of-mouth when there is an unreplied word-of-mouth. For example, the server 1 refers to the word-of-mouth DB 143 at regular intervals to determine whether or not there is an unreplied word-of-mouth, and if there is an unreplied word-of-mouth, notifies the person in charge terminal 3. This makes it possible to manage replies to word-of-mouth on this tool.

FIG. 10 is an explanatory diagram showing an example of a transmission history screen. When the operation input to the transmission history 51 displayed on the menu bar is accepted, the person in charge terminal 3 displays the transmission history screen shown in FIG. The transmission history screen is a display screen that displays a list of word-of-mouth posting requests (request information) made to users by each person in charge of the facility, and is a display screen that displays the word-of-mouth request history (transmission history). ..

The person-in-charge terminal 3 displays a list of the contents of the word-of-mouth posting request for each request made to each user. For example, the person in charge terminal 3 displays the name of the person in charge who made the request, the date and time, the name of the user who received the request (recipient name), and the latest operation history (status). Further, the person in charge terminal 3 displays the browsing button 101 for each request.

FIG. 11 is an explanatory diagram showing an example of the request details screen. When the person in charge terminal 3 receives the operation input to the browsing button 101, the person in charge terminal 3 displays the request details screen of FIG. The request details screen is a display screen that displays the request contents (request information) for the user and the user's action history for the request. For example, the person in charge terminal 3 sets the request contents as the request date and time (the date and time when the message was sent or the date and time when the QR code was read), the name of the person who made the request, the name of the user who received the request, the comment entered by the person in charge, and the like. Display on the left side of the screen.

Further, the person in charge terminal 3 displays the operation history of the user terminal 2 on the right side of the screen as the user's action history. The operation history is information including at least the access to the request page based on the shortened URL and the presence or absence of the transition to the posting page, and the time is a series of operation contents from requesting the user to post a review to posting. It is the data represented along the series. For example, as shown in FIG. 11, the person in charge terminal 3 displays a series of operations such as sending a message, accessing based on a shortened URL, and transitioning to a posting page in order from the bottom of the screen according to the date and time. The server 1 displays the operation history of FIG. 11 based on the information of each request stored in the request DB 144 and the session data on the request page stored in the session DB 145.

Although the operation related to the evaluation of the facility (and the person in charge) is not displayed in FIG. 11, "No" is selected as the evaluation of the facility, and "No" is selected only when no review is posted. Is displayed. Further, in the example of FIG. 11, the case where the message is transmitted is illustrated, but when the QR code is read, instead of "sent the message", the name input performed after reading the QR code is performed. The presence or absence is displayed as the operation history. In this way, the number and contents of the items displayed as the operation history (behavior history) are changed according to the operation contents and the mode of the request.

Further, the person in charge terminal 3 displays the word-of-mouth selection field 111 on the request details screen. The word-of-mouth selection field 111 is an input field for selecting a word-of-mouth posted on the search site by the posting request (request information) displayed on the request details screen, and associates the posting request and the word-of-mouth in the database (request DB 144). It is an operation input field for. The word-of-mouth DB 143 and the request DB 144 store word-of-mouth and request contents, respectively, but since it is not known which word-of-mouth corresponds to which request, the server 1 responds to the posting request by the word-of-mouth selection column 111. Let the person in charge select the word of mouth.

When the operation input to the word-of-mouth selection field 111 is accepted, the person in charge terminal 3 pulls down the word-of-mouth that is not yet associated with the posting request in the request DB 144. In this case, for example, the person in charge terminal 3 displays the word-of-mouth with the newest posting date and time in order from the top, so that the person in charge can easily identify the related word-of-mouth. The person in charge terminal 3 accepts a selection input for selecting a word-of-mouth to be associated with a posting request from the word-of-mouth displayed from the pull-down display. The word-of-mouth ID of the selected word-of-mouth is stored in the request DB 144 in association with the posting request being displayed.

In the above, the person in charge manually associates the word-of-mouth with the request, but for example, the server 1 automatically narrows down the word-of-mouth according to the user name, date and time (word-of-mouth request date and time, and posting date and time). You may make an association with. Further, for example, the server 1 may narrow down word-of-mouth by user name or date and time, and pull down the word-of-mouth that is presumed to be highly relevant to the request being displayed on the request details screen.

FIG. 12 is an explanatory diagram showing an example of a report screen. When the operation input to the report 53 displayed on the menu bar is accepted, the person in charge terminal 3 displays the report screen of FIG. The report screen is a display screen that displays a report on the posting request using this tool, and the predetermined aggregation items are aggregated for the posting request made to the user by the person in charge and the word-of-mouth posted by the posting request. This screen displays the total result for each person in charge. For example, as shown in FIG. 12, the person in charge terminal 3 displays a list of the number of posted reviews, the average value of the evaluation points of the word-of-mouth, the average value of the evaluation points for the person in charge, and the like for each person in charge. The server 1 aggregates the request contents (request information) stored in the request DB 144 and the word-of-mouth information associated with each request on the request details screen of FIG. 11, and reports the aggregated result in FIG. Display on the screen.

From the above, according to the present embodiment, a shortened URL corresponding to the target facility (search target), person in charge, user, etc. is generated, access based on the shortened URL is accepted, and the redirect (forwarding) is performed to the request page. , Directs you to the posting page of the search site. By using a shortened URL, SMS and QR code can be suitably used, and at the same time, the user's action history (operation history) is saved as session data, and a series of user actions from request to posting are preferably used. Can be recorded.

FIG. 13 is a flowchart showing an example of a processing procedure executed by the server 1. For example, the server 1 executes the following processing when the screen shown in FIG. 5 or the like is output in response to the request from the person in charge terminal 3.
The control unit 11 of the server 1 determines whether or not to output a request form for requesting the user to post a word-of-mouth in response to a request from the person in charge terminal 3 (step S11). When it is determined to output the request form (S11: YES), the control unit 11 outputs the request form (step S12).

The control unit 11 determines whether or not to output the shortened URL as a QR code (bar code) based on the operation input in the person in charge terminal 3 (step S13). When it is determined that the QR code is not output (S13: NO), the control unit 11 evaluates the user information such as the name and contact information (telephone number or e-mail address), and the evaluation type (evaluates only the facility or the facility). And whether to evaluate the person in charge) is accepted (step S14). The control unit 11 generates a shortened URL of the request page based on the facility requesting the word-of-mouth, the user, the person in charge, and the evaluation type (step S15). The control unit 11 is a message requesting the posting of word-of-mouth communication, and transmits a message including the generated shortened URL to the user terminal 2 (step S16).

When it is determined that the shortened URL is output by the QR code (S13: YES), the control unit 11 generates the shortened URL of the request page based on the facility requesting the word-of-mouth and the person in charge (step S17). The control unit 11 outputs a QR code describing the generated shortened URL to the person in charge terminal 3 (step S18).

After executing NO or the process of step S16 or S18 in step S11, the control unit 11 determines whether or not to output a list of word-of-mouth based on the operation input in the person in charge terminal 3 (step S19). When it is determined to output a list of word-of-mouth (S19: YES), the control unit 11 outputs a word-of-mouth list screen showing a list of word-of-mouth corresponding to the facility of the person in charge to the person in charge terminal 3 (step S20). The control unit 11 displays the information of each word-of-mouth on the person in charge terminal 3 according to the operation input on the word-of-mouth list screen (step S21), and ends a series of processes.

When it is determined not to output the word-of-mouth list (S19: NO), the control unit 11 determines whether or not to output the list of word-of-mouth posting requests (request information) based on the operation input in the person in charge terminal 3. (Step S22). When it is determined to output the list of posting requests (S22: YES), the control unit 11 outputs a transmission history screen showing a list of word-of-mouth posting requests by each person in charge to the person in charge terminal 3 (step S23).

The control unit 11 causes the person in charge terminal 3 to display the information of each posting request based on the operation input on the transmission history screen (step S24). Then, the control unit 11 accepts the selection input of the word-of-mouth associated with the posting request being displayed (step S25). The control unit 11 stores the designated word-of-mouth in the request DB 144 in association with the posting request (step S26), and ends a series of processes.

When it is determined that the request history is not output (S22: NO), the control unit 11 responds to the operation input on the person in charge terminal 3 by requesting the posting of the word-of-mouth and the total result of the word-of-mouth posted by the posting request. The report screen shown for each is output (step S27), and a series of processes is completed.

FIG. 14 is a flowchart showing an example of a processing procedure executed by the user terminal 2. The processing contents executed by the user terminal 2 will be described with reference to FIG.
The control unit 21 of the user terminal 2 acquires the shortened URL of the request page (step S31). Specifically, as described above, the control unit 21 acquires the shortened URL by receiving a message including the shortened URL or reading a QR code representing the shortened URL. The control unit 21 performs a redirect based on the shortened URL and transitions to the request page (step S32).

The control unit 21 receives an evaluation input for the facility and / or the person in charge on the request page (step S33). When the request page is accessed by reading the QR code, the input of user information such as the name is first accepted, and then the evaluation input is accepted.

The control unit 21 determines whether or not to post a word-of-mouth in response to an operation input by the user (step S34). Specifically, the control unit 21 determines that the word-of-mouth is posted when a positive evaluation (“Yes”) is selected in the evaluation input in step S33. When it is determined not to post (S34: NO), the control unit 21 ends a series of processes. When it is determined to post (S34: YES), the control unit 21 transitions to the word-of-mouth posting page corresponding to the facility (step S35). The control unit 21 posts a word-of-mouth according to the operation input on the posting page (step S36), and ends a series of processes.

From the above, according to the present embodiment, posting of word-of-mouth can be suitably promoted by transferring to the request page using the shortened URL and guiding (transitioning) to the posting page of the search site.

Further, according to the present embodiment, by transmitting a shortened URL to the user terminal by a message such as SMS or e-mail, it is possible to suitably request the posting of word-of-mouth communication.

Further, according to the present embodiment, the request can be made by reading a barcode such as a QR code, and the convenience can be improved.

Further, according to the present embodiment, by using the shortened URL generated in association with the target facility (search target), the user, etc., the user's action history (session) can be grasped, and the posting request can be made. Success or failure can be presented to the facility side.

Further, according to the present embodiment, word-of-mouth can be collected from the search site, managed in a database, and presented in a list to the facility side. In addition, it can be managed in association with the request, and the convenience of the facility that implements word-of-mouth measures (preferably MEO measures) can be improved.

Further, according to the present embodiment, it is possible to present a report (posting request and total result of word-of-mouth) for each person in charge, and it is possible to more preferably implement word-of-mouth measures.

The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

1 Server (information processing device)
11 Control unit 12 Main storage unit 13 Communication unit 14 Auxiliary storage unit P program 2 User terminal 21 Control unit 22 Main storage unit 23 Auxiliary storage unit 24 Communication unit 25 Display unit 26 Input unit 3 Person in charge terminal 4 Search engine server

Claims (7)

A storage unit that stores the URL of the posting page that can be posted on the Web search site, and a storage unit that stores reviews related to the search target that can be searched on the Web search site.
A generation unit that generates a shortened URL that is a request page for requesting a user to post a review and shortens the URL of the request page for transitioning to the posting page according to the search target.
An output unit that outputs the shortened URL and
When an access based on the shortened URL is received from the user terminal, the transfer unit that transfers to the request page and
With the reception department that accepts the input of the information of the user who requests the posting of the word of mouth
Equipped with
The generation unit generates the shortened URL according to the search target and the user, and generates the shortened URL.
The output unit is a message requesting the posting of the word-of-mouth, and sends the message including the shortened URL to the user terminal.
The storage unit stores request information indicating the content of the request to the user, and stores the request information indicating the search target related to the shortened URL and the information of the user.
A collection unit that collects the word-of-mouth for the search target from the Web search site,
Further equipped with a second reception unit that accepts the selection input of the word-of-mouth corresponding to the request information.
The storage unit stores the selected word-of-mouth and the request information in association with each other.
An information processing device characterized by this. The output unit outputs a barcode representing the shortened URL, and outputs the barcode.
The transfer unit receives access from the user terminal that has read the barcode and transfers it to the request page.
The information processing apparatus according to claim 1, further comprising a third reception unit that receives input of information of the user who posts the word-of-mouth on the request page. The storage unit stores the session data on the request page in association with the search target and the user.
The information processing apparatus according to claim 1 or 2 , further comprising a second output unit that outputs an action history of the user from receiving a posting request of the word-of-mouth to posting based on the session data. The generation unit generates the shortened URL according to the search target and the person in charge of requesting the posting of the word-of-mouth.
The storage unit stores the request information indicating the search target, the user who received the posting request of the word-of-mouth regarding the search target, and the person in charge who made the posting request in association with the word-of-mouth.
Claim 1 is characterized in that it includes a third output unit that outputs a total result of the posting request made by the person in charge and the word-of-mouth by the person in charge for each person in charge with reference to the storage unit. The information processing apparatus according to any one of 3 to 3 . The Web search site is a search site capable of performing a map search based on a region name and a search query.
The storage unit stores the URL of the posting page for posting the word-of-mouth regarding the target facility when the target facility is searched by the map search.
The information processing apparatus according to any one of claims 1 to 4 , wherein the generation unit generates the shortened URL according to the target facility. A request page for requesting a user to post a review about a search target that can be searched on a Web search site, and a URL of a request page for transitioning to a posting page that can post the review on the Web search site. Generate a shortened URL according to the search target,
Output the shortened URL and
When the access based on the shortened URL is received from the user terminal, it is forwarded to the request page and transferred to the request page.
Accepting the input of the user's information requesting the posting of the review,
Generate the shortened URL according to the search target and the user,
It is a message requesting the posting of the word-of-mouth, and the message including the shortened URL is transmitted to the user terminal.
Request information indicating the content of the request to the user, the request information indicating the search target related to the shortened URL and the information of the user is stored.
The word-of-mouth for the search target is collected from the Web search site, and
Accepting the selection input of the word-of-mouth corresponding to the request information,
An information processing method, characterized in that a computer executes a process of associating and storing the selected word-of-mouth and the request information . Obtain the shortened URL of the request page for requesting the user to post a review about the search target that can be searched on the Web search site, and obtain the shortened URL according to the search target.
By redirecting based on the shortened URL, the request page is displayed on the display unit.
In response to the operation input of the user on the request page, the user transitions to a posting page where the word-of-mouth related to the search target can be posted on the Web search site.
A message requesting the posting of the word-of-mouth, the message including the user requesting the posting of the word-of-mouth and the shortened URL corresponding to the search target is acquired.
Accepts selection input for the word-of-mouth for the search target collected from the Web search site,
Causes the computer to execute a process of associating the selected word-of-mouth with the request information indicating the content of the request to the user, the search target related to the shortened URL, and the request information indicating the information of the user . A program characterized by that.

Images