#TTTC0 debatiendo

A few weeks ago at True to the Core (TTTC) during TDX, I asked the Salesforce Team to clarify the pricing for Prompt Builder. 

Salesforce Foundations is a free offering that includes Agent Conversations, Data Cloud, and features from Marketing and Commerce. However, despite what Trailhead and Salesforce Pricing pages suggest, it does not include Prompt Builder. 

Since raising this at TTTC, I’ve spoken with multiple Salesforce teams, and even they can’t agree—some say Prompt Builder is included, others say it isn’t. In practice, it’s not available in a Salesforce Foundations org, as the required Permission Sets (Prompt Template Manager, Prompt Template User) and Permission Set Licenses (Einstein Prompt Templates) are not provisioned. 

Currently, it appears Salesforce intends to require an Einstein for Service, Einstein for Sales, or Einstein for Platform license — effectively making Prompt Builder subject to both user-based and consumption-based licensing. 

I appreciate that Salesforce teams have been working on this behind the scenes, and I’ve noticed a shift in messaging. Since TDX, Agentforce’s response on Salesforce Help has changed from ❌ “Prompt Builder is not explicitly mentioned as part of Foundations” to ⚠️ “Prompt Builder is available with Salesforce Foundations, but on a limited basis.”

This lack of clarity is a problem for the nonprofit clients I work with, as they rely on the Power of Us Program for courtesy licenses in the first place. 

I’d like the Salesforce team to: 

1️⃣ Clarify whether Prompt Builder is included in Salesforce Foundations, as the official materials currently contradict each other. 

 2️⃣ If Prompt Builder requires per-user licensing (even temporarily), consider extending the Power of Us Program to provide courtesy Prompt Builder licenses alongside the standard courtesy Salesforce licenses. 

 3️⃣ Correct all marketing and documentation to clearly reflect whether Prompt Builder is included with Foundations (or not). 

At TTTC, it was suggested that Prompt Builder was coming to foundations, but I didn’t get a clear time commitment to the above, so I’m posting here. 

Before I raised this at TTTC I verified this was not currently available in two separate orgs both with Salesforce Foundations enabled. 

If you need a recap you can watch the recording of this question from 11:27 on Salesforce+

#TTTC #True To The Core #Prompt Builder #Power Of Us HUB #AI #Prompts #TDX25

@Prompt Builder @* Salesforce Platform * @Trailblazer Community Cove @* Customer Success * @Nonprofit Hub 

100 Coins Coming Your Way!

Our product teams are about to start planning for the Winter '23 release, so you know what that means...it's time to help them shape the product roadmap with IdeaExchange Prioritization. 

From Monday, January 24 - February 7, you can visit the IdeaExchange to review a list of features our teams are considering. Take your replenished bucket of 100 coins and allocate them on the ideas you'd like to see our teams work on. At the end of the two weeks, the results are what the teams will use to refresh their roadmaps for Winter '23 and beyond.

And don't forget to check on the status of the winning ideas. See which teams are still hard at work on ideas you prioritized in prior cycles.

The IdeaExchange Roadmap

Here at IdeaExchange headquarters (currently, my living room), we're also refreshing our roadmap for the IdeaExchange itself. By popular request from many of you and our product teams, we're working on the ability to have product/topic-focused lists for you to prioritize in the future. For example, three times a year instead of giving you one list with a mix of product features, we ask you to prioritize a list for each of the products you care about.

We're thinking through how to streamline a multi-product prioritization cycle so it's as easy as prioritizing today. We're also toying with concepts such as having the list be a mix of features the product teams have come up with alongside top ideas you all have come up with. The goal: bring balance to the roadmap so our products continue to be innovative and useful to your needs. If you have thoughts, don't be shy - let us know.

Going Analog

While we're excited to continue to invest in the IdeaExchange, listening to you and co-creating our products with you is about more than just improving the site. February marks the beginning of our new fiscal year, which means we're refreshing our organizational priorities via the V2MOM. Our team is working closely with our product executives to set clearer expectations with our product teams about what it means to have a balanced customer-infused product roadmap. We'll be showcasing the value your voices bring to the product planning process, celebrating the wins, and supporting areas that could benefit more from engagement with all of you.

Stay plugged into this community group, as we'll have questions for you about how to best evolve the site and our program. In the meantime, prioritize with those coins!

For the True to the Core session at Dreamforce, @Automation User submitted the following question that we didn't have time to answer: "What's the criteria for something being a Known Issue?"

Generally, if a customer reports an issue that is investigated by our engineering/product teams and is found to be reproducible, a bug is logged and a corresponding Known Issues entry is created.

However, Paul (and others) pointed out that sometimes it feels less clear about whether something becomes a Known Issue when it's investigated and the result is it's described as a platform limitation. As part of the @* Known Issues * program, we'll be looking as situations like this (as well as when customers are directed to create an idea in a support/Known Issues context).

In speaking to leaders in support and product, there's a general philosophy that if there's a perceived bug/issue from our customers and our response is that it's a limitation, then we should ensure that limitation is documented and point you to it. There's work to do here.

Examples of when you're left scratching your head help. Let us know here or via direct message if you have other situations that we should work with the various teams to help smooth out.

And while I'm here, let me plug that as of a few hours ago, the new IdeaExchange is now live. Take it for a spin and let us know what you think. We'll be taking certain elements (i.e., improved search and filtering) and applying it to Known Issues.

**The Pre-Release Sign Up is LIVE...and you know what that means**

💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎

The #Winter21  Treasure Hunt is ON! #BeReleaseReady

Sign up for a Winter ‘21 Pre-Release Org:

https://www.salesforce.com/form/signup/prerelease-winter21/

Post your treasure here: https://sforce.co/3gfARfX

Post your treasures right here in this group:

www.salesforce.com/success-releasereadiness

You can comment on this thread or create a new post tagged with #Winter21Treasure

Anyone who posts about the treasure they discover will be awarded a special Treasure Hunter badge! Don't forget to use the hashtag!

Let us know what you find that you like and why!

***Make sure you're in Lightning Experience when you start exploring***

Uncover those gems we have all been waiting for!

Ready, Set...GO!

--------------------------------------

Note: If your email address already has an org associated to it, you will be returned to the signup page and prompted to create a new username in the Username field.

This username should be in the form of an email address. You will still receive the verification email in the address you provided in the email field (must be an active email). You will also need to re-select your Pre-Release edition.

#RRTreasureHunts

@Chris Collins @Jacinta Burke @Michael Broome @Diana Carter @Noelle Bloomfield @Amanda Lane @Rebecca Saar