How Het Nationale Theater's Events team finally got onto Salesforce — without leaving Outlook.

In short. Het Nationale Theater's Events team had Salesforce in the organisation but couldn't get the team onto it. Outlook ran the work; the data marketing needed sat in email folders, invisible. With FlowRunner — a Salesforce managed package plus an Outlook add-in — the team kept their existing Outlook process and got clean Salesforce records as a byproduct of how they already worked.

The recognition.

For years, Het Nationale Theater's Events team — the team that books corporate and cultural rentals of HNT's venues — ran their entire request process out of Outlook. A shared mailbox. A folder structure organised by year and by venue. A tight rhythm for handling inquiries.

It worked for communication. It didn't work for marketing. Hundreds of inquiries arrived every season carrying the exact data the marketing team needed for targeted campaigns like promotion of specific available dates, follow-up to past clients, segmented outreach. And that data was sitting in email folders. Invisible to Salesforce.

Salesforce was already in the organisation. Previous attempts to bring the Events team onto it had failed but not for lack of trying. The system didn't fit how the team worked. Manual data entry was heavy enough that it didn't get done. The native Outlook plug-in was visually noisy and asked the team to log into the main Salesforce app for everything that mattered. Data quality suffered. The marketing campaigns the data was supposed to power didn't have anything to power them.

The recognition wasn't a single Friday afternoon. It was a slow read of the situation: the data the team needed was being generated every day. The system that was supposed to capture it kept getting in the team's way.

What was actually broken.

According to HNT's Sales Manager Stijn ter Horst, four things stood out before FlowRunner.

1. Outlook was the de-facto CRM. Inquiries arrived via web form or shared mailbox. Order was kept with a folder hierarchy by year and by venue. Communication worked. Data didn't.
2. Previous Salesforce adoption attempts had failed. Not because the team didn't try but because the system didn't align with the workflow. Manual data entry was heavy enough that it didn't get done.
3. Data quality suffered as a direct consequence. Without disciplined entry, the records were too sparse to power targeted marketing campaigns. The whole reason Salesforce was wanted in the first place was the thing it couldn't deliver.
4. The native Salesforce Outlook plug-in didn't fix it. Visually noisy and too rigid to fit their use case. Full of fields the team didn't use. Forced people back into the main Salesforce app which felt time-consuming. The plug-in solved the wrong half of the problem.

What they tried, and what they ruled out.

Before FlowRunner, the team weighed the options most teams in their position weigh. The native Salesforce Outlook integration was the obvious first stop — and the obvious first disappointment. A third-party sidebar tool was considered briefly; it solved the visibility problem (records in the sidebar) but not the actual problem (a streamlined process the team would use).

What stayed off the list, deliberately: replacing Outlook. Outlook wasn't the problem. The folder structure, the shared mailbox, the rhythm of inbound inquiries were the parts that worked.

Why FlowRunner — the hinge.

If you ask Stijn ter Horst — the team's Sales Manager — why the Events team finally got onto Salesforce, the answer is in something he said about the system before FlowRunner.

"It felt like the team had to work for the system, rather than the system working for us." — Stijn ter Horst, Sales Manager — Events, Het Nationale Theater

FlowRunner is the system working for them.

Together with HNT's Salesforce partner Artomation, the Events team built a service blueprint. The discipline: keep what worked in the Outlook process; only bring in Salesforce functionality that earned its place. Capture the data the team had been losing, in a format that didn't ask anyone to leave the inbox.

How it actually worked.

The rollout was a blueprint exercise, not a software install. Together with Artomation, the Events team mapped what to keep and what to add — then built a minimum, opinionated set of Salesforce functionality on top of the workflow they already trusted.

The blueprint, not the install.

Together with Artomation, the Events team mapped what they wanted to keep (the Outlook workflow, the folder discipline, the team's rhythm) and what they wanted to add (clean Salesforce data, marketing-ready records, visibility into deal phase and source). The blueprint came first. The install came after.

The first Flow that earned its place.

The Create Event Opportunity action became the first Flow surfaced in Outlook, a streamlined form with first name, last name, company name, plus three Events-specific fields: the request phase, how the client found the theatre, and a workload estimate on a 1-to-5 scale. Nothing else. Every field on the form had to justify being there.

The architecture, plainly.

FlowRunner ships as a Salesforce managed package + an Outlook add-in. The team's Salesforce admin pinned the Flow; HNT's IT pushed the add-in to the Events team's Outlook. No new automation tool to learn. No parallel system to maintain.

Launch reality.

The plug-in launched coinciding with a busy season. The team is getting used to it. Data is now being logged neatly and structurally for the first time consistently.

Where the Events team is now.

According to Stijn ter Horst, four observations describe the team's current steady-state with FlowRunner.

1. The Outlook process the team trusted is intact. None of the folder structure, the shared mailbox, the rhythm of inbound requests was touched. Salesforce sits underneath now; the team didn't move into it.
2. Data is being captured cleanly at first contact. Each new request writes structured Salesforce records automatically, with the fields the Events team actually uses (request phase, source, workload 1–5). The records the team has now are the records the marketing team can finally use.
3. The team implemented it smoothly. Even though peak season was there the team got onboarded quickly. The system is working with the workload, not on top of it.
4. The next phase is using the accumulated data for marketing. Targeted email campaigns to past inquiries. Promotion of specific available dates. Segmented follow-up. The original reason Salesforce was wanted is finally on the runway.