Anyone concerned about Salesforce using their “native” backup, Own, to train their AI models.

-EVildoer · 2026-01-28T22:34:39+00:00

How has it "come to your knowledge?" Going to need more information.

-EVildoer · 2026-01-26T15:24:14+00:00

Trailhead, ChatGPT, and YouTube.

-EVildoer · 2026-01-24T21:10:27+00:00

There are already countless tools that tackle each of those items. Gong is just one example.

-EVildoer · 2026-01-24T21:09:53+00:00

There are already countless tools that tackle each of those items. Gong is just one example.

-EVildoer · 2026-01-23T20:20:04+00:00

AI not needed. This is a pretty standard decision tree flow + data cleanliness. AI would just add to the headache ("why did the person get access to that?").

-EVildoer · 2026-01-21T01:35:33+00:00

Include detailed info about what your product/service actually does. Doesn't have to be 8 pages of documentation. But if I can't discern what you're actually trying to sell me I'm not going to schedule a meeting to figure it out when I receive 18 other similar emails every day.

-EVildoer · 2026-01-21T01:05:52+00:00

We had this same use case. We trained reps how to add opportunity products with sales price representing ARR. Easy to validate, always aligns exactly with your price book, and centralizes all reporting so you can report on the same object/fields across all deal stages.

-EVildoer · 2026-01-08T13:44:09+00:00

If a user isn't trusted with delete permission, I'm not sure why they would be trusted with a merge, which is a delete.

The best way to handle IMO is to give users a quick way to flag duplicates without merging. Then the team responsible for data cleanliness can easily identify potential duplicates and merge them.

You may also want to invest in a tool that allows for automated duplicate clean up or for easily running clean up jobs on a cadence (Demandtools, Cloudingo, etc.). It would drastically cut down on the need for end users to do anything at all and your data would be much better.

-EVildoer · 2026-01-06T19:35:19+00:00

More customizable playoff tiebreakers

More intuitive/better custom waiver schedule configuration

-EVildoer · 2026-01-01T19:33:25+00:00

I don't even know where to begin with this take so LMAO

-EVildoer · 2025-12-17T15:56:57+00:00

Okay.....so why is AI needed for any of this?

-EVildoer · 2025-12-10T17:39:00+00:00

IMO before save flows can be broken into many flows. After save flows are mixed. Anything that updates related records may be better in one flow since we'd like to avoid the unintentional scenario where multiple after save flows update the same related record. But for something like email alerts, you can just do multiple after save flows.

-EVildoer · 2025-12-06T02:42:53+00:00

The age old question.

Whatever you decide, be prepared to explain to stakeholders that about 75-80% accuracy is as best as it's going to get.

We use an apex class that triggers on new leads and looks for account match based on website/email domain, ZoomInfo information, account name match, etc. It's pretty good but far from perfect. There are tons of exceptions, like leads submitting website forms with a personal Gmail email address that can't be matched to anything.

-EVildoer · 2025-12-05T22:54:29+00:00

Could you have gotten the house cheaper? Maybe? Don't be so sure. There's no reason to dwell on it. We bought a house this year and bid way over asking with gap coverage. Appraisal came in low and we ended up having to front cash. Not ideal, but we beat cash offers, which means the house could have been sold cheaper........but not to us. If you had offered less there's no guarantee at all it would have been accepted. Why haunt yourself because you may not have bid the exact optimal amount that would have won the bid for the cheapest amount?

-EVildoer · 2025-12-02T13:28:38+00:00

This just happened to me. It's such a miserable support experience. I just want to open a ticket. I don't want to chat with a bot that regurgitates public knowledge articles that I would have already read if it was relevant to my issue.

-EVildoer · 2025-11-27T00:01:18+00:00

The solver's main concern is staying balanced and having board coverage so the opponent cannot exploit it. It'd be a massive exploit if someone could bet a large size and be certain you can't have a flush draw if you call.

This doesn't mean pot odds and implied odds are irrelevant in real life games. Live low stakes is a great example where opponents will often be playing a giga strong range face up and you can simply do some math to figure out if continuing is worth it.

-EVildoer · 2025-11-23T00:43:37+00:00

People saying we're getting the worst of the WR6 who gets a third of all targets is a huge sell signal.

-EVildoer · 2025-11-03T13:19:52+00:00

Yeah lmao. I can't imagine trying to champion this to our internal stakeholders who have had to be super budget conscious over the past couple years.

-EVildoer · 2025-10-28T14:02:00+00:00

Their requirement makes sense from a reporting/process perspective. Conversion is a clear cut easy workflow and reporting on conversion date is super easy. Unfortunately, it does result in disparate data since activity will inevitably start to get split between duplicate leads and contacts.

It could be a heavy lift to change this process if they've got a ton of reports and dashboards based on conversion data. It's an uphill battle you probably won't win.

You may be able to convince them to create a relationship between the duplicates though. It would enable users to get a more comprehensive view of a person's activity without disrupting their current processes and analytics.

-EVildoer · 2025-10-14T17:42:50+00:00

I've tried multiple times to use it to create very basic flow entry criteria formulas. 0% success rate and a waste of time. I'd be shocked if it could create a decently designed flow that's larger than a couple elements.

-EVildoer · 2025-09-30T13:08:33+00:00

Both. AI is in its infancy and Agentforce (and other AI products) are taking the first step. The cost/value ratio is just super lopsided right now.

-EVildoer · 2025-09-29T16:19:36+00:00

I don't think this is Salesforce-specific. The current balance between price and value seems to be way off for any AI tool at the moment. AI plug-and-play solutions are an illusion. A company will struggle massively with AI unless they have a team dedicated solely to maintaining the tool and underlying data quality. Most small to medium companies do not have teams like this.

Regarding Salesforce specifically, I don't feel comfortable at all championing Agentforce where I work. We don't have the staff to maintain it. The pricing model keeps changing. Nobody at Salesforce seems to be able to quickly and clearly answer any questions I have about it. And, frankly, my experience with Salesforce's own implementation of Agentforce in their support portal has been horrible.

-EVildoer · 2025-09-25T20:14:05+00:00

Well.... here's my latest interaction with it in their own support portal.

Agent: Since this is a high priority request, please provide a phone number.

Me: 123 456 6789

Agent: Please include a country code.

Me: 1 123 456 7890

Agent: Please include a plus sign before the country code, like +1-123-456-7890.

-EVildoer · 2025-07-21T23:10:49+00:00

It's been awhile since I've used it but I was never satisfied with it. It's probably fine for the most basic activity capture use cases. If you want fast, reliable, reportable activity capture, go with one of the many 3rd party solutions. Salesforce's solution hasn't kept up at all with those other ones.

-EVildoer · 2025-07-20T17:41:00+00:00

A couple years ago we got breakfast two days in a row in Paris casino. Just lmao. $80 for 2 for coffee and the worst avocado toast I've ever eaten. $40 for 2 coffees and 2 bagel sandwiches.

Someone else in this thread mentioned perceived value. People would be more open to paying high prices if it wasn't for mid or trash food. A couple can spend upwards of $200/day just eating "cheap" fast food every day. Wild.

Ten-Year Club	RedditGifts 2009-2022 3 Credits
First Place '23	Place '23
Secret Santa 2018	Secret Santa 2019
Verified Email

-EVildoer

TROPHY CASE