feratel

The guest is in Deskline. They are spoken to somewhere else.

In the destination, guest registration runs through Deskline. The guests are there, the businesses are there, the activities are there. It is the system that actually knows the place.

But the path from the registration form to the guest email leads through an export, a spreadsheet and somebody holding the two together. And the more often that path is walked, the less it holds.

The feratel interface to Caymland M4 takes that path out. Guest data from Deskline arrives in Caymland continuously, and in such a way that a guest who has been here before stays the same contact.

Two routes in one interface

feratel does not deliver on one channel but on two. The integration serves both, and you set up what you need.

The web service collects only what is new. The interface remembers the point up to which it last read and continues from there next time. No full extract on every run, no runtime creeping up across the season.

How a returning guest is recognised

This is where guest data differs from address data. The same guest comes every year, sometimes spelled differently, sometimes with their partner's address, sometimes with no email address at all.

The interface therefore works in a fixed order: first the primary match code from Deskline, then the second, and only after that the email address. If none of them hits, a new contact is created.

That order is deliberate. The identifier from guest registration is more stable than an address that changes. Matching on the email address first creates a second contact on every stay with a new address – and that is exactly what produces the databases nobody wants to sort out.

Deskline also supplies an address quality indicator. It sits on the contact and can be used in segments, for instance to limit a send to addresses of dependable quality.

The switch we talk about openly

There is a setting called "import may change registration status". It is set to No by default, and that is the right default.

On "No" the import does not touch existing blocks. Anyone who has unsubscribed stays unsubscribed, even if they arrive again next week and reappear on a registration form.

On "Yes" an import lifts existing blocks – with the exception of the blacklist, which always remains. That is only defensible if your registration form genuinely carries a fresh consent and you can justify it.

We do not quietly set this switch to "Yes". Anyone who needs it decides that deliberately.

When the drop location is not yours

The activity export often lands somewhere you may only read from. Processed files can be neither moved nor deleted there.

The interface solves this with a record of what it has already read, identified by name, size and timestamp. The same file is therefore not read a second time, even though it stays where it is.

In fairness this belongs with it: if a file's timestamp changes on the far side, it counts as new and is read again. If your drop location rewrites files regularly, we settle that during setup rather than hunting for it later.

When your export looks different

Destinations do not all deliver identically. If your export deviates from the template, a mapping file is stored describing which field goes where. It overlays the built-in mapping selectively.

Which means: a deviating destination is a setting, not a piece of programming.

What you need

On the feratel side:

• Access to the Deskline Service Interface with endpoint, originator, query type and code
• The languages in which you want to draw data
• For activities: a directory or an SFTP account

On the Caymland M4 side:

• Activate the feratel integration and store the credentials
• Decide whether the import may change registration status
• Store the mapping file if your export deviates

The attributes the interface needs on the contact are created by it during setup. You do not have to prepare any fields.

What this looks like day to day

The anticipation email. The registration is recorded, the contact is in Caymland, and the pre-arrival journey starts – without anyone exporting a list.

The returning guest. On the fourth stay it is the fourth stay and not the fourth contact. The message is allowed to refer to that.

The clean send. Anyone who left an address of doubtful quality can be left out through a segment, rather than dragging down the delivery rate of the whole send.