Installs in ~2 min· 3 assets · 8 steps

Get every piece of feedback to the team that owns it, same day

Every piece of feedback reaches the team that owns it, the day it arrives.

Feedback comes in through a form, or gets imported from the places you already collect it. AI classifies each response, reads the sentiment, groups the recurring themes, and routes it to the team that can actually act: Product, Engineering, Support, or your marketing testimonial pile. At the end of every week it writes the trend report for you.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Customer Feedback is submitted
Every run starts from one submission.
Transform
AI Classify & Route
AI reads the input and returns a structured result.
Transform
Save Analysis + Team
Action
Route to Team Channel
Action
Email Stakeholders
What gets built

3 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormCustomer Feedback

form for collecting feedback directly. Feedback imported from other sources lands in the same table. Publishing it auto-creates the Customer Feedback response sheet, the single system of record.

WorkflowAnalyze & Route Feedback

Fires on each new response. Classifies it, reads sentiment, groups it with related feedback, and routes it to the owning team.

WorkflowWeekly Feedback Summary

Runs weekly. Emails stakeholders the top requested features, common bugs, sentiment trends, and recurring complaints, with a link to the table.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Feedback Notification
Slack *

Posts every routed, AI-classified feedback item to a shared team channel with its category, assigned team, and a pointer to the sheet. Swap for Telegram, Discord, or Google Chat.

Weekly Summary
Gmail *

Emails the weekly AI feedback summary to stakeholders.

How it works

Step by step, once it is running.

  1. 01
    Feedback Comes In

    A form collects feedback directly, or you import it from the multiple sources you already use. Either way it ends up in one place instead of four.

  2. 02
    Every Response Is Stored

    Each submission is written to TinyTables automatically.

  3. 03
    AI Classifies Each Submission

    Every response is sorted into one or more categories: Feature Request, Bug Report, Complaint, Praise, or General Feedback. One piece of feedback can legitimately carry more than one, and it's tagged with all of them.

  4. 04
    Sentiment and Recurring Themes Surface

    AI determines the customer's sentiment and groups similar feedback together to identify recurring trends and frequently reported issues, so twelve people describing the same frustration read as one trend, not twelve unrelated tickets.

  5. 05
    It Routes to the Team That Can Act

    Feature Requests are assigned to the Product Team. Bug Reports go to Product/Engineering. Complaints go to Customer Support. Positive feedback is stored for future testimonials and marketing opportunities.

  6. 06
    Ownership and Progress Stay Visible

    The categorized feedback sits in TinyTables where teams track ownership, status, and resolution progress from one centralized dashboard.

  7. 07
    A Weekly Trend Report Writes Itself

    At the end of each week, AI generates a summary highlighting the most requested features, the most commonly reported bugs, customer sentiment trends, and recurring complaints. It's emailed automatically to the relevant stakeholders with a link to the TinyTables.

  8. 08
    Teams Close the Loop

    As each item is reviewed, addressed, or resolved, team members update its status directly in TinyTables, giving the whole organization visibility into where customer feedback actually stands.

What you walk away with
FAQ

Questions about Customer Feedback Analysis.

What do I need to connect?
Slack and Gmail are both required. Slack carries each classified item to the team channel that owns it, and Gmail sends the weekly summary to stakeholders. Telegram, Discord and Google Chat are supported swaps.
How is the feedback classified?
Each response gets a sentiment, a primary feedback type, categories, a theme, an urgency and a short summary. Those are written back as columns on the same response sheet the form created, alongside assigned team, status and resolution notes.
Where does the feedback come from?
A short Customer Feedback form you share by link or embed in-app. It captures a star rating, free-text feedback, a product area and an optional email, which is enough structure for classification without making the form a chore.
What is in the weekly report?
The Weekly Feedback Summary workflow emails stakeholders the top requested features, common bugs, sentiment trends and recurring complaints, with a link back to the records. It runs on a schedule, so nobody has to assemble it.
Can we track whether feedback was acted on?
Yes. Assigned team, status and resolution notes live on the same sheet as the feedback itself, so closing the loop is a status change on the original record rather than a separate tracker someone has to remember to update.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.