Salesforce Agentforce Sales Assistant Template

Reusable, anonymized accelerator for deploying a Salesforce Employee Agent that:

• answers sales-support questions with AnswerQuestionsWithKnowledge
• escalates unresolved issues into a Case
• creates a clickable case link for end users
• captures a summary plus relevant conversation excerpt in case description

This package is designed for fast rollout from Cursor or terminal into any org/sandbox.

What is included

• Agent Script template: config/agent-script-template.yaml
• Case creation flow metadata: force-app/main/default/flows/Sales_Assistant_Create_Case.flow-meta.xml
• Agent access permission set: force-app/main/default/permissionsets/Sales_Assistant_Agent_Access.permissionset-meta.xml
• Deploy + setup scripts: scripts/
• Installation and customization guides: docs/
• Dependency inventory: docs/ASSETS.md

Tokenized values

Branding and org-specific values are parameterized with tokens:

• ${COMPANY_NAME}
• ${ORG_DOMAIN}
• ${AGENT_LABEL}
• ${AGENT_DEVELOPER_NAME}
• ${FLOW_API_NAME}

Use scripts/apply-branding.sh to replace these values before deploy.

Quick start

1. Update config from example:
   • copy config/install-config.example.json to config/install-config.json
   • set your company and org values
2. Apply branding tokens:
   • bash scripts/apply-branding.sh config/install-config.json
3. Deploy metadata:
   • bash scripts/deploy.sh <target-org-alias>
4. Run post-deploy setup:
   • bash scripts/post-deploy.sh <target-org-alias> <username-or-user-id>
5. In Agent Builder Script Editor, paste/import:
   • config/agent-script-template.yaml
6. Publish and activate the agent version.

Customer onboarding checklist

Use this section as a copy/paste runbook for new customer rollouts.

1) Clone and configure

git clone https://github.com/charles-ensley/agentforce-sales-assistant-template.git
cd agentforce-sales-assistant-template
cp config/install-config.example.json config/install-config.json

Edit config/install-config.json:

• COMPANY_NAME: customer name, for example Acme
• ORG_DOMAIN: customer Lightning domain, for example https://acme-dev.lightning.force.com
• AGENT_LABEL: display label shown in Agent Builder
• AGENT_DEVELOPER_NAME: API/developer name for the agent
• FLOW_API_NAME: case flow API name (default Sales_Assistant_Create_Case)

2) Authenticate to customer org

sf org login web --alias <customer-org-alias>

3) Apply branding and deploy

bash scripts/apply-branding.sh config/install-config.json
bash scripts/deploy.sh <customer-org-alias>

4) Assign access and publish

bash scripts/post-deploy.sh <customer-org-alias> <username-or-user-id>

Then in Agent Builder:

• open Script Editor
• paste/import config/agent-script-template.yaml
• save, publish, and activate

5) Smoke test

• Ask a knowledge-grounded question and verify response quality.
• Ask to escalate and verify case creation with:
  • inferred CaseType
  • formatted description including --- Conversation Excerpt ---
  • clickable case link.

Notes

• The knowledge action points to the standard Employee Agent knowledge action and expects each customer to provide their own Agentforce data library content.
• MessagingSessionId remains in the flow/action contract for compatibility, but behavior should not depend on it in Employee Copilot channels.