The Post-Meeting Rating Loop Nobody Bothers to Build, And Why It Quietly Multiplies Revenue

Most teams collect feedback by "sending out a survey once a quarter." The response rate is 3%. The data is stale. Half the respondents are people who already churned and the other half are people who would never churn anyway. The signal-to-noise is so bad that the chart at the top of the QBR slide rounds to "we think it's fine."

The teams that actually retain customers do something different. They ask one question after every meeting, route the answer into the CRM, and pipe a follow-up to whoever needs to see it.

Here's the loop, and how to build it inside ThorStack in an afternoon.

The loop

1. Meeting ends.
2. 30 minutes later, the guest gets a single short email: "How did it go?" with five stars.
3. They tap a star. Maybe they leave a comment.
4. The score lands against the booking, the guest's CRM contact, and the event-type analytics.
5. If the score is ≤ 2, an alert fires to the meeting host's inbox and a CSAT-at-risk badge appears on the contact.
6. The Customer Success agent reads the comment and drafts a recovery email.
7. The host approves the recovery email or edits it.
8. The contact's health score is updated.
9. Next week's QBR slide rounds to "we know exactly which 11 customers had a bad meeting this month and what we did about each one."

Most teams stop at step 2 because they're stitching Calendly to Typeform to HubSpot via Zapier and the maintenance is a part-time job. The loop fails on the day someone changes a column name.

How to build it inside ThorStack

You build it once. The whole loop is a single workflow.

Step 1, Create the workflow.

Go to /scheduling/workflows. Click New workflow.

• Name: Post-meeting CSAT
• Trigger: After the meeting ends
• Offset: 30 minutes
• Action: Request a rating
• Applies to: All event types (or scope to specific ones)

Save it. That's the whole technical setup.

Step 2, Let the AI draft the email body.

In the same editor, expand Draft with AI. Type:

"Warm two-line thank-you, mention we'd love any feedback, light tone, sign off as the organizer."

Press ⌘↵. A subject and body arrive with {{guest_name}}, {{event_title}}, and {{rating_url}} already substituted. The default template ThorStack ships with works fine, but a custom one in your voice gets ~25% higher response rates in our testing.

Step 3, Wire the alerting.

The CSAT-at-risk badge and the inbox alert are already built. The platform reads csat = "negative" (any 1- or 2-star rating) and:

• Tags the booking in /scheduling/bookings
• Updates the Insights "Lowest rated" leaderboard
• Decreases the contact's health score
• Surfaces in the Executive Brief the next morning

Step 4, Let the AI draft the recovery email.

This is the only manual step. When a low rating arrives, open the contact, click Draft reply. The Customer Success agent reads:

• The original booking notes
• The rating comment
• The contact's prior 6 months of activity
• The CRM custom fields

And drafts an email in your voice. You approve, edit, or rewrite. It ships.

What the numbers look like

Response rates in production:

• Cal.com → Typeform survey stitched via Zapier: 3–7%
• ThorStack inline rating page (one click on a star): 31–48%

The difference is friction. A one-click star on a public page that loads in 600ms beats a multi-question Typeform every time. Comments are optional, most don't leave one. That's fine. The score alone is the signal.

CSAT-as-leading-indicator:

• Customers who give a meeting ≥4 stars renew at 96%
• Customers who give a meeting ≤2 stars renew at 41%, but the ones who get a personal recovery email within 24 hours renew at 78%.

That gap, 41% vs 78%, is the entire point of the loop.

Why nobody builds it

It's not technically hard. It's organizationally invisible. Nobody owns it. The marketing team thinks it's customer success. Customer success thinks it's sales. Sales thinks it's a product survey. So everyone schedules a quarterly Typeform and goes back to chasing pipeline.

When the scheduling tool, the survey, the CRM, the inbox, and the AI drafter are the same product, the ownership collapses. The workflow is one row in /scheduling/workflows. The dashboard is one tab. The follow-up is one click.

How to try it

Book a demo. Bring a real CSAT comment your team is currently ignoring, we'll show you the recovery email it would write, live.