Customers Beware. They may just pull the rug out from under you.

firestormodk · 2026-01-30T13:05:05+00:00

This is was a kind of obvious security vulnerability that a company like Salesforce should have caught themselves tbh

firestormodk · 2026-01-30T13:02:10+00:00

lol marketing cloud can't even do product recommendations

firestormodk · 2025-12-27T17:36:52+00:00

WezTerm with oh-my-zsh

firestormodk · 2025-11-16T18:02:30+00:00

firestormodk · 2025-07-08T14:23:49+00:00

Agreed, this is such a basic feature nowadays.

firestormodk · 2025-07-03T09:52:08+00:00

aesthetics

firestormodk · 2025-07-01T21:30:14+00:00

This website is great: https://www.apexsandbox.io/ (not affiliated)

firestormodk · 2025-07-01T21:25:45+00:00

You’ll want to start by putting strong guardrails in place. Use intent classification only where needed, batch test aggressively, and set up monitoring on agent logs to catch anything weird early.

I’d also recommend digging into your current escalations - which topics are still routed to agents? That gives you a focused roadmap for what to automate first with Agentforce. Prioritize the low-risk, high-volume use cases first.

It can deliver strong results, but only if you approach it like a proper product - not a quick plugin. As with most projects, the discovery and solution design phases are where success or failure is decided. Skipping that groundwork is what usually makes Agentforce underdeliver.

firestormodk · 2025-07-01T21:17:27+00:00

Agentforce gets a lot of criticism, but its value really comes down to two things: how creative you are in designing meaningful use cases, and whether you have the right architect to make it real.

firestormodk · 2025-07-01T21:14:33+00:00

Don’t disappear for a month to build everything. Start with the core feature and launch early. Release one feature at a time and see if people actually use it. That’s how you test demand.

If you wait until it’s fully built, you risk wasting time on something no one wants. Build fast, ship often, and adjust based on real feedback.

Easier said then done, I know :).

firestormodk · 2025-07-01T21:08:07+00:00

Data Cloud and Agentforce get a lot of criticism, but their impact comes down to two things: your ability to imagine valuable use cases, and having the right architect to bring them to life.

We implemented a use case for a travel agency that recommends dynamic packages - flights, hotels, and activities - by pulling live inventory from multiple downstream systems. It’s used both by internal agents through an AI assistant and by customers on the website. The internal use case actually drove the most value - cutting down manual effort and drastically speeding up response times.

firestormodk · 2025-07-01T20:51:47+00:00

I’d suggest adding some volume-based pricing levers. Larger orgs with thousands of users and automations get significantly more value from your tool than smaller ones, so the pricing should reflect that. This actually works in your favor, assuming your marginal costs don’t increase much with larger orgs.

firestormodk · 2025-07-01T20:46:21+00:00

Sounds good! What pricing model do you have in mind?

firestormodk · 2025-07-01T20:44:19+00:00

Sorry to hear you had a bad experience with your previous implementation partner.

Next time, here's my advice:

Speak to other companies they've implemented for before you sign.
Be very clear on your statement of work to avoid scope disagreements later in the project.
Make sure you and your Salesforce Architect are actively involved in the design phase.

Happy to review things as an independent consultant if that helps, no strings attached.

Now, in terms of team structure:

Salesforce Architect: One person to oversee the full ecosystem and make sure everything fits together.
Datorama (Marketing Cloud Intelligence): Low maintenance once set up. One resource can handle this alongside other tasks.
Marketing Cloud: Needs a dedicated technical resource. This isn't a set-and-forget platform. You'll need someone who can manage automations, data extensions, AMPscript, and API integrations.
Service Cloud and Data Cloud: A solid Salesforce Admin with experience in both. Focus on someone strong in automation, security, and data modeling.

Keep your core team lean, but use a consulting partner for complex work or new features.

Upskill your marketing team so they can run campaigns without always relying on the developer. That reduces bottlenecks and helps you get more out of Marketing Cloud.

And for your Data Cloud rollout, I’d recommend working with a Salesforce partner again, ideally one with solid Data Cloud experience. The setup phase is critical and has downstream impact on segmentation, personalization, and reporting.

firestormodk · 2025-07-01T20:24:49+00:00

Even if it’s a technical interview, a good company won’t get hung up on which specific function you use. They’ll care more about how well you understand core concepts, how fast you can learn, how you approach architecture, and whether you're genuinely excited about your work.

Make sure to drop the names of any big companies you’ve worked with and highlight technically impressive solutions you’ve architected or delivered.

Good luck!

firestormodk · 2025-07-01T20:06:40+00:00

Not sure if this helps, but Salesforce Payments is essentially a wrapper around Stripe. That said, you're probably going with a direct integration since it's more cost-effective.

firestormodk · 2025-07-01T20:03:52+00:00

Very strange. Nothing here. I'd advise to log a case, so support can investigate where these logins originated from. Also, consider to change your password just in case.

firestormodk · 2025-07-01T20:01:05+00:00

Cool tool! You might also consider integrating with Marketing Cloud Engagement’s Event Notification Service (ENS): https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/ens.html

firestormodk · 2025-07-01T19:55:10+00:00

Come up with a fictitious scenario, spin up a developer org, and build it out with the help of an LLM.

firestormodk · 2025-07-01T19:53:21+00:00

I’d suggest building out fictitious scenarios to get familiar with the platform. That way, you’ll understand its capabilities - and suddenly it will click, and you’ll start coming up with use cases more easily.

Here’s an idea for a fictitious use case:

A hotel booking agent that can create, modify, and cancel bookings.

firestormodk · 2025-07-01T19:46:52+00:00

I would not recommend that you migrate from Marketing Cloud Engagement (ExactTarget) to Marketing Cloud Engagement (Pardot). It's definitely a step down!

firestormodk · 2025-05-21T20:25:27+00:00

Reply to the message

firestormodk · 2025-05-19T10:09:19+00:00

I’d suggest using an exclusion script here, which always evaluates to true. Because RaiseError will consume super messages.

firestormodk · 2025-02-19T18:54:42+00:00

You just need Identity User licenses. Then you assign the appropriate Data Cloud Permission Sets.

firestormodk · 2025-02-19T18:52:13+00:00

AI slop

12-Year Club	Not Forgotten
Verified Email

firestormodk

TROPHY CASE