# HubSpot integration > Canonical: https://skedsocial.com/integrations/hubspot-social-media-integration When a social comment or DM needs support, send it to HubSpot as a ticket. The transcript, the requester's handle and a link back to Sked travel with it. ### One click, one ticket, no duplicates. - **1 click** – conversation to ticket - **Outbound only** – nothing imported - **No duplicates** – retries reconcile ### Social support belongs in your help desk. Your inbox catches the complaint. Your support team lives in HubSpot. Escalation sends the conversation across as a ticket, so nobody rebuilds the context in a copy and paste. ### Escalation without the copy-paste. - **The whole conversation travels** – The ticket carries the message transcript, the requester's social handle, and a deep link back to the Sked conversation. - **Retries never duplicate** – Each escalation carries its own id. Send it twice and HubSpot still shows one ticket. - **Assign it to the right owner** – Pick a default HubSpot owner when you connect, so escalated tickets land with the right person. - **It only goes one way.** – This connection pushes Sked inbox conversations out to HubSpot as tickets. It does not bring HubSpot tickets, contacts or deals into Sked. ### What lands on the ticket, exactly. The subject, a transcript excerpt of the customer conversation, the requester's name and handle, priority mapped to your HubSpot values, your tags, and a deep link back to the conversation in Sked. Internal notes are stripped before anything leaves: what your team says to each other stays in Sked. - Transcript excerpt, requester and priority included - Deep link back to the Sked conversation - Internal notes never leave Sked ### One custom property makes retries bulletproof. Add a sked_escalation_id ticket property in HubSpot and every escalation is deduped on it: a retried escalation finds its existing ticket instead of opening a second one. Without the property everything still works; you just lose the dedupe. Default ticket owners come from your own HubSpot owner list. - Dedupe keyed on sked_escalation_id, never the subject - Works without the property; better with it - Default owner picked from your HubSpot owners ### Escalation is one workflow of many. HubSpot handles the tickets. Salesforce and Zendesk connect the same way, and the ideas board reads Notion, Asana and RSS. ### Get the HubSpot connection first. Workflow integrations are rolling out to pilot accounts first. Tell us how your team uses HubSpot and we'll let you know the moment the connection opens up. ### Does Sked Social integrate with HubSpot? Yes, as an outbound escalation path. When a social comment or DM needs support, Sked Social sends it to HubSpot as a ticket carrying the message transcript, the requester's social handle and a deep link back to the conversation. Nothing is imported: HubSpot tickets, contacts and deals stay in HubSpot, and with a sked_escalation_id ticket property, a retried escalation reconciles to its existing ticket. - One click turns an inbox conversation into a HubSpot ticket - Ticket carries transcript, social handle and a deep link to Sked - Outbound only: no HubSpot tickets, contacts or deals imported - Retries dedupe via the sked_escalation_id property ## 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 HubSpot integration ### Does this bring HubSpot tickets into Sked? No, it works the other way. When a social conversation in Sked's inbox needs support, you escalate it and Sked creates a ticket in HubSpot. Nothing is imported from HubSpot into Sked. ### What lands on the HubSpot ticket? The conversation transcript, the requester's social handle, and a deep link back to the conversation in Sked so an agent can reply where it started. ### What happens if an escalation is retried? Each escalation carries its own id, stored on the ticket. A retry updates the existing ticket rather than creating a second one. ### Do our internal notes go to HubSpot? No. Internal notes are stripped before the escalation leaves Sked. The ticket carries the customer conversation, not your team's commentary. ### Do I need to configure anything in HubSpot? One optional custom ticket property: sked_escalation_id. With it, retried escalations dedupe onto their existing ticket. Without it everything still works; duplicates just become possible on retry. ### Who gets assigned the ticket? A default owner you choose from your own HubSpot owner list when setting up the connection. Reassign inside HubSpot as usual after that. ### Can the support team see the original conversation? Yes. Every ticket carries a deep link back to the conversation in Sked, so an agent can read the full social thread in one click. **See HubSpot 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.