Follow up on marketing unsubscribes with support tickets

When a contact unsubscribes in TextSpot, automatically create a ticket in Re:plain so account managers can reach out and gather feedback.

Try:

See all Re:plain + TextSpot integrations or talk to a human

Trusted by teams already building on Knit·

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.

Re:plain Explore Re:plain →

Triggers

New ticket created

Fires when a new support ticket is created in Re:plain.

Ticket status changed

Fires when a ticket's status changes in Re:plain.

Ticket assigned

Fires when a ticket in Re:plain is assigned to an agent.

SLA breached

Fires when a ticket in Re:plain breaches its response SLA.

Actions

Create ticket

Creates a new ticket in Re:plain.

Update ticket status

Updates a ticket's status in Re:plain.

Assign ticket

Assigns a ticket in Re:plain to an agent.

Add ticket comment

Posts an internal or public comment on a ticket in Re:plain.

TextSpot Explore TextSpot →

Triggers

Subscriber added

Fires when a new subscriber is added in TextSpot.

Campaign sent

Fires when a campaign is sent from TextSpot.

Subscriber unsubscribed

Fires when a subscriber unsubscribes in TextSpot.

Actions

Add subscriber

Adds or updates a subscriber in TextSpot.

Send campaign

Creates or sends a campaign from TextSpot.

Add to segment

Adds a subscriber to a segment in TextSpot.

Target struggling support contacts with retention segments When an SLA is breached in Re:plain, automatically add the affected customer to a specialized retention segment in TextSpot for tailored follow-up. See details

Subscribe support contacts to marketing campaigns When a new ticket is created in Re:plain, automatically add the customer as a subscriber in TextSpot to ensure they receive critical product updates. See details

See all Re:plain + TextSpot integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Follow up on marketing unsubscribes with support tickets” between Re:plain and TextSpot?

Yes — describe it in the box above and Knit's Integrations Agent researches Re:plain and TextSpot'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.

How does connecting TextSpot and Re:plain help our support team?

It gives support agents full visibility into recent marketing touchpoints and allows team members to handle subscriber churn risks automatically.

Can unsubscribing from marketing emails generate a support ticket?

Yes, when a contact unsubscribes in TextSpot, you can automatically create a ticket in Re:plain so customer service teams can investigate potential churn.