​
Scenario

Customer support agents often identify issues or requests reported by customers in Slack channels that require a formal case to be logged in Salesforce Service Cloud (Salesforce Core). Manually creating these cases involves copying information, switching between applications, and can lead to delays or missed details. The goal is to empower support agents to quickly create a Salesforce case directly from a Slack conversation with the help of an Agentforce agent.

​
Actors

  • Customer Support Agent (using Slack)
  • Customer (interacting in Slack)
  • Agentforce Agent (powered by ACP)

​
ACP Components Involved

  • Slack Connector:
    • slack_get_message_details: To retrieve the content and context of a specific Slack message or thread.
    • slack_get_user_profile: To get details about the Slack user who reported the issue (potentially to map to a Salesforce Contact).
    • slack_post_message_reply (or similar): To confirm case creation back in the Slack thread.
  • Salesforce Core Connector (Service Cloud):
    • salesforce_create_case: To create a new case with relevant details.
    • salesforce_search_contact_by_email (or salesforce_search_account_by_name): To find an existing Contact or Account to associate with the case.
    • salesforce_get_case_details: To retrieve the newly created Case Number and link.
(Tool names are illustrative and will depend on the final ACP connector implementation.)

​
Workflow

  1. Issue Identification in Slack: A Customer Support Agent identifies a customer message in a Slack channel (or direct message) that warrants a Salesforce Case.
  2. Agent Invocation: The Support Agent invokes the Agentforce agent, often by mentioning it in the Slack thread or using a slash command, and provides context, e.g., “@Agentforce create a case from this thread.”
  3. Information Gathering (Slack):
    • The Agentforce agent uses slack_get_message_details to retrieve the relevant Slack message(s), including the user who reported it.
    • Optionally, it might use slack_get_user_profile to get the user’s email if available, to help find them in Salesforce.
  4. (Optional) Contact/Account Lookup (Salesforce):
    • The agent may attempt to find an existing Contact in Salesforce using the Slack user’s email (via salesforce_search_contact_by_email) or ask the Support Agent for the customer’s name/company to search for an Account.
  5. Case Creation (Salesforce):
    • The Agentforce agent uses salesforce_create_case. It populates fields like:
      • Subject: Derived from the Slack message or a summary.
      • Description: The content of the Slack message(s).
      • Contact/Account: Linked if found in the previous step.
      • Origin: Set to “Slack” or a similar identifier.
      • Priority/Status: Can be set to default values or prompted from the Support Agent.
  6. Confirmation and Feedback (Slack & Salesforce):
    • Once the case is created, the agent uses salesforce_get_case_details to retrieve the new Case Number and a direct link to the case in Salesforce.
    • The agent then uses slack_post_message_reply to post a confirmation back into the original Slack thread, e.g., “Case #00123456 has been created for this issue: [Link to Case].”
    • The Support Agent can then click the link to view or update the case in Salesforce.

​
Key Outcomes & Benefits

  • Faster Case Logging: Significantly reduces the time taken to create cases from Slack conversations.
  • Improved Data Accuracy: Minimizes manual data entry errors by directly transferring information.
  • Enhanced Agent Productivity: Allows support agents to remain in their primary communication tool (Slack) while still efficiently logging issues in Salesforce.
  • Better Customer Experience: Quicker case creation can lead to faster acknowledgment and resolution for the customer.
  • Centralized Tracking: Ensures all customer issues, regardless of where they are first reported, are tracked within Salesforce Service Cloud.
  • Streamlined Workflow: Simplifies the process for support agents, reducing context switching.
This use case demonstrates how ACP can connect communication platforms like Slack with core CRM systems like Salesforce Service Cloud to create a more efficient and responsive customer service operation.