Outlook

Half the customer relationship sits in a mailbox nobody else can reach

A customer writes in with a question. The answer goes out from an adviser's personal mailbox. Both are part of the relationship, and both are invisible to everyone else. Whoever picks the account up later starts from nothing.

Meanwhile the complete list of employees already exists — in the Microsoft 365 directory. For internal mailings it still gets rebuilt by hand, because it is missing from the marketing platform.

The Outlook integration for Caymland M4 answers both, in two halves that run independently of each other.

Part one: the add-in in the mailbox

An add-in for Outlook that your IT deploys centrally, once. After that every person has two buttons.

• While writing: a toggle, "Track in Caymland M4". On send, the message is filed to each recipient's history. A recipient who is not yet a contact is created.
• While reading: a button, "Transfer to Caymland M4". The received email lands in the sender's history. It never counts as an open.

None of this is automatic. The person decides per message. Private correspondence stays private, because they simply do not use the toggle.

Runs on Outlook on the web, Outlook for Windows in both the new and the classic build, and the new Outlook for Mac. The interface follows Outlook's display language, German or English.

On open tracking, and why it has a limit

If the message goes to exactly one recipient, open tracking is included. You see whether and when it was read.

If it goes to several, the email is filed to each history but without tracking. That is a decision, not a missing feature: Outlook sends one and the same message body to every recipient. Per-recipient tracking cannot be placed inside it. Doing it anyway would mean a single open marking every recipient as a reader — awarding points, firing campaigns and clearing suppressions for people who never opened anything.

We would rather leave the number empty than wrong.

Part two: the directory as your contact list

The second half needs no Outlook and no user. It runs in the background and pulls your organisation's Microsoft 365 directory across as contacts.

Disabled accounts, guests, rooms and equipment are skipped. What remains are people.

You set the mapping. Which directory property goes into which field is configured in the interface. Before deciding, you can have it show how many people actually populate a given property — which saves mapping a field that is empty across your organisation anyway.

Countries are normalised. "Schweiz", "SUISSE" and "CH" all land as the same value, so your reporting holds together.

Maintained data stays. If the directory has nothing for a field, an existing entry is not cleared.

Groups become audiences

Group memberships can optionally be brought across as tags. Every distribution list becomes an audience that nobody maintains. Nested groups are resolved: someone in a subgroup also carries the parent group's tag.

When a person leaves a group, the tag disappears on the next run. So that your hand-made tags are left alone, the imported ones can carry a prefix — "M365: ", for instance. What carries that prefix belongs to the sync; everything else belongs to you.

Every imported contact can additionally carry one shared tag. Build an "all employees" segment on it and it keeps itself current.

How the sync works

Direction: from Microsoft 365 to Caymland M4. In both halves nothing is written back. Your mailbox and your directory are left unchanged.

Timing: the add-in transfers at the moment of sending, or on a button. The directory sync runs on a schedule in the background.

Matching: on the email address. Existing contacts are updated; no duplicates are created.

The rest holds as everywhere in Caymland M4: all data on a person sits in one profile, can be viewed, exported and deleted, every change is logged, and operation in Switzerland or the EU is possible.

Requirements

For the add-in:

• Deployment through the Microsoft 365 admin centre. This is Microsoft's rule: without central deployment the on-send recording does not fire
• Set a secret in Caymland M4 once and enter it in the add-in's side panel

For the directory sync:

• An app registration in Entra with permission to read users, plus permission to read groups for the group filter and group tags, each with admin consent
• Tenant id, application id and secret stored in Caymland M4. They are kept encrypted
• Set the field mapping and the schedule

Before the first live run you can start a dry run that only counts and shows a sample mapping, without writing anything.

What this looks like day to day

The adviser goes on holiday. Her correspondence with customers sits on the contact, not in her mailbox. Whoever covers can see the history instead of having to ask.

The internal announcement. The "all employees" segment comes from the directory. New colleagues are included from the next sync, leavers drop out, with nobody maintaining a list.

The specialist team. Distribution lists in Microsoft 365 become audiences. The message to the field sales team goes to the field sales team, defined where that membership is maintained anyway.