Every support email arrives already read, sorted, and half-answered.
The recipe watches your shared support inbox. Every new email is read by AI, sorted into one of six categories, scored for priority and sentiment, and logged as a ticket in TinyTables. The questions you answer constantly get a draft reply pulled from your own knowledge base; everything else routes to the right team with the context attached. Your dashboard updates itself as tickets open, move, and close.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Every ticket with its category, priority, sentiment, assigned owner, status, and resolution. This is what the portal dashboard reads from.
Connected to your support knowledge base. Retrieves the relevant material and drafts replies to common questions, for review, or auto-send if you configure it that way.
Fires on inbound email. Reads it, categorizes it, scores priority and sentiment, logs the ticket, then either drafts a reply or routes it to a team.
You connect your own accounts. Swap any app that offers an alternative at install.
Watch the support inbox via the email-received trigger, read each email, and create AI reply drafts in-thread.
Post urgent or non-support tickets to the owning team's channel for immediate pickup. Swappable for Telegram or Discord at install.
The workflow monitors your shared support address, support@yourcompany.com, or whichever you connect, for new mail. Nothing to poll, nothing to check by hand.
The moment a message lands, AI reads its contents. Everything downstream depends on this one analysis: the routing, the priority, and the draft reply all read from it.
Billing, Technical Issue, Feature Request, Bug Report, Account Management, or General Inquiry. A fixed set, deliberately, it's what keeps your reporting comparable week to week.
AI judges how urgent the email is and how the customer sounds, then writes the ticket into TinyTables. An angry billing escalation never sits in line behind a routine how-do-I question.
For the questions you answer constantly (password resets, billing queries, account changes) an AI Agent connected to your support knowledge base retrieves the relevant material and drafts an accurate reply. You decide at install whether it sends automatically or waits for a human to review it.
If the issue needs a person, the ticket is assigned to the appropriate support team based on its category and priority. Nobody works a queue by hand to figure out who owns what.
They get an email or Slack message carrying the ticket details and a direct link to open it in TinyTables.
Every request lives there with its category, priority, assigned owner, and current status. A dashboard in the portal gives authorized users real-time numbers: total open tickets, tickets by category, tickets by priority, and overall support workload.
When the team fills in the resolution column, an email goes to the customer and the ticket is marked closed. The dashboard reflects it immediately, no one updates a status report.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
