KogniFeed
Try AI interviews free
← Back to templates

Workflows

Post-interaction CSAT

Short CSAT with mandatory score and interaction type, plus one meaningful follow-up when expectations were missed — ideal for receipt, email, or API triggers.

A star alone rarely tells ops what to fix. Low CSAT without drivers becomes a KPI theater; high CSAT without quotes hides fragile wins.

This template asks for a CSAT score and interaction type, then the Insight agent digs into why — especially when the score is middling or low. Blueprint fields keep waves comparable after you change packaging, scripts, or SLAs.

Trigger from receipt emails, ticket-close webhooks, or delivery events so feedback arrives while memory is fresh.

Best for

  • Ecommerce and marketplace CX
  • Support and success after ticket close
  • Ops teams comparing process changes

Outcomes

  • CSAT with explained drivers
  • Resolution and fulfillment gap themes
  • Comparable waves after process changes

How it works

  1. 1

    Tie the invite to an event

    Checkout, delivery, or ticket close. Pass interaction type and order/ticket id as metadata when your stack allows.

  2. 2

    Require score + type fields

    Keep CSAT and interaction type as required blueprint slots so dashboards stay clean.

  3. 3

    Probe only when it matters

    Pulse pacing with a stronger follow-up on low scores protects completion rates while still explaining drivers.

  4. 4

    Compare before/after process changes

    Tag waves by experiment or release. Use hub compares instead of gut feel from ticket volume.

Sample questions

  • QOverall, how satisfied were you with that interaction?
  • QWhat kind of interaction was it — purchase, delivery, support, or something else?
  • QWhat went better or worse than you expected?
  • QWhat would have made this a clear win for you?

Setup tips

  • Send within hours of the event; next-day surveys lose detail.
  • Keep the first screen under a minute; save deep probes for detractors.
  • Do not combine relationship NPS and transactional CSAT in one study.

Frequently asked questions

CSAT vs NPS — which template?
Use this after a specific interaction. Use Relationship / NPS pulse for overall loyalty on a cadence. Mixing both in one interview confuses participants and charts.
Can we trigger this from our helpdesk?
Yes. Use CRM/webhooks or the REST API when a ticket closes. Pass agent team or channel as metadata for hub filters.
What if scores are high but themes are negative?
That is exactly why explained CSAT matters. Treat quotes and themes as leading indicators even when averages look fine.