Skip to content

forcedotcom/sf-skills / skills/service-itsm-teams-employee-agent-configure

service-itsm-teams-employee-agent-configure

Verified

Configure the embedded Agentforce Employee Agent so it replies inside the Microsoft Teams ITSM custom client ('Salesforce Employee Assist' / 'Ask AI Agent'). Use this for: 'set up employee agent in Teams', 'embed Agentforce agent in Teams', 'make the IT Service Employee Agent reply in Teams', 'Teams Ask AI Agent not responding', 'agent joins then leaves without replying', 'configure MIAW deployment for Teams employee agent', 'Teams embedded messaging agent setup'. Builds the whole stack headlessly (zero Setup-UI clicks): the Web messaging channel with User Verification ON, the Enhanced Chat User Verification Key Set (JWKS_URL) it requires, the Teams_AgentForce custom-client deployment, the routing flow to the agent, and the Agent Access permission set that lets the portal user reach the agent. DO NOT TRIGGER for enabling the Teams feature Salesforce Go page toggle (service-itsm-teams-configure) or for configuring notification preferences.

assets/Teams_AgentForce.EmbeddedServiceConfig-meta.xml

View on GitHub
<?xml version="1.0" encoding="UTF-8"?>
<!--
  Deployable EmbeddedServiceConfig source template for the Teams "Ask AI Agent" custom client.
  Canonical guidance lives in references/teams-embedded-employee-agent.md §C — this file is the
  same metadata as a ready-to-deploy asset; keep the two in sync if you edit either.
  Place at: force-app/main/default/embeddedServiceConfigs/Teams_AgentForce.EmbeddedServiceConfig-meta.xml
  Deploy with the "sf project deploy start" command shown in reference §C (kept out of this
  comment because XML comments cannot contain a double-hyphen, which CLI flags use).

  Placeholders / invariants:
    - DeveloperName (the file's API name) MUST be exactly "Teams_AgentForce" — Teams hard-codes
      esDeveloperName; do not rename per-org.
    - <messagingChannel> below is a PLACEHOLDER: replace "Teams_AgentForce_Channel" with YOUR
      MessagingChannel's metadata developer name (from §A of the reference) — it is NOT required to
      equal the ESD name.
    - Do NOT add a <site> element — a deploymentType=API custom-client ESD has none (correct).
    - <isEnabled>true</isEnabled> is the equivalent of "published" for an API-type ESD.
    - <masterLabel> is a human label; adjust freely.
-->
<EmbeddedServiceConfig xmlns="http://soap.sforce.com/2006/04/metadata">
    <areGuestUsersAllowed>false</areGuestUsersAllowed>
    <deploymentFeature>EmbeddedMessaging</deploymentFeature>
    <deploymentType>API</deploymentType>
    <embeddedServiceMessagingChannel>
        <isChatInvitationCustomizable>false</isChatInvitationCustomizable>
        <isEnabled>true</isEnabled>
        <isInvitationEnabled>false</isInvitationEnabled>
        <isSendInvtAllowedAfterAccept>false</isSendInvtAllowedAfterAccept>
        <isSendInvtAllowedAfterReject>false</isSendInvtAllowedAfterReject>
        <messagingChannel>Teams_AgentForce_Channel</messagingChannel>
        <shouldShowAgentforceTagline>false</shouldShowAgentforceTagline>
        <shouldShowDeliveryReceipts>false</shouldShowDeliveryReceipts>
        <shouldShowEmojiSelection>false</shouldShowEmojiSelection>
        <shouldShowReadReceipts>false</shouldShowReadReceipts>
        <shouldShowTypingIndicators>false</shouldShowTypingIndicators>
        <shouldStartNewLineOnEnter>false</shouldStartNewLineOnEnter>
    </embeddedServiceMessagingChannel>
    <isEnabled>true</isEnabled>
    <isTermsAndConditionsEnabled>false</isTermsAndConditionsEnabled>
    <isTermsAndConditionsRequired>false</isTermsAndConditionsRequired>
    <masterLabel>Teams AgentForce</masterLabel>
    <shouldHideAuthDialog>false</shouldHideAuthDialog>
</EmbeddedServiceConfig>
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall