KR101857964B1 - O2O omitted - Google Patents

Abstract

The present invention relates to an integrated management system which manages customer information and service reservations or registration by a company providing a customer with a service and provides customized event information performed by the company. The present invention has the following effects. Customer information of a customer who has reserved or registered a service using an application and customer information in existing customer information of a customer management system used by an existing company can be collected to manage service reservations or registration. Also, a target customer can be specified at a desired time to transmit customized event information based on customer information in a text message or a push notification form by a company. Specifically, the customer receiving the event information is induced to read the event information and store the corresponding event information to check the event information again when the customer wants, thereby expecting practical advertisement effects.

Description

Custom event dispatch and customer management system based on O2O {omitted}

The present invention relates to an integrated management system for managing customer information and service reservation or reception in a company providing a service to a customer, and providing event information customized for the event.

When a user orders a product or service online such as a smart phone, providing it offline is referred to as an O2O (Online to Offline) service. O2O services, which are based on the development of ICT and LAN technology, have penetrated various fields of daily life. Food delivery, taxi ride requests, accommodation reservations are specific examples. In addition, customer information can be grasped based on the location information to induce visits or purchases to nearby stores.

However, in the conventional system, a customer simply requests an order or a reservation to a company, and the company provides the service. This structure only allows the vendor to manually provide services or advertisements to customers who require orders, reservations, or the like, that is, customers who need to find a vendor if necessary.

On the other hand, there are many systems that present various advertisements to an unspecified number of users through push notifications. However, a system that advertises a customer who meets the conditions such as sex, age, Not much. Even if the event information is transmitted, it is not easy for the customer to guide such advertisement to actual browsing.

On the other hand, even in the case of customers who receive the advertisement event information, when the advertisement text message is received, they are not interested and are not stored.

In particular, companies that continuously provide customized services such as hospitals, nail shops, beauty salons, and spas improve customer management efficiency by integrating customer management, reservation and acceptance of services, dispatching advertising events, and earning points You need a system that can.

Published Patent No. 10-2012-0140465 (2012. 31. 2012)

The present invention aims to solve the following problems.

That is, by collecting customer information of a customer who subscribes (reservation or acceptance of a service) through existing customer information and an app in the customer management system used by an existing company, it manages service reservation and reception, The information is sent to the customer who wants to specify the target customer at a desired time and sent in the form of a character or a push notification. The customer who receives the event information is guided to browse, and the event information is stored (stored) In order to verify the system.

In order to solve the above problems,

A server 300 including a database in which customer-specific customer information and event page information are stored; A client terminal (100) for receiving an event page sent from a company registered with the corresponding customer information in the server (300) and outputting it as a message or a push notification form or for browsing in the application (10); And a business terminal 200 extracting customer information registered in the server 300 and sending out the event page in the form of a message or a push notification or providing the event page so that it can be browsed by the application 10, A customer-specific DB 310 for storing customer information and an event page for each company, a customer-specific DB 310 allocated for each customer, and a customer-specific DB 320 for storing customer information and received event pages, Includes an app customer information DB 311 for storing customer information of a customer who has reserved or accepted a service through the app 10 installed in the customer terminal 100, The customer-specific DB 320 includes an existing customer information DB 312 in which a customer installs the app 10 in the customer terminal 100, Customer information is stored A customer information DB 321, a reception event page DB 322 in which an event page received by the customer from the business terminal 200 to the customer terminal 100 is stored for a predetermined period of time, 100 includes a storage event page DB 323 in which an event page stored by the customer is stored permanently or until the expiration date of the event period. The company terminal 200 collects customer information, An event management module 250 for registering an event page for each company in the DB 310 for each company and sending an event page using the customer information collected in the customer management module 210, , And a point management module (260) for charging and managing a point to be provided to the customer terminal (100) of the customer whose customer information is registered in the app customer information DB (311) or a point to be used in sending the event, The management module 210 receives the customer information including the customer's personal information and the contact information from the customer's customer information DB 321 requesting service reservation or reception through the app 10 of the customer terminal 100, An app member information collecting unit 211 for storing the app information in the app customer information DB 311, customer information including the customer's personal information and contact information from the existing customer information managed by the customer management system of the company, An app installer character transfer unit 212 for transferring a message including an app install address to a contact of a specific customer among customers having customer information stored in the existing customer information DB 312, The specific customer is extracted as a customer who is not registered in the app customer information DB 311. In the case of the customer terminal 100 in which the application 10 for performing the push notification is not installed, Event page The event management module 250 includes an event diffusion check unit 253 for collecting customer reaction information on a corresponding event and storing the collected response information in a DB 310 The customer response information is stored in the DB 310 of each company by the event diffusion check unit 253 to allow the customer viewing the event page to select the customer reaction information, And the point management module 260 can confirm the service reservation through the app 10 of the customer terminal 100, receive the service, view the event page, archive the event page, and deliver the event page And a point setting unit 263 for individually setting points to be provided. The customer terminal 100 searches for a company registered in the server 300, A vendor connection module 110 for selecting a vendor who wants to confirm or inquire service information, a service provider for reserving or accepting a service selected by the vendor connection module 110, A customer information management module 130 for receiving the customer information including the request module 120 and the personal information of the customer possessing the customer terminal 100 and storing the customer information in the customer specific DB 320, An event management module 150 for storing and viewing or storing an event page transmitted to the terminal 100 in the customer-specific DB 320, a point for confirming the accumulated points and switching to cash Management module 160. The service request module 120 requests the server 300 to receive a service only when the business terminal 200 is within a predetermined distance range, And a service acceptance unit (122) for manually requesting reception of the reservation service if the customer is a reservation customer and providing a service selectable by the company when the reservation is not made, The module 150 stores the event page transmitted to the customer terminal 100 by the event sending unit 252 of the business terminal 200 in the reception event page DB 322 in the per-customer DB 320, When the customer selects and views a specific event page out of the event pages output from the event receiving unit 151, the event receiving unit 151 outputs the event page to the customer DB 100 An event storage 152 for storing in the archive event page DB 323, a case where a customer selects and views a specific event page out of the event pages output from the event receiver 151 And an event forwarding unit 153 for forwarding the event page to a terminal of another person. When a customer selects and views a specific event page among the event pages output from the event receiving unit 151, And is stored in the storage unit 152 or transferred to the other person by the event transfer unit 153 or directly deleted so as not to be displayed in the output list of the event receiving unit 151,

The customer information management module 130 may include a customer information collection module for inputting or modifying customer information including personal information of a customer who has a customer terminal 100 and a contact and storing the customer information in a customer information DB 321 in a customer- (132), and the event management module (250) creates an event page including event information, a target customer condition, and an event period, and registers it in an event page DB (313) 251) and an event forwarding unit 252 for forwarding the event page created by the event creating unit 251 to a customer meeting the target customer condition of the event page,

The customer terminal 100 may further include a survey request module 170 for providing a survey page through the app 10 of the customer terminal 100 when the customer terminal 100 moves away from the company by a certain distance O2O-based customized event dispatch and customer management system.

delete

delete

delete

delete

The present invention has the following effects.

That is, the service reservation and reception can be managed by collecting the customer information of the customer who subscribes (reservation or acceptance of the service) through the existing customer information and the app in the customer management system used in the existing company.

In addition, customized event information based on customer information can be sent to a company in a form of a push notification of a character or an application by specifying a desired time and a target customer.

In particular, it is possible to expect a substantial advertisement effect by causing a customer who receives event information to browse and store (store) the corresponding event information, and to confirm the event information again when the customer desires.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a schematic representation of the overall configuration of a system of the present invention.
2 is a block diagram of a configuration of a customer terminal;
3 is a block diagram of a configuration of a business terminal;
FIG. 4 is an exemplary screen by a business connection module and a service request module of a customer terminal.
5 is an exemplary screen for performing a service acceptance request by a service request module of a customer terminal.
6 is an exemplary screen by the waiting order checking unit of the customer terminal.
7 is an exemplary screen displayed by an event receiving unit of a customer terminal;
8 is an exemplary screen by the event storage unit of the customer terminal.
9 is an exemplary screen by the point management module of the customer terminal.
10 is a block diagram showing a configuration of a server;

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. However, the scope of the present invention should be understood from the description of the claims. Further, the description of known technology which obscures the gist of the present invention is omitted.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram schematically showing the overall configuration of the system of the present invention. Fig.

The present invention relates to an event information providing system based on customer information, and basically comprises a customer terminal 100, a business terminal 200 and a server 300 as shown in FIG. At this time, 'terminal' includes various smart devices including a smart phone, a PDA, and a PC.

The customer terminal 100 is a terminal owned by a customer who visits a company in which the business terminal 200 is installed and wants to use the service and is an application 10 for executing each module included in the customer terminal 100 of the present invention. Or may receive various information including the event information only in a text message without installing the app 10. [

10 is a block diagram showing a configuration of a server.

The server 300 is configured with a company-specific DB 310 for storing company information and event pages for each company, a customer-specific database 320 for storing customer information and received event pages, and a customer-specific DB 320.

As shown in FIG. 10, the company-specific DB means that a database is configured for each of the A company, the B company, and the C company. Similarly, the DB for each customer means that the database is configured for the K customer, the L customer, and the M customer.

The company-specific DB 310 includes an app customer information DB 311, a chart customer information DB 312, an event page DB 313, and a service DB 314.

The app customer information DB 311 is a database in which customer information of a customer who has made a reservation or received a service through the app 10 installed in the customer terminal 100 is stored. The stored customer information is received from the customer information DB 321 in the customer-specific DB 320 of the customer.

The existing customer information DB 312 is a database in which customer information extracted from existing customer information in the customer management system managed separately from the company is stored. When a company uses a separate customer management system, it extracts (extracts) customer information from existing customer information stored in the system (electronic customer chart, etc.) 312).

The event page DB 313 is a database in which event information provided by a vendor is stored, and specific storage information includes information generated by the event creator 251. [

The service DB 314 is a database in which service information that can be provided for each company is stored.

The customer-specific DB 320 includes a customer information DB 321, a reception event page DB 322, and a storage event page DB 323.

The customer information DB 321 is a database in which customer information including personal information of a person and contact information inputted by a customer by installing the app 10 in the customer terminal 100 is stored. The personal information may include a name, an age, a gender, an area, and the like of the customer possessing the customer terminal 100, and information previously input by the customer through the customer information collection unit 132 is included.

The reception event page DB 322 is a database in which event pages received by the customer from the business terminal 200 to the customer terminal 100 are stored for a predetermined period of time. The predetermined period can be set from several days to several months through the customer terminal 100 or the business terminal 200, and can be automatically canceled after a certain period of time.

The archive event page DB 323 is a database in which an event page stored by the customer among the event pages received by the customer from the business terminal 200 to the customer terminal 100 is stored permanently or until the expiration date of the event period. 'Archiving' means storing interesting events among the various events provided by the event receiving unit, such as putting a favorite item in a shopping cart during Internet shopping, separately in a customer's own archive list.

In the present invention, 'reserved' means that the customer delivers a doctor's intention to use the service in advance, and 'accept' means that the company accepts the customer's intention to use the service and performs the service immediately .

However, if there is a line acceptor, the waiting sequence will be generated at the subordinate position.

The customer terminal 100 receives an event page sent from a company registered with the corresponding customer information in the company-specific DB 310 of the server 300 and outputs the received event page in the form of a message or a push notification, 2, a business connection module 110, a service request module 120, a customer information management module 130, an event management module 150, a point management module 160, a survey request module 170 ).

The message includes SMS, LMS, and MMS, and provides an event page in the form of a message in the case of the customer terminal 100 in which the application 10 for performing push notification is not installed.

The business connection module 110 provides a function for searching for a company registered in the server 300 and checking a specific business information or selecting a business to which a service is to be reserved or accepted. The business connection module 110 includes a business search unit 111, And a vendor output unit 112.

The vendor search unit 111 provides a function of searching for a business by selecting a region or a service or inputting a keyword.

The interested vendor output unit 112 provides a function of automatically outputting a vendor that is reserved or accepted more than a few times or outputting a vendor manually designated by a customer among the vendors searched by the vendor search unit 111.

FIG. 4 is an exemplary screen displayed by the business connection module and the service request module of the customer terminal. In this case, it is possible to use the reception function immediately without confirming the business information, You may also want to have the vendor list in the.

The service request module 120 provides a function for reserving or accepting a service selected from a vendor selected by the vendor connection module 110 or a vendor within a certain distance range, and includes a service reservation unit 121, a service acceptance unit 122, And a waiting order confirmation unit 123.

The service reservation unit 121 reserves a service by filling in a service and a date to be used, changes or cancels the reserved service, or provides a reservation history in the form of a message or a push notification before the reservation date and time.

The service accepting unit 122 requests the service to be accepted by the local communication module 201 installed in the company to the business terminal 200 or accepts the service to the server 300 only when the business terminal 200 is within a certain distance range In the case of a customer who reserves a service, the reservation service is automatically requested to be accepted. In the case of a customer who does not reserve a service, the service provided by the corresponding company is provided and a function of receiving a request manually is provided.

The waiting order confirmation unit 123 outputs the waiting order numbers according to the reception order or the order set by the vendor, and provides the waiting time by adding up the line reception service times. If the waiting order or waiting time is less than a predetermined standard, And provides a function of informing that an order is imminent in a notification form (see FIG. 6).

Likewise, the message includes an SMS, an LMS, and an MMS. In the case of the customer terminal 100 in which the application 10 for performing push notification is not installed, the message is provided in the form of a message.

The configuration in which the server 300 requests the server 300 to receive a service only when the company terminal 200 is within a certain distance range is for preventing a no-show from being canceled without prior notice after receipt. It is possible to receive the actual receipt only from the customer terminal within a certain distance from the business terminal. The fact that the company terminal 200 is within a certain distance from the customer terminal 100 can be detected by using the company terminal 200 or the company address and the customer terminal 100 using various location recognition technologies such as local area communication, , And the distance range may be limited to a few hundred meters (preferably 100 to 500 meters).

Meanwhile, FIG. 5 is an exemplary screen for performing a service acceptance request by a service request module of a customer terminal, and may configure a acceptance request screen by differentiating it according to a service provided for each vendor. For example, in the case of a hospital, the service request module may be configured to select whether to start or resume service reservation or reception. In case of a hospital, customer information is registered in the app customer information DB 311, To accept it. As another example, in the case of a skin care shop, it is possible to select the first visiting / returning visit in the service request module, register the customer information in the app customer information DB 311 for the first visit, and check the customer information And to accept it.

The customer information management module 130 provides a function of confirming the details of the service used or receiving the customer information including the personal information and the contact information of the customer possessing the customer terminal 100 and storing the customer information in the customer specific DB 320, A history checking unit 131, and a customer information collecting unit 132.

The service history confirmation unit 131 provides a function of outputting a complete list of services used by the customer, outputting a filtered list for each company, period or service, and summing up the costs of the entire or filtered list.

The customer information collecting unit 132 provides a function for inputting and modifying customer information including personal information of a customer possessing the customer terminal 100 and a contact. At this time, the inputted or modified customer information is stored in the customer information DB 321 in the customer-specific DB 320 of the customer holding the customer terminal 100. For example, when the L customer inputs his or her personal information and contact information through the customer information collection unit 132, the L customer is stored in the customer information DB 321 in the customer-specific DB 320.

The event management module 150 provides a function of storing an event page transmitted to the customer terminal 100 by the business terminal 200 in the customer specific DB 320 and browsing or storing the stored event page, 151, an event storage unit 152, and an event delivery unit 153.

The event receiving unit 151 stores the event page transmitted to the customer terminal 100 by the event forwarding unit 252 of the business terminal 200 in the reception event page DB 322 in the per-customer DB 320, And outputs the list through the customer terminal 100. For example, the event page sent from the company A, the company B, and the company C to the customer K is received by the event receiving unit 151 in the customer terminal 100 of the customer K, And the list of each event page stored in the reception event page DB 322 is output to the customer terminal 100 of the customer K. [

At this time, when a customer selects and views a specific event page among the event pages output from the event receiving unit 151, the event storage unit 152 stores the event page, or the event delivery unit 153 transmits the event page to another person, And can be made invisible in the output list of the event receiving unit 151. [ And deletes the corresponding event page from the reception event page DB 322 when deleting the event page. If it is not directly deleted, it can be stored in the reception event page DB 322 for a predetermined period of time and then automatically deleted after expiration of the period. At this time, the period setting can be set by the customer through the customer terminal 100, and the company sending the event page can be set through the business terminal 200, or can be collectively set as the default value of the app 10 It is possible.

The event storage unit 152 provides a function of storing a corresponding event page when a customer selects and views a specific event page among the event pages output from the event receiving unit 151. [ The event page selected to be stored at this time is stored in the archive event page DB 323 and the event page list stored in the archive event page DB 323 is output to the customer terminal 100 as a separate archive list.

The event forwarding unit 153 provides a function of forwarding a corresponding event page to a terminal of another user when a customer selects and views a specific event page among the event pages output from the event receiving unit 151. [ The form provided is such that when the app 10 is installed in the customer terminal 100 of another person (for example, a customer M), the event page transmitted through the event receiver 151 of the customer M is transmitted to the reception event page DB 322 ).

FIG. 7 is an exemplary screen displayed by the event receiving unit of the customer terminal, FIG. 8 is an exemplary screen by the event storage unit of the customer terminal, and FIG. 9 is an exemplary screen by the point management module of the customer terminal.

According to the viewing / storing / forwarding of the event page, as shown in FIG. 9 and later, points are paid differentially to induce event page access.

The point is provided from the vendor terminal 200 through the server 300, and the vendor terminal 200 sets a payment point amount for browsing / storage / delivery.

The point management module 160 provides a function of confirming accumulated points and exchanging them with exchangeable means by reserving or accepting a service or browsing, storing or delivering an event page, And an exchange unit 162. At this time, the points are accumulated in the virtual account assigned to each customer in which the customer information is stored in the customer information DB 321. [

The accumulation point confirmation unit 161 provides a function for confirming the points accumulated from the company terminal 200 through the server 300. [ The accumulated points are accumulated in a virtual account assigned to each customer in which the customer information is stored in the customer information DB 321. [

The point exchange unit 162 provides a function of exchanging the accumulated points for a gift certificate, for exchanging a specific product, or for transferring it to cash and transferring it to a customer's actual account.

The survey request module 170 is a module for requesting a customer having a customer terminal 100 to visit a company having the company terminal 200 and moving the place after terminating the service using the customer terminal 100, When the customer terminal 100 moves away from the business terminal 200 or a business address by a distance of at least a predetermined distance from the customer terminal 100 using the location recognition technology such as local communication, Wi-Fi, GPS, The user can provide the survey page in the form of a push notification or the like. Survey pages may include service satisfaction surveys, revisit intentions, etc. This is to encourage customers to conduct surveys easily while traveling to other locations after using the service from the business. The predetermined distance is preferably in the range of several hundred meters. This is set as a condition to terminate the business visit when the customer is away from the business by more than a few hundred meters, but to request the survey as soon as possible after the end of service.

The company terminal 200 extracts customer information registered in the server 300 and sends out the event page in the form of a message or a push notification or provides the event page so that it can be browsed in the application 10, Module 210, a request service management module 220, a business information management module 230, a business service management module 240, an event management module 250, and a point management module 260.

The customer management module 210 provides a function of collecting customer information and storing the collected customer information in the company-specific database 310 of the server 300. The customer management module 210 includes an app membership information collecting unit 211, an existing customer information interworking unit 212, And a character transmission unit 213.

The app member information collecting unit 211 receives the customer information including the customer's personal information and the contact from the customer's customer information DB 321 requesting the service reservation or acceptance through the app 10 of the customer terminal 100 And stores it in the app client information DB 311 in the DB for each vendor.

The existing customer information interworking unit 212 extracts the customer information including the customer's personal information and the contact information from the existing customer information managed by the customer's management system of the company and stores the extracted customer information in the existing customer information DB 312 in the DB for each company do.

The app install character transmission unit 213 provides a function of transmitting a message including an app install address to a contact of a specific customer among customers having customer information stored in the existing customer information DB 312. At this time, a specific customer may be extracted as a customer who is not registered in the app customer information DB 311.

The requested service management module 220 provides a function for registering and managing a service reservation or a service reception request in the customer terminal or a service for requesting reservation or acceptance offline in the business terminal 200. The reservation management unit 221 ), A reception management unit 222, and a standby management unit 223.

The reservation management unit 221 can automatically register the reservation information including the service and the date and time by the customer terminal 100 or manually register the reservation information by the business terminal 200 and change or cancel the registered reservation service, Message or a push notification form to the customer terminal 100 in the form of a message.

The reception management unit 222 receives a reception service from the client terminal 100 through the local communication module 201 installed in the company or according to a reception request from the server 300 or a reception request from the company terminal 200 Register, and change, cancel or delete the registered reception service.

The waiting management unit 223 provides a waiting order number in the order received by the reception management unit 222 and provides a function of changing the waiting order through the business terminal 200, changing the reception order, or changing the waiting time.

The vendor information management module 230 provides a function for confirming the details of the provided service or for correcting the vendor information registered in the server 300. The vendor information management module 230 includes a service history confirmation unit 231, .

The service history confirmation unit 231 outputs a complete list of the services provided by the vendor or outputs a filtered list for each customer, period or service, and provides statistical data.

The vendor information modifier 232 provides a function of modifying the vendor information including the location and the contact of the vendor of the vendor terminal 200.

The vendor service management module 240 provides a function for registering and managing company-provided services in the company-specific DB 310 of the server 300 and includes a service registration unit 241, a service change unit 242, 243).

The service registration unit 241 provides a function of registering service information such as a service name, a required time, and a service cost in the service DB 314 in the DB for each company.

The service changing unit 242 provides a function of changing a part of the service information registered by the service registering unit 241. [

The service deleting unit 243 provides the service DB 314 with a function of deleting the registration service.

The event management module 250 registers a company-specific event page in the company-specific DB 310 in the server 300 and provides a function of sending an event page using the customer information collected in the customer management module 210, An event forwarding unit 252, and an event diffusion check unit 253. The event generation unit 251 includes an event generation unit 251, an event forwarding unit 252,

The event creating unit 251 creates an event page including the event information, the target customer condition, and the event period, and registers the event page in the event page DB 313 in the DB for each company.

The event information may include information such as a service name and a service cost. A target customer condition may include customer information such as the age, sex, and location of the event target customer. The event period may include a time and an event . The event page may include an electronic leaflet in which various event information is described, and may be composed of only text in consideration of transmission in the SMS method.

The event sending unit 252 provides a function of sending an event page created by the event creating unit 251 to a customer meeting the target customer condition of the corresponding event page.

At this time, it is possible to transmit the corresponding event page to the event receiver 151 in the customer terminal 100 of the customer meeting the target customer condition of the event page to be transmitted among the customer information stored in the app client information DB 311 in the vendor DB The customer's contact information corresponding to the target customer condition of the event page to be sent out of the customer information stored in the existing customer information DB 312 can be extracted and the corresponding event page can be transmitted in the form of a text message such as SMS, MMS or LMS.

At this time, when the app 10 is installed in the customer terminal 100 of the customer who receives the event page and receives the event 10 by the event receiving unit 151, the event page may be output through the customer terminal 100 as a push notification . Also, if you send it as a text message, you may be able to install the app by including the app install URL in the text message.

If the customer is registered in both the app customer information DB 311 and the existing customer information DB 312, the customer terminal 100 may determine the priority or send it simultaneously in the form of a push notification and a message.

The event diffusion check unit 253 includes a customer response collecting unit in the event page to collect customer response information about the event. The customer response information can be composed of simple appeal of the event (can be collected by the number of stars, etc.) or whether the participant intends to participate in the event, and allows the customer viewing the event page to select. The customer response information according to the selection may be stored in the company-specific DB 310 by the event diffusion check unit 253 and confirmed by the business terminal 200. Furthermore, it can be calculated by multiplying the profit of the event by a certain rate of favorability or participating, or the like, and then it can be used to calculate the estimated profit of the event.

The point management module 260 provides a function for charging and managing a point to be provided to the customer terminal 100 of the customer whose customer information is registered in the app customer information DB 311 and a point to be used in sending the event, A point history confirmation unit 262, a point setting unit 263, and a point setting unit 263.

The point charging unit 261 charges a point to be provided to the customer terminal 100 of the customer whose customer information is registered in the app customer information DB 311 (at the time of customer viewing / storage / delivery) Function.

The point history confirmation unit 262 provides a function of outputting the charging date and time, the charging amount, the providing date and time, the providing amount, the point detail charging including the customer to be provided, and the providing details.

The point setting unit 263 provides a function of individually setting points to be provided according to service reservation, service acceptance, event page viewing, event page storage, and event page delivery through the app 10 of the customer terminal 100 .

According to the present invention, existing customer information in a customer management system used by an existing company and customer information of a customer who has booked or received a service through the app 10 can be collected to manage service reservation and reception.

In addition, customized event information based on the customer information can be specified in a desired time by a company, and can be sent in a character or push notification form.

In particular, it is possible to expect a substantial advertisement effect by causing a customer who receives event information to browse and store (store) the corresponding event information, and to confirm the event information again when the customer desires.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It will be clear to those who have knowledge.

100: Customer terminal
110: Business connection module
111:
112: interested vendor output section
120: service request module
121: Service reservation section
122: Service reception
123: waiting sequence number confirmation unit
130: Customer information management module
131: Service History Verification Unit
132: Customer information collecting section
150: Event management module
151: Event receiver
152: Event storage
153:
160: Point management module
161: Earning points confirmation section
162: Point exchange section
170: Survey request module
200: Company terminal
210: Customer Management Module
211: App member information collecting unit
212: Existing customer information linkage section
213: App Install Text Transmission Unit
220: Request service management module
221: reservation management section
222: Receptionist
223:
230: Business information management module
231: Service History Verification Unit
232: Company Information Correction
240: Business service management module
241:
242:
243:
250: Event Management Module
251:
252: Event sending section
253: Event Diffusion Checker
260: Point management module
261:
262: point history confirmation unit
263: Point setting section
300: server
310: DB by company
311: App Customer Information DB
312: Existing customer information DB
313: Event page DB
314: Service DB
320: Customer DB
321: Customer Information DB
322: Receive event page DB
323: Archive event page DB

Claims (7)

A server 300 including a database in which customer-specific customer information and event page information are stored;
A client terminal (100) for receiving an event page sent from a company registered with the corresponding customer information in the server (300) and outputting it as a message or a push notification form or for browsing in the application (10);
And a business terminal (200) for extracting customer information registered in the server (300) and sending out an event page in the form of a message or a push notification or providing the event page so that it can be browsed by the application (10)

The server (300)
Customer-specific customer information and event pages are stored, and a company-specific DB 310 allocated for each company,
Customer-specific DB 320 that stores customer information and received event page and is allocated to each customer,

The vendor-specific DB 310
An app customer information DB 311 for storing customer information of a customer who has booked or received a service through the app 10 installed in the customer terminal 100,
And an existing customer information DB 312 in which customer information extracted from existing customer information in a customer management system managed separately from the company is stored,

The customer-specific DB 320
A customer information DB 321 for storing customer information including the personal information and the contact information of the customer who installed the app 10 on the customer terminal 100,
A reception event page DB 322 in which an event page received by the customer from the business terminal 200 to the customer terminal 100 is stored for a predetermined period,
And a storage event page DB 323 in which event pages stored by the customer among the event pages received by the customer from the business terminal 200 to the customer terminal 100 are stored permanently or until the expiration date of the event period,

The business terminal 200
A customer management module 210 for collecting customer information and storing the customer information in the DB 310 for each company,
An event management module 250 for registering an event page for each company in the DB 310 for each company and sending an event page using the customer information collected by the customer management module 210,
And a point management module (260) for charging and managing a point to be provided to the customer terminal (100) of the customer whose customer information is registered in the app customer information DB (311) or a point to be used for sending the event,

The customer management module 210
The customer information including the customer's personal information and the contact information is received from the customer's customer information DB 321 requesting service reservation or reception through the app 10 of the customer terminal 100, ), An app membership information collecting unit 211,
An existing customer information interworking unit 212 for extracting customer information including customer's personal information and contact information from existing customer information managed by the company's customer management system and storing the extracted customer information in the existing customer information DB 312 in the DB for each company,
And an app install character transferring unit 213 for transferring a message including an app install address to a contact of a specific customer among customers having customer information stored in the existing customer information DB 312,
The specific customer is extracted as a customer who is not registered in the app customer information DB 311,
And the event page is provided in the form of a message in the case of the customer terminal 100 in which the application 10 for performing the push notification is not installed,

The event management module 250
And an event diffusion check unit (253) for collecting customer reaction information for the event including the customer response collecting unit on the event page to be transmitted and storing the collected information in the DB 310 for each company,
The customer response information includes whether or not the customer wants to participate in the event,
The customer response information according to the selection of the customer viewing the event page is stored in the company DB 310 by the event diffusion check unit 253 and can be confirmed by the business terminal 200,

The point management module 260
A point setting unit 263 for individually setting points to be provided according to service reservation, service reception, event page viewing, event page storage, and event page delivery through the app 10 of the customer terminal 100,

The customer terminal (100)
A business connection module 110 for searching for a company registered in the server 300 and confirming specific business information or selecting a business to reserve or accept a service,
A service request module 120 for reserving or accepting a service available from a vendor selected by the vendor connection module 110 or a vendor within a certain distance range,
A customer information management module 130 for receiving customer information including personal information and contact information of the customer terminal 100 and storing the customer information in the customer-specific DB 320,
An event management module 150 for storing and browsing or storing event pages transmitted to the customer terminal 100 by the business terminal 200 in the customer-specific DB 320,
And a point management module 160 for confirming the accumulated points according to the viewing or storing box of the event page and switching to cash,

The service request module 120
Only when the vendor terminal 200 is within a certain distance range, it requests the server 300 to accept the service,
If the customer reserves the service, the reservation service is automatically requested.
And a service acceptance unit (122) for receiving a request for acceptance manually by providing a service selectable by the vendor if the customer does not reserve the service,

The event management module 150
The event page transmitted to the customer terminal 100 by the event sending unit 252 of the business terminal 200 is stored in the reception event page DB 322 in the per-customer DB 320 and the list is transmitted to the customer terminal 100 An event receiving unit 151,
An event storage unit 152 for storing the event page in the archive event page DB 323 in the per-customer DB 320 when the customer selects and views a specific event page from the event page output from the event reception unit 151 ),
And an event delivery unit (153) for delivering the event page to another terminal when the customer selects and views a specific event page among the event pages output from the event reception unit (151)
When a customer selects and views a specific event page among the event pages output from the event receiving unit 151,
The event page is stored in the event storage unit 152 or transferred to another person or deleted directly by the event transfer unit 153 so that the event page is not shown in the output list of the event receiving unit 151
Custom event dispatch and customer management system based on O2O.
The method according to claim 1,
The customer information management module 130
Further comprising a customer information collecting unit (132) for inputting or modifying customer information including personal information and contact information of the customer terminal (100) and storing the customer information in the customer information DB (321)

The event management module 250
An event creating unit 251 for creating an event page including event information, a target customer condition, and an event period and registering the created event page in the event page DB 313 in the DB for each company,
And an event forwarding unit (252) for forwarding the event page created by the event creating unit (251) to a customer meeting the target customer condition of the event page
Custom event dispatch and customer management system based on O2O.
3. The method of claim 2,
The customer terminal (100)
And a survey request module (170) for providing a survey page through the application (10) of the customer terminal (100) when the customer terminal (100)
Custom event dispatch and customer management system based on O2O.



delete delete delete delete

Images