Salesforce MVP Hall of Fame · Certified Partner since 2010
Marketing Cloud journeys, once the profile can carry them.
Marketing Cloud is the send stack. We implement journeys after the customer profile and consent can support them. The first week is in the org, reading what already exists.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
In the org
What this cloud is actually for.
Marketing Cloud is the send stack across email, mobile, social, and web. We implement journeys after your customer profile and consent can support them, because a journey on a list your branch does not recognise is still a blast. Your team owns the journeys after handover.
Who this is for
The desks that live here.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Architecture
Where this cloud sits in your agent architecture.
A journey is only as good as the profile behind it, and the consent on the write.
Questions
What we actually say.
- Can you “turn on” Marketing Cloud without a customer profile?
- You can send. You should not. We connect journeys to a profile the branch already trusts, or we tell you the send is still a blast list.
- Do you implement WhatsApp and SMS?
- When the clinic or the desk already uses that channel. We do not invent a channel the customer does not open.
- Is this the same as Pardot?
- No. Marketing Cloud is the send stack across channels. Pardot is the B2B marketing desk. We will say which the process actually is.
The brief
Send the situation.
Name the cloud. Name the week.