I recently built this workflow in n8n to automate the first stage of handling customer support requests.

The idea was to take an incoming ticket and let the system handle the repetitive work:

→ Receive the customer request through a webhook

→ Process and structure the incoming data

→ Use an AI Agent to understand the ticket

→ Classify it as Genuine, Spam, or Unclear

→ Route it based on the classification

→ Trigger the appropriate email action

→ Log the interaction in Google Sheets

I also added an Unclear path so that tickets the AI isn’t confident about don’t get blindly processed.

The goal isn’t to remove humans from customer support.

It’s to reduce the repetitive sorting and routing work, so the team can spend more time on the requests that actually need their attention.

Would you automate customer support differently? I’d love to hear how you’d approach it.

The Unclear lane is exactly the right guardrail. I’d add two production checks: redact PII before sending ticket text to the model, and measure false-positive/false-negative rates by category rather than a single accuracy score. Logging resolutions and human overrides back into...

I’ve officially launched StoryMint🚀 Turn one rough idea into a connected visual story - from planning the content to generating and editing the final carousel. You can now support the launch on both platforms: Peerlist: https://peerlist.io/vaibhavgareja/project/connected-story-ai-carousel-generator Product Hunt: https://producthunt.com/posts/storymint-2/maker-invite?code=AO1IjN And if you have a minute, try StoryMint → http://story-mint.com Would genuinely love your feedback. What would you improve?

Looking too nice