# Booking to Follow-Up in One Connected Flow for a Five-Brand Events Group

> A corporate events group ran five brands, booked multi-activity events by hand and mailed customers from a separate tool. We built a guided booking wizard and automated event communications in Sales Cloud, then moved about 11,000 subscribers with their consent into branded Marketing Cloud journeys.

- Source: https://synconai.com/case-studies/corporate-events-booking-to-marketing-journeys
- Publisher: SynconAI (https://synconai.com)
- Type: Case study
- Evidence: Delivered client engagement. The client is anonymised; the industry, products and outcomes are theirs.
- Organisation: An Australian corporate events and team experience group operating five brands, delivering multi-activity events for corporate clients
- Industry: Commercial & Business Services
- Products: Sales Cloud, Marketing Cloud Growth, Flow, Salesforce Platform, Mailchimp migration
- Service: Marketing Cloud Next (https://synconai.com/salesforce-marketing-cloud-next)
- Reading time: 6 minutes

## In short

We connected a five-brand events group’s booking, delivery and marketing in Salesforce. A Book Event wizard handles multi-activity bookings, Flows send branded confirmations, staff calendar invites, 21-day reminders and post-event impact reports, and about 11,000 Mailchimp subscribers moved with consent into branded Marketing Cloud Growth segments and journeys.

## Key points

- A guided booking wizard is worth more than any report. When every booking is captured the same way, every automation after it works.
- Give automated emails an off switch. Send toggles on follow-up and impact reports let coordinators hold a message when an event did not go to plan.
- Migrate consent before you migrate contacts. Subscribers moved from Mailchimp kept their consent and unsubscribe status, which protects the brands and the sender reputation.
- Test automation like code. Phase 1 went live with a documented test suite, 21 of 21 passing, and that discipline made Phase 2 faster.

## The event lifecycle, from booking to the next booking

A coordinator books an event through a guided wizard in Sales Cloud, choosing one or more activities. Salesforce sends a confirmation under the right brand, invites the staff who will run it to their calendars and sends a reminder 21 days before the date. After the event, a follow-up and an impact report go to the client, each behind a send toggle so a coordinator can hold it when needed. The client then sits in a branded Marketing Cloud Growth segment and journey, built on audiences migrated from Mailchimp with their consent and unsubscribe status intact, which leads to the next enquiry.

### 1. Book

- Book Event wizard
- Multiple activities
- Brand
- Opportunity

One guided path for every brand and every event type.

### 2. Confirm

- Branded confirmation
- Staff calendar invites
- 21-day reminder

The customer and the crew hear the same plan.

### 3. Deliver

- Event day
- Activity records
- Staff schedule

Everything the team needs is on the booking.

### 4. Follow up

- Post-event email
- Impact report
- Send toggles

Automated, with a human able to hold it.

### 5. Nurture

- Consent mapping
- Branded segments
- Journeys
- Newsletter

Marketing reads the same customer record as sales.

## The starting position

The group designs and runs corporate events: team experiences, offsites and activity days for companies of every size. It operates five brands, each with its own audience and voice, and a single event can combine several activities, each with its own staff, timing and requirements.

Before this engagement, bookings were assembled by hand. Coordinators created records one at a time, copied details between them and wrote confirmation emails themselves. Staff found out about events through messages and spreadsheets. Reminders depended on someone remembering to send them, and post-event follow-up was inconsistent, which mattered because the group sends clients an impact report after each event, and that report is part of what brings them back.

Marketing ran separately again. Subscribers lived in three Mailchimp audiences, with no link to the bookings in Salesforce. The marketing team could not see who had just run an event, and sales could not see who had engaged with a newsletter. Every campaign meant exporting lists and hoping the consent status was still right.

The cost was not only time. Every manual step was a chance for a client to receive the wrong brand, a facilitator to miss an event or a past client to be emailed after unsubscribing, and each of those mistakes lands on a business that sells experiences.

The brief had two phases: automate the event lifecycle in Sales Cloud first, then bring marketing onto the same platform without losing a single subscriber's consent.

## What we built in Phase 1: the event lifecycle

### 01 The Book Event wizard

We built a custom Book Event wizard that supports multi-activity bookings. A coordinator chooses the brand, the client and the activities, and the wizard creates the booking and its related records in the right order with the right details. Every booking is now captured the same way, which is what makes the rest of the automation reliable.

### 02 Branded confirmations

When a booking is confirmed, Salesforce sends the confirmation email automatically, with the signature of the right one of the five brands. Clients receive a consistent, branded message within moments of the booking being made.

### 03 Staff calendar invitations

The staff assigned to the event receive calendar invitations automatically, so the team running the day sees the same plan the client does, without a coordinator forwarding details.

### 04 Reminders and post-event communication

A reminder goes out 21 days before the event. After the event, a follow-up email and an impact report go to the client. Each of these automated sends sits behind a controlled toggle, so a coordinator can hold a message when the circumstances call for a personal touch.

### 05 Tested before go-live

Phase 1 was deployed with a documented test suite, and all 21 of 21 tests passed before release. Every flow was tested against real booking scenarios across the brands.

## What we built in Phase 2: marketing on the same record

### 06 A consent-safe migration from Mailchimp

We moved three Mailchimp audiences, about 11,049 records, into Salesforce. Consent and unsubscribe status were mapped first, so no one who had opted out was ever emailed again, and every subscriber was attached to the right brand.

### 07 Branded segments, templates and journeys

In Marketing Cloud Growth we built branded segmentation, email templates and multi-step journeys, plus the scope for the newsletter campaigns each brand sends. Because the journeys read the same records as the booking process, marketing can now speak to a client based on the events they have actually run.

### 08 Website opt-in and journey corrections

Website opt-ins were connected so new subscribers enter the right journey for their brand. During acceptance we corrected journey membership where the first rules did not match how the brands wanted to communicate, and the customer confirmed the flows for each brand before Phase 2 was signed off as complete.

## A booking, followed from start to finish

Take a typical booking. A corporate client calls to book an event for its sales team: a morning activity, lunch and an afternoon challenge, run under one of the group's brands. The coordinator opens the Book Event wizard, selects the brand and the client, and adds each activity with its timing and requirements. The wizard creates the booking and its related records in one pass, so nothing depends on the coordinator remembering the order.

As soon as the booking is confirmed, the client receives a confirmation email signed by the right brand, and the facilitators assigned to each activity receive calendar invitations with the details they need. Nobody has to forward anything.

Twenty-one days before the event, the reminder goes out automatically. It gives the client time to confirm the final details while there is still room to change the plan, and any changes are recorded on the same booking the staff are working from.

After the event, the follow-up email thanks the client and the impact report shows what the day achieved. If something on the day did not go to plan, the coordinator can switch the automated send off and call the client personally first. Either way, the outcome is recorded.

From then on, the client is part of the brand's marketing audience in Marketing Cloud Growth, with their consent status intact. The journeys they receive reflect the event they have just run, so the next message they get is relevant rather than generic. When they come back to book again, the coordinator sees their whole history on one record: past events, emails received and engagement.

That is the practical meaning of connecting booking to marketing. It is not one big feature. It is a series of small, reliable steps, each one triggered by the step before it, so the client experiences one organized company rather than five brands and a mailing tool.

## How we delivered it, end to end

**Lifecycle first, marketing second.** Automating bookings before marketing meant that by the time the journeys were built, the customer data underneath them was consistent.

**Brand as a rule, not a copy.** Rather than duplicating each automation five times, the brand on the booking decides the signature, template and journey. Adding or changing a brand is a configuration change.

**Tests as acceptance criteria.** Phase 1 shipped against a written test suite. The same approach carried into Phase 2, where each brand's journeys were confirmed by the customer before sign-off.

**Consent mapped before contacts.** The migration plan started with consent and unsubscribe rules, because a marketing migration that loses consent creates a legal and reputational problem bigger than the one it solves.

## The decisions that mattered

**A wizard over a form.** Multi-activity events are complex. A guided wizard took the complexity away from coordinators and made the data consistent at the source.

**Automation with toggles.** Fully automatic post-event emails are efficient until an event goes wrong. Toggles keep the efficiency and give people the final say.

**Growth edition on the core platform.** Keeping marketing on the same platform as sales and events made one customer profile possible without an integration to maintain.

## What changed

| Area | Before | After |
| --- | --- | --- |
| Booking | Records created by hand | Guided Book Event wizard for multi-activity events |
| Confirmations | Written individually | Branded confirmations sent automatically for five brands |
| Staff briefing | Forwarded messages | Calendar invitations from the booking |
| Reminders and impact reports | Sent when remembered | 21-day reminders and post-event emails with send toggles |
| Subscribers | Three disconnected Mailchimp audiences | About 11,049 records in Salesforce with consent preserved |
| Marketing | Exports and manual lists | Branded segments, templates and journeys on the same record |

## What we would tell an events business starting this

Capture every booking the same way first. Everything good that follows, from confirmations to impact reports to targeted marketing, depends on it. Then treat consent as the first field you migrate, keep a human switch on the messages that matter most, and test your automation the way you would test software. The result is a business where the client hears from the right brand at the right moment, every time.

## Questions

### Why build a custom booking wizard instead of using standard screens?

A single event can include several activities, each with its own details, staff and timing, across five brands. Standard record screens would have meant several records created by hand in the right order. The wizard guides a coordinator through one booking and creates everything consistently, which is what every downstream automation relies on.

### How were the Mailchimp subscribers moved safely?

Three Mailchimp audiences, about 11,000 records, were mapped into Salesforce with their consent and unsubscribe status preserved. Website opt-ins were connected so new subscribers join the right journeys, and journey membership was corrected where the first mappings did not match the brand rules.

### Why Marketing Cloud Growth?

The group needed branded email, segmentation and multi-step journeys on the same customer record its sales and events teams use. Marketing Cloud Growth runs on the Salesforce platform, so a booking, a past event and a newsletter preference are all part of one profile.

---

SynconAI. https://synconai.com/case-studies/corporate-events-booking-to-marketing-journeys