Index

Intro

This document is written for project managers, technicians and responsible security officers at the involved departments of our client and/or the parties that are connected. This document contains 2 subjects:

• Data structure XML, CSV, ODS and XLSX
  Meant for the stakeholders that deliver the data, ie. the selection of data, the collection of data both on query basis or manual delivery.

• Data transport
  The secure transport of customer data to and from Alphacomm

Intention

The goal of this document is to clarify how Alphacomm’s Collectmaxx platform works, to determine a standard concerning the delivery of data and the importance of transport security of data and to bring your attention to other technical security affairs.

How does Collectmaxx work?

Collectmaxx is a reminder service that can remind people of upcoming events, payments or share important information through phone, text messages (SMS), e-mail or other channels. Go to alphacomm.io/collectmaxx for a demonstration of the possibilities.

With the data format that is described in this document, all services can be directed.

Contact or support

Do you have a question or problem? Please log on to our service desk to create a ticket.

Data structure

To process data correctly it is important that this data is delivered in a reliable way. The content of the data has to be structured correctly to make sure it can be automatically processed. The cleaner (better) the input data is, the better the result of our services.

It is recommended to automate the selection of data - the process that determines which data is send to Alphacomm. This decreases the chance of human errors and makes the dependency of humans to make the export smaller.

All records that are delivered at Alphacomm will be processed automatically with the agreed settings in Alphacomm Live. Don't deliver records that should not be processed.

Input file format

There are five possible file formats to deliver data: CSV, XLSX, XLS, ODS and XML. The information in this document applies all formats. The conversion of this information to the required file format is shown in a required fields matrix. This field matrix is located at the end of this document.

Example files are custom made for you. You will receive a complete custom CSV example from Alphacomm with all the necessary fields and specifications.

Technical specifications XML

• The file must be encoded in UTF-8.

• The root-element is <annabel>, every record has to be surrounded by <record>.

• Every category has to be surrounded by a new element. The fields of these categories are sub-elements. For an example of the element names of the different categories see the table below.

Technical specifications csv-file

• The file must be encoded in UTF-8.

• The field are divided by an delimiter. This delimiter has to be an semicolon (;).

Example: “person_familyname”;”contact_phonenumber_1”

• All fields must be enclosed by an qualifier. This qualifier must be a double quote (“).

Example: “value"

• Records have to be divided by a newline, according to the UNIX notation, or ASCII code 0x0A, or represented in most program languages by “\n”.

• Field names have to be exactly the same as described n the documentation below^**.

• Fields cannot have unnecessary tabs and/or spaces. This can be solved with the so called trim() function.

• Fields cannot be longer than the maximum described value.

• A phone number can have a + or – sign, spaces are also allowed. It cannot have other alphanumeric signs.

• Phone numbers must be delivered with a country code.

Technical specifications ODS or XLSX file

• The first row should contain the field names and have to be exactly the same as described in the documentation below^**.

• Fields cannot be longer than the maximum described value.

• A phone number can have a + or – sign, spaces are also allowed. It cannot have other alphanumeric signs.

• Phone numbers must be delivered with a country code.

File names

Import

The names of the files that are sent to Alphacomm must be unique, even when the content is identical. The prefered format is described below:

Results

You can find our result files in our Portal or get them from our SFTP. The result files are created at night for the previous day. So at 6 AM, the results are available from the previous day.

Result files will have the following filename format:

Field specification delivery file

For every message sent by Alphacomm, a separate record must be delivered. Every record contains the necessary information from the specified fields below.

Every category can be delivered once or more times per record. This is mentioned in the header of every category. When an entity can be delivered more than once in a category it is required to number the entities by a '_X' suffix.

Example:

CONTACT_PHONENUMBER_1, CONTACT_PHONENUMBER_2

Identification (IDENTIFICATION)

The IDENTIFIER field is used to make sure that every record can be identified as unique. When there are 2 records containing the same IDENTIFIER the system will treat it as one (only the last one will be used). Therefore it is important that this identifier is unique, not only in a single file but in all your delivery history.

Person (PERSON)

Describes the customer.

Address (ADDRESS)

Describes an address.

Contact (CONTACT)

Contains all contact information from 1 person. It is possible to add multiple phone numbers for a record. The maximum is 3. To add multiple phone numbers simply add a number to the column name, for example:

CONTACT_PHONENUMBER_1;CONTACT_PHONENUMBER_2;CONTACT_PHONENUMBER_3

Invoice information (INVOICE)

All information that concerns a specific payment.

Payment arrangement (INVOICE_ARRANGEMENT)

All fields that concern a payment arrangement of a specific invoice.

Invoice lines (maximum 3) (INVOICELINES)

Describes the individual lines of an invoice. Use the '_X' suffix for multiple lines, for example:

INVOICELINES_1_DESCRIPTION

Emandate information (EMANDATE)

The fields are used to generate an Emandate.

Contract information (CONTRACT)

These fields describe the value of products or contracts.

Contractor information (CONTRACT_CONTACT)

These fields are used to present the contact information of the company for a specific contract or product.

Alphacomm control elements (CONTROL)

These fields are used to control the messages that are send by Alphacomm.

Used services (SERVICES)

Field specification result files

General result file

For the result files the same rules apply as for the input file. This means that the result file also contains field names to indicate the various results. Because of the dynamic character of the results, there can be no guarantee about the location of the different fields.

Each result contains these fields. When there are 2 phone numbers given, but when we used only one number to reach your customer, there is only 1 call result mentioned. This concerns all fields that can occur more than once.

Identification (IDENTIFICATION)

Callresult (multiple occurrences possible) (CALLRESULTS_CALL)

These fields contain all information concerning the result of the call actions. For each called phone number these fields are reported.

Possible result codes for ‘RESULT’

SMS Results (SMSRESULTS_SMS)

These fields contain all information about the sent text messages. For each phone number we send a text message to, there is one result record.

Result codes for SMS results

(Pay)mail results (multiple occurrences possible) (PAYMAILRESULTS_EMAIL_1)

These fields contain information about the sent emails. For each email address there is one record.

Result codes for (pay)mail results