# Salesforce integration > Canonical: https://skedsocial.com/integrations/salesforce-social-media-integration Escalate any Sked inbox conversation into your Salesforce org. A Case is created with the transcript and a link straight back to the thread. ### Outbound only. Deduped by design. - **1 click** – conversation to case - **Outbound only** – nothing imported - **No duplicates** – retries reconcile ### The escalation starts in the inbox. Comments and DMs from every connected channel land in one queue. When one of them is really a support case, escalate it from right there: the Case opens in Salesforce carrying the conversation transcript and the requester's social handle, deduped so a retry can never open a second one. ### The conversation follows the customer. - **A real Salesforce Case** – Escalation creates a Case in your org, carrying the conversation transcript and the requester's social handle. - **Deduped by design** – Every escalation writes its id to a field on the Case, so a retry reconciles to the same Case instead of creating another. - **Straight back to the thread** – The Case links to the Sked conversation, and Sked keeps the Case link, so the two never drift apart. - **Outbound only.** – Sked pushes inbox conversations into Salesforce as Cases. It does not read your accounts, contacts or opportunities, and it imports nothing. ### A real Case, with real context. The Case lands in Salesforce with a subject, a transcript excerpt of the customer conversation, the requester's name and handle, priority mapped to your Case values, your tags and a deep link back to Sked. Internal notes are stripped before anything leaves, so team commentary stays where it was written. - A standard Salesforce Case, not a webhook blob - Requester, priority and tags included - Internal notes never leave Sked ### One custom field, zero duplicate Cases. Add the Sked_Escalation_Id__c custom field to Cases and every escalation dedupes on it: a retry finds its existing Case instead of opening a second one. Sked never matches on subject, because two different complaints can share one. Without the field it still works; you just lose the dedupe. - Dedupe keyed on Sked_Escalation_Id__c - Subject matching deliberately avoided - Default Case owner from your own user list ### The service cloud is one connection of many. Salesforce takes the Cases. HubSpot and Zendesk escalate the same way, and content flows in from Drive, Notion and RSS. ### Get the Salesforce connection first. Workflow integrations are rolling out to pilot accounts first. Tell us how your team uses Salesforce and we'll let you know the moment the connection opens up. ### Does Sked Social integrate with Salesforce? Yes, as an outbound Case path. Escalate any inbox conversation and Sked Social creates a Case in your Salesforce org carrying the conversation transcript, the requester's social handle and a deep link back to the thread. Sked never reads your accounts, contacts or opportunities, and with the Sked_Escalation_Id__c field on Cases, a retried escalation finds its existing Case instead of opening a second one. - One click escalates a conversation to a Salesforce Case - Case carries transcript, handle and a deep link to the thread - Outbound only: accounts, contacts and opportunities are never read - Dedupe on Sked_Escalation_Id__c; never matched on subject ## The proof behind the workflow - **94%** – customer satisfaction (CSAT) (Measured across 10,000+ marketers who run their social on Sked.) - **90s** – average first response (Average time to a real human reply from the support team.) - **4.6/5** – on G2 from verified reviews (80+ verified customer reviews on G2.) - **SOC 2** – Type 2 certified (Your content and your audience data, handled to enterprise standard.) ## Questions about Salesforce integration ### Does Sked read my Salesforce accounts or contacts? No. The connection is outbound only. Escalating a Sked inbox conversation creates a Salesforce Case. Sked does not read your accounts, contacts or opportunities. ### What does the Salesforce Case contain? The conversation transcript, the requester's social handle, and a link back to the thread in Sked. Sked stores the Case link too, so the two stay connected. ### Can the same conversation create two Cases? No. The escalation id is written to a field on the Case, so retries reconcile to the same Case instead of duplicating it. ### Do our internal notes go to Salesforce? No. Internal notes are stripped before the escalation leaves Sked. The Case carries the customer conversation, not your team's commentary. ### Do I need to configure anything in Salesforce? One optional custom Case field: Sked_Escalation_Id__c. With it, retried escalations dedupe onto their existing Case. Without it everything still works; duplicates just become possible on retry. ### Who owns the Case when it arrives? A default owner you pick from your Salesforce users during setup. Your usual assignment rules and queues take it from there. ### Can agents see the original social conversation? Yes. Every Case carries a deep link back to the conversation in Sked, so an agent reads the full thread in one click. **See Salesforce integration in action.** Start your 14-day trial. > Sked Social changed the game and became the operational backbone of the agency almost overnight. > > – Salomé Thériault, CEO & Founder, Ampersand Social Co.