Pause marketing messages when critical support tickets open
When a new support ticket is created in Crisp, automatically apply a temporary hold tag to the contact in Platform.ly.
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.
Platform.ly Explore Platform.ly →
TriggersFires when a new lead or contact is captured in Platform.ly.
Fires when a contact enters an automation in Platform.ly.
Fires when a field on a contact changes in Platform.ly.
Fires when a contact unsubscribes in Platform.ly.
Creates or updates a contact in Platform.ly.
Adds a contact to a workflow or campaign in Platform.ly.
Sends an email or message to a contact via Platform.ly.
Changes a contact's tags in Platform.ly.
Crisp Explore Crisp →
TriggersFires when a new support ticket or chat conversation starts in Crisp.
Fires when a ticket's status changes in Crisp.
Fires when a ticket in Crisp is assigned to an agent.
Fires when a ticket in Crisp breaches its response SLA.
Creates a new ticket in Crisp.
Updates a ticket's status in Crisp.
Assigns a ticket in Crisp to an agent.
Posts a reply or internal note on a ticket or conversation in Crisp.
More Platform.ly + Crisp workflows
Create support tickets for unengaged or unsubscribed leads
When a lead unsubscribes in Platform.ly, automatically create a ticket in Crisp for an account manager to investigate potential churn.
See details
Send follow-up communications upon ticket resolution
When a support ticket status changes to solved in Crisp, update the contact profile in Platform.ly and add them to a customer satisfaction sequence.
See details
See all Platform.ly + Crisp integrations → · Browse the full workflow library →
Common questions
Can Knit build “Pause marketing messages when critical support tickets open” between Platform.ly and Crisp?
Yes — describe it in the box above and Knit's Integrations Agent researches Platform.ly and Crisp'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 Crisp, a tag can be applied in Platform.ly to pause marketing emails until the issue is resolved.
Can customer marketing unsubscribes update open support tickets?
Yes, when a contact unsubscribes in Platform.ly, a comment can be automatically added to open tickets in Crisp to keep support agents informed.