Mehmet Orun

A couple of months ago, I shared with you my initial impressions of Salesforce Headless Data 360: First Look and my sense that the agentic interface has real potential to change how Data 360 implementations are approached. I also promised a follow-up, and I’ll be honest – day 2 was more interesting than day 1, for reasons I didn’t fully anticipate. While day 1 was about capability exploration, day 2 was about attempting something real.

We’re in one of those rare moments when technology, process, and organizational ambition converge. Everywhere I look on LinkedIn, I see two dominant camps: Those excited about the possibilities of agentic AI (for example, Agentforce-style solutions) and the transformational potential it offers. Those urging caution, reminding us of the many “too early” technologies and unfulfilled promises of past innovation waves.

A lot of Salesforce professionals at the moment are still navigating the complexities of agentic AI and how to adopt it by learning from both the past and the present. As I was catching up on recent Trailhead content, which included modules that distinguished chatbots from agentic service, I found myself reflecting on how familiar these concepts felt – not just theoretically, but personally. The timing was uncanny.