discover.swiss

A newsletter for every guest is a newsletter for nobody

The destination knows what is happening next week. The guest does not. Between the two sits a newsletter that tells everyone the same thing — usually the three events somebody picked by hand, for a region stretching from one end of the valley to the other.

For the guest at one end, half of it is too far away. For the guest arriving in four weeks, all of it is over before they get there.

The discover.swiss integration for Caymland M4 turns that around. It fetches events and weather at send time — around the accommodation this guest booked, and for the days they are actually there.

What the integration gives you

• Content from the booking. Radius and period come from the reservation, not from an editorial guess.
• A block instead of an editorial meeting. You place it in the mailing once; the content is assembled at send time.
• No empty frame. If nothing is found, the block disappears along with its heading.
• No outage from a third party. If discover.swiss is unreachable, the email goes out anyway.
• Several places on one set of credentials. A region made up of several valleys can run on one account.

The two blocks

Events. A card block of what is happening nearby during the stay. You can set:

Weather. A forecast block for the same place. You can set the period — again optionally the length of the stay — the link, the alignment and the title.

Both blocks are one line in the mailing. Everything else happens in the background.

Where the location comes from

The decisive point is how the system knows which place is meant. It does not guess.

The accommodation from the guest's reservation is mapped to the matching discover.swiss identifier. The radius is drawn around that point. Someone staying down in the valley gets different events from someone staying up the mountain — without anyone building two newsletters.

A reservation for the guest is therefore the precondition. Without a booking there is no location, and the block stays empty. That is the honest boundary of this integration: it earns its keep in communication with guests who have already booked — before arrival, during the stay, immediately afterwards.

How the fetch works

Direction: from discover.swiss to Caymland M4. Nothing is written back. Your content at discover.swiss is left untouched.

Timing: not on a schedule, but at the moment of sending. The content is therefore as current as the email itself. Yesterday's cancellation is no longer in it.

Per recipient, but not per call. The content is determined per guest. Identical requests — same place, same period — are cached within one send run. A newsletter to thousands of guests in one destination therefore does not produce thousands of calls.

When something is missing, it is missing quietly. If discover.swiss returns nothing or is unreachable, the block stays empty and the email still goes. A heading without content is not rendered.

In the preview you see something. Test sends and previews have no real guest behind them. So that the block does not look invisible, a sample is shown there.

Requirements

On the discover.swiss side:

• Access with the interface address and a key
• Your project identifier. Several projects can be listed side by side if your region consists of several places

On the Caymland M4 side:

• Enable the discover.swiss integration and store the credentials
• A connected reservation source, so that the location can be derived
• Place the blocks in the mailing where they should appear

Setting this up is an appointment, not a project.

What this looks like day to day

The pre-arrival email. Seven days before arrival the guest gets the forecast for their travel days and four events within twenty kilometres. Two guests in the same region get the same email with different content.

The email during the stay. On the second day comes a note about what is still on during the days that remain. The period is not guessed; it is what is left of the booking.

The destination with several valleys. One set of credentials, several projects. Guests in each valley see their valley, and the editorial team still builds only one newsletter.