loading...
 

  How it Works (Top)

We support the use of files to import large quantity's of customers and even preset messages. The files can be XML, CSV, Excel, or even HL7 data. The files should be well formed and complete with all names, phone numbers and email address that will be used in the message content by way of macro.

 

  Macro Considerations (Top)

Macros are simple customer data place holders. The place holders are replaced by customer data which match the customer stored value for the name.

Let's say you have three messages:
"Uncle Mark, will you be able to pick up my uniform on the way to the game?"

"James, will you be able to pick up my child on the way to the home?"

"Fred, will you be able to pick up my prescription on the way to the home?"

These three messages are mostly the same, so three individual messages won't be necessary.
"#NAME#, will you be able to pick up my #ITEM# on the way to the #LOCATION#?"


This now requires some sort of definition, so for each customer you intend to get the message, you will want to add a macro value to the record for the macros,#NAME# (required data already),#ITEM# and #LOCATION#, or they'll get a message like:
", will you be able to pick up my on the way to the ?"


The macro character is simply a beginning and end to the keyword you want to replace. This keeps it separate from other text, and gives us a filter to prevent erroneous replacements. The macro character may be any character on the keyboard, but is worth noting that making numbers and letters macro characters could produce unintended replacements.

 

  Import XML customer file (Top)

To import a file you must have the proper product type which comes with XML import capability. In the campaign management screen there will be an option to upload a file, granted you have selected a file import campaign type. Simply select the file from your HDD and save your campaign. Each customer record found will create a customer and all associated data for use in messages, unless the number or email already exists in this campaign. To correct this either delete the previous version, or simply deselect them from the campaign customers list and save the campaign then re-upload the file. NOTE: larger files may need more time, or possibly be cut into several pieces, depending the size of the file.

 

  XML customer data node (Top)

If you are using XML, we will need to know which node to look into in order to find the customers data. This will be case sensitive, so be sure to match it exactly. In order to provide multiple nodes, and possibly access databases, we are implementing the ability to use a comma separated name set to provide multiple table inclusions.

 

  Customer name node location (Top)

In the data provided by file, one of the columns will need to be designated as the customer name. This is used to identify customers requesting to be removed from contact or troubleshoot reported issues.

 

  Phone number node location (Top)

In the data provided by file, one of the columns will need to be designated as the phone number. If you are only using an email survey campaign, obviously this will not be required, though. NOTE: in the event an email campaign is created and the customers do not have phone numbers, in order to convert that campaign to IVR or SMS, each customer will need to have a telephone number, or the message cannot be delivered. In these cases it may be easier to create a new campaign.

 

  Email node location (Top)

In the data provided by file, one of the columns will need to be designated as the customer email address. If you are only using an SMS/IVR survey campaign, obviously this will not be required, though. NOTE: in the event an phone campaign is created and the customers do not have email addresses, in order to convert that campaign to EMail, each customer will need to have an email address, or the message cannot be delivered. In these cases it may be easier to create a new campaign.