Pipeline architecture diagram, feedback to owner routing.
Sentiment & Routing Pipeline
Hundreds of feedback entries a week, sorted without hands.
2025 · Automation architect
Domain
AI & Automation
Timeframe
2025
Role
Automation architect
Outcome
Manual review eliminated
The backstory.
A team was reading everything. Every survey response, every support note, every form submission, one by one.
It was careful work done by people who had better work to do.
Zapier classification workflow.
The situation.
By the time feedback reached the person who could act on it, the moment had passed. Patterns were invisible because nobody could hold a week of entries in their head.
The backlog was not a staffing problem. It was a missing system.
What was built.
An end-to-end pipeline. Entries land, get classified for sentiment and topic, and route to the owner responsible for that category with the context attached.
Everything writes to a single sheet of record, so trends are readable at a glance instead of reconstructed at quarter end.
Nobody sorts anything anymore. People respond instead.
Placeholder: Classified and routed dashboard, after.
Placeholder: Unsorted feedback inbox, before.
Stack
- Zapier
- Gemini
- Google Sheets
- Slack
Gallery.
Outcomes.
Hours → minutes
Time from entry to owner
100%
Of manual sorting removed