Send follow-up communications upon ticket resolution
When a support ticket status changes to solved in Snappy, update the contact profile in LeadConnector and add them to a customer satisfaction sequence.
See all Snappy + LeadConnector integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Snappy Explore Snappy →
TriggersFires when a new support ticket or chat conversation starts in Snappy.
Fires when a ticket's status changes in Snappy.
Fires when a ticket in Snappy is assigned to an agent.
Fires when a ticket in Snappy breaches its response SLA.
Creates a new ticket in Snappy.
Updates a ticket's status in Snappy.
Assigns a ticket in Snappy to an agent.
Posts a reply or internal note on a ticket or conversation in Snappy.
LeadConnector Explore LeadConnector →
TriggersFires when a new lead or contact is captured in LeadConnector.
Fires when a contact enters an automation in LeadConnector.
Fires when a field on a contact changes in LeadConnector.
Fires when a contact unsubscribes in LeadConnector.
Creates or updates a contact in LeadConnector.
Adds a contact to a workflow or campaign in LeadConnector.
Sends an email or message to a contact via LeadConnector.
Changes a contact's tags in LeadConnector.
More Snappy + LeadConnector workflows
Pause marketing messages when critical support tickets open
When a new support ticket is created in Snappy, automatically apply a temporary hold tag to the contact in LeadConnector.
See details
Create support tickets for unengaged or unsubscribed leads
When a lead unsubscribes in LeadConnector, automatically create a ticket in Snappy for an account manager to investigate potential churn.
See details
See all Snappy + LeadConnector integrations → · Browse the full workflow library →
Common questions
Can Knit build “Send follow-up communications upon ticket resolution” between Snappy and LeadConnector?
Yes — describe it in the box above and Knit's Integrations Agent researches Snappy and LeadConnector's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can support team members manage marketing messaging when an SLA is breached?
Yes, when an SLA breach occurs in Snappy, a tag can be applied in LeadConnector to pause marketing emails until the issue is resolved.
Can customer marketing unsubscribes update open support tickets?
Yes, when a contact unsubscribes in LeadConnector, a comment can be automatically added to open tickets in Snappy to keep support agents informed.