JP7134299B2 - Information notification system, information notification method, and information notification program - Google Patents

Description

The present invention relates to, for example, an information notification system, an information notification method, and an information notification program for notifying a user of information.

2. Description of the Related Art Conventionally, information such as telephone bills, water bills, electricity bills, rent, taxes, and other personal monetary value information related to personal monetary values have been mailed by crimped postcards or the like and notified to users. It is

Taxes and insurance premiums for the purpose of promoting the collection of taxes, insurance premiums, etc. has been proposed (see Patent Document 1).

This tax/insurance notice/reminder system reads out taxpayers from a taxpayer database, creates data on those who have arrears or delinquency, and sends e-mails to those people. In this way, e-mails are used to send notices of payment deadlines and reminders to delinquents.

However, in the method proposed in Patent Document 1, e-mail is used to send notices of payment deadlines and reminders to delinquent taxpayers. There is a problem that when someone else obtains the e-mail, the other person sees the content of the reminder.

JP-A-63-132549

SUMMARY OF THE INVENTION In view of the above problems, an object of the present invention is to provide an information notification system, an information notification method, and an information notification program capable of reliably notifying a user of information.

The present invention comprises a user portable terminal used by a user, a requester terminal used by a requester who wants to transmit information to the user, and a notification server for notifying the user portable terminal of the information, The client terminal comprises user information storage means for storing at least telephone number information indicating the telephone number of the user portable terminal and the information to be notified to the user in association with each other, and the notification server receives the information from the client terminal. telephone number information acquisition means for acquiring the telephone number information; URL transmission means for notifying the mobile terminal of the user of the telephone number of a URL including an identifier uniquely assigned to the user of the telephone number information in a text format; Based on the telephone number information, a reminder call means for making a call to the user portable terminal of the telephone number, and an automatic response voice requesting an answer by a push button when the call made by the reminder call means is answered. The information notification system, the information notification method, and the information notification program are characterized by comprising means for reproducing information on the user portable terminal, and means for acquiring answer information from the user portable terminal through a push button .

According to the present invention, it is possible to provide an information notification system, an information notification method, and an information notification program capable of reliably notifying a user of information.

1 is a block diagram showing the system configuration of an information notification system; FIG. FIG. 4 is an explanatory diagram of a screen displayed on a user portable terminal; FIG. 4 is an explanatory diagram of a screen displayed on a user portable terminal; FIG. 4 is a flow chart of SMS transmission operation of the SMS transmission program; FIG. 4 is a flow chart of information notification operation of the information notification program. FIG. 11 is a block diagram showing the system configuration of an information notification system according to the second embodiment; FIG. FIG. 4 is a screen configuration diagram of a call list setting screen; FIG. 4 is a screen configuration diagram of an incoming call list setting screen; FIG. 4 is a screen configuration diagram of a call list screen. FIG. 4 is a screen configuration diagram of an incoming call list screen; The flowchart figure of the remind call operation|movement of a remind call program. FIG. 4 is a screen configuration diagram of a display content setting screen; FIG. 10 is a screen configuration diagram of a tool detail setting screen for accepting detailed settings for a tool selected on the WEB display screen display unit;

An embodiment of the present invention will be described below with reference to the drawings.
<Example 1>

FIG. 1 is a block diagram showing the system configuration of an information notification system 1 in this embodiment. The information notification system 1 includes a client terminal 2 mainly used by a client who is a creditor (person who notifies a user of personal-related monetary value information), a questionnaire collector, or an information transmitter, and a debt notification (personal-related monetary value information). A notification server 3 that executes information notification such as value information notification), and users such as obligors who owe debts to obligees (personal-related monetary value information notification targets) and information recipients who receive information and a user portable terminal 4 used by the. Client terminal 2 , notification server 3 , and user portable terminal 4 are connected to Internet 6 , and notification server 3 and user portable terminal 4 are connected via a public general telephone line 7 . It should be noted that the personal-related monetary value information is monetary value information related to an individual. Also, the requester can access the notification server 3 by a login operation (not shown), can access only information created by the requester, and cannot access information created by other clients.

This information notification system 1 (individual-related monetary value information notification system) can be used for many purposes as shown in the following (1) to (7).
(1) Usage fee or debt "dunning" by financial institutions, debt collection companies, legal corporations, real estate management companies, rent guarantee companies, electric power companies, gas companies, telecommunications companies, or mail order companies. In this case, the usage fee or debt becomes personal related monetary value information.

(2) Issuance of "convenience store payment slips and bills" (with usage fees, etc.) issued by electric power companies, gas companies, telecommunications companies, post-payment settlement companies, etc. (substitute for crimped postcards). In this case, usage charges of electric power companies, gas companies, telecommunications companies, or deferred payment settlement business operators are personal related monetary value information.

(3) Use of "contract renewal" (contract fees, etc. are described) performed by contract renewers such as real estate agents. In this case, the contract amount described in the contract becomes the personal related monetary value information.
(4) Reporting use of "moving-in attendance records" conducted by real estate management companies (reports on the current state of the property, etc., to be filled in by the tenant when moving into the rental property). In this case, the items described in the moving-in witness record (for example, money-related information such as a record of items to be restored to the current state, such as damage to walls and windows) become personal-related monetary value information.

(5) Issuance purpose of "Defined Contribution Pension Transaction Details" for companies that have introduced 401K. In this case, the defined contribution pension becomes personal related monetary value information.
(6) Primarily used for issuance of “investment trust performance details” by regional banks, securities companies, etc. In this case, the amount of money described as the performance record of the investment trust becomes the personal related monetary value information.
(7) Used for notification of maturity of term deposits. In this case, the amounts of principal and interest received (after tax) are personal related monetary value information.

(8) Use for issuance of "deduction certificate" issued by insurance company. In this case, the insurance premium described in the deduction certificate becomes personal related monetary value information.
In this embodiment, among the various uses described above, the case of using personal related monetary value information for demanding "debt" will be described.

In addition, the term "debt" used in this embodiment refers to, for example, one-time debts such as telephone bills, water bills, electricity bills, rent, and taxes not paid by the due date, or monthly repayments of loans Not the full amount of debts such as underpayment, but various debts that have passed the due date (due date), such as some debts that have passed the due date (due date). Therefore, the user includes the dunning target person, the debt notice includes the dunning notice, the debt content includes the dunning content, and the user portable terminal 4 includes the dunning target person portable terminal.

The client terminal 2 includes, for example, a control unit 20 configured with a CPU, a ROM, a RAM, etc. as hardware elements to execute various calculations and control operations, and a hard disk, a flash memory, etc., configured to read and write information. A storage unit 21 that permits, a communication unit 22 that is configured by a LAN board, a WiFi unit, etc. and is connected to the Internet 6 by wire or wirelessly to transmit and receive data, a touch panel, a keyboard, a mouse, a push button, or a plurality of these and a display unit 24 configured by a liquid crystal display, an organic EL display, or the like for displaying images such as characters and figures.

The storage unit 21 stores user name information and address information, telephone number information indicating the telephone number of the user portable terminal 4, and personal-related monetary value information ( Information) is stored in a user information database 210 that associates and stores information.

The notification server 3 includes, for example, a control unit 30 configured by a CPU, a ROM, a RAM, etc. as hardware elements to execute various calculations and control operations, and a hard disk, a flash memory, etc. to allow reading and writing of information. a storage unit 31 configured with a LAN board, a WiFi unit, etc. and connected to the Internet 6 by wire or wirelessly to transmit and receive data; a touch panel, a keyboard, a mouse, a push button, or a plurality of these A line connection unit connected to the general telephone line 7 via an input unit 33 configured to receive input by touch operation and a display unit 34 configured by a liquid crystal display, an organic EL display, or the like to display images such as characters and drawings. 35.

The storage unit 31 stores an SMS transmission program 310 executed by the control unit 30, a notification program 311 (individual-related monetary value information notification program), an access log database 312 for storing user access logs, and mail transmission data. 313 and notification data 314 are stored.

The access log data stored in the access log database 312 includes screen display log data of screen display performed by accessing a specific URL from the user mobile terminal 4 and input log data of input received from the user mobile terminal 4. and

The mail transmission data 313 has items of ID, distribution call ID, order, destination phone number, SMS body, MESSAGEID, token, registration date/time, update date/time, and deletion date. The SMS body stores a sentence to be delivered to the user and a URL for accessing. This URL stores a shortened URL, which will be described later. With this configuration, a different message can be sent for each telephone number, and more specifically, a message with the same contents can be sent with different personal identification parts for personal identification in shortened URLs.

The notification data 314 is data for dynamically creating a homepage to be displayed when the user accesses the URL on the user mobile terminal 4, and includes column name, ID, delivery call ID, CSV record number, URL, personal Each item has identification ID, telephone number, name, date of birth, authentication information, debt content, debt amount, expiration date, information 1, information 2, ..., date of creation, and date of update. is doing.
If there are multiple records for the delivery call ID, they are displayed on the web page in order of the CSV record numbers. That is, it is displayed on multiple pages.
This notification data 314 is received from the client terminal 2 and stored in the storage unit 31 of the notification server 3 for use. The personal identification ID is not limited to being received from the client terminal 2, but may be randomly generated by the notification server 3 and given to each person as a unique ID.

For example, the user portable terminal 4 includes, as hardware elements, a control unit 40 configured with a CPU, a ROM, a RAM, etc. to perform various calculations and control operations, and a flash memory, etc., to allow reading and writing of information. A storage unit 41, a communication unit 42 configured by a WiFi unit or the like and wirelessly connected to the Internet 6 to transmit and receive data, and an input configured by a touch panel, a push button, or a plurality of these to receive input by contact operation. a display unit 44 configured by a liquid crystal display, an organic EL display, etc., for displaying images such as characters and diagrams; It is a mobile terminal such as a smart phone or a mobile phone.

FIG. 2A is an example of a screen configuration diagram of a notification message 440 that is transmitted by the notification server 3 to the user portable terminal 4 by SMS (Short Message Service) and displayed on the display unit 44 .

The notification message 440 is composed of a character display 441a for notifying that there is a notification, such as "I have a notification", and a URL 441b that allows access to a specific page when pressed. This notification message 440 is the content stored in the SMS body of the mail transmission data 313 .

The URL 441 b is generated by the control unit 30 of the notification server 3 or the control unit 20 of the client terminal 2 . Furthermore, the character string and access destination of the URL 441b differ for each notification message 440. FIG. That is, the generated URL 441b differs depending on the content of the debt owed by the user. Specifically, a URL as a connection destination address is assigned to each requestor or to each debt type of the requestor, and a short code of the personal identification ID assigned to the user is added to the end of this URL. A shortened URL (individual URL) is created, and this shortened URL is assumed to be URL 441b. For example, the shortened URL is "http://example.com/nw9i3m", and this shortened URL is restored according to a predetermined rule to "http://example.com?did=9999". In this case, "9999" is the personal identification ID, and "http://example.com" is the URL as the address for accessing the home page.

FIG. 2B is a screen configuration diagram of an access error screen 442 displayed on the display unit 44 of the user portable terminal 4 under predetermined conditions when the notification server 3 receives a URL access signal from the user portable terminal 4. is an example.

The access error screen 442 is composed of an error message 443 indicating an access error. The error message 443 includes, for example, the reason for the access error and the telephone number indicating the contact information for the client (creditor). FIG. 2B shows that the URL 441b has expired on the date when the notification server 3 receives the access to the URL 441b from the user portable terminal 4, that is, the debt repayment deadline (personal related monetary value payment deadline). ) has ended. Note that the error message is not limited to an error message indicating expiration (expired message), but may be an appropriate error message, such as indicating unauthorized access or simply indicating that display is not possible. . As a result, information such as debt (individual-related monetary value information) can be treated as an error without being displayed on the user portable terminal 4, and information such as debt (individual-related monetary value information) can be prevented from being displayed after the deadline. It is preferable that this error message is displayed on the user portable terminal 4 if the time limit has expired when the notification server 3 receives the access signal to the URL from the user portable terminal 4 . As a result, useless input for authentication can be prevented.

FIG. 2C is an example of a screen configuration diagram of a first authentication screen 444 for requesting input from the user portable terminal 4 when the notification server 3 receives access to the URL 441b from the user portable terminal 4. FIG.

The first authentication screen 444 has a first authentication information input section 445 for requesting the input of personal authentication information that allows the user to be identified, and an input completion button 446 . Examples of the personal authentication information include name information and date of birth information, but any information that can identify the person himself/herself may be used. When the input completion button 446 is pressed, the user portable terminal 4 transmits the input contents of the first authentication information input section 445 to the notification server 3 .

FIG. 2D is an example of a screen configuration diagram of a second authentication screen 447 displayed on the display unit 44 of the user portable terminal 4 after the notification server 3 performs the first personal authentication.

The second authentication screen 447 has a second authentication information input portion 448 for requesting the input of personal authentication information that allows the user to be identified, and an input completion button 449 . Examples of the personal authentication information include name information and date of birth information, but any information that can identify the person himself/herself may be used. Also, the personal authentication information requested in the second authentication is different from the personal authentication information requested in the first authentication. When the input completion button 449 is pressed, the user portable terminal 4 transmits the input contents of the second authentication information input section 448 to the notification server 3 .

FIG. 3A shows a debt list screen 450 (individual-related monetary value information list screen, information display screen) dynamically displayed on the display unit 44 of the user portable terminal 4 by the notification server 3 referring to the notification data 314. is an example of a screen configuration diagram of.

The debt list screen 450 includes a name display portion 450a that displays the name of the user, a total amount display portion 451 of the debt (individual-related monetary value information) owed by the user, and an individual-related monetary value information display portion 452 of the debt. (information display section) and a payment guide button 453 .

The total amount display portion 451 displays the total amount of money that needs to be repaid (paid) for the debt (individual-related monetary value information) owed by the user to the obligee (client). The displayed amount allows the user to easily grasp the total amount of debts currently owed by the user (individual-related monetary value that must be paid).

The personal-related monetary value information display section 452 displays detailed information on the contents of all obligations that the user owes to the obligee. The detailed information includes, for example, the name of the borrowing, the debt amount of the debt (the amount of the personal-related monetary value information), the date of the debt contract, the date of the repayment deadline, and the like. In addition, the individual-related monetary value information display section 452 displays the content and amount of the shortfall in payment among the plurality of debts owed by the user. In addition, if installments are set to repay the repayment in multiple installments, the amount already paid out of the debt amount, the remaining debt amount obtained by subtracting the repayment completion amount from the debt amount, and the user additionally displays the amount due and the expected date of payment.

In addition, although this example shows the case of borrowing with a loan, it is not limited to this, but one-time debts such as telephone bills, water bills, electricity bills, rent, and taxes that have not been paid by the due date, There can be various past due debts. In this case, when displaying a list of multiple debts of multiple users, the total amount of the debts is displayed in the total amount display portion 451 .

When the payment guidance button 453 is pressed, the notification server 3 or the user portable terminal 4 requests input of payment information such as credit information.

FIG. 3B shows an authentication error screen 454 displayed on the display section 44 of the user portable terminal 4 when the first authentication information or the second authentication information is incorrect.

The authentication error screen 454 is displayed when the notification server 3 or the requester terminal 2 refers to the user information for the personal authentication information received from the user portable terminal 4 and cannot confirm the personal authentication information. Displayed on the display unit 44 .

The authentication error screen 454 includes an authentication error message 455 indicating that the result of personal authentication is an error, and an authentication screen display button 456 that displays the authentication screen that caused the error when pressed.

The content of the authentication error message 455 is, for example, the content of notifying the user that the authentication information entered immediately before is different. Further, when the authentication screen display button 456 is pressed, the notification server 3 displays the previous authentication screen again.

FIG. 4 is an example of a flow chart in which the notification server 3 executes the SMS transmission program 310 and transmits an SMS related to information notification such as a debt notification (individual-related monetary value information notification) to the user portable terminal 4 .

The control unit 30 of the notification server 3 receives information including the telephone number of the user to whom the SMS is to be sent from the requester terminal 2, specifically the same information as the mail transmission data 313 or part thereof, and the URL. Receive expiration date information indicating the expiration date (step S1). Information such as the telephone number received at this time may be acquired at the same time as user information other than the telephone number information.

Subsequently, the control unit 30 of the notification server 3 creates mail transmission data 313 from the received information (step S2). The mail transmission data 313 contains a message to be transmitted as a short message, and this message contains a URL (shortened URL). At this time, information for creating notification data 314 is also received, and notification data 314 is also created. Note that the creation of the notification data 314 may be completed before the message is delivered. Also, the received expiration date information is stored in the notification data 314 . Note that the expiration date information may be stored as separate information in association with the notification data 314 instead of being stored in the notification data 314 . Information necessary for creating the mail transmission data 313 and the notification data 314 is extracted from the user information database 210 by the client terminal 2 and transmitted.

Subsequently, the control unit 30 of the notification server 3 transmits an SMS message (short message) having the SMS text of the mail transmission data 313 as the message content to the user portable terminal 4 of that telephone number via the general telephone line 7. (Step S3). At this time, it is preferable that the SMS message includes not only the URL, but also a text that motivates the user to access the URL, such as "I have news for you." The transmission of this SMS message is repeated by the number of telephone numbers (that is, the number of records) stored in the mail transmission data 313, and the SMS message is distributed to everyone.

Note that an SMS message transmission server may be provided separately from the notification server 3 . In this case, the notification server 3 transmits the mail transmission data 313 to the SMS message transmission server via the Internet 5, and the SMS message transmission server sends an SMS message to the user mobile terminal 4 of each telephone number based on the mail transmission data 313. is transmitted via the general telephone line 7. Also, the SMS message is sent to a telephone number (mobile phone number) and is sent by the SMS message sending function installed in the notification server 3 .

FIG. 5 is an example of a flow chart in which the notification server 3 executes the notification program 311 and causes the display unit 44 of the user portable terminal 4 to display the details of the debt.

The control unit 30 of the notification server 3 receives an access signal by pressing the URL (URL link) described in the SMS message from the user portable terminal 4 (step S11).
The control unit 30 converts the received URL (abbreviated URL) into the original URL, separates it into the URL, which is an address, and the individual identification ID, and uses the individual identification ID as a fragment to identify the accessing user. (step S12).

Subsequently, the control unit 30 of the notification server 3 determines whether or not access can be permitted (step S13). This determination is made, for example, when the expiration date has passed, repayment has been completed, an authentication error has occurred more than a certain number of times, the personal identification ID is inappropriate, or the payment time entered in step S20 described later is currently in error. can be disabled. Whether the expiration date has passed is determined by referring to the expiration date of the data with the matching personal identification ID in the notification data 314 to see if the date on which the access signal was received has passed the expiration date of the URL. For completion of repayment, the access log database 312 is referenced to determine whether the user has already completed repayment. If the authentication error occurs more than a certain number of times, the access log database 312 is referred to and it is determined whether or not the authentication information has been erroneous for more than a certain number of times.

Regarding whether the current time is an error time relative to the payment time, it is an error time that does not need to be displayed after the notification because the payment time has not yet arrived, or the payment time It is set as appropriate according to the request of the requester, for example, it is an error time because it has passed. Note that the repayment information that the user has already completed repayment and the payment information (including payment time) registered by the user are not limited to being registered in the access log database 312, but are stored in an appropriate format for each user as user-related information. , you may use it.

The URL has expired, or the user's repayment has already been completed, or the authentication information has been incorrect more than a certain number of times, or the payment time determined to be registered by the user is currently in error. If it is time (step S13: NO), the control unit 30 of the notification server 3 causes the display unit 44 to display the access error screen 442 and terminates the notification program 311 .

If the URL is valid (step S13: YES), the control unit 30 of the notification server 3 causes the user portable terminal 4 to display the first authentication screen 444 (see FIG. 2(C)) to enter the authentication information. request (step S14). The first authentication screen 444 displayed at this time is a homepage screen dynamically created using the data of the first page of the record with the matching personal identification ID in the notification data 314 . The authentication information to be input is information for confirming that the user who inputs it is the user himself/herself, and is, for example, the user's name and date of birth.
The control unit 30 of the notification server 3 accepts valid authentication information to the first authentication information input unit 445 (step S15).

The control unit 30 of the notification server 3 compares it with the authentication information stored in the notification data 314 to confirm whether they match (step S16). Alternatively, the control unit 30 may request user information from the client terminal 2 and determine whether it matches the received authentication information.

If the control unit 30 of the notification server 3 determines that the authentication information does not match the user information (step S16: NO), it records the authentication error in the access log database 312, and records the recorded number of authentication failures ( If the total number of authentication failures so far) has not been drafted for the predetermined number of authentication failures (step S17: NO), the process returns to step S14 to display the authentication error screen 454 on the display unit 44, and then again. Accepts input of authentication information.
The control unit 30 of the notification server 3 terminates the notification program 311 when the number of authentication errors is equal to or greater than the predetermined number (step S17: YES).

The control unit 30 of the notification server 3 determines whether or not all authentications set in the notification program 311 have been completed (step S18). If all authentication has not been completed (step S18: NO), the control unit 30 displays the second authentication screen 447 as the second web page, and accepts input of the next authentication information. The next credential is a credential that is different from the credential previously entered. For example, if the first authentication uses the user's name as the authentication information, the second authentication uses the date of birth as the authentication information.

If all the authentications are completed (step S18: YES), the control unit 30 of the notification server 3 refers to the notification data 314 and dynamically creates a debt list, which is a home page based on data such as the details and amounts of debts. The screen 450 is displayed on the display unit 44 of the user portable terminal 4 (step S19).

The control unit 30 of the notification server 3 receives input of payment information from the user portable terminal 4 (step S20). As payment information, it is possible to adopt a configuration that accepts input of payment time, payment method, and both. Payment methods include, for example, credit card information (credit card number, expiration date, and security code), bank account information (bank name, branch name, ordinary/checking account, and account number), or electronic payment settlement code or the like. Also, payment may be made for all of a plurality of obligations at once, or may be in a form in which input is received for each obligation. Alternatively, the user may be allowed to select one debt from a plurality of debts, and input of payment information for the selected debt may be accepted. In addition, it is desirable that the payment time (scheduled payment date) is always input.

If payment information such as the payment date has already been registered in the access log database 312, the input of this payment information is omitted. At this time, if only the payment date has been entered, the input of the payment information is omitted, or only the payment method is displayed so that the payment method can be entered and the display of the payment date is omitted or cannot be changed (locked). may be In either case, it is possible to make it impossible to change the payment date once input, thereby preventing the payment date from being postponed.

The control unit 30 of the notification server 3 records the received input result in the access log database 312 (step S21), and terminates the notification program 311. FIG.

With the above configuration, it is possible to provide an information notification system, a debt notification method, and a notification program that can reliably notify a user of information such as personal-related monetary value information.
The debt list screen 450 has an individual-related monetary value information display portion 452 showing details of a plurality of debts owed by the user to creditors, and a total amount display portion 451 showing the sum of the debt amounts. As a result, the user can easily grasp the total amount of the debt owed by the user himself/herself, and can easily make a repayment plan.

In addition, since the first short message contains only the text requesting access and the URL, it can be prevented from being recognized as a demand for debt. Therefore, if the mobile phone number has been changed, it is possible to prevent sending a short message that can be understood as a demand for debt to a mobile phone number other than the person himself/herself.

In addition, since characters other than the URL are short sentences such as a sentence requesting access, it is possible to transmit necessary information even in a short message (SMS) with a limited number of characters. In addition, the total length of the URL can be shortened by using a shortened URL, or by dynamically creating a home page using an identifier uniquely assigned to the user (personal identification ID) at the end of the URL. You can send the necessary information even with a short message (SMS) that has a character limit.

In addition, the control unit 30 of the notification server 3 causes the individual-related monetary value information display unit 452 to display the details and amounts of the payment shortfalls for which payments are overdue among the plurality of debts owed by the user. This allows the user to reliably grasp the debt information (individual-related monetary value information) that the user has not yet paid. In addition, for example, automatic withdrawal from a bank account has been set, but if sufficient amount has not been transferred to the corresponding bank account, the fact can be known.

In addition, when the personal-related monetary value information display unit 452 sets the installment payment in which the repayment is divided into a plurality of times, the control unit 30 of the notification server 3 , the remaining balance after subtracting the repayment completion amount (payment completion amount) from the debt amount, the amount that the user must pay by the repayment deadline (payment deadline), and the scheduled date of repayment are additionally displayed. As a result, the user can easily grasp the amount currently required to be repaid (paid) after subtracting the amount that has already been repaid (paid). In addition, the user can easily check whether the planned repayment plan is progressing smoothly.

In addition, since the content of obligation is displayed only when the authentication is OK, it is possible to prevent a person other than the person from confirming the content of obligation. In particular, when sending short messages using a mobile phone number, even if the mobile phone number is valid or not, and if the user has not been canceled or the user has not changed, even if the message is sent without checking, the identity verification will be OK. Since the debt details (individual-related monetary value) are not displayed, it is possible to prevent disclosure of the debt details (individual-related monetary value) to others. Therefore, validation of the mobile phone number can be omitted.

Further, when the control unit 30 of the notification server 3 receives the access signal of the URL, it determines whether or not the validity period of the URL has expired. no access. As a result, it is possible to set the deadline for repayment of the debt as the expiration date of the URL and not to accept repayments exceeding the deadline for repayment. Also, by checking the error message, the user can recognize that the repayment deadline has passed, and can take appropriate action such as contacting the contact address described in the message if necessary.

Further, when receiving the access signal of the URL, the control unit 30 of the notification server 3 determines whether or not the accessing user has already completed repayment, and displays the access error screen 442 if the repayment has been completed. and do not access the URL. As a result, even if the user completes repayment of the corresponding debt after receiving the SMS message and then tries to access the URL described in the SMS message, the access will not be made, and the debt may be collected twice or more. do not have.

Further, the control unit 30 of the notification server 3 does not display the user information when the authentication information received from the user portable terminal 4 does not match the user information for a specific number of times or more. Furthermore, the number of times the URL does not match is stored as a log, and if the URL does not match a certain number of times, the account is locked so that the URL cannot be accessed. As a result, even if the telephone number information is erroneously registered or the owner of the telephone number information is changed, the liability list information is not displayed, thereby preventing personal information from leaking out. can be done.
<Example 2>

A description will be given of a second embodiment in which a part of the configuration is changed from the first embodiment. In the description of the second embodiment, since the configurations and operations similar to those of the first embodiment are the same as those of the first embodiment, the same elements are denoted by the same reference numerals, and detailed description thereof will be omitted.
Briefly, the information notification system 1 of the second embodiment freely sets (changes) the display contents of the reminder call function that sends a confirmation call (reminder call) to the user and the authentication screen that accepts the input of authentication information. and a display content setting function.

FIG. 6 is a block diagram of the information notification system 1 according to the second embodiment. The storage unit 31 of the notification server 3 of the second embodiment stores a reminder call program 315, an incoming call response program 316, outgoing/incoming call data 317, a screen custom program 318, and a screen custom data 319 in addition to those of the first embodiment.

The incoming/outgoing call data 317 includes, for example, callee telephone number information indicating the telephone number of the callee, ringing time information indicating the ringing time at the time of the call, and how many times the call was not received for one piece of telephone number information. Retry count information indicating whether to repeat the call, retry interval information indicating the interval time when the call is repeated, response information indicating the result of the response to the call, and IVR information, which is automatic response voice data to be played during the call, Contains answer information data indicating whether the response resulted in a valid answer. As a result, a reminder call to the same telephone number can be executed up to the number of retries. The incoming/outgoing call data 317 includes, for example, incoming telephone number information indicating the telephone number of the destination when an incoming call is received, incoming call time information regarding the date and time of receiving an incoming call, and IVR information, which is automatic response voice data to be played during a call. and answer information indicating whether a valid answer was obtained. The content of the incoming/outgoing call data 317 is not limited to the above information, and may store any information related to the call destination, call result, caller, and call result as data. Also, the incoming/outgoing call data 317 may be configured to receive the called party's phone number from the user information database 210 of the client terminal 2 instead of storing the called party's phone number information.

The screen custom data 319 is data indicating screen configurations (display contents) of various authentication screens such as the first authentication screen 444 (see FIG. 2) and the second authentication screen 447 . The screen custom data 319 includes, for example, screen content information to be displayed such as text size information and layout information included in each authentication screen, or screen function information such as tool size information and layout information that functions on each authentication screen. including. The screen content information and screen function information of the screen custom data 319 are not limited to these pieces of information, and any information necessary for displaying each authentication screen may be stored as data.

FIG. 7 is a screen configuration diagram of a call list setting screen 500 for setting reminder call conditions for the notification server 3 to make a call (remind call).
Note that the transmission list here is information necessary for the notification server 3 to execute the reminder call. Such information includes, for example, call list name information, call start date and time information, call end date and time information, time zone information, callee telephone number information, callout IVR data information, destination number file information, answering machine detection information, call There are time information, retry count information, retry interval information, channel number information, automatic stop valid reply number information, and automatic stop connection number information.

The call list setting screen 500 is mainly composed of a menu section 501 on the left and a content display section 510 on the right. In addition, an update button 514 for the latest information is provided on the upper right of the screen. When the update button 514 for the latest information is pressed, each set value displayed on the screen is updated to the content stored in the incoming/outgoing call data 317 . As a result, when editing is being performed on the screen and the edited content has not yet been registered, the state before editing can be restored.

The menu section 501 has an SMS delivery setting tab 502, a telephone delivery setting tab 503, a resource tab 504, and a help tab 505 in this order from the top.
An SMS delivery setting tab 502 is a tab for displaying a screen for setting SMS delivery in the content display section 510 . Although the details are omitted, similar to the telephone delivery setting, the call list name, delivery date and time, delivery time zone, caller number, destination number file, retry count, channel count, and automatic stop valid response count are provided. The number of retries is the number of retries when the short mail message is not received. The functions of other items have the same functions as the same items on the telephone setting tab, which will be described later.

A telephone delivery setting tab 503 is a tab for setting telephone delivery, and when selected, detailed items are expanded downward to include an incoming call list setting tab 503a, an outgoing call list setting tab 503b, an incoming call list list tab 503c, and an incoming call list setting tab 503c. A call list list tab 503d is displayed.

A resource tab 504 is a tab for displaying a screen for selecting a resource on the content display portion 510 .
A help tab 505 is a tab for displaying a screen for explaining an operation method on the content display portion 510 .

When any one of incoming list setting tab 503a, outgoing list setting tab 503b, incoming list list tab 503c, and incoming list list tab 503d in menu section 501 is selected, notification server 3 displays a screen corresponding to each tab. Displayed on the display unit 510 . For example, the notification server 3 is accessed from the client terminal 2 through the Internet 5 and displays a screen corresponding to the tab selected by the client terminal 2 on the display unit 24 of the client terminal 2 .

The call list setting screen 500 is displayed when the call list setting tab 503b is selected, and setting items of the call list are displayed in the content display portion 510. FIG.
In this case, the contents display section 510 includes a call list name input section 511, a call date and time input section 512, a time zone setting section 513, a call destination telephone number data input section 515, an outgoing IVR data input section 516, A destination number file selection unit 517, an answering machine detection selection unit 518, a ringing time input unit 521, a landline phone retry count input unit 522, a mobile phone retry count input unit 523, a retry interval input unit 524, and the number of channels. 525 , the number of automatic stop valid responses 526 , the number of automatic stop connections 527 , and a registration button 531 . Each configuration of the call list setting screen 500 of the present embodiment is an example, and the configuration and arrangement of each input section of the call list setting screen 500 are not limited to the present embodiment. Any input unit may be provided, and it may be arranged in any manner on the screen.

Call list name input unit 511 accepts input of the name of the created call list setting (call list name). The transmission list name input here is stored in the storage unit 31 as the name of the transmission list setting, and displayed on the transmission list list screen 700 (described later).

The transmission date and time input unit 512 receives the input of the transmission start date and time when the transmission of the reminder call is started and the transmission end date and time when the transmission of the reminder call is terminated. The transmission start date and time and the transmission end date and time may be entered by directly entering the year, month, day, and time. It is also possible to accept the selection of the date and time.

Further, the notification server 3 may automatically set the date and time based on the personal monetary value information related to the user information database 210 uploaded from the client terminal 2 as the transmission start date and time and the transmission end date and time. For example, if the personal monetary value information indicates payment amount information for which the payment due date is set, the transmission start date and time is automatically calculated according to a predetermined rule (e.g., a predetermined number of days before, a predetermined number of days after, etc.) from the payment due date. It can be set automatically as As such a form, for example, "12 o'clock on the date three days before the payment due date" or "9 o'clock in the morning of the day after the payment due date" can be set as appropriate.

In addition, the notification server 3 may update the data of the transmission start date and time as appropriate. For example, when the person is authenticated from the user portable terminal 4, the transmission start date and time can be updated to the date and time calculated according to a predetermined rule from the date and time when the person is authenticated. As such a form, for example, although the transmission start date and time is originally set to be 3 days after the short mail is sent, the person is authenticated one day later, and the person is not authenticated. The transmission start date and time can be updated three days after the date (four days after the short mail transmission date).

Note that when the transmission start date and time are automatically set or updated, the transmission end date and time are also automatically set or updated. For example, if the transmission start date and time is updated one day after the first set date and time, the transmission end date and time is also updated one day later. In any case, the transmission start date and time and the transmission end date and time that are input or set are the dates and times after the URL 441b is notified (transmitted) to the user portable terminal 4 by e-mail or short mail.

The notification server 3 may limit the date and time accepted by the transmission date and time input unit 512 based on personal monetary value information related to the user information database 210 uploaded from the client terminal 2 . For example, if the personal monetary value information indicates payment amount information with a payment due date, the input of a date and time after the payment due date may not be accepted. Alternatively, the notification server 3 may display a warning when the date and time received by the transmission date and time input unit 512 is after the payment due date.

The time period setting unit 513 has a plurality of outgoing time period input units each composed of a start time input unit and an end time input unit. As a result, it is possible to set the calling time zone, for example, to make a call during the lunch break and after the evening, or to make a call during the daytime.

Destination telephone number data input unit 515 accepts input of telephone number information to be the destination. Destination telephone number data input portion 515 accepts input of one or more pieces of telephone number information. The input of the telephone number information may be performed by directly inputting the telephone number, or by uploading the user information database 210 from the client terminal 2 . It is preferable that the telephone number information that can be selected here is the telephone number information linked to the calling account selected in advance by the calling account selection unit (not shown). As a result, it is possible to select only the phone number information managed or provided by the user who is using the outgoing account, and the phone number information used by other users may be mistakenly used. You can prevent being selected.

The outgoing IVR data input unit 516 accepts input of processing flow data including an automatic response voice to be played during a call after outgoing calls. This processing flow is composed of a flow necessary for a series of responses, such as, for example, the voice to be reproduced and the next operation for each answer number to the question in the voice. The input process flow data may be selected from a plurality of process flow data created in advance and stored in the storage unit 31, or may be in a form in which input of a newly created process flow is accepted. may be In addition, the data of the processing flow may be uploaded from the requester terminal 2 including the data of the automatic response voice.

Destination number file selection unit 517 accepts selection of a destination number file in which a plurality of telephone numbers to be called is stored.
An answering machine detection selection unit 518 receives a selection input as to whether or not to detect that the response after an outgoing call is an answering machine.

Ringing time input unit 521 receives an input of a ringing time for outgoing calls. The call time may be in a form in which the basic call time is automatically input, or in a form in which the requester can arbitrarily change it. When the call time is automatically set, it can be set to a predetermined time such as "60 seconds". The requester can change the automatically entered "60 seconds" as desired.

Retry count input units 522 and 523 are used to set how many times a reminder call is to be sent (retryed) after the end of a call (retry count) when no call is received even after the call time has passed. accept. A fixed phone retry count input section 522 is the retry count for the fixed phone, and a mobile phone retry count input section 523 is the retry count for the mobile phone. Whether the destination is a landline phone or a mobile phone is determined from the area code. For example, if "3" is input to the landline phone retry count input unit 522 or the mobile phone retry count input unit 523, four reminder calls (first time and three retries) will be made between the call start date and time and the call end date and time. executed. In other words, if "0" is entered in the retry count input sections 522 and 523, a call is made only once (first time) to the target telephone number, and subsequent calls are made regardless of whether the call was received or not. Not done.

The retry interval input unit 524 accepts input of the time (retry interval time) from the end of the call to the transmission of the next reminder call when the call is not received even after the calling time elapses. The input of the retry interval time may be in a form in which the basic retry interval time is automatically set and the requester can arbitrarily change it. When the retry interval time is automatically set, it can be set to a predetermined time such as "120 minutes". The requester can change the automatically entered "120 minutes" as desired. Further, the automatically set retry interval time may be calculated based on the transmission start date and time, the transmission end date and time, and the number of retries. For example, if the call start date and time is "April 1, 12:00", the call end date and time is "April 1, 18:00", and the number of retries is "2", the retry interval is set to "180 minutes". Similarly, the value obtained by dividing the time from the call start date and time to the call end date and time by the number of retries may be set automatically by an appropriate method such as setting the time until the next retry.

The number of channels 525 accepts an input of the number of simultaneous outgoing calls and calls (1 call, 1 channel). It is preferable that the number of channels 525 is configured such that a maximum set number is appropriately set for each outgoing account according to a separately defined contract, and input can be made within the maximum set number.

The number of automatic stop valid responses 526 accepts an input as to how many valid responses must be obtained before the call is stopped (no more calls are made). If it is not entered or is 0, automatic stop based on the number of valid responses is not performed.

The number of automatic stop connections 527 accepts an input as to how many calls are connected after the call is made before the call is stopped (no more calls are made). If it is not input or if it is 0, automatic stop by the number of connections is not performed.

Upon receiving an input from the registration button 531, the notification server 3 stores the data received by each input unit in the storage unit 31 as transmission list setting data. At this time, a unique ID may be given to the call list data.

FIG. 8 is a screen configuration diagram of an incoming call list setting screen 600 on which the notification server 3 receives settings for incoming calls from the user portable terminal 4. As shown in FIG.
The incoming call list setting referred to here is information necessary for the notification server 3 to respond to a call received from the user portable terminal 4 (for example, a call related to personal monetary value information). Such information includes, for example, incoming call list name information, incoming call start date and time information, incoming call end date and time information, time zone information, incoming telephone number information, incoming IVR data information, destination number file information, channel number information, automatic stop enable There is information on the number of responses and information on the number of automatic termination connections. As for the phone calls made from the user portable terminal 4, for example, it is assumed that the short mail sent contains the phone number of the contact, or that the outgoing call (including a reminder call) is returned. In such a case, the phone number of the caller becomes the phone number information of the user portable terminal 4 .

The incoming call list setting screen 600 is displayed when the incoming call list setting tab 503a is selected, and setting items of the incoming call list are displayed in the content display portion 510. FIG.
In this case, the content display section 510 includes an incoming call list name input section 611, an incoming call acceptance date and time input section 612, a time zone setting section 613, a caller telephone number data input section 615, an incoming call IVR data input section 616, It consists of a destination number file selection section 617 , the number of channels 625 , the number of automatic stop valid responses 626 , the number of automatic stop connections 627 , and a registration button 630 . Each configuration of the incoming call list setting screen 600 of this embodiment is an example, and the configuration and arrangement of each input section of the incoming call list setting screen 600 are not limited to this embodiment. Any input unit may be provided as long as it is related to the setting, and it may be arranged in any way on the screen.

Incoming call list name input unit 611 accepts input of the name of the created incoming call list setting (incoming call list name). The name of the incoming call list input here is stored in the storage unit 31 as the name of the incoming call list setting, and displayed on the incoming call list screen 800 (described later).

The incoming call acceptance date and time input unit 612 accepts input of an incoming call start date and time to start accepting incoming calls from the user portable terminal 4 and an incoming call end date and time to end the incoming calls. The incoming call start date and time and the incoming call end date and time may be entered directly. Alternatively, when the incoming call reception date and time input section 612 is selected, a calendar and clock setting screen may be displayed and the selection may be accepted. good.

The time period setting section 613 has a plurality of incoming call time period input sections each composed of a start time input section and an end time input section. This makes it possible to set the incoming hours, such as accepting incoming calls only during business hours during the day.

Originator telephone number data input unit 615 accepts input of telephone number information that is the originator. Caller telephone number data input portion 615 accepts input of one or more pieces of telephone number information. The input of the telephone number information may be performed by directly inputting the telephone number, or by uploading the user information database 210 from the client terminal 2 .

The incoming call IVR data input unit 616 accepts data input of an automatic response voice to be reproduced during a call when an incoming call is received. The input automatic response voice data may be selected from a plurality of automatic response voice data created in advance and stored in the storage unit 31, or may be newly created automatic response voice data. It may be in the form of receiving an input. Further, the automatic response voice data may be input by uploading the automatic response voice data from the client terminal 2 .

Destination number file selection unit 617 accepts selection of a destination number file in which a plurality of telephone numbers that are callers of incoming calls are stored.
The number of channels 625 accepts an input of the number of simultaneous incoming calls and calls (1 call, 1 channel). It is preferable that the number of channels 625 is configured such that a maximum set number is appropriately set for each outgoing account according to a separately defined contract, and input can be made within the maximum set number.

The automatic stop number of valid responses 626 accepts an input as to how many valid responses are obtained to stop incoming calls (announce the end of the questionnaire acceptance period, etc., and no more incoming calls). If it is not entered or is 0, automatic stop based on the number of valid responses is not performed.
The number of automatic stop connections 627 accepts an input as to how many calls are to be connected after receiving an incoming call to stop incoming calls (no more incoming calls). If it is not input or if it is 0, automatic stop by the number of connections is not performed.

Upon receiving an input from the registration button 630, the notification server 3 stores the data received by each input unit in the storage unit 31 as incoming call list setting data. At this time, a unique ID may be given to the incoming call list setting data.

FIG. 9 is a screen configuration diagram of a transmission list list screen 700 that displays a list of saved transmission list setting data. This call list list screen 700 is a screen displayed when the call list list tab 503 d is selected in the menu portion 501 .

Content display portion 510 of transmission list list screen 700 includes creation date/time display portion 711 , status selection portion 712 , and transmission list list display portion 715 .
The creation date and time display section 711 displays the date and time when creation was started and the date and time when the last edit was made.

Status selection section 712 selects data to be displayed on call list display section 715 from among "all", "waiting for call", "preparing for call", "ready for call", "during call", "canceled call", and "completed call". Specify one or more. By this designation, the data corresponding to the designated status is displayed in the call list list display portion 715, and the overall call status can be confirmed for each status.

The transmission list list display section 715 displays a title that displays the transmission list name, IVR flow name, transmission start date and time, transmission end date and time, number of transmissions, number of connections, number of valid responses, number of channels, number of automatic stop valid responses, automatic stop connection The number and status are listed with one outgoing list name per line. In addition, for each call list name, a detailed display selection portion for displaying a separate detailed display screen and an edit display selection portion for displaying a separate edit screen to enable editing are displayed.

Each configuration of the call list list screen 700 of this embodiment is an example, and the contents, configuration, and arrangement of each display part of the call list list screen 700 are not limited to this embodiment. (including a reminder call), any display may be provided, and may be arranged in any manner on the screen. Display items other than the above include, for example, an answer display section that indicates whether or not a clear answer has been obtained to the automatic voice. Moreover, it may have a search function for displaying only a specific transmission list setting using the setting contents of each display unit. For example, by selecting one of the setting contents of each display section, it is possible to display only the transmission list settings having the corresponding setting contents. Furthermore, it may be possible to set whether or not to execute a reminder call based on each transmission list setting. For example, when the selection of each call list setting is accepted, a setting such as "stop call" or "resume call" may be further accepted.

The transmission list setting data displayed on the transmission list list screen 700 may display, for example, each item associated with a unique ID (or transmission account) assigned when each transmission list setting data is saved. As a result, it is possible to list only the data of the transmission list associated with that ID (or transmission account).

The “number of outgoing calls” in the outgoing call list display portion 715 displays the number of outgoing calls (including reminder calls). Although the display form of the present embodiment is "the number of calls actually made/the number of registered telephone numbers", it is not limited to this form and various display forms are possible. For example, only the number of calls actually made may be displayed, or the number of received calls among the number of calls made may additionally be displayed.

“Status” in the call list list display portion 715 displays the execution status of calls (including remind calls) based on the call list settings. For example, if all the set calls have been made, "finished" is displayed, and if no calls have been made yet, "waiting" is displayed. Also, when the outgoing call is stopped, it may be displayed as "stopped".

FIG. 10 is a screen configuration diagram of an incoming call list list screen 800 that displays a list of registered incoming call list setting data. This incoming call list list screen 800 is a screen that is displayed when the incoming call list list tab 503 c is selected in the menu portion 501 .

The content display portion 510 of the incoming call list list screen 800 includes a creation date/time display portion 811 , a status selection portion 812 , and an incoming call list list display portion 815 .
The creation date and time display portion 811 displays the date and time when creation was started and the date and time when the last edit was made.

Status selection section 812 designates one or more data to be displayed in incoming call list display section 815 from among "all", "preparing for disclosure", "ready for disclosure", "opening", "cancelling disclosure", and "end of disclosure". . By this designation, the data corresponding to the designated status is displayed in the incoming call list list display portion 815, and the overall call status can be confirmed for each status.

The incoming call list list display section 815 displays a title that displays the incoming call list name, IVR flow name, publication start date and time, publication end date and time, incoming rate, number of connections, number of valid responses, number of channels, number of automatic stop valid responses, and automatic stop connection. The number and status are listed one line per incoming list name. Further, for each call list name, a detailed display selection portion for displaying a separate detailed display screen and an edit display selection portion for displaying a separate edit screen to enable editing are displayed.

Each configuration of the incoming call list screen 800 of this embodiment is an example, and the contents, configuration, and arrangement of each display part of the incoming call list list screen 800 are not limited to this embodiment. Any display unit may be provided as long as it is a display related to an incoming call from the mobile terminal 4, and it may be arranged in any way on the screen. Display items other than the above include, for example, an answer display section that indicates whether or not a clear answer has been obtained to the automatic voice. Moreover, it may have a search function for displaying only a specific incoming call list setting using the setting contents of each display unit. For example, by selecting one of the setting contents of each display section, it is possible to display only the incoming call list settings having the corresponding setting contents. Furthermore, it may be possible to set whether or not to execute each incoming call list setting. For example, when the selection of each incoming call list setting is accepted, a setting such as "stop accepting incoming calls" or "resume accepting incoming calls" may be made.

The incoming call list setting data displayed on the incoming call list list screen 800 may display, for example, each item associated with a unique ID (or calling account) assigned when each incoming call list setting data is saved. As a result, only the incoming call list data associated with that ID (or outgoing account) can be displayed.

The “incoming rate” in the incoming call list display portion 815 of the incoming call list screen 800 displays the number of incoming calls from the user portable terminal 4 . Although the display form of the present embodiment is "the number of actually received calls/the number of registered telephone numbers", it is not limited to this form and various display forms are possible. For example, only the number of calls actually received may be displayed.

"Status" in the incoming call list display portion 815 of the incoming call list screen 800 displays the execution status of incoming call acceptance based on the incoming call list setting. For example, if the set incoming call acceptance time is over, "End" is displayed, and if the incoming call acceptance has not yet been executed, "Waiting" is displayed. Also, when the reception of incoming calls is stopped, the message "stopped" may be displayed.

FIG. 11 is a reminder call flow diagram in which the control unit 30 of the notification server 3 executes the reminder call program 315. As shown in FIG. Before or after the flow for making this remind call, the SMS transmission of the SMS transmission program 310 described with FIG. 4 of the first embodiment is executed.

The control unit 30 acquires the call list setting information from the call data 317 (step S41). The information acquired here includes, for example, the start date and time of the outgoing call, the end date and time of the outgoing call, the time period, the destination phone number data, the outgoing IVR data, the destination number file, the answering machine detection, the ringing time, the fixed phone retry count, and the mobile phone retry count. , the retry interval, the number of channels, the number of auto-stop valid responses, and the number of auto-stop connections. By making the destination telephone number data used here the same as the destination telephone number data used in SMS transmission of the SMS transmission program 310, a reminder call is sent to all users who have sent or sent SMS. be able to.

Also, while using the same destination telephone number data, if whether or not to send a reminder call is determined according to the conditions for judging the transmission target of the reminder call, only SMS is sent to some users who do not need the reminder call, Reminder calls can be made to the rest of the users, and so on.

Next, the control unit 30 determines whether or not to make a call to the user portable terminal 4 indicated by the acquired destination telephone number information (step S42). For example, the acquired transmission start date and time information and/or the transmission end date and time can be used as elements used for determination. That is, the control unit 30 compares the current date and time with the call start date and time, and if the current date and time is after the call start date and time (if the current date and time has passed the call start date and time), it makes a call. In addition, the control unit 30 compares the current date and time with the outgoing call end date and time, and if the current date and time is before the outgoing call end date and time (if the current date and time has not passed the outgoing call end date and time), the call is made. . That is, in terms of time, the control unit 30 makes a telephone call if the current date and time is later than the call start date and time and before the call end date and time.

Furthermore, for example, attribute information of personal monetary value information may be used to determine whether or not to make a reminder call. The attribute information here is, for example, information that payment for the personal monetary value information has already been completed, or information as to whether or not the personal monetary value information requires a reminder call in the first place. For example, personal monetary value information that requires a reminder call is personal monetary value information with a payment deadline set. Such personal monetary value information includes, for example, electricity bills and gas bills. Conversely, personal monetary value information that does not require a reminder call includes personal monetary value information for which a payment deadline is not set, personal monetary value information that does not require payment in the first place, and the like.

The attribute information can be acquired from the user information database 210 uploaded from the client terminal 2 in advance, for example. If it is determined at step S42 that a reminder call is to be sent, a telephone call is made, and if it is determined at step S42 that a reminder call is not to be sent, the process proceeds to step S49 to determine whether all the calls have been completed.

If the control unit 30 determines to make a reminder call based on the determination result of step S42, the control unit 30 makes a call (including a reminder call) from the line connection unit 35 through the general telephone line 7 to the user mobile terminal 4 indicated by the destination telephone number information. is executed (step S43). At this time, the caller's phone number, which is the destination of the call, is the caller's phone number of the current data (current record) among the caller's phone numbers registered in the caller's phone number information. That is, if it is the first case, the current data is the first, so the call is made to the first caller telephone number. If it is the nth case, the current data is n, so the call is made to the nth caller telephone number. It will happen. This current movement will be described later.

After the transmission, the control unit 30 determines whether or not the call has been received (the user has received the transmission) (step S44). If the message is received (step S44: YES), the process proceeds to the message reproduction step (step S45). If the message is not received (step S44: NO), the process proceeds to the time elapsed determination step (step S46).

If the control unit 30 determines that the call has been received in step S44 (step S44: YES), it reproduces the automatic response voice to the user portable terminal 4 according to the IVR flow (step S45). As the data of the automatic response voice to be reproduced, the data received by the outgoing IVR data input unit 516 can be used. At this time, the control unit 30 may request the user portable terminal 4 to respond by pressing a push button, and obtain the response information. The processing performed according to the outgoing IVR data also includes sending a short message (SMS). This short message can include a URL. Therefore, the responder who has received the short message can select the URL in the short message and display the home page.

When the call is not received in step S44 (step S44: NO), the control unit 30 determines whether or not a predetermined time has passed since the call was started (step S46). The predetermined time here can be the call time received by the call time input unit 521 . If the control unit 30 determines that the predetermined time has not passed, the control unit 30 shifts to the call receiving determination step (step S45) again, and if it determines that the predetermined time has passed, the control unit 30 shifts to the call termination step (step S47).

When the series of processes based on the IVR flow such as the reproduction of the automatic response voice in step S45 is completed, the control unit 30 determines whether a predetermined period of time has passed without the call being received (step S46: YES), or when the call destination user When the call is ended from the portable terminal 4, the call is ended (step S47).

The control unit 30 stores information (call log) on the call result in the storage unit 31 as call call data 317 (step S48). The information about the result of the call here is, for example, the destination telephone number information, the date and time information of the call, the result of the call, the obtained answer information, etc., and also includes whether or not the call was received. Based on the content of the call result, it can be determined whether or not to make a reminder call to the destination telephone number.

After the call log is recorded or when the call is not made, the control unit 30 determines whether or not the termination condition is satisfied (step S49). End conditions are completion of sending reminder calls for all phone number information in the call list setting information, receipt of responses for the number of valid automatic stop responses, or reaching the number of automatic stop connections. Conditions are set, and if any one of the conditions is met, the process ends.

At this time, based on the retry count information received by the retry count input units 522 and 523, it is determined whether all reminder calls have been sent. Since the outgoing call log is recorded in step S48 for each outgoing call destination telephone number (also recorded at the time of the reminder call), if there is a call destination telephone number that has not been received yet, the termination condition is not met. becomes. If there is no called party telephone number that is not receiving a call, all the calls are completed and no transmission call is required.

If the termination condition is not met (step S49: NO), the control unit 30 moves the current data in the destination telephone number information to the next destination telephone number information (step S50). At this time, if there is no need to make a call, such as when the next destination telephone number has already received a call, the current data is moved to the next destination telephone number. If the final destination telephone number of the originating telephone number information is in a state in which it is not necessary to make a call, the current data is advanced to the first destination telephone number and the next necessary destination telephone number. Then, the process returns to step S42 and is repeated. If the callee telephone number information does not contain the callee telephone number to which the call is to be made, the process is terminated.

In addition, when sending a reminder call to the same telephone number from the second time onwards, the retry interval time information received by the retry interval input unit 524 is added to the judgment element when making the judgment in step S42, and the retry is performed. If the interval time has passed, a reminder call is sent, and if the retry interval time has not passed, the call is not sent.

Further, the control unit 30 may execute the incoming call response program 316 upon receiving an incoming call based on the incoming call list setting information received on the incoming call list setting screen 600 to automatically answer the call. In other words, if there is an incoming call from the telephone number accepted by the caller telephone number data input unit 615 between the start date and time for accepting an incoming call and the end date and time for accepting an incoming call accepted by the incoming call acceptance date and time input unit 612, Receiving a call and using the incoming IVR data received by the incoming IVR data input unit 616, the automatic response voice is reproduced on the user portable terminal 4, and the information (incoming call log) on the result of the incoming call is stored as outgoing/incoming data 317. Store in section 31 . At this time, the control unit 30 may request the user portable terminal 4 to respond by pressing the push button, and include the obtained response information in the incoming/outgoing call data 317 .

FIG. 12 is a screen configuration diagram of a display content setting screen 900 (authentication screen display setting screen) used by the notification server 3 to receive the setting of the display content of the authentication screen.
When receiving a request to set (edit or customize) a web display screen to be displayed as a home page, control unit 30 executes screen custom program 318 and displays display content setting screen 900 . The display content setting screen 900 is displayed on the display unit 24 of the client terminal 2, for example. Screens created as web display screens include, for example, questionnaire screens for conducting questionnaires, authentication screens for authenticating individuals, and personal-related monetary value information display screens for displaying personal-related monetary value information, as appropriate. screen.

The display content setting screen 900 mainly has an element placement canvas portion 901 (element placement portion) and a tool palette 930 (element selection portion).

The element arrangement canvas portion 901 is a canvas for arranging elements (objects, parts) to create a WEB screen, and accepts insertion of tools from among the tools displayed on the tool palette 930 . At this time, elements are basically arranged in a row from top to bottom, and elements (tools) can be added in row units. If you want to separate columns in the horizontal direction in one row, use a column tool that can divide the area into two or three. As a tool insertion method, for example, a form in which a tool to be inserted is selected from the tool palette 930, dragged, and dropped on the element arrangement canvas portion 901 can be used. The control unit 30 performs processing for incorporating the received tool into the element placement canvas unit 901 as code.

In the illustrated example, an element frame 902 is indicated by a dotted line for each element. Inside the element frame 902, for example, a text 903, a selection box 904, a numeric input field 905, and a press button 906 are arranged.

Tools 911 to 919 for overall display operation are arranged above the element arrangement canvas portion 901 . Each configuration of the display content setting screen 900 of the present embodiment is an example, and the configuration and arrangement of each input section, display section, and buttons of the display content setting screen 900 are not limited to the present embodiment. Any input section may be provided as long as it is set related to screen display and editing, and may be arranged in any manner on the screen.

A view component 911 is a button that displays a component, and displays an HTML element.
A preview button 912 displays a preview screen as a separate screen. This preview button 912 is a button for displaying a screen actually displayed on the user portable terminal 4 based on the element layout canvas portion 901 . When the preview display button 912 is pressed, the control unit 30 configures a screen based on the code configuring the display and displays it as a WEB display screen preview.

A full screen button 913 displays in full screen.
A code confirmation button 914 displays the code (HTML) of the WEB screen arranged on the element arrangement canvas portion 901 . When the code confirmation button 914 is pressed, the control unit 30 switches the display to a screen on which code information constituting the element arrangement canvas portion 901 is described, or displays a window (small window) on which code information is described. display.

An undo button 915 undoes the previous action when selected.
Redo button 916 re-executes the undone action.
An input button 917 imports a template written in code into the element placement canvas portion 901 .

A clear canvas button 918 deletes all canvas elements.
A save button 919 saves the contents created in the element layout canvas portion 901 . Upon receiving the input of the save button 919 , the notification server 3 saves the code information forming the element layout canvas portion 901 in the storage portion 31 as the screen custom data 319 .

Further, when an element frame 902 is selected on the element placement canvas portion 901, a move button, a copy button, and a delete button (not shown) are displayed. When the move button is selected, the position of the element frame 902 can be moved, when the copy button is selected, the element frame 902 can be duplicated, and when the delete button is selected, the element frame 902 can be Deleted.

At the top of the tool palette 930, an open style manager button 921 for displaying a menu for changing the detailed settings of the selected element placed in the element placement canvas area 901 and a created page (web screen) hierarchy are displayed. An open layer manager button 922 to display and an open block button 923 to display a list of elements (tools) to be arranged are provided.

A tool palette 930 is displayed when the open block button 923 is selected, and icons corresponding to each element (tool) to be displayed on the web display screen or functioning on the web display screen are arranged. Tools can be, for example, text boxes, checkboxes, URL links, images, custom code, sliders, navigation bars, tooltips. The tools to be arranged are not limited to these examples, and any tools may be provided as long as they are related to the display and functions of the WEB display screen.

In the illustrated example, a slider 931 for switching and displaying multiple images in the horizontal direction, tabs 932 for switching the display content with tabs, custom code 933 for entering arbitrary codes, tooltips 934 for adding pop hints, text A type 935 that can add an input box, a navigation bar 936 that can add a navigation bar container, a link or a burger, a countdown 937 that can add a countdown, a 1 column 941 that can add one frame, and a 2 columns 942 that can add two frames on the left and right. , 3 columns 943 to which 3 frames can be added to the left and right, 2 columns (3/7) 945 to which 2 frames with a ratio of 3 to 7 can be added to the left and right, text 946 to which text can be entered, and links to which links can be entered 947 is provided. In addition, although not shown, images for placing images, videos for placing movies, maps for placing maps, link blocks, quotes, text sections, forms, inputs, text areas, selects, buttons, labels, Check boxes, radios, etc. are arranged.

FIG. 13 is a screen configuration diagram of a tool detail setting screen 950 that accepts detailed settings for elements within the element frame 902 selected on the element placement canvas portion 901 . This screen is displayed when the open style manager button 921 (selection tool detail setting button) is selected.
Upon receiving an input from the open style manager button 921, the control unit 30 displays a tool detail setting screen 950 for further receiving detailed settings of the selected tool. FIG. 13 shows an example of a screen when an input from the open style manager button 921 is received with "Slider" selected.

The tool detail setting screen 950 mainly includes an element placement canvas portion 901 and a setting palette 960 . The setting palette 960 displays the state of the element within the element frame 902 selected in the element placement canvas portion 901 .

The setting palette 960 displays setting items for the element in the selected element frame 902 and accepts selection of which item to set. The setting items displayed on the setting palette 960 differ for each selected element. For example, if the selected element is a text box, setting items for editing the text in the text box are displayed, and if the selected element is a URL link, input of the link destination URL is accepted. Setting items are displayed. The control unit 30 accepts editing of the selected element for the selected setting item, updates the code information according to the content of the editing, and reflects the display on the element placement canvas unit 901 .

The example in the drawing shows setting items when "slider" is selected as an element in the element frame 902. FIG.
The settings palette 960 displays classes 961, settings 963, general 964, dimensions 965, typography 966, decorations 967, extras 968, and flexes 969.

Class 961 can specify settings such as state, mouse over, mouse click, even/odd.
A setting 963 can specify settings for an ID and a title.
General 964 can specify settings such as vertical display format, horizontal display format, horizontal display format with height and width, and flexible display format.

Dimensions 965 can specify settings for width, height, maximum width, minimum height, top, bottom, left, and right border margins, and top, bottom, left, and right border margins.
Typography 966 specifies font, font size, weight, character spacing, font color, line height, character alignment, character decoration, character shadow, horizontal, vertical, blur, and color settings can.

Decorations 967 can specify transparency, rounded corners on the top, bottom, left, and right, underline width, style, and color, shadow style, and background settings.
Extras 968 can specify settings for various variations such as horizontal rotation and vertical rotation.
The flex 969 can designate settings such as whether or not flexible size changes are possible.

The homepage created on the display content setting screen 900 of FIG. 12 and the tool detail setting screen 950 of FIG. be done. That is, since the mail transmission data 313 and the home page are created by the same requester, the URL of the mail transmission data 313 created by the logged-in requester contains the URL of the home page created by the requester. It is configured so that it can be selected or automatically inserted.

With the configuration of the second embodiment described above, it is possible to provide an information notification system, an individual-related monetization position information notification method, and an information notification program that can reliably notify a user of personal-related monetary value information.
After transmitting the URL in text format to the user portable terminal 4 , the control unit 30 executes the remind call program 315 to make a remind call to the user portable terminal 4 . With this configuration, the user is repeatedly notified of information such as personal monetary value information related to the user, and information (individual related monetary value information, etc.) can be notified more reliably.

In addition, the control unit 30 sets the date and time of sending the confirmation call set in relation to the information to be transmitted to the user (individual-related monetary value information, etc.) as the reminder call condition information for determining whether or not to make a reminder call. By including time condition information, which is information, it is also possible to execute a reminder call at the date and time for making a phone call set based on the date and time related to the personal-related monetary value information. With this configuration, it is possible to re-notify the user of the personal-related monetary value information in accordance with the deadline for the personal-related monetary value information.

In addition, by including attribute information indicating whether or not to make the confirmation call based on the attribute of the information as the remind call condition information for determining whether to perform the remind call, the control unit 30 can Based on attribute information related to personal monetary value information, such as information that payment for monetary value information has already been completed, or personal monetary value information that does not require a reminder call in the first place (no payment deadline) You can also perform a reminder call. With this configuration, the reminder call is executed only to the user who really needs it, and the degree of satisfaction for the requester and the user can be improved.

Further, the control unit 30 sets the WEB display screen to be displayed on the user portable terminal 4 by inserting each tool to be displayed on the screen. With this configuration, the client does not need to enter the code of each tool for screen setting, and can easily set the WEB display screen.
In this way, (1) a message including a URL in text format is sent to the user mobile terminal 4 by message sending means such as SMS (short message), and (2) an automatic call is made to the user mobile terminal 4. It is possible to freely combine sending a response voice message and obtaining a response by number push.
In particular, sending a message including a URL in text format to the user mobile terminal 4 by message sending means such as SMS (short message) and sending a voice message by calling are executed for the same list of telephone numbers. Therefore, before or after sending a message such as SMS, guidance for accessing the URL in the message can be provided by voice guidance.
As a result, the URL of the campaign will be sent by SMS to notify the customer, and at the same time, the customer will be notified by a phone call with an automatic voice message. Send a message such as SMS and enter the address at the URL, or send a message such as SMS to the user who answered that they would cooperate by calling and asking if they would cooperate with the questionnaire, and sending the URL for the questionnaire to the user. can be said.
In addition, such a voice message is used as a reminder call, and a message such as SMS is sent and sent at a predetermined time (30 minutes, 1 hour, etc.) or after a predetermined time (30 minutes, 1 hour, etc.) Since it can be sent, even a user who suspects that a message such as SMS is a phishing scam can be informed by a voice message that there is no problem with regular guidance, and the access rate to the URL can be dramatically increased.
In addition, since the homepage to be displayed after the URL is accessed can be easily created using a graphical user interface, even users without programming knowledge can create appropriate pages such as questionnaire pages, information input pages, and information transmission pages. A homepage can be easily created, and can be linked with a message such as SMS with a URL.

It should be noted that the present invention is not limited to the configurations of the above-described embodiments, and many embodiments can be obtained.
In this embodiment, the control unit 30 of the notification server 3 accepts an access signal to the URL from the user portable terminal 4 and authenticates the access. However, for example, the notification server 3 may transmit the received access signal to the client terminal 2, and the control unit 20 of the client terminal 2 may perform access authentication. Alternatively, the control unit 30 may request the control unit 20 of the client terminal 2 for an authentication result for a part of authentication such as whether the user has completed repayment.

Further, in this embodiment, the control unit 30 of the notification server 3 accepts input of authentication information from the user portable terminal 4 and performs personal authentication. However, for example, the notification server 3 may transmit the received authentication information to the client terminal 2, and the control unit 20 of the client terminal 2 may refer to the user information database 210 to perform personal authentication.

Further, in this embodiment, the control unit 30 of the notification server 3 sets the validity period of the URL generated in advance, and refers to the date of receiving the access signal and the validity period to perform access authentication. However, the control unit 30 of the notification server 3 may change the content of the home page of the URL to a page displaying a message indicating that the URL has expired when the URL expires. .

Further, in this embodiment, the control unit 30 of the notification server 3 determines whether the user has completed repayment from the access log data, and authenticates the access. However, when there is a repayment procedure by the user, data indicating completion of repayment is stored in the user information database 210 of the requester terminal 2, and the control unit 30 of the notification server 3 notifies the requester terminal 2 of the user may be required to determine whether the company has completed repayment. Alternatively, at the same time that the requester terminal 2 stores the data indicating the completion of repayment in the user information database 210, the requester terminal 2 or the notification server 3 notifies the content of the homepage of the URL that the repayment of the corresponding debt has been completed. The page may be changed to display a message indicating that.

In addition, although the requester terminal 2 and the notification server 3 are configured separately, the configuration is not limited to this, and the function of the requester terminal 2 and the function of the notification server 3 are installed in one computer and executed by one computer. may be

The user information storage means in this invention corresponds to the user information database 210, and so on.
The telephone number information acquisition means corresponds to the control unit 30 and the communication unit 32 of the notification server 3 that execute step S1,
URL transmission means corresponds to the control unit 30 and the line connection unit 35 of the notification server 3 that executes step S3,
The remind call condition information acquisition means corresponds to the control unit 30 of the notification server 3 that executes step S41,
The remind call determination means corresponds to the control unit 30 of the notification server 3 that executes step S42,
The reminder call means corresponds to the control unit 30 and the line connection unit 35 of the notification server 3 that execute step S43,
The authentication request means corresponds to the control unit 30 of the notification server 3 that executes steps S13 to S14,
Display content setting means corresponds to the control unit 30 that executes the screen custom program 318.
The present invention is not limited to this embodiment, and various other embodiments are possible.

INDUSTRIAL APPLICABILITY The present invention can be used in industries that use SMS to notify individuals about monetary value information.

1... Information notification system 2... Client terminal 3... Notification server 4... User portable terminal 5... Internet 7... General telephone lines 20, 30, 40... Control units 21, 31, 41... Storage units 22, 32, 42... Communication Units 23, 33, 43 Input units 24, 34, 44 Display units 35, 45 Line connection unit 210 User information database 310 SMS transmission program 311 Notification program 312 Access log database 313 Mail transmission data 314 ... notification data 440 ... notification message 441b ... URL
442... Access error screen 443... Error message 444... First authentication screen 445... First authentication information input part 446, 449... Input completion button 447... Second authentication information input part 450... Debt list screen 451... Total amount display part 452 Individual-related monetary value information display portion 453 Payment guidance button 454 Authentication error screen 455 Authentication error message 456 Authentication screen display button 901 Element arrangement canvas portion 930 Tool palette

Claims (7)

An information notification system comprising: a user portable terminal used by a user; a client terminal used by a client who wants to transmit information to the user; and a notification server for notifying the user portable terminal of the information. ,
The client terminal is
User information storage means for storing at least telephone number information indicating the telephone number of the user mobile terminal and the information to be notified to the user in association with each other;
The notification server
telephone number information acquiring means for acquiring the telephone number information from the client terminal;
URL transmitting means for notifying, in a text format, a URL including an identifier uniquely assigned to the user of the telephone number information to the user portable terminal of the telephone number;
reminder call means for making a call to the user mobile terminal of the telephone number based on the telephone number information;
means for reproducing, on the user portable terminal, an automatic response voice requesting an answer using a push button when a call made by the remind call means is answered;
and means for acquiring answer information from the user's mobile terminal by means of a push button. The notification server
2. The information notification system according to claim 1, further comprising means for transmitting a short message including a URL when the answer information obtained by said answer information obtaining means is a request for a short message. An information notification system comprising: a user portable terminal used by a user; a client terminal used by a client who wants to transmit information to the user; and a notification server for notifying the user portable terminal of the information. ,
The client terminal is
User information storage means for storing at least telephone number information indicating the telephone number of the user mobile terminal and the information to be notified to the user in association with each other;
The notification server
telephone number information acquiring means for acquiring the telephone number information from the client terminal;
URL transmitting means for notifying, in a text format, a URL including an identifier uniquely assigned to the user of the telephone number information to the user portable terminal of the telephone number;
reminder call means for making a call to the user mobile terminal of the telephone number based on the telephone number information;
means for reproducing, on the user portable terminal, an automatic response voice requesting an answer when a call made by the remind call means is answered;
means for acquiring answer information from the user mobile terminal;
an incoming call response means for reproducing the automatic response voice by the reproducing means when an incoming call is received from the telephone number, and acquiring the answer information by the means for acquiring the answer information. An information notification system comprising: a user portable terminal used by a user; a client terminal used by a client who wants to transmit information to the user; and a notification server for notifying the user portable terminal of the information. ,
The client terminal is
User information storage means for storing at least telephone number information indicating the telephone number of the user mobile terminal and the information to be notified to the user in association with each other;
The notification server
telephone number information acquiring means for acquiring the telephone number information from the client terminal;
URL transmitting means for notifying, in a text format, a URL including an identifier uniquely assigned to the user of the telephone number information to the user portable terminal of the telephone number;
reminder call means for making a call to the user mobile terminal of the telephone number based on the telephone number information;
an element arrangement section for arranging elements to be displayed as a homepage;
an element selection unit that receives selection of an element that can be placed in the element placement unit;
The element is placed in the element placement section by inserting a tool indicating the element from the element selection section into the element placement section,
An information notification system configured to save a homepage created by arranging elements selected by the element selection part in the element arrangement part as a homepage to be displayed when the URL is accessed. The insertion is accepted by a method of selecting and dragging the element from the element selection section and dropping it on the element placement section,
5. The information notification system according to claim 4, wherein said notification server comprises means for performing processing for incorporating said element received by said element placement unit as a code. An information notification method comprising: a user portable terminal used by a user; a requester terminal used by a requester who wants to transmit information to the user; and a notification server for notifying the user portable terminal of the information. ,
The client terminal is
at least storing telephone number information indicating the telephone number of the user mobile terminal and the information to be notified to the user in association with each other;
The notification server
acquiring the telephone number information from the client terminal by telephone number information acquiring means;
Notifying a URL including an identifier uniquely assigned to the user of the telephone number information in a text format to the user mobile terminal of the telephone number;
making a call to the user mobile terminal of the telephone number based on the telephone number information;
Playing an automatic response voice requesting an answer by push button on the user portable terminal when the outgoing call is answered,
An information notification method for obtaining answer information from the user's mobile terminal by pressing a button. the computer,
user information storage means for storing at least telephone number information indicating the telephone number of the user mobile terminal and information to be notified to the user in association with each other;
phone number information acquisition means for acquiring the phone number information from the client terminal;
URL transmitting means for notifying, in a text format, a URL including an identifier uniquely assigned to the user of the telephone number information to the user portable terminal of the telephone number;
reminder call means for making a confirmation call to the user mobile terminal of the telephone number based on the telephone number information;
means for reproducing, on the user portable terminal, an automatic response voice requesting an answer using a push button when a call made by the remind call means is answered;
An information notification program functioning as a means for acquiring answer information from the user's mobile terminal by pushing a button.

Images