#Agentforce321 debatiendo

Hi Trailblazers., 

I’m exploring Agentforce

 and would love to learn from teams who have already implemented it. 

 If you’ve deployed Agentforce in any capacity, could you share your experience?

Specifically, I’d love to know:

1. What did you use Agentforce for?

• What business problem were you trying to solve?
• Was it customer-facing, agent-facing, or used for back-office automation?
• Which parts of your Salesforce stack did you integrate with (Service Cloud, Data Cloud, Omni-Channel, Knowledge, etc.)?

2. How did you deploy it?

• Architecture or setup approach
• Custom prompts vs. out-of-the-box configurations
• How you handled grounding, data governance, and security
• How you integrated it into existing workflows (e.g., case swarming, chat, voice, digital channels)

3. Did it work?

• What outcomes did you see (qualitative or quantitative)?
• What worked exceptionally well?
• What didn’t work or required rethinking?
• Any surprises during rollout?

4. What would you ask or consider before deploying again?

Any lessons learned around:

• Change management
• Agent adoption
• Hallucinations or accuracy
• Scalability
• Required cleanup of knowledge articles/data
• Measuring success
• Skills or personas required to maintain Agentforce long-term

5. Any clever tips or things you wish you knew earlier?

• Configuration tricks
• Testing strategies
• Guardrails or safety measures
• Prompt engineering best practices
• Organizational prerequisites

Thanks in advance for sharing your insights! Your real-world experiences will really help guide our approach. 

Hi everyone,

I’d like to understand whether Zoom Phone, RingCentral, and Agentforce (including Prompt Builder) can be integrated with or used within Salesforce Experience Cloud.

Specifically, I’m looking for information on the following:

1. Zoom Phone: Can Zoom Phone be integrated with Experience Cloud for making and receiving calls? Are features such as click-to-call, call logging, and CTI supported for community users?
2. RingCentral: Does RingCentral support integration with Experience Cloud? If so, what calling and telephony features are available to external or community users?
3. Agentforce and Prompt Builder: Can Agentforce agents be deployed within an Experience Cloud site? Can prompts created using Prompt Builder be used by community users, and what are the available options and limitations?
4. Licensing requirements: What Salesforce licenses, Experience Cloud licenses, Agentforce licenses, or third-party subscriptions are required to enable these features?
5. Configuration and limitations: Are there any additional setup requirements, supported integration approaches, permissions, or known limitations to consider?

If anyone has implemented these solutions, I’d appreciate details about the recommended approach, licensing costs or requirements, and any practical experience or documentation you can share.

Thanks in advance! 

Registering a Streamable HTTP MCP server with no authentication, then allowlisting a tool, fails with "We couldn't allowlist the tools due to an internal error: <id> (1360387860)". The tool selection resets and no agent action is created. 

The trigger is any parameter whose `type` is a list, even a plain nullable one. A parameter with `"type": "string"` allowlists fine. All of these fail: `["null","string"]`, `["null","array"]`, `["null","integer"]`, `["null","boolean"]`, and `["null","string","integer"]`. 

The server answers `initialize`, `notifications/initialized` and `tools/list` correctly before the error. A tool with the same description and plain types passes, so it isn't the description length. Type lists are valid JSON Schema, and many servers emit `["null", X]` for optional fields automatically (Go's schema generator does), so this will hit a lot of servers. 

Expected: the tool imports, or the error says which schema was rejected. The Considerations for MCP for Agentforce page says tool schemas that don't map to Lightning types still work, only without variable storage. 

Repro: one tool with one optional parameter `{"type": ["null","string"]}`. Developer Edition org created 2026-10-28. Setup > Agentforce Registry > Register MCP Server > No Authentication > Create and Continue > Add Tool > Allow and Continue. 

Workaround: allowlist only tools whose parameters have a single plain type. 

Related: Known Issues has an entry, "Adding an MCP tool fails when its schema includes both a default value and unevaluatedProperties: false" (Service/Agentforce, Solution in Progress), which shows the same kind of "internal error" on save. My schema has neither keyword, so this looks like a separate trigger, but it may share the schema-import step.