Add respondents to follow-up surveys when tickets close

When a ticket status is updated to resolved in ArtiBot.ai, add the customer as a respondent in 97Display to send a satisfaction survey.

Try:

See all 97Display + ArtiBot.ai 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.

97Display Explore 97Display →

Triggers

New form response

Fires when a form is submitted in 97Display.

Survey completed

Fires when a respondent finishes a survey in 97Display.

Response updated

Fires when an existing response is edited in 97Display.

Actions

Create or update form

Creates or updates a form or survey in 97Display.

Retrieve a response

Looks up a specific form response in 97Display.

Add a respondent

Adds a respondent or contact to a form in 97Display.

ArtiBot.ai Explore ArtiBot.ai →

Triggers

New ticket created

Fires when a new support ticket is created in ArtiBot.ai.

Ticket status changed

Fires when a ticket's status changes in ArtiBot.ai.

Ticket assigned

Fires when a ticket in ArtiBot.ai is assigned to an agent.

SLA breached

Fires when a ticket in ArtiBot.ai breaches its response SLA.

Actions

Create ticket

Creates a new ticket in ArtiBot.ai.

Update ticket status

Updates a ticket's status in ArtiBot.ai.

Assign ticket

Assigns a ticket in ArtiBot.ai to an agent.

Add ticket comment

Posts an internal or public comment on a ticket in ArtiBot.ai.

Generate support tickets from form responses When a customer submits a web form in 97Display, automatically create a detailed support ticket in ArtiBot.ai for team review. See details

Attach survey updates as comments on open tickets When a customer updates an existing survey response in 97Display, automatically post the new feedback as a comment on their ticket in ArtiBot.ai. See details

See all 97Display + ArtiBot.ai integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Add respondents to follow-up surveys when tickets close” between 97Display and ArtiBot.ai?

Yes — describe it in the box above and Knit's Integrations Agent researches 97Display and ArtiBot.ai'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 are survey responses transferred into support tickets?

Submitting a completed survey in 97Display automatically creates a new ticket in ArtiBot.ai containing all the respondent's answers.

Can ticket updates prompt custom survey distributions?

When a ticket status changes in ArtiBot.ai, you can automatically add the customer as a respondent in 97Display to collect feedback.