Support Automation #3366: NPS Collection with Typeform + Airtable + Chargebee

Problem

Agents switch between Typeform and Airtable to complete nps collection, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

Typeform ticket event → classify/priority rules → update Airtable → ping channel in Chargebee.

Tools Used

• Typeform
• Airtable
• Chargebee

Setup Steps

1. Create credentials for Typeform, Airtable, Chargebee in your orchestration platform.
2. Define the nps collection trigger in Typeform.
3. Map required fields from Typeform to Airtable.
4. Add error handling appropriate for a Hard workflow.
5. Run a test payload, then enable production execution (~14 min typical setup in our dataset).

Expected Outcome

• A repeatable nps collection path for support teams.
• Less context switching between Typeform and Airtable.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Low ROI tier · Hard difficulty · ~14 min setup estimate.
• Reduces manual nps collection steps between Typeform, Airtable, Chargebee.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Troubleshooting

• Confirm ticket status enums match between helpdesk and downstream tools.
• Test reopened tickets to avoid duplicate threads.
• Map priority and assignee fields explicitly.