Today on the Salesforce Admins Podcast, we talk to Khushwant Singh, SVP, Product Management at Salesforce. Join us as we talk about his role heading up all things Experience—not just Experience Cloud but Experience Services, too.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Khushwant.
Khushwant, AKA “Khush”, heads up Experience at Salesforce. If that term is a little nebulous to you, you’re not alone, but Khush breaks it down for us. Experience Services brings a few teams together: the UI Platform team, the Experience Cloud team, the Mobile team, and the Mobify team. “We’re responsible for all things Experience, and it helps us build a common product strategy across the board,” Khush says, “whether you’re building an experience for an employee, a customer, or partner.”
Lightning Experience has really changed the game for admins in terms of stepping up in their thinking about design, but Khush points out there’s also a bit of a divide there. “If you build a component for the App Builder, it may or may not work in the Experience Builder,” he says, “but as a Salesforce Admin or Developer, you want your investments to go across all of your various endpoints.”
Experience Cloud is a very flexible tool that you should really look into if you haven’t yet. You can use it to build out a simple marketing website, a self-service destination like a help center or account management site, or even a channel reselling portal or commerce storefront.
While Lightning and Aura have done a lot to enable admins to build out things they never thought possible with low code and fast time to market, Khush admits we seem to have hit a wall from a performance, scale, and customizability point of view. To address that, they’ve been re-architecting to let you build new things more easily at a consumer-grade scale.
One thing that will be going live soon (forward looking statement) is a major performance boost to public-facing apps and sites. They’ve revamped the out-of-the-box CDN (Content Delivery Network) to allow public aspects of your site and mobile apps to be cached at endpoints closer to the consumer, enabling much faster delivery. One other change is adding dynamic image resizing so the same image looks equally good on mobile, desktop, and tablet. The best part is these and many more improvements are enabled by default, so you get the performance boost without having to lift a finger.
Looking forward, Khush and his team are revamping the Salesforce Content Management System (CMS) to make it more robust, powerful, and responsive. They’re breaking down the barriers and rolling out the advanced version of Salesforce CMS to all customers for free, and you can get access to the new-and-improved JSON-based CMS 2.0 beta with an opt-in.
Khush also gives a preview into what he and his team are working on to make improvements to data to, for example, bring Dynamic Forms to all standard objects, and even more goodies for desktop, mobile, and everything in between. Make sure you listen to the full episode to hear what’s coming your way soon.
Gillian Bruce: Welcome to the Salesforce Admins Podcast, where we talk about product, community and careers to help you be an awesome admin. I’m your host today, Gillian Bruce, and we have a really fun episode lined up for you. We are talking with Khushwant Singh, AKA Kush, who’s SVP of Product Management here at Salesforce, in charge of all things Experience. And I mean all things Experience, not just Experience Cloud, but Experience Services. And if you’re wondering what all that means, don’t worry, he’s going to answer that for you. So without further ado, let’s get Kush on the pod. Kush, welcome to the podcast.
Khushwant Singh: Thank you, Gillian.
Gillian Bruce: It’s wonderful to have you on. I am very much looking forward to our discussion because we are talking about something that might be a little nebulous to some of us, especially if you’ve been in the Salesforce ecosystem for a while. We have Experience Eloud, Experience Services, Experience all the things. Kush, clarify for us what all of that means.
Khushwant Singh: Well, Gillian, I wish I got that question, or rather I wish I had proactively answered that question at the recent TDX. So just a bit of a sidetrack, a little, for those of you who attended the recent TDX, we had a true to the call session where a few of us were up on stage and I introduced myself as, “My name’s Kush, I’m a product manager and I work on all things experiences.” Now, I honestly thought that I would be inundated with questions, but I realized that I actually got zero questions, and I realized that people just probably didn’t get what all things experience means. So I’m going to learn from that, and be very clear in our conversation over here. So taking a step back, when we say, we just recently realigned some of our teams internally, and we’ve created this group internally called Experience Services. And what Experience Services is, is that it brings together a few teams together.
First and foremost, we have our UI platform team. And so from a UI platform perspective, think of it as all things web runtime, whether it’s Aura, Lightning Web Runtime, LWC or Lightning Web Components. It includes things that all of the good components you have in Lex, so the record forms, lists, performance, et cetera, so that’s the UI platform team. Then we also brought the experience cloud team, which really is, takes all the goodness that we have in Lex, and manifests it to customers and partners, external facing customers and partners. We do have instances where it’s also facing employees as employee intranets, but it takes all of that goodness. We also brought together our mobile teams. So whether that’s the Salesforce Flagship mobile app, whether that’s our mobile SDK, whether that’s taking an experience cloud side and creating a hybrid mobile app out of it through Mobile Publisher, we brought the mobile team together as well.
And then finally, we brought the MobiFi team, which some of you may know as the managed runtime offering to build out these progressive web apps for commercial use cases. So in a nutshell, this Experience Services team brings together the UI platform, brings together experience cloud, brings together the mobile teams and brings MobiFi together. So what we can do now is collectively, we are responsible for all things experiences, and it helps us build a common product strategy across the board, whether you’re building an experience for an employee, a customer, or a partner for that matter.
Gillian Bruce: So that was really helpful, it helped me understand this because again, experience is one of those words that, especially as a Salesforce admin, we’re always thinking about our end users experience. That’s our whole goal is to make it seamless and make it really useful. But as you just described, experiences is so many things. And I really appreciate that you have explained how the teams are uniting under this umbrella, to really think about the holistic picture when it comes to these different experiences pieces. UI, designers’ mindset, is one of the core admin skills that we have because it’s always thinking about how is my user experience in this? How can I maximize that experience, make it more efficient? And when you talk about Lightning experience that, God, talk about something that changed the game for admins.
Khushwant Singh: I know, it did. It did entirely. It changed the game, but it also in full transparency, we added a bit of a divide as well. So if you take examples where you build a component for the App Builder, it may or may not work in the Experience Builder. You have a set of record components that look gloriously well on Lex, but they may not surface all of the capabilities, the actions don’t surface in the Experience Builder or vice versa, the branding, the themeing, the mobile web responsiveness aspect of things that show up on Experience Builder, don’t show up in the App Builder side of things. And so we have introduced this divide, which actually has made our… Well, each team has done a phenomenal job in going deep in their use cases, it’s been at an expense of a divide where, as a Salesforce admin, as a Salesforce developer, you want your investments to go across all of your various endpoints. You might be a Salesforce admin for a company that is using Salesforce for their employee experience. For example, the service agents.
Similarly, within your same company, you may have an endpoint, a customer help center, which is customer facing, or you might be selling products through channels, which is also partner facing, and you want your investments to be able to run across ideally. So again, all teams have done great in their specific areas, but by bringing us together, we are really hopeful that we can deliver more value for our Salesforce admins and our developers as they manage all of these various endpoints.
Gillian Bruce: Yeah. I think as a company, for someone who’s maybe been in the ecosystem for a long time, this is a familiar road, is that we develop something really close. One team goes down and develops this new way of doing something and then we have shadow examples of it happening all separately within the company. And then, hey, let’s bring everybody together, let’s make this a more cohesive, holistic experience for our admins, for our developers. And it’s exciting to bring all those really smart brains together to work together versus everyone working in a silo.
Khushwant Singh: Indeed. And I think it’s also indicative of trying to complete what we start. I think we’ve heard from admins, just this recent TDX, I mean, and at every TDX or any Dreamforce we do, any through the core session or any feedback we get from our MVPs and our admins out there, developers. They’ll give us feedback, which is actually quite true. We start something, but we don’t complete it. We say something that we will deliver something, but we, at times, don’t deliver it. And so I think by bringing all of our teams together, that manage experience, I think it really… Organizational differences should not be the reason why we are not able to complete what we start or deliver what we say we will deliver. And so we are really hopeful that we’ll be able to actually address those two key areas.
Gillian Bruce: Yeah. I’ve always heard the joke. We don’t want to let our org chart show.
Khushwant Singh: Exactly. Across both desktop and mobile for that matter.
Gillian Bruce: Totally. Yeah. So Kush, before we get a little bit further, I mean, clearly you’ve got a big undertaking that you and your teams are doing. Can you tell me a little bit about you and how you got here? How long have you been at Salesforce because all of these works have been in progress for a long time. You mentioned when we released Lightning experience. Tell me a little bit about your background.
Khushwant Singh: Oh yeah, sure. So I’ve been at Salesforce, I think, May sometime this month is my seventh year anniversary.
Gillian Bruce: Congratulations.
Khushwant Singh: Thank you. And I have truly enjoyed every single day of my time here at Salesforce. If you look at my background, I rarely spend more than five to six years in a company. And the fact that I’m here for the seventh year and still super challenged, just speaks towards what Salesforce offers from a challenge, point of view. There’s always something new, there’s always a new challenge for us to work on. And I’ve actually spent probably six and a half or six and three quarters of that seven years working on Experience Cloud. And so most of my background is from a B2C side of things. I spend some time at eBay, at Microsoft, at a startup called Mozi, working on a number of B2C oriented products. And I wanted to build products in an enterprise setting for enterprise, but I didn’t want to veer too far away from the consumer side of things, the B2C side of things. And Experience Cloud really helped me walk that fine line where you’re building these digital experience products that are used by enterprises for their customers, for their partners. So it really gave me a good middle ground.
That said, Experience Cloud is a, it’s a platform upon the overall Salesforce platform. And so over the last six and a half years or so, I’ve had the opportunity to work with some immensely dedicated individuals on the platform side of things as well. And so that bring a lot of the goodness that we see in Lex and Experience Cloud and Mobile to life. And so bringing the teams together was like bringing a group of old friends together.
Gillian Bruce: I love that, getting the band back together, that’s good.
Khushwant Singh: There you go.
Gillian Bruce: Okay. So let’s talk a little bit about what’s currently going on in Experience Cloud. So I know there were some good announcements at Dreamforce last year, at DBX this year. Can you talk a little bit about where we’re currently at with Experience Cloud and why maybe an admin who hasn’t yet dabbled in Experience Cloud might consider it?
Khushwant Singh: Sure. So again, just to level set, one more time, a customer uses Experience Cloud for a number of use cases. You could use Experience Cloud to build out a simple marketing website, corporate website. You could use Experience Cloud to build out a self-service destination, so that self-service destination could be a help center, where you want to surface your knowledge base articles, where you wish to surface chat bots, where you wish to, for example, give your customers the ability to log in and manage their account, manage their profile for that matter. Similarly, you could use Experience Cloud to build out a channel reseller portal, where you may not be selling direct or you may be selling direct, but you also sell through your various channels and you need a way to manage your channels. You could use Experience Cloud to build a commerce storefront, whether it’s a B2B commerce storefront, a B2C commerce storefront, et cetera.
So Experience Cloud, you can use it for a variety of different customer facing, partner facing use cases. In fact, I should also mention employee facing use cases. You could build out a company intranet for that very matter as well. And so over the last years, last few years with introduction of Lightning and Aura, for that matter, it really revolutionized the ability for our customers to build all of this out in a very low code, fast time to market aspect of things. And we’ve seen phenomenal adoption, super humbled, by the adoption, we’ve gotten North of 70,000 odd sites. I think our MAU is around, our monthly active usage is maybe about 40 to 50 million. We have a daily active usage of about five to 6 million. And so, I mean, again, super thankful to all of the customers and the admins and the developers out there who have invested so much of their time in Experience Cloud.
That said, as with every technology, there comes a time where you’ve hit a bit of a wall and we hit a wall with Aura, from a performance, from a scale, from a customizability point of view. Where you can see that as you are trying to build out these next generation consumer grade experiences like storefronts, like websites, even these consumer grade portals, where you expect an iPhone like Experience, whether it’s employee facing or customer facing experience. So we hit a bit of a wall with Aura. And so over the last, I would say 18 months, we’ve been, for lack of a better way to put it, somewhat silent in terms of our feature deliverables. Sure, we’ve been delivering a few features here and there, but like our MVP, we have a really passionate and amazing MVP out there. His name is Phil Weinmeister-
Gillian Bruce: Yes. We know Phil very well.
Khushwant Singh: Exactly. And so I think many of you must have seen his post where he’s actually tracking the number of features that Experience Cloud launches. And he showed this bar graph, that showed the decreasing number of features over the last 18 months. And I replied to him and again, huge respect for Phil. And the fact of the matter is that we’ve had to go under the hood and rebuild from ground up using Lightning Web Runtime, using Lightning Web Components, so that we can actually deliver this consumer grade scale and performance and customizability, whether it’s a B2B, B2C or B2E type of use case. And so we’ve been “silent for a while” but I’m super excited at what’s coming in this summer release, and what’s going to go. A lot of it going to go generally available this winter release. So again, long story short, we have been re-architecting for consumer grade across the entire customer journey.
So whether you’re looking at an awareness use case, whether you’re looking for an acquisition use case, a service use case, a loyalty use case, you want to deliver consumer grade across the board. And with Lightning Web Runtime, with Lightning Web Components, we do believe that we’ve got the right foundation upon which we can actually deliver these experiences. So that’s the overarching area where we’re headed.
Gillian Bruce: I mean, that’s impressive. I mean, we talk, especially even as admins, we have our own technical that we accrue over many years of admining a specific org. And sometimes you do, you got to just go back, peel back the covers and go in and make sure everything, the foundations are updated and running better. And hey, if you got a system that’s not working for you, you got to invest the time and pause on the new stuff for a minute. Let’s make the core stuff really work and function so that we can continue to build. So I love that transparency. I think it’s really useful to help our admins and everybody understand what all of the hard work that your team is doing. And yeah, I mean, hey, now that we talked about all the hard work that you’ve all been doing, let’s talk about some of the shiny new fun things that you have coming down the page.
Khushwant Singh: Yeah, of course. So now I think on that note, I do also want to underscore that we have so many, all of that adoption stats that I talked about, they’re all visual force or mostly Aura investments. And I want to underscore that we’re not just leaving Aura or VF behind. And so there are many aspects that customers on Aura or customers on VF would also be able to benefit from. So let’s dive into those shiny aspects of things. So I think if we think of this as maybe a stack diagram, maybe we’ll start at the lowest level of infrastructure. What are we doing from an infrastructure point of view to help deliver that consumer grade type of experiences? So, first and foremost, we’ve invested a fair amount of time and effort to deliver performance. And so, one of the things you’ll start to notice is, our out of the box CDN, so behind the scenes we work with Akamai, and what that does is that it allows, it just provides customers an out of the box CDN that they can actually choose to use.
Gillian Bruce: So Kush, before we go forward, what is a CDN? Let’s break down that.
Khushwant Singh: Sure. It’s a content delivery network. What that does is it allows your public aspects of your site, of your mobile app to be cashed on these endpoints, which are closer to the consumer, and so that allows for faster delivery. And if it doesn’t change, if that public information doesn’t change very much, it’s served out of cash versus another round hub back. So again, at the end of the day, it’s about better delivery of, faster delivery of the experience. Now this used to be a bit of an opt in thing and so what we have done now is as of spring and summer and winter, what we’re doing is behind the scenes, we are rolling out as part of the secure domains effort, as secure domains is being enabled across all net new sites and existing sites. We are just enabling the default CDN by default, so it’s an opt out versus an opt in.
So from that perspective, we are trying to ensure that everyone gets a phenomenal performance from the get go. Now, similarly, another thing that we are really excited about is, and the teams working on it, is as part of the out the box, CDN from an infrastructure point of view is being able to get more capabilities out of that, out of CDN. Now, have you gone to a site where the images look really weird, wonky, feels like this is a desktop site they’re trying to throw onto a mobile or a tablet?
Gillian Bruce: Yeah. Everything’s out of perspective. And you got to try and scroll weird ways. Yeah.
Khushwant Singh: Exactly. So another thing that if you use the out of the box CDN, another thing that our customers can look forward to is dynamic image resizing. So when you are the same image renders well on a mobile, a tablet, a desktop, and similarly, if you are an admin, you may inadvertently upload a, I don’t know what? 20 MB file, image, and then say, “Look, why is my site loading so slowly?” And so what we’re trying to do is also correct that, where you may upload a 20MB file, please don’t, but what we’ll do on our side, on the CDN side of things, we’ll resize that and ensure that we are delivering a more optimized image to the customer. So that’s another thing that we are really excited about, from an infrastructure point of view. So lots of good work happening from a perf point of view.
Now, then there is scale. So from a scale point of view, we have aspects like concurrency. So concurrent user scale, so how many users can you support on that portal? Concurrent read scale, so how many requests are coming in concurrently? And before the site just says, “Look I can’t handle this.” And concurrent rights. So for example, you may be running a promotion and that promotion, you may advertise that on Twitter or on Instagram, and then you suddenly have this massive surge of folks coming to your site and they all want to sign up to know when it’s going to be made available. How do we ensure that those rights don’t kneel over and just fall over? So again, a lot of the work that we are doing around infrastructure, whether it’s performance and scale, are things that we have been rolling out slowly over the last few releases. And then we really look to bring it home over the course of the summer and the winter releases, so that’s from an infrastructure point of view.
Gillian Bruce: Nice.
Khushwant Singh: Now, as we move up the stack, we can talk about things like data and content. Now, let’s start off with content Salesforce in general, has had a bit of a content management gap for a little while. And we have customers using third party content management systems, et cetera, to compliment the data investments that they have in Salesforce. Now, probably I would say 24 months back, we introduced Salesforce CMS, which was, for the very first time a content management system from Salesforce. Now, what we’ve come to realize over the 24 months is that boy, do we need a lot more improvements to it. And so over the last, I would say 18 months, we have been actually re-architecting the content management system from ground up. It is going to be JSON based. So very standard point of view.
JSON also would allow our customers to model many different types of content, whether that content is a blog, an email et cetera. Very extensible, so from that point of view, if we don’t offer something out of the box, you can add a sidebar extension that allows you, like Grammarly that would say, “Hey, look,” while you’re typing this thing, it’s telling you, you should add X, Y, and Z, et cetera. We also, 24 months back introduced two versions of the content management system. One was a free version, included version I would say, I shouldn’t say free, the included version, and the other one was the paid version. What we realized really was, you know what, it’s just artificial. Our customers really, they’re coming to Salesforce for a variety of different use cases and content really should be something that supports and brings those use cases to life.
And so what we have done is as of the summer release, we have basically provided the paid CMS, which we have gotten rid of, and just given it, included it as part of all experienced cloud licenses. In fact there are so many licenses out there at Salesforce that use Experienced Cloud licenses. And so as of this summer, all of our customers will get the advanced version of content management. And at the same time, they will get access to the beta version of this new, what we call CMS 2.0 internally, we call that the JSON based. They’ll get beta access to that as well, without any sort of opt-in, there’s a check box, they have to check and they’ll be able to take it for a spin. But we look to make that CMS 2.0, our next version of CMS generally available in the winter timeframe as well. So that’s another massive uplift and improvement that we’re doing from a content management point of view. And democratizing content altogether.
Gillian Bruce: That’s great. I mean, I know admins are going to be very excited to be able to access that great capability without having to jump through any additional hoops to get it. So thank you.
Khushwant Singh: Exactly. Now, let’s talk about data. Now, when we think about the data side of things, this is where a lot of our investments, at least from an Experience services point of view is that we have teams that are experts in records, Dynamic Forms, lists, and they’re doing a lot of good work to expand. For example, Dynamic Forms today it’s only available in custom objects, why? It should go across all standard objects. That’s something that the team is working on. I’m really glad that we are going to stay really true to the fact that when we start something, we are going to end it and we are going to go all the way, at the same time this team is also working to bring all of that goodness across to not just employee facing experiences in Lex but also to customer facing, partner facing experiences via Experience Cloud.
And so that’s one example where, as one unit Experience Services, it really brings benefit across all of the various endpoints, whether it’s Lexio Experience Cloud or mobile for that matter. So that’s something that we are really looking forward to. And then over on top of that, the ability to surface that data, but represent it in different visualizations. So you may want to show a list view in the form of a grid or in the form of a certain set of tiles. Because again, you want to do that because it’s customer facing, it’s partner facing, you have to apply your style guide on it, et cetera. So that’s all the goodness that you can expect to see over the course of the next two releases from a data point of view.
Gillian Bruce: I mean, that’s major stuff. I know that Dynamic Forms is one of the top favorite admin feature overall. And so being able to bring that to standard objects will be huge. So thank you. Thank you on behalf of all admins everywhere.
Khushwant Singh: It’s a shout out to all of the good teams that are working on that front. So we touched about infra, we touched about content, we touched about data. Now, let’s touch about the UI run time itself, which is Lightning Web Runtime and Lightning Web Components. Clearly the degree of, out of the box components for Aura, there are a lot more out of the box components for Aura than they are for LWCs, no doubt about it. And so what we’re trying to do is we are trying to catch up to a certain degree, but catch up in a way that is addressing the most important use cases from out the box component point of view, but at the same time, not sacrificing customizability. And so from an LWR point of view, a few things to call out.
One is, I’ll start off first with, when you build a site with Experience Cloud and with LWR and LWCs, search is always a use case that comes up. And by search, we tend to just think maybe at times CRM search, but really our customers are thinking of it as site search. They want to be able to cut across whether it’s a CRM, whether it’s site meta information, like the page title, the site title, or something that’s in a text, a rich text component, whether that’s CMS content, whether those are products or any other objects, they want to be able to search the entire site.
Gillian Bruce: Yeah. They don’t know the differences between that, they just want to find what they need.
Khushwant Singh: Exactly. And so for them, this is complexity that we should abstract from them. And so again, this is something that our customers can expect to see in beta, in the summer timeframe. And all goes, well, we’re going to take the hood off and generally make it available in the winter timeframe, starting with site meta information and CMS content as part of the index. And then we’re going to expand that to CRM and to other objects for that matter.
Gillian Bruce: All right. So just a reminder to all listeners, forward looking statement applies to everything that Kush just said, this is what happens when we get excited in product information. Yeah.
Khushwant Singh: Exactly. And that too, as well. Yes. So I think, again from an LWR point of view, there’s just so much more maturity that customers can expect to see with LWR and Experience Cloud. Because whether it’s out of the box components for content, for data, whether it’s search, whether it is even the ability to deliver these dynamic experiences. So one of the things that our customers really appreciate in Aura is the ability to personalize the experience using CRM information. So show me this content, this data, if user.account equals to X, Y, Z, et cetera. And so the ability to deliver that type of personalization is key, but at the same time, they want to be able to do things like real time personalization. So using, for example, Evergage or interaction studio for that matter.
So as you’re browsing the site or portal, you’re able to get relevant information that’s on the fly generated. So those are another aspects of LWR that we are investing in very heavily. So whether it’s infrastructure, whether it’s data, whether it’s content, whether it’s the UI framework and the various personalization aspects of things, lots of investment happening. Now, all of this has to translate and manifest on mobile. And so that’s the other dimension that we are heavily investing in. So whether you are customizing the experience in design time, as an admin, to say, “Hey, look, you know what? I want to show this image on desktop, but another image on mobile, or I want to have this font you applied in mobile versus on desktop. I want to be able to take my LWR site and use Mobile Publisher to create a mobile app that I can deploy via the app stores.” Those are all areas that we are working on over the course of the next two releases as well. So again, lots of excitement as we work across this entire site.
Gillian Bruce: Yeah. Lots coming. Well, Kush I so appreciate you taking the time to chat with us here on the podcast about all things, Experience Services, Experience Cloud. I know I got a lot of questions answered. I’m sure a lot of people listening are very happy to hear all of the things that you and your team are working on. And I’m sure they will have many more questions. So I’ll include links to some of the great trailblazer community groups that you have set up for Lightning Experience and for Experience Cloud, for people to submit feedback. And thanks again for all of the work that you and your team do. And I look forward to checking back in with you after a couple releases here and coming back to what you all have done and hearing about what is even next from then on.
Khushwant Singh: For sure Gillian. I mean, I truly appreciate the opportunity. And again, to all our Salesforce admins, you are our eyes and ears out there. Feedback is a gift, please keep it coming. And we’re so appreciative of all that you do for us.
Gillian Bruce: Huge, thanks to coach for taking the time to chat with us. He and his team have been so busy working on really important foundational improvements to both Experience Cloud and Experience Services. And it’s so great to now understand what Experience Services mean because for us admins, it means a lot of the stuff that we use every day. So, hey, I don’t know about you, but I’m excited about Dynamic Lightning pages coming for standard objects. Woo, woo. Again, forward looking statement, but I look forward to getting Kush back on the podcast to ask him about that once it has been released in a few releases. So if you want to learn more or you have more feedback about anything, Experience Cloud or Experience Services, Kush, and his team pay close attention to the trailblazer community. So go to the Lightning Experience group or the Experience Cloud group on the trailblazer community and put your feedback in there, put your questions in there. He’s got an amazing team of very talented people.
And if you want to learn anything else about how you can be a successful Salesforce admin, go to my favorite website, admin.salesforce.com. There you can find other great podcasts, blogs, and videos to help you in your Salesforce admin journey. I also encourage you to check out the new Salesforce admin skills kit, which we just launched last month. And it is right there on the admin@salesforce.com webpage. Check it out, let me know what you think, we’re going to do some great podcast episodes about that, coming up here real soon. If you want to follow my guest today, Kush, you can find him @Kush_singh. You can follow me @Gilliankbruce. And you can follow Mike, my amazing co-host @Mikegerholdt. You can follow everything awesome admin related @Salesforceadmns, no I, on Twitter. With that, I hope you have a great rest of your day and I’ll catch you next time in the cloud.
Today on the Salesforce Admins Podcast, we talk to Eddie Cliff, VP of Product Management at Salesforce. Join us as we chat about Salesforce Foundations and how it can give you access to even more capabilities within Sales, Service, and beyond. You should subscribe for the full episode, but here are a few takeaways from […]
Today on the Salesforce Admins Podcast, we talk to Lisa Tulchin, Senior Curriculum Developer at Salesforce. Join us as we chat about user learning styles and how to use them to create better training sessions. You should subscribe for the full episode, but here are a few takeaways from our conversation with Lisa Tulchin. Choose […]
Today on the Salesforce Admins Podcast, we talk to Ella Marks, Senior Marketing Manager at Salesforce. Join us as we chat about the keys to creating an effective presentation, how to prep, and how to create a strong ending. You should subscribe for the full episode, but here are a few takeaways from our conversation […]
