I have this agent built using agentscript and it is working just fine but my client would like to make it available on our communities as well, to allow users to access it without the need for the Salesforce app. Is there a way to deploy an employee agent? I know that Service ones are possible but I dont know if i would be able to do all the things the employee one is doing
#Agentforce #Salesforce Developer
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:
https://trailhead.salesforce.com/content/learn/modules/agentforce-deployment-quick-look/deploy-an-ai-agent-with-agentforce
