#Agentforce347 discutindo

I dont think there is a way to share grids except publish them as templates (without the data), so others can start-off from the template instead of having to build everything (columns, prompts, logic etc) from scratch. Think of it like an Excel Template

with all the columns, formulae, scripts, macros, charts etc) but without the data, so you can fill-in your own data. 

P.S.:  If this genuinely human written reply answers your question as compared to random AI-generated crap, please upvote and accept it. Thank you!

•  Metered: Agentforce usage is charged based on consumption; for agentic usage, the main unit is generally actions, not simply tokens or conversations.  
• Flex Credits: A standard Agentforce action currently consumes 20 Flex Credits, while custom actions are also measured by the number of actions called. 
• Unmetered: Certain licensed users/features can use qualifying Agentforce capabilities without consuming Flex Credits, when the required licensing, permissions, and execution conditions are satisfied. 
• Important: “Unmetered” does not mean everything in the agent is free; underlying services such as Data 360 can still consume credits. 
• Employee Agents: Agentforce add-ons provide unmetered Agentforce usage for employees; the Agentforce User License, by contrast, provides metered employee usage and requires Flex Credits. 
• Customer-facing Agents: Salesforce currently offers both Flex Credits (pay per action) and Conversations (pay per conversation) for customer-facing agents. 
• High-volume usage: Consumption-based pricing makes the cost depend on actual usage, so action/conversation volume and the specific features used need to be estimated rather than assuming one fixed cost. 
• Monitoring: Use Digital Wallet to monitor Agentforce consumption and usage in the org. 
• Forecasting: Salesforce recommends reviewing actual Digital Wallet consumption and working with your Salesforce Account Executive for contract-specific pricing and usage estimates. 
• Bottom line: Metered = pay according to usage; Unmetered = qualifying usage included through specific licenses/permissions. Which is more cost-effective depends on your users, volume, features, and contract—not simply whether the agent is internal or external. 

Also, go through the doc it helps you--->

 Agentforce and Generative AI Usage and Billing | Salesforce Help

Considerations for Agentforce Employee Agent | Salesforce Help

Metering for Agentforce and Generative AI Usage | Salesforce Help

Salesforce Agentforce Pricing | Salesforce 

Hello Link for 'Template' is given in the new Test Suit Upload Test Cases  you can  give any temporary name like 'test agent' to the new test suit agent then select einstein copilot go next next till data and then go Upload to test Tab given in screenshot where Template link is provided  

@Bodala Pallavi

What I'd try, quickly - 

1. Populate the template without opening it in Excel if you can, or re-save explicitly as CSV UTF-8, to eliminate the encoding angle. 

2. Check the exact header spelling and order against any current Salesforce Help doc for Conversation-Level Testing, in case the tool expects a slightly different header (for example a "Conversation" vs "Conversation Transcript" naming drift between template versions). 

--> If both check out, treat it as a known Beta issue. Conversation-Level Testing is new in Summer '26 and this is exactly the kind of template-versus-parser mismatch that shows up in Beta.  

Since the template came straight from the tool and Turn-Level works with its template, this points to a Beta bug rather than user error. I'd log it with Salesforce Support, referencing Testing Center Beta, and note that the tool-provided Conversation-Level template is rejected on upload.

Hi Guilherme, 

Salesforce's Agentforce Deployment documentation lists the supported channels this way: Employee Agents are supported on Salesforce Lightning Experience, Salesforce Mobile, Slack, and Enhanced Web Chat — internal-only surfaces. Experience Cloud sites aren't a supported channel for Employee Agents. Service Agents are what support deployment to Experience Cloud, via Enhanced Chat/messaging channels. 

So Ajaypreet's answer is on the right track: there's no supported way to deploy an Employee agent directly to a community/Experience Cloud site. Your practical path is: 

1. Create a new Service Agent for the external-facing use case 

2. Rebuild the topics/instructions/actions using AgentScript — you can largely copy over your existing AgentScript code for instructions and action logic, since the underlying script structure is similar 

3. Deploy that Service Agent to your Experience Cloud site via Enhanced Chat / messaging channel (Omni-Channel routing) 

One thing to check while migrating: Employee Agents run with the logged-in employee's own permissions/context, while a Service Agent on a community typically runs under a dedicated integration/agent user or the guest/community user's context. Review sharing rules and object/field access for whatever user the Service Agent will run as — that access model differs from what your Employee Agent currently relies on, and it's usually the part that needs the most rework, not just copying the actions over. 

Reference: