JP6746147B1 - Event execution system, event execution method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an event execution system used for payment management business. An event execution system sets an execution schedule of a series of events until a job is completed for a job related to a job performed by a second user and a delivery destination of the first user. Information from the second user, a control unit that executes the event by delivering the information to the delivery destination of the first user based on the setting of the execution schedule, and an execution result of the event And an information presenting unit that presents the execution result to the second user. [Selection diagram] Figure 1

Description

The present invention relates to an event execution system, an event execution method and a program.

When an enterprise charges a customer for goods or services, the payment from the customer may be delayed. In that case, the company sends a reminder notice to the customer to prompt payment. At this time, a series of operations such as billing, payment confirmation, extraction of unpaid customers, reminder notification to the extracted customers, etc. occur, but each operation is often managed separately. For example, a reminder notification service may be outsourced to a print/shipper of a mail or a call center, and the subcontractor may send a reminder letter in paper or reminder by telephone.

As a related technique, Patent Document 1 discloses a server that charges gas charges and makes electronic payments on behalf of gas companies. Patent Document 2 discloses a system that automates billing for products or services that are regularly purchased by customers.

JP, 2009-288921, A JP, 2016-126599, A

In a company, since each work of a series of works is managed separately, there arises a problem that a management load increases, a human error occurs, a working time and a labor cost increase.

Therefore, an object of the present invention is to provide an event execution system, an event execution method, and a program that solve the above-mentioned problems.

According to an aspect of the present invention, a scenario in which the event execution system executes a series of the events including one or a plurality of the events related to an operation performed by the second user on the plurality of first users Setting of the number of executions indicating the maximum number of times that the job is executed until the task is completed, setting of an arbitrary execution schedule for each of the events included in the scenario, and information of the delivery destination of the first user for each of the events And a program for executing the scenario by executing the event from the second user, and executing the event based on the execution schedule when a predetermined execution condition is satisfied for each of the events included in the scenario. An acquisition unit that acquires the described program, a control unit that executes the event by distribution of information to the distribution destination of the first user by executing the program, and an execution result of the event and acquire the execution result. An information presenting unit for presenting to the second user, wherein the control unit repeatedly executes the program with the execution count as an upper limit when the work is not completed , and the control unit when the work is not completed. The program is repeatedly executed with the number of executions being the upper limit, the business is a payment management business, and the execution schedule is set to a payment reminding execution date set before a predetermined payment date. An execution date and a second execution date, which is an execution date of the payment reminder, are included, and the program describes that the payment reminder is executed when a predetermined payment reminder execution condition is satisfied. When the first execution date arrives by executing the program, the message delivery unit is instructed to remind the payment, the message delivery unit notifies the reminding of the payment by sending the first message, and the control unit executes the program. When the second execution date comes when the payment reminder execution condition is satisfied, the message distribution unit is instructed to reminder the payment, and the message distribution unit urges payment and guides the payment method. When the second message including information is sent to notify the payment reminder and the terminal device used by the first user accesses the address information, the content distribution unit guides the payment method to the terminal device. When the first user makes a payment, the control unit acquires the notification and pays the payment among the plurality of the first users. The first user who has not made a payment is extracted, and the reminding of the payment and the reminder of the payment are executed the number of times until the extracted first user makes a payment .

According to an aspect of the present invention, address information of the content is included in a message related to the payment reminding message in addition to the message related to the payment reminder.

According to an aspect of the present invention, the information presenting unit responds to the action of the first user with respect to the message regarding reminding of the payment, the action of the first user with respect to the message related to the demand for payment, and the distribution of the content. The viewing history of the first user and information indicating the payment status of the first user are presented to the second user.

According to one aspect of the present invention, displays setting of the execution schedule, and the first user of the distribution destination information, and the program, a registration screen for inputting, setting and the execution count, the acquisition The section acquires the setting information and the distribution destination information input on the registration screen.

According to one aspect of the present invention comprises an event execution system, described above, the second user via a network from a terminal device to be used, setting of the execution schedule, and the delivery destination information, said program And a setting of the number of times of execution, and a cloud computing system configured to be input to the registration screen.

According to an aspect of the present invention, there is provided an event execution method in which a second user provides a plurality of first users with a message delivery unit that delivers a message and a content delivery unit that delivers content . Regarding an event related to a business to be performed, a scenario for executing a series of the events composed of one or a plurality of the above events is set in the number of executions indicating the maximum number of executions until the business is completed, and included in the scenario. A program for executing the scenario and the step of acquiring from the second user the setting of an arbitrary execution schedule for each event and the information of the delivery destination of the first user for each event, which is included in the scenario. For each of the events, a step of acquiring the program in which it is described that the event is executed based on the execution schedule when a predetermined execution condition is satisfied, and execution of the program to the distribution destination of the first user The step of executing the event by delivering the information and the step of acquiring the execution result of the event and presenting the execution result to the second user, the business is a payment management business and the execution schedule The setting includes a first execution date set before a predetermined payment due date as a payment reminding execution date and a second execution date which is a payment dunning execution date. Is not completed, the program is repeatedly executed with the number of executions as an upper limit, and the program is described to execute the payment dunning when a predetermined payment dunning execution condition is satisfied. When the first execution date arrives, the message delivery unit is instructed to remind the payment, and the message delivery unit notifies the payment reminding by sending the first message. When the payment reminder execution condition is satisfied, the second execution date comes. Then, the message delivery unit is instructed to remind the payment, and the message delivery unit notifies the reminder of the payment by transmitting a second message including address information of the delivery source of the content that provides the reminding of the payment and the payment method. When the address information is accessed from the terminal device used by one user, the content distribution unit distributes the content for guiding the payment method to the terminal device, and when the first user makes a payment, obtains the notification. And extracting the first user who has not made the payment from the plurality of first users Then, until the extracted first user makes the payment, the reminding of the payment and the reminder of the payment are executed the number of times of execution.

According to one aspect of the present invention, the program causes the computer about events relating to the business in which the second user is performed for a plurality of the first user, performs a series of the event that is configured with one or more of said event Setting the number of executions indicating the maximum number of times that the scenario is executed until the task is completed, setting an arbitrary execution schedule for each event included in the scenario, and setting the execution time of the first user for each event. A delivery destination information and a user program for executing the scenario, which is based on the execution schedule when a predetermined execution condition is satisfied for each of the events included in the scenario. Means for acquiring the user program in which execution of the event is described, means for executing the event by distribution of information to the distribution destination of the first user by execution of the user program, acquisition of execution result of the event Then, the execution means is caused to function as means for presenting the execution result to the second user, and the execution means repeatedly executes the user program with the execution count as the upper limit when the business is not completed, and the business is payment management. In the business, the execution schedule setting includes a first execution date that is set as a payment reminding execution date before a predetermined payment date, and a second execution date that is a payment dunning execution date. The user program is described to execute the payment dunning when a predetermined payment dunning execution condition is satisfied, and the executing means sends a message when the first execution date arrives by executing the user program. When a reminding of payment is instructed to the message delivery unit that delivers the message, and the second execution date arrives when the payment reminder execution condition is satisfied, the message delivery unit is notified of the content of the reminder of payment and the payment method When a payment reminder is instructed by transmitting a second message including address information of a delivery source, and the first user makes a payment, the notification is acquired, and the payment is made among the plurality of first users. The first user who is not yet selected is extracted, and the reminding of the payment and the reminder of the payment are performed the number of times until the extracted first user makes a payment.

According to the present invention, management of a series of events can be unified.

It is a block diagram of the event execution system in 1st embodiment of this invention. It is a figure which shows an example of the management data in 1st embodiment of this invention. It is a figure which shows an example of the registration screen in 1st embodiment of this invention. It is a figure which shows an example of the scenario in 1st embodiment of this invention. It is a figure which shows the example of the execution result of the scenario in 1st embodiment of this invention. It is a figure which shows an example of the delivery content in 1st embodiment of this invention. It is a figure which shows an example of the statistical data by 1st embodiment of this invention. 6 is a first flowchart showing an example of an event management process according to the first embodiment of the present invention. 7 is a second flowchart showing an example of an event management process according to the first embodiment of the present invention. It is a figure which shows an example of the hardware constitutions of each system by 1st embodiment of this invention.

<First embodiment>
The event execution system according to the first embodiment of the present invention will be described below with reference to FIGS. FIG. 1 is a configuration diagram of an event execution system according to the first embodiment of the present invention.
The event execution system 1 is a system that executes an event related to payment management business (payment reminder or collection business) to a customer (end user) of a user company.

As shown in FIG. 1, the event execution system 1 includes a user company system 10, an event management system 20, a content distribution system 30, a payment system 40, end user terminal devices 50A and 50B, and an SMS distribution system 60. The email distribution system 70 is included.

The user company system 10 and the event management system 20 are communicatively connected via a network such as the Internet. The event management system 20 and the content distribution system 30 are communicably connected. The content distribution system 30 is communicatively connected to the event management system 20 and the end user terminal devices 50A and 50B. The payment system 40 is communicatively connected to the content distribution system 30 and the user company system 10. The end user terminal devices 50A and 50B are communicatively connected to the SMS distribution system 60, the Email distribution system 70, and the content distribution system 30.

The user company system 10 is a system of a user company that requests execution of an event. The user company system 10 is composed of one or more computers such as server terminal devices. The user company system 10 registers, in the event management system 20, information necessary for executing an event, such as personal information of an end user who is an event execution target, an event execution scenario, and the like. User companies are, for example, insurance companies such as life insurance and car insurance, and financial institutions such as banks, and events are a series of billing, payment confirmation, extraction of unpaid customers, and reminder notification to the extracted customers. Reminders of payments, reminders, payment guidance, thank-you notices, etc.
The user company system 10 also receives the execution result of the event from the event management system 20 and related systems. Alternatively, the person in charge of the user company can access the event management system 20 and refer to the execution result of the event.

The user company system 10 is not limited to one company, public organization, or organization. The event management system 20 can receive event execution instructions from a plurality of user company systems 10 and manage event execution.

The event management system 20 creates an execution schedule according to the scenario registered by the user company system 10, and notifies the end user of the message by using notification means such as SMS (short message service) or electronic mail. As illustrated, the event management system 20 includes a Portal system 201, an FTP management system 202, an SMS management system 203, an Email management system 204, an API management system 205, a main DB 206, and an execution result DB 207.

The Portal system 201 has a portal function for the user company system 10 and a function of controlling execution of events. For example, the Portal system 201 has a function of registering information of a user company and end users, a setting function of a scenario, a function of executing an event based on a scenario, and an event of executing an event at an arbitrary timing regardless of the scenario, according to an instruction of the user company. It has a function of performing, a function of managing and displaying statistical information such as a history of event execution, progress, and a result report.
For example, the portal system 201 generates a web screen for registering data necessary for event execution, and provides the web screen to the user company. When the data required for event execution is registered, the Portal system 201 writes and saves the data in the main DB (DB is an abbreviation for database) 206.

Further, when the data necessary for executing the event is registered, the Portal system 201 links the data with the content distribution system 30. For example, the Portal system 201 may transmit data to the content distribution system 30, or the main DB 206 may be accessible from the content distribution system 30.

The FTP management system 202 registers in the main DB 206 the data uploaded from the user company and necessary for executing the event. For example, the FTP management system 202 constantly monitors the upload folder, and when it detects the uploaded data, it immediately performs the registration process to the main DB 206.
The user company can register data using either the Web screen provided by the portal system 201 or the FTP management system 202.
An example of data uploaded from a user company will be described next with reference to FIG.

The SMS management system 203 controls SMS delivery based on the event information registered in the main DB 206. For example, the SMS management system 203 manages an SMS delivery instruction and an SMS delivery history and log. The SMS management system 203 uses the external SMS delivery system 60 to deliver SMS. Alternatively, the SMS management system 203 may have an SMS distribution function and perform SMS distribution.

The email management system 204 controls the delivery of the electronic mail based on the event information registered in the main DB 206. For example, the email management system 204 manages an email delivery instruction, an email delivery history, and a log. The email management system 204 uses the external email delivery system 70 to deliver an email. Alternatively, the email management system 204 may have an email delivery function and perform email delivery.

The API management system 205 cooperates with an external system via an API (Application Programming Interface). For example, the SMS management system 203 issues an SMS distribution instruction to the SMS distribution system 60 via the API management system 205. For example, the email management system 204 issues an email delivery instruction to the email delivery system 70 via the API management system 205. Further, for example, the API management system 205 issues a content distribution instruction to the content distribution system 30 based on the event information registered in the main DB 206. The API management system 205 can also set system control or the like for linking the event information to an external system such as issuance of a paper notice. The event information will be described with reference to FIGS.

The main DB 206 is a database that stores information on user companies and end users, event information, and event execution results.
The execution result DB 207 is a database that is replicated in synchronization with the main DB 206. The main DB 206 is updated in real time, while the execution result DB 207 is updated regularly. The contents of the main DB 206 at each point of time are copied and stored in the execution result DB 207 as history information.

The content distribution system 30 distributes content including guide information to end users based on the event information registered in the main DB 206 of the event management system 20. The content includes content that prompts action on the event. For example, if the event is a payment reminder, the content distribution system 30 distributes content that prompts payment for the bill and guides the payment.

For the content distribution system 30, any content distribution system can be used. For example, it may be a moving image distribution system or the content distribution system disclosed in Japanese Patent No. 6368876. This content distribution system provides information such as HTML (HyperText Markup Language), Javascript (registered trademark), CSS, etc. to a Web browser that operates on the EU terminal device 50, instead of playing back moving information. By using this technology, we will distribute still images, text data and video data to deliver personalized content.By using this system, we can create content that is specialized for each end user. It can be delivered efficiently at low cost.

The payment system 40 is a generally provided payment system used by end users for payment. The payment system 40 may be provided in a plurality of types so that the end user can select it according to his or her preference. The payment system 40 notifies the content distribution system 30 and the user company system 10 of the payment processing status. The payment collected by the payment system 40 is sent from the payment system business operator to the user company.

Next, the information stored in the main DB 206 will be described with reference to FIG.
FIG. 2 is a diagram showing an example of management data in the first embodiment of the present invention.
The company information, department information, and case information include the company name of the user company that is the request source of the event execution, the department name, and the management case name given for a series of event executions.
The event information includes an event execution period and an execution schedule (scenario), data for specifying an event execution target (for example, an ID of an end user who is an SMS delivery destination), a setting content of a text of an email or an SMS, The delivery means (e-mail or SMS) or the like.
The personal information is the end user's name, address, email address, telephone number, or the like.
The action information is, for example, the status of event execution such as up to which stage of the scenario is executed, the distribution status of SMS, etc., error information if any error occurs, distribution of whether the message has been opened, etc. It is various log information including the above status and the like. The behavior information is provided to the user company as statistical information.

These pieces of information are registered in the main DB 206. Of these, company information, department information, case information, event information, and personal information are registered via the Portal system 201 or the FTP management system 202. The behavior information is registered by various systems along with the execution of the event.

Next, the event information will be described. FIG. 3 is a diagram showing an example of a registration screen in the first embodiment of the present invention.
The screens illustrated in FIGS. 3A and 3B are registration screens generated by the portal system 201 and provided to the person in charge of the user company.
The registration screen illustrated in FIG. 3A is an example of a scenario registration screen. On this screen, the program and the number of sets are registered for one item. For example, when the case with the case ID “A1” is composed of a group of events such as “remind” and “remind” in order to execute a series of tasks such as billing, payment confirmation, and notification of reminder to unpaid customer Settings for the entire item “A1” are registered in FIG. 3A, and settings for each event are performed on the screen in FIG. 3B. In the “case” column, an ID such as A1 is set. In the "Program" column, the file name and path information of the file in which the program for controlling the execution of the event is described are set. In "Number of sets", the number of executions is set. Execution of the scenario is completed when the set number of programs set on this screen are executed.

The screen illustrated in FIG. 3B is an event registration screen. On this registration screen, each item of "event ID", "delivery means", "text", "delivery destination", "schedule", and "delivery condition" can be set.
The event ID is information that distinguishes a series of events for each case. For example, the event “remind” is assigned with an ID such as A1-001, and the event “reminder to an unpaid customer” is assigned with an ID such as A1-002. In the "Event ID" column, an ID such as A1-001 is set. In the "Distribution means" column, SMS or electronic mail is selected. In the “body” field, the wording of the message delivered by SMS or the like is set. {NM} and {URL} in FIG. 3 are variables. At the time of actual distribution, the name of the distribution destination end user is set in {NM}, and the URL (Uniform Resource Locator) of the content (content distributed by the content distribution system 30) to guide the end user is set in {URL}. Sent. In the "Delivery destination" column, the ID (U01 etc.) of the delivery destination end user is set. When there are many delivery destinations, for example, a setting file in which the delivery destinations are described may be prepared, and the path information of this setting file may be set in the “delivery destination” column. In the "schedule" column, the execution date and time of the event is set.
When the person in charge presses the registration button on the registration screens of FIGS. 3A and 3B, the contents set on each registration screen are registered in the main DB 206 as event information.

Each event set on the registration screen of FIG. 3B is executed by the program set on the registration screen of FIG. This program is written so that, for example, after the event ID "A1-001" (remind) is executed, the event ID "A1-002" (reminder) is executed only for unpaid end users. Has been done. If the payment has been made to the bill, the payment system 40 notifies the content distribution system 30 of the status information indicating that the payment has been completed, and the content distribution system 30 notifies the event management system 20 of this status information. In the event management system 20, the program controls the execution of the event ID “A1-002” depending on whether or not the status information indicating the completion of payment is notified. The program may be, for example, one that can be described in a script language or the like. The program may be created by the user company, or a person in charge on the event management system 20 side may create the program by listening to the requirements from the user company.

Next, a scenario based on the event information registered in the main DB 206 will be described.
FIG. 4 is a diagram showing an example of a scenario in the first embodiment of the present invention.
The scenario shown in FIG. 4 relates to insurance premium payment management operations. Insurance is paid once a month by direct debit. The withdrawal date is set to the 15th of every month. If the account cannot be debited, payment will be reminded. At the time of reminder, the end user is instructed to select from among (a) a credit card, (b) convenience store payment, and (c) payment of two insurance premiums at the same month when the account is debited next month. In addition, it will be expired if you are not paid twice in a row. For such payment management work, a person in charge of the system company registers, for example, a scenario in which two sets of the following three events are performed.

I. Remind before withdrawal: Execute 5 days before the day of withdrawal (15th) (10th of every month).
B. Reminder... Immediately executed for end users who could not be transferred on the 15th.
C. Payment thank-you note: The thank-you note is sent to the end user who received the payment as a result of the reminder.

FIG. 4 shows an example of scenario execution. The event “1. Remind before withdrawal” is executed for a certain end user α. The event management system 20 sends, for example, a message such as “XX, every month on the 15th of every month, the insurance premium withdrawal date. Please prepare the insurance premium in your account.” by SMS or email. The account debit is executed by the system β (not shown) of the financial institution where the end user α has an account on the 15th. Whether or not the account can be debited is notified to the event management system 20 (Portal system 201) via the user company system 10 or the API management system 205. If the account cannot be debited, the event management system 20 conducts the event "2.1st reminder". The event management system 20 sends a message including the content urging the payment of insurance premium and the URL of the content by SMS or e-mail. As will be described later, by viewing the content, the end user α can select any one of (a) credit card, (b) convenience store payment, and (c) collective payment twice when the account is debited next month. When the method (a) or (b) is used for payment, the event management system 20 performs the event “3. Thank-you note for payment”. On the 10th day of the next month, the event management system 20 executes the event “4. Remind before withdrawal”. If the transfer cannot be made on the 15th, the event management system 20 carries out the event “5.2nd reminder”. When the payment can be confirmed after the reminder, the event management system 20 performs the event "6. Thank-you note for payment". If the payment cannot be confirmed even after executing two sets of the above events (1) to (2), the fact is notified to the user company system 10. The user company system 10 notifies the end user α of the contract expiration guide. FIG. 5 shows an example of the execution result of the same scenario.

FIG. 5 is a diagram showing an example of a scenario execution result in the first embodiment of the present invention.
In the example of FIG. 5, “1. Remind before withdrawal” and “3. Thank-you note for payment” are performed by email, and “2. Reminder” is performed by SMS. In “2. Reminder”, the content distribution system 30 and the payment system 40 are linked. The same applies to 4 to 6. Next, these cooperation functions will be described with reference to FIG.
Note that the paper delivery method indicates that the delivery/printing system can be linked to the mail printing/delivery system via the API management system 205. For example, in the case of the "5.2nd reminder", a reminder letter may be sent by mail in addition to the reminder by SMS.

FIG. 6 is a diagram showing an example of distribution contents in the first embodiment of the present invention.
FIG. 6 shows an example of content distributed by the content distribution system 30. This content is distributed when the URL included in the reminder message is accessed using the EU terminal device 50. Material data, HTML files, Javascript (registered trademark), moving image files in MPEG format, etc. necessary for content distribution are registered in the content distribution system 30.

The content distribution system 30 first distributes the image M1, and when a predetermined time has elapsed, distributes the image M2 and then the image M3. The content distribution system 30 may distribute audio information corresponding to each image together with these images. For example, the image M1 including the name of the end user is generated by the content distribution system 30 with reference to the personal information (FIG. 2) registered by the user company. Similarly, the image M2 including the insurance premium withdrawal date is generated by the content distribution system 30 by referring to the execution result of the event related to the end user in the main DB 206 or the execution result DB 207.

In image M3, content distribution system 30 waits until the end user selects a payment method. When "account debit" is selected, the content distribution system 30 distributes the image M4a displaying the billing content for the next time the account is deducted and requests confirmation. When the end user presses "procedure completed", the end screen is displayed and the content distribution is completed. Information on the payment method selected by the end user is recorded in the content distribution system 30.

When "convenience store or credit card" is selected, the content delivery system 30 delivers a screen M4b that prompts the user to select between credit card payment and convenience store payment. When "Pay with credit card" is selected, the content distribution system 30 sequentially distributes the images that lead to the payment completed state by operating according to the guidance. For example, the content distribution system 30 distributes an image (not shown) for inputting credit card information or an image (not shown) requesting confirmation of payment details, and when the end user agrees to the payment details, the payment system. 40 is notified of credit card information and the like, and is requested to perform settlement processing. The content distribution system 30 also distributes the end screen to complete the distribution of the content.

When “Pay at convenience store” is selected, the content distribution system 30 distributes an image (not shown) showing a payment method at the convenience store or an image (not shown) requesting confirmation of payment application at the convenience store. When the end user agrees to the payment application, the end screen is delivered and the content delivery is completed.

In addition to notification of messages by SMS and e-mail, the content distribution system 30 can distribute a wealth of information by distributing contents, so that not only unilateral information notification but also end user operation Interactive correspondence is possible. As a result, it is possible to reduce the cost and human error by unmanning the payment reminder and the collection work that have been entrusted to the call center operator and the like.

The distribution of the content described in FIG. 6 is also an example of event execution (for example, the event “payment guidance”). The event management system 20 can execute an event by causing the content distribution system 30 to distribute the content in cooperation with the content distribution system 30.

The payment method on the spot is not limited to the payment at the convenience store or the credit card. It is possible to pay by various online payment methods by linking with online payment systems provided by various agents through the API management system 205. With online payment, the end user can immediately complete the payment by simply following the guidance of the content at a convenient time.

FIG. 7 is a diagram showing an example of statistical data according to the first embodiment of the present invention.
FIG. 7 illustrates a display screen of an e-mail delivery log. The "date" and "time" are the date and time when the event was executed, respectively. "Personal ID" is the ID of the end user of the e-mail delivery destination, "Recipient" is the delivery destination e-mail address, and "Status" is the state where all the data is ready to be sent. , The processing status such as opening by the other party is recorded. The Email management system 204 cooperates with the Email distribution system 70 to acquire the processing status and register it in the main DB 206 (action information). Regarding the information of the “personal ID” and the “recipient”, the Email management system 204 refers to the personal information of the main DB and acquires the information.

Similarly, when the SMS delivery is performed, the SMS management system 203 registers the delivery log in the main DB 206. The "situation" can be arbitrarily set according to the event. For example, the API management system 205 acquires the processing status such as whether the content URL is accessed, the content is viewed, the payment is executed, or the like from the content distribution system 30 and registered in the main DB 206.

The Portal system 201 generates and outputs a screen displaying an event log illustrated in FIG. 7. The person in charge of the user company can understand the event execution status for each end user and the action of the end user with respect to the notification of the event, by referring to the displayed contents.

Next, the flow of the event management processing of this embodiment will be described with reference to FIGS. 8 and 9 by taking the execution of the scenario described in FIG. 4 as an example.
FIG. 8 is a first flowchart showing an example of the event management process according to the first embodiment of the present invention. FIG. 9 is a second flowchart showing an example of the event management process according to the first embodiment of the present invention.
First, the user company system 10 transmits event information to the event management system 20 (step S1). The FTP management system 202 acquires event information and the like and registers it in the main DB 206 (step S2). The event information may be registered by the person in charge of the user company from the registration screen generated by the Portal system 201. In that case, the Portal system 201 registers the event information in the main DB 206.

At the same time, the person in charge of the content distribution system 30 inputs material data, HTML files, source codes of programs such as Javascript (registered trademark), moving image files, etc., necessary for content distribution to the content distribution system 30. The content distribution system 30 registers the material data, the source code, the moving image file, etc. in the storage unit (step S3). The content distribution system 30 stores the material data, the source code, etc. in a predetermined position, and prepares so that the content can be distributed when the predetermined URL is accessed.

In parallel, the person in charge of the payment system 40 inputs information necessary for payment processing into the payment system 40. The payment system 40 registers the input information in the storage unit (step S4).

Next, the user company system 10 transmits company information, department information, case information, and end user personal information to the event management system 20 (step S5). The FTP management system 202 acquires personal information and the like and registers it in the main DB 206 (step S7).

The event management system 20 also transmits personal information and the like to the content distribution system 30 (step S6). The content distribution system 30 acquires personal information and the like and registers it in the storage unit (step S8).

The Portal system 201 generates event execution plan information (step S9). Specifically, the Portal system 201 sets the program that realizes the scenario included in the event information to an executable state. The Portal system 201 executes a program. The program is written so as to execute an event at a required timing (for example, the schedule shown in FIG. 3B). Further, the program is written so as to execute an event (send a message) to “data specifying a target” (event information in FIG. 2) registered for the case. The Portal system 201 transmits a message based on the scenario (step S10). In the example of the scenario of FIG. 4, on the 10th day of every month, the Email distribution system 70 sends a pre-withdrawal remind message by e-mail according to an instruction from the Email management system 204.

The event management system 20 generates an execution result and updates the main DB 206 (step S11). For example, the email management system 204 registers in the main DB 206 the statuses such as the transmission of e-mail (success, error), the status after transmission (opening), and the like. Further, the Portal system 201 acquires a notification of whether or not an account is debited on the 15th through the API management system 205 and records the result in the main DB 206 (action information).

Next, the Portal system 201 transmits a message based on the scenario (step S12). The program describes not to execute the message transmission of step S12 when an appropriate action is taken for the message transmission of step S10. The message is transmitted only when there is no appropriate action for the message transmission in step S10. In this transmission, a content distribution guide and a message in which the URL of the content is embedded are transmitted. In the example of the scenario of FIG. 4, if the withdrawal cannot be made on the withdrawal date, the SMS delivery system 60 sends a reminder message by SMS according to an instruction from the SMS management system 203.

The event management system 20 generates an execution result and updates the main DB 206 (step S13). For example, the SMS management system 203 registers the transmission of the SMS and the processing status after the transmission in the main DB 206 (action information).

Next, the end user receiving the message transmission transmits a content distribution request using the EU terminal device 50 (step S14). Specifically, the URL of the message is accessed from the EU terminal device 50. Then, as described using FIG. 6, the content distribution system 30 generates the content (step S15) and distributes the content to the EU terminal device 50 (step S16). The content distribution system 30 records the content viewing record by the end user in the storage unit (step S17). The viewing record is information such as the date and time when the viewing is started and how far the content is viewed. In addition, the content distribution system 30 generates statistical information of viewing results (step S18). The statistical information is, for example, the number of times of access, the number of times of viewing, the viewing situation (for example, the number of times each scene of M1 to M4a, M4b in FIG. 6 is viewed), and the like.

For example, the Portal system 201 acquires viewing record information and statistical information via the API management system 205, and provides this information to the user company. Alternatively, the content distribution system 30 may generate a Web screen displaying the statistical information and provide it to the user company.

Next, the content distribution system 30 transmits the status information to the event management system 20 (step S19). The status information is a viewing record for each end user. The event management system 20 acquires the status information and registers it in the main DB 206 (step S20). The status information is registered in the main DB 206 as action information.

When the end user views the content to the end and chooses to pay immediately, the end user requests the payment system 40 to perform payment processing (step S21). The payment system 40 executes a payment process (step S22), and sends the result to the content distribution system 30 (step S23).

When the content distribution system 30 receives the execution result of the payment process, the content distribution system 30 records the payment status (step S24). The content distribution system 30 transmits the status information to the event management system 20 (step S25). The event management system 20 generates an execution result of the payment process and updates the main DB 206 (step S26). In the action information of the main DB 206, processing statuses of event execution, content distribution, and payment are registered.

When the user company system 10 makes a request to confirm the execution result of the event (step S27), the Portal system 201 transmits the execution result of the event (step S28). For example, the person in charge of the user company accesses the Web screen provided by the Portal system 201 and refers to the screen displaying the execution result in the event. In the event execution result inquiry screen, for example, reminding and dunning transmission history, end user action (opening) for those messages, access history to URL included in dunning message, content viewing history, settlement processing history, etc. Are displayed in chronological order. The Portal system 201 registers the inquiry history of the execution result of the event by the user company system in the main DB 206 (step S29).

According to the present embodiment, the user company only sets the event information and the personal information of the end user in the event management system 20, and performs billing, payment confirmation, extraction of unpaid customers, and reminder notification to the extracted customers. It is possible to centrally manage each event in a series of operations. As a result, the user company can save labor and automate tasks that were previously distributed and performed by its own company and other companies. As a result, the management burden can be reduced, labor costs and work time can be suppressed, and costs can be reduced. Further, the automation can prevent the occurrence of human error.

The event management system 20, the content distribution system 30, and the payment system 40 mainly cooperate with each other to provide an event execution service as a SaaS (Software as a Service) type service. By providing the service as the SaaS type service, the user company can easily perform event management simply by setting necessary information on the scenario registration screen provided by the portal system 201.

In addition, the end user can perform settlement processing in accordance with the guidance of the distributed content, which improves convenience. This improves the service level from the user company to the end user.

In the above embodiment, the user company provides the end user information and requests notification of reminding or reminder. However, when the contract for purchasing the product or service is made, the use of the event management system 20 is terminated. The user may be allowed to select. With such a contract, the event management system 20 can easily acquire the personal information of the end user. A user company that provides products and services can let the event management system 20 manage the reminder and collection operations. In addition, since the end user understands the service provided by the event management system 20, there is a possibility that the end user may take actions such as preparing an amount to be charged in advance in the account when the reminding before the withdrawal is given. You can expect reliable collection of charges. The event management system 20 can also be used to collect taxes, pay electricity, gas, and water.

In the above embodiment, the fee is paid by direct debit, but even in the case of a payment method in which the fee is transferred to the designated account by the due date, the scenario similar to that of FIG. If the payment is not made on the due date, a reminder and a thank you note can be sent. In the case of this example, the URL for distributing the content of the payment guide may be guided even before the deadline to guide the transfer before the deadline. In addition, if there is a transfer before the due date, the thank-you note of payment may be notified.

The present invention is not limited to the payment management described above, and can be widely applied to events related to work performed by the second user on the first user. For example, the user company can utilize the sales promotion activity when promoting its products and services to end users.

FIG. 10 is a diagram showing an example of the hardware configuration of each system according to the first embodiment of the present invention.
The computer 900 is, for example, a PC (Personal Computer) or a server terminal device including a CPU 901, a main storage device 902, an auxiliary storage device 903, an input/output interface 904, and a communication interface 905. Each of the user company system 10, the event management system 20, the content distribution system 30, and the payment system 40 described above is implemented in the computer 900. Each processing described above is stored in the auxiliary storage device 903 in the form of a program. The CPU 901 reads the program from the auxiliary storage device 903, expands it in the main storage device 902, and executes the above-described processing according to the program. Further, the CPU 901 secures a storage area in the main storage device 902 according to the program. Further, the CPU 901 secures a storage area for storing data being processed in the auxiliary storage device 903 according to the program.

Note that in at least one embodiment, the auxiliary storage device 903 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memories, etc. connected via the input/output interface 904. Further, when this program is distributed to the computer 900 via a communication line, the computer 900 that receives the distribution may expand the program in the main storage device 902 and execute the above processing. Further, the program may be a program for realizing some of the functions described above. Further, the program may be a so-called difference file (difference program) that realizes the above-described function in combination with another program already stored in the auxiliary storage device 903.

In addition, it is possible to appropriately replace the constituent elements in the above-described embodiments with known constituent elements without departing from the spirit of the present invention. Further, the technical scope of the present invention is not limited to the above embodiment, and various modifications can be made without departing from the spirit of the present invention.
The user company is an example of the second user. The end user is an example of the first user.
The function of registering the information of the user company and the end user of the portal system 201, the scenario setting function, and the FTP management system 202 are examples of an acquisition unit. The function of executing an event based on the scenario of the Portal system 201 is an example of a control unit. The function of managing and displaying statistical information such as the history of event execution, the progress in progress, and the result report of the Portal system 201 is an example of an information presenting unit. The programs, the number of sets, and the schedule illustrated in FIGS. 3A and 3B are examples of event execution settings.

1... Event execution system 10... User company system 20... Event management system 30... Content distribution system 40... Payment system 50, 50A, 50B... End user terminal device 201... Portal system 202... FTP management system 203... SMS management system 204... Email management system 205... API management system 206... Main DB
207... Execution result DB
900... Computer 901... CPU
902... Main storage device 903... Auxiliary storage device 904... Input/output interface 905... Communication interface

Claims (7)

Regarding an event related to a work performed by a second user for a plurality of first users, an upper limit for executing a scenario in which a series of the events configured of one or a plurality of the events is executed until the work is completed Acquiring from the second user the setting of the number of times of execution indicating the number of times, the setting of an arbitrary execution schedule for each of the events included in the scenario, and the information of the delivery destination of the first user for each of the events , Acquiring the program for executing the scenario, wherein for each of the events included in the scenario, the program is described to execute the event based on the execution schedule when a predetermined execution condition is satisfied. Department,
A control unit that executes the event by distributing the information to the distribution destination of the first user by executing the program ;
An information presenting unit that obtains the execution result of the event and presents the execution result to the second user;
A message delivery unit for delivering a message, and a content delivery unit for delivering content , wherein the control unit repeatedly executes the program when the task is not completed, with the execution count as an upper limit,
The operation is a payment management operation, and the execution schedule is set by a first execution date set before a predetermined payment due date as a payment reminding execution date and a payment dunning execution date. 2 execution days are included, and the program is described to execute the payment dunning when a predetermined payment dunning execution condition is satisfied,
When the first execution date arrives due to the execution of the program, the control unit instructs the message delivery unit to remind payment, and the message delivery unit notifies the payment reminding by sending the first message. ,
If the payment reminder execution condition is satisfied by executing the program, the control unit instructs the message delivery unit to urge payment when the second execution date arrives, and the message delivery unit urges payment. And a payment reminder by sending a second message that includes the address information of the content delivery source that guides the payment method,
When the address information is accessed from the terminal device used by the first user, the content distribution unit distributes the content instructing the payment method to the terminal device,
When the first user makes a payment, the control unit acquires the notification, extracts the first user who has not made the payment from a plurality of the first users, and extracts the first first user. An event execution system for executing the reminding of the payment and the reminder of the payment for the number of executions until the user makes the payment . The addition to the message according to demand payment, address information of the content is included in the message according to remind of the payment, an event execution system of claim 1. The information presenting unit may: the first user's action with respect to the payment reminding message, the first user's action with respect to the payment reminder message, the first user's viewing history with respect to the distribution of the content, the the information indicating the payment status of the first user to present to the second user, an event execution system of claim 2. Setting of the execution schedule, to display the first user of the delivery destination information, and the program, a registration screen for inputting, setting and the run count,
The acquisition unit acquires the setting information and the distribution destination information input to the registration screen,
The event execution system according to any one of claims 1 to 3 . Includes an event execution system of claim 4, wherein the second user via a network from a terminal device to be used, setting of the execution schedule, and the delivery destination information, and the program, the number of executions And a cloud computing system configured to input the setting of 1. to the registration screen. An event execution system that includes a message delivery unit that delivers a message and a content delivery unit that delivers content ,
Regarding an event related to a work performed by a second user for a plurality of first users, an upper limit for executing a scenario in which a series of the events configured of one or a plurality of the events is executed until the work is completed A step of acquiring from the second user the setting of the number of executions indicating the number of times, the setting of an arbitrary execution schedule for each of the events included in the scenario, and the information of the delivery destination of the first user for each of the events And a program for executing the scenario, wherein for each of the events included in the scenario, it is described that the event is executed based on the execution schedule when a predetermined execution condition is satisfied. a step of, by the execution of the program, the steps to run the pre-Symbol event by the delivery of the first information to a user of the destination, obtains the execution result of the event, the first results of this execution 2 presenting to the user, and
The operation is a payment management operation, and the execution schedule is set by a first execution date set before a predetermined payment due date as a payment reminding execution date and a payment dunning execution date. 2 execution days are included, and in the step of executing the event, when the business is not completed, the program is repeatedly executed with the execution count as an upper limit, and the program satisfies a predetermined payment reminder execution condition. Is described to execute the payment reminder, and when the first execution date arrives by the execution of the program, the message delivery unit is instructed to remind the payment, and the message delivery unit reminds the payment. When the notification is made by sending the first message and the payment reminder execution condition is satisfied, when the second execution date arrives, the message reminder is instructed to reminder the payment, and the message reminder receives the payment reminder and the payment. When the second message including the address information of the delivery source of the content that provides the method guidance is sent to notify the payment reminder, and the address information is accessed from the terminal device used by the first user, the content delivery unit Distributes the content that provides a payment method to the terminal device, obtains a notification when the first user makes a payment, and selects one of the plurality of first users who has not made the payment. An event executing method , wherein a first user is extracted, and the reminding of the payment and the reminder of the payment are executed by the number of executions until the extracted first user makes a payment . Computer,
Regarding an event related to a work performed by a second user for a plurality of first users, an upper limit for executing a scenario in which a series of the events configured of one or a plurality of the events is executed until the work is completed Acquiring from the second user the setting of the number of times of execution indicating the number of times, the setting of an arbitrary execution schedule for each of the events included in the scenario, and the information of the delivery destination of the first user for each of the events , A user program for executing the scenario, wherein for each of the events included in the scenario, it is described that the event is executed based on the execution schedule when a predetermined execution condition is satisfied. Means for executing the event by distributing the information to the distribution destination of the first user by executing the user program, acquiring the execution result of the event, and presenting the execution result to the second user Means for executing as a means, the means for executing, if the job is not completed, repeatedly executes the user program with the execution count as an upper limit,
The operation is a payment management operation, and the execution schedule is set by a first execution date set before a predetermined payment due date as a payment reminding execution date and a payment dunning execution date. 2 execution days are included, and the user program is described to execute the payment dunning when a predetermined payment dunning execution condition is satisfied, and the executing unit is configured to execute the user program by executing the user program. When the first execution date arrives, the message delivery unit that delivers the message is instructed to remind the payment, and when the payment reminder execution condition is satisfied, when the second execution date arrives, the message delivery unit is notified of the payment. , Instructing a payment reminder by transmitting a second message including the address information of the distribution source of the content that provides the guidance of the payment method, and when the first user makes a payment, the notification is acquired, and a plurality of notifications are obtained. Of the first users, the first user who has not made the payment is extracted, and the reminding of the payment and the reminder of the payment are executed by the number of executions until the extracted first user makes the payment. Yes, the program.

Images