KR20020019496A - The procedure for cutting off rejected E-mail addresses on sending messages for marketing and infomation using E-mail - Google Patents

Abstract

PURPOSE: A method for interrupting double sending to an identical e-mail address is provided to maximize the effectiveness of on-line marketing and information transfer by previously preventing identical information from being transmitted to an identical person doubly. CONSTITUTION: An e-mail sending system compares the present destination e-mail address and other necessary additional items through a receiving denier management database, previously registered, before every e-mail is transmitted. If the e-mail address is for a receiver who is not registered as a receiving denier, the e-mail sending system transmits it to the receiver. If the receiver of the e-mail is a registered receiving denier, the e-mail sending system cancels its transmission.

Description

The procedure for cutting off rejected E-mail addresses on sending messages for marketing and infomation using E-mail}

The present invention is a technology of the field of e-mail transmission (DB marketing and Email marketing) linked to the database, conventionally received by cleaning or filtering the original database itself, such as deleting the original database itself, in order to block sending to the recipient email address. Only sent to email addresses that do not reject. This method can be used as a one-off blocking method despite much effort, but it essentially sends shipments to the recipient's email address contained in different databases, different shipping systems at the same company, and new data obtained. It cannot be blocked.

The ultimate object of the present invention is to maximize the publicity effect and contribute to the image of the company by blocking the transmission to the recipient in advance in sending e-mail for promotional and information delivery purposes. There are a number of situations that can be sent to the rejector, so the basic task is that transmission to the rejector should be blocked for all expected situations, and it can be divided into detailed tasks as follows.

1. In sending e-mails, transmissions should be blocked to the recipient's email addresses in different data files of the same sending system.

2. In sending e-mails, transmissions should be blocked to the recipient's email address, even if sent on different dates in the same sending system.

3. When sending an e-mail, the sending should be blocked to the recipient's email address, regardless of what network or group the sending system is sending.

4. In sending e-mail, no matter what date it is sent by the network or group's sending system, the sender's email address should be blocked.

In the present invention, in order to block the transmission of the recipient's email address in all the above situations, the present invention is characterized in that it operates separately by specifying a new or already created database for the recipient management . In other words, the email addresses of all the messages sent and the email addresses of the recipients registered in the recipient management database are compared and matched so that the transmission is canceled.

FIG. 1 schematically illustrates a method of blocking transmission to an unsubscriber email address in the simplest form for better understanding of the present invention. (Note: Drawings in this specification are not treated as identifiers due to SGML conversion errors.)

Figure 1. Schematic diagram for blocking transmission to the rejection

The email sending system is configured to compare the email address to be sent now with other necessary additional conditions in the pre-registered recipient management database as shown in FIG. 1 before all emails are actually sent. If the email address is not registered as a rejection after comparison, it is sent to the receiver and if it is registered, the transmission is canceled. This is not the same concept as sending an existing recipient email address by filtering only those email addresses that have not been previously removed or unsubscribed from the original data file. Regardless of whether or not the user is unsubscribed, even if it is sent unknowingly, the user is compared with the database for the recipient management and is blocked from being transmitted.

The creation of the complaint management database is described later in this specification by way of examples included in the solution.

As a concrete comparison method, the SQL statement as shown in the following example can be used. The following statement is the simplest form for comparing the recipient's email address.

Comparative syntax example 1)

Select [Email] From [Rejector Table] Where [Email] = 'aaaa@company.com'

In the above syntax, "aaaa@company.com" refers to the email address to be sent, which is variable.

If there is a record that is returned as a result of executing the above statement, "aaaa@company.com" is an email address that has been unsubscribed and is not sent because it is determined as a rejection.

In addition, the recipient management database is non-temporary and semi-permanent, so that email addresses sent on different dates can be checked for unsubmissions without any additional work.

FIG. 2 is an extension of the single configuration of FIG. 1 to a network. In other words, place the recipient management database in a shareable location on the network (for example, in a shared folder or an RDBMS DB such as SQL Server) to be accessed simultaneously by multiple computers.

Figure 2. A system conceptual diagram for blocking sender transmission in the network

This allows you to prohibit transmission to the Recipient's Email address even in a group-level work environment.

By designating the same database for the recipient management in all the email sending systems shown in FIG. 2, it is possible to prevent duplicate sending in groups.

Among SK Soft's products, the method of the present invention is specifically included in the Email marketing and customer management solution (refer to the product execution screen of FIG. 3).

Figure 3. Email marketing and customer management solution execution screen

4 shows an example of a detailed configuration of a screen for setting a database for managing recipients in an email marketing and customer management solution.

Figure 4. Example of screen configuration for database settings for complaint management

In Figure 4, if you already have a database for managing recipients, you can specify it by clicking the Browse MDB or Connect ODBC button. If it is not already created, create a database for managing recipients through the normal database creation method. After that, specify it in the above screen.

The table structure of the recipient management database shown in FIG. 4 is as follows.

Table Structure (Table Name: unsub)

Field name Data format size Usage

no Serial number 4 Sequence

username text 255 unsubscriber (for reference only)

company text 255 Unsubscribed company (for reference only)

Email Text 255 Unsubscribed Email Address

ref text 255 for additional condition queries

flag text 255 For additional condition queries

In the structure of the above table, the [Email] field is used for basic rejection judgment, and the other fields are used for specifying additional conditions or for reference.

In addition, in FIG. 4, the user can specify whether to use the recipient management database setting arbitrarily, and additional conditions can be specified by allowing the user to directly input a SQL query syntax.

[Note]: Registering the recipients in the recipient management database can be automatically updated through the unsubscribe hyperlink in the body of the outgoing email message or manually updated based on the sender information of the returned email. .

The program (email marketing and customer management solution) is blocked or transmitted by determining whether to reject based on the flowchart shown in FIG. At this point, the email address is usually taken from a data file (usually a database), so it will repeat until the email is sent.

Figure 5. Blocking block diagram included in Email marketing and customer care solutions

In FIG. 5, a function including the following SQL statement was used for the complaint evaluation.

usql = "Select [email] From [unsub] Where [email] = '% 1'"

'In the above syntax, the% 1 character is replaced with the email address actually sent.

Public Function IsUnsub (ByVal UnsubList As String, ByVal id As String,

Optional udb As Object, Optional usql As String, Optional ByVal

OnSend As Boolean = True) As Boolean

Dim rsUnsub As Recordset

IsUnsub = False

If Not udb Is Nothing And usql <> "" Then

'Return records that meet the specified SQL syntax

Set rsUnsub = GetRecordSet (udb, Replace (usql, "% 1", id))

If rsUnsub.RecordCount> 0 Then 'If there is a returned record, unsubscribe

IsUnsub = True

End if

rsUnsub.Close

End if

End function

If the result of the above function is true, the email address to be sent is blocked from being sent as a recipient.

Using a separate recipient management database instead of editing the original database to block transmissions to the recipient email addresses can save a lot of work and time for the practitioner.

Ultimately, it will contribute to the improvement of productivity by not only improving the image of the external company but also spending the surplus time on other productive tasks.

In addition, the present invention is a method that can block the sender's sending to the email address in advance even in the multi-sending system of the group unit, which can solve the problem of the sender's retransmission, which is becoming a social problem in recent years. It is a good solution.

It is no exaggeration to say that the continued growth of the email marketing market stems from thorough complaint management.

Claims (1)

In the online marketing and delivery of information by email, the method of blocking the sending of the unsubscriber to the email address in advance, Interworking the recipient management database with an email sending system; Comparing the email address registered in the recipient management database with the email address to be sent, canceling the transmission if it is already registered and sending if it is not registered. To block sending emails to email addresses