A real Salesforce Case
Escalation creates a Case in your org, carrying the conversation transcript and the requester's social handle.
Salesforce
BetaSend a social conversation to Salesforce as a case.
Escalate any Sked inbox conversation into your Salesforce org. A Case is created with the transcript and a link straight back to the thread.
Sked · Inbox · Salesforce
Outbound only. Deduped by design.
1click
conversation to case
From any Sked inbox conversation.
Outbound only
nothing imported
Sked never reads your accounts or opportunities.
No duplicates
retries reconcile
The escalation id is stored on the Case.
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.
Does Coach Park have any 1:1 slots open? Chasing a 200kg deadlift by March and the group programming has me close but not there.22h
Park's 1:1 book is full until next month but Reyes has Tuesday and Thursday afternoons open. He's pulled 290 and coaches the deadlift block. Want us to set up an intro chat?21h
Yes please, Thursday works. And tell him I'm bringing my own belt, I've heard about the loaner bin.45m
The conversation follows the customer.
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.
Found Salt Theory on a slow Sunday and left with the perfect linen cover-up. The team helped me size two swimsuits without any pressure and the fit is exactly right. Easily my favourite shop on the coast.
thank you, maya. slow sundays are exactly what we are made for. so glad the linen cover-up and both suits fit just right, come back any time, the kettle is always on.
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
Salt Theory@salttheory
FiltersDisplay
Internal review0
Client approval0
Approved1
ScheduledTue 21 Jul, 12:00 PM
Salt Theory
five years of salt theory this month. we started with one suit and a folding table at a saturday market. there's a pattern room now, and eleven pieces, and all of you. thank you. anniversary offer drops next week. waitlist hears first, link in bio. and if you were one of our first hundred orders, check your inbox this week. #fiveyears #smallbusiness
Collection+1
ApprovedScheduled3
ScheduledMon 13 Jul, 11:00 AM
Salt Theory
pre-orders open thursday 10am: the winter capsule. long-sleeve suit, thermal-lined brief, and the recycled-wool beach coat we've spent two years getting right. small run, made to order, ships in four weeks. sizing is identical to the main line. the coat won't restock this season. link in bio.
Collection+2
ScheduledScheduledThu 16 Jul, 1:30 PM
Salt Theory
the kelp story. our green started as a dye-lot mistake. it came back darker than the swatch and better than the brief. we kept it and built the brand around it. swipe for the original swatch next to the finished suit. kelp pieces are all in stock, link in bio.
Collection+1
ScheduledScheduledSun 19 Jul, 10:00 AM
Salt Theory
slow mornings: linen, salt water, coffee gone cold because the swim ran long. our autumn board is live: the full low tide collection styled the way we actually wear it, off the beach and into the day. save what you like, links on every pin.
Collection
ScheduledOne 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.
+ more
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.
Loading form…
The proof behind the workflow.
- 91%customer satisfaction (CSAT)Measured across 10,000+ marketers who run their social on Sked.
- 4.6/5on G2 from verified reviews80+ verified customer reviews on G2.
- SOC 2Type 2 certifiedYour content and your audience data, handled to enterprise standard.
“Sked Social changed the game and became the operational backbone of the agency almost overnight.”
Common questions
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.
Updated
See Salesforce integration in action. Start your 14-day trial.
Try Sked free for 14 days. No credit card, no lock-in. Just the connected workspace your team has been asking for.
Can we swap the second photo? Otherwise good to go.