Home > Information > Focus Reports > Campaigns > Creating 1:1 Personalized Mailshots

Creating 1:1 Personalized Mailshots

The Papyrus Document Framework enables you to design and produce 1:1 mailshot letters, customer offers with reply forms and marketing mailings in record time and at substantially lower cost.

A Typical Campaign Generation Workflow

1	Different letter types about fund offerings (M1, M2, M3) that contain logic, templates and text elements are defined by the Administrator and stored in the central Papyrus Repository.

2	The User selects a letter type (e. g. M1) and fills in the attributes: e. g. a type of fund which has more than 500 but less than 2000 shares.

3	A DB query using the Papyrus TypeManager is started to check the availability of this fund.

4	If the result is positive, a number of different templates are shown to the User for the selected letter type (e. g. M1)

5	The User selects templates and depending on his selection, a DB query is made to the customer database using Papyrus TypeManager. The input data, for example a certain group or age and type of customer with a certain living pattern, is delivered for the selected letter templates.

6	The personalized letter generation is started with the received data. All elements of the letter, such as text, images, marketing inserts, can be defined as conditional and dependent on certain demographics of the prospect or customer.

7	The letters are automatically sent to the Supervisor for review and sign off. In case a letter is rejected it goes back to the user or the supervisor makes the necessary changes.

8	Once the letters are successfully signed off all campaign letters are formatted, printed and mailed using the central high speed print and mail facilities.

Papyrus TypeManagers

provide simple user and application access to supported databases without coding SQL and the need for acquiring or installing database clients on each PC.

The TypeManager is instantiated by the developer on a database server. A simple IMPORT command will extract the table definitions and create CLASS definitions in the Papyrus Repository. With these definitions, the developer or administrator can now define business object TEMPLATES. One row of the DB represents one object instance. In these definitions, the fields of the tables are mapped to the defined business object. Queries produce a list object, which is a table extract of the database. In this query template the user can now edit the search or key criteria. This is much simpler to use than SQL.

Once the data is entered the user can drag the query to the type manager and drop it. This will execute the search in the database. Alternatively the user can also click on 'GET DATA' in the query template.

In the above view, the message window is opened so that the Oracle DB messages can be seen. In case the query returns more than one row, a QUERY LIST is created containing the hit list.

The query list object can be used immediately in any Papyrus application as an input data object. This object can also be used in any other application. It can also be saved as an ASCII delimited or XML tagged file.

A TypeManager provides a universal set of data templates, which can be reused in any Papyrus Objects application and on any of the supported platforms.

The 4 EYE Principle for Campaign Sign-off

The marketing coordinator sets the status 'Document Complete' which makes the document available for verification to a supervisor. The supervisor can, according to this role and document state, perform further editing or release or “Sign-Off” the document.

The User Management

Papyrus Objects uses an integrated authorization system, to ensure that no user or program can access the system without the proper authorization. Authorized users have full management control of all phases of correspondence production, from document assembly to content approval.

Interfacing with RACF, LDAP and ACTIVE Directory

Logging onto the Papyrus Desktop executes the given ID and password from the customer’s existing security system. Papyrus can interface with the company security system on the mainframe (i.e. RACF) and provides Adapter i.e. for LDAP. Papyrus Objects can also maintain security information by itself in its own storage.

© 2008 ISIS Marketing GmbH - legal disclaimer • Impressum • ISIS is not associated with Research Software Design (RSD), nor it's Papyrus Bibliography software.