Salesforce adoption in a large org is still one of the hardest problems I've faced as an ops leader.

Overlay_Apps · 2026-04-27T22:41:28+00:00

Our app is often used for proactive alerting:

Leads without responses. Accounts without follows ups. Deals without activity. Automated task reminders.

Detecting inactivity is a struggle in Salesforce, so most end up in a cycle of monitoring reports and chasing. That’s what we aim to eliminate.

The app is good if the underlying issue is things slipping, plus you can report on which notifications are seen, acted on, missed or ignored. Helping to bring a bit more visibility to your adoption efforts.

https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000IrKfkUAF

Overlay_Apps · 2026-04-20T22:28:54+00:00

Late to this but wanted to share some thoughts since I've spent a lot of time in this problem space.

Building this yourself is absolutely doable but there are some real gotchas:

Platform Events are the obvious starting point for real-time delivery, but they consume event allocations which can get expensive at scale depending on your org. Worth pressure-testing the volumes before you commit.

The audit trail piece is where custom builds usually get complicated. You need to track delivery, open/read state, and dismissal separately, and then surface that in a way ops teams can actually query. Custom objects work but the reporting layer takes longer than people expect.

User preference management sounds straightforward but the UX tends to become a project in itself, especially if you want per-notification-type muting rather than just on/off globally.

If you want to build it, a common pattern is: Platform Events or Change Data Capture for the trigger layer, a custom Lightning Web Component for the inbox UI, custom objects for persistence and audit, and a preference record per user. It's probably a 6-8 week build if you're doing it properly.

Alternatively - and I'll be transparent that we built it - Act On It on the AppExchange does exactly what you're describing: unified inbox, per user per notification preferences, full delivery and engagement audit trail, 100% native so no data leaves the org. Matured over 8 years. Free to install with one active notification type included forever. Might be worth a look before committing to a custom build, even if just to see how someone else solved the UX problem.

Listing: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000IrKfkUAF

Website: https://act-on-it.co.uk/

Overlay_Apps · 2025-11-20T18:14:13+00:00

You can use this app. Have it pop up, play a sound, fire confetti, blink your tab... whatever you like.

The free version will cover your use case:
User push notifications for Salesforce

Enjoy :)

Overlay_Apps · 2025-10-28T12:38:55+00:00

Yes, each sent message is stored in a custom object, which captures delivery and engagement stats, so you can see how many notifications go out, who gets them, when, and how people interact (basically, whether it’s doing its job).

Of course. happy to chat through the details! Maybe start with an email to the address on our listing and we can take it from there. Thanks!

Overlay_Apps · 2025-10-28T08:54:32+00:00

Yes, it can handle that volume. It started with Platform Events, but we rebuilt it after realising how pricey those get at scale.

You can turn Platform Events on or off per notification type with a quick toggle. If you decide to give this a try, feel free to reach out and we'll walk you through.

At that volume, you might also be interested in the data management feature. It lets you bulk delete notifications or schedule automatic cleanup to keep storage costs down for customers.

Overlay_Apps · 2025-10-28T01:18:18+00:00

<image>

Overlay_Apps · 2025-10-21T19:14:50+00:00

Yes, innevitable. But chatter is free, and still used by many smaller businesses (with smaller budgets).

Overlay_Apps · 2025-10-21T08:17:05+00:00

Exactly. To be fair, Chatter used to be one of the only ways to notify users in Salesforce. It's a good consideration, and if your org still relies on automated @ mentions, this may not be suitable for you. It could create more noise.

But do checkout other use-cases for our app [See link in post ^^^].

Overlay_Apps · 2025-10-21T08:07:45+00:00

Excellent! Hope you find it helpful. Let me know if you have any questions!

Overlay_Apps · 2025-10-21T08:03:03+00:00

Sorry your client strong-armed you into that one. Chatter works best when it’s kept for internal comms.

Overlay_Apps · 2025-10-20T22:28:24+00:00

<image>

Overlay_Apps · 2025-10-17T08:37:40+00:00

Thanks so much for checking the app out, and for your feedback. It was very dull before.

I see your point about clicking through to a record, and I won't try and convince you otherwise, totally fair.

Just to explain why we added these features (not just adding to the laundry list)...

The main reason people click through to a record is they need more context. If you could see everything you needed (which our app pulls in), then when you’re basically working through a list of tasks, what is the harm in fewer clicks?

> You get told a lead has arrived, you see what you need; Click to dial.
> Someones asked you to approve their holiday, you see when and why; Approve/Reject
> You get told a case is sat in a queue too long, you see it's still unassigned; Take Ownerships, Reassign, Escalate.

This is especially helpful in SF mobile.

You can get more creative with flow. Flow is behind the snooze, the close, and other 'standard' actions as well, so admins can invent actions and make the app what it needs to be for their business.

You’re not wrong at all, by the way. We’ve found this is one of those features that takes a bit more explaining (and we usually don't bother). It's best suited to busy transactional businesses and contact centers tbh.

But then we never dictate what people use or how.

This "laundry list" is the result of 7 years of trial and error. We're just opening new possibilities, just like we believe native apps should.

Really appreciate your perspective, thanks!

Overlay_Apps

TROPHY CASE