The Hidden Work You’re Doing That Isn’t in Your Job Description

How to design a better operating model that doesn't bog your marketing efforts

Why does launching a simple promotion take weeks?

Why do guests still ask, “Where’s my free play?”

Why do reports never match across systems?

Why does marketing feel like the clean-up crew for everyone else’s technology decisions?

If these questions sound familiar, the problem isn’t your team. It’s the invisible role hospitality marketers have been forced into: accidental system integrator .

Why Does Every Promotion Feel Like a Systems Project?

Most hospitality tech stacks were assembled one department at a time. Loyalty bought a points engine. Hotel operations bought a PMS. Casino operations bought a player system. Marketing added a CRM later.

Each system works well on its own. None were designed to own the entire guest journey.

So when marketing launches a promotion that touches eligibility, communication, redemption, and reporting, the work spills across systems. The integration does not exist, so people fill the gap.

That work does not show up in job descriptions, project plans, or timelines. But it shows up everywhere else.

Where Is the Work Actually Breaking Down?

Let’s take one real, common example: a promotional credit tied to a special event.

• The offer is defined in the loyalty system.
• The invitation is sent through marketing automation.
• Attendance is tracked separately by events or casino ops.
• The credit is loaded later, sometimes manually.
• Customer service fields the calls when something fails.

Marketing becomes the hub. You reconcile lists. You confirm eligibility. You chase down missing credits. You explain to guests why the system did not behave the way the message promised.

The cost is not just time. It's trust. It's customer experience.

When a guest shows up for a promotion and the system cannot confirm their status in real time, the experience feels broken. When a marketer cannot see whether a credit actually landed, or they have to look in 3 systems to figure out if the customer is in the event, reporting becomes defensive instead of insightful.

What Does This Broken Structure Really Cost You?

Speed is the obvious loss. Campaigns that should take days take weeks.

Accuracy suffers next. Double entry creates mismatches. One system says a guest qualified. Another says they did not.

Then comes the hidden cost: organizational drag . Senior marketers spend time validating mechanics instead of designing strategy. Teams stop pushing creative ideas because setup feels risky. Innovation slows because failure is expensive.

None of this shows up in a budget line item, but everyone feels it.

What Does “Better” Actually Look Like in Practice?

Better does not mean buying more tools. It means designing workflows where systems share responsibility.

A concrete example that exists today is the integration between Oracle OPERA PMS and Salesforce Marketing Cloud when implemented correctly.

In a well-designed workflow:

• Guest eligibility is defined once and passed downstream.
• The CRM knows, in near real time, whether a guest checked in, attended, or redeemed.
• Marketing messages reference actual system status, not assumptions.
• Frontline teams can see promotion state without calling marketing.
• Reporting ties message, action, and outcome together without manual reconciliation.

Operationally, this means fewer spreadsheets, fewer handoffs, and fewer “can you double-check this for me?” moments. It means fewer bottlenecks around that one employee who seems to have their finger on the pulse (read: institutional knowledge is between their ears, not in a system.) Strategically, it means marketing can focus on behavior change, not damage control.

Who Should Own This Work—and Why Isn’t It Marketing?

The uncomfortable truth is that marketing absorbed this role because it was flexible enough to do so, and because it was the main stakeholder. It's left holding the bag if the thing doesn't work. That does not make it correct.

Ownership should live with the guest journey , not individual systems. Integration should be treated as ongoing infrastructure, not a one-time IT project. Marketing should help define requirements, not be responsible for stitching execution together.

Is guest journey an ownership track in your IT division? How does IT collect feedback on it, arrive at solutions, implement, and learn? (And is it working?)

If you're not happy with the answer to these questions, that's normal. Start simple: with just one journey (e.g. A guest books a room promotion.) Assign a BA to map the process, talking to whomever owns each piece. Have them sniff for double-entry, one job requiring multiple tools, guest confusion, employee frustration. From here, the solutions often become obvious, and you can start picking off new integration points you want to build that get you the most bang for your buck.