No shared catch-all inbox. Every request is read, ranked, and handed to the team that owns it.
A shopper submits a support form. Before any human opens it, AI has read it, assigned a category and priority, and picked the owning team from your list. A real helpdesk ticket is opened, its link saved back to the row, the right Slack channel is notified (urgent ones flagged) and the customer gets an instant confirmation telling them who's handling it and when to expect a reply.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Customer-facing intake: topic, message, optional order number, optional attachment. Publishing it auto-creates the Support Requests response sheet, which the workflow extends with ticket ID, submitted-at, category, priority, assigned team, helpdesk ticket URL, and status.
A reusable template that instantly acknowledges the request so the customer knows it landed and who has it.
Fires on every submission. Classifies the request, logs it, opens the helpdesk ticket, saves its link, notifies the owning team's channel with urgent ones flagged, and confirms with the customer.
You connect your own accounts. Swap any app that offers an alternative at install.
Creates the actual support ticket in the helpdesk, tagged with the routed team and priority. Swap for HubSpot.
Posts each routed ticket into the owning team's channel, flagging urgent ones. Swap for Telegram or Discord.
Sends the customer an instant confirmation their request was received. Swap for Brevo.
The shopper fills the Support Request Form: topic, message, an optional order number, and an optional attachment for screenshots or photos. Submitting it fires the routing workflow immediately; there's nothing for your team to trigger.
A TinyGPT step reads the request and returns three things: category (orders, billing, product, logistics, technical, or other), priority (low, medium, or urgent), and the assigned team, chosen from the team list you configure at install, so it can only route to teams you actually have.
Publishing the form auto-creates its Support Requests response sheet, one record of every submission that ever comes in. The workflow stamps the AI verdict and a status of new onto that same row. There's no second sheet to keep in sync.
A real ticket is created in Freshdesk with the request details, tagged with the routed team and priority, and its link is written back to the row, so the sheet and the helpdesk never drift apart. Prefer HubSpot? Swap at install.
The owning team's Slack channel gets the ticket, with urgent ones flagged for immediate pickup. The point is that nothing lands in a shared queue where everybody assumes somebody else has it. Swap Slack for Telegram, Discord, or Google Chat at install.
An instant Ticket Received Confirmation email goes out naming who's handling the request and the first-response time you've committed to. The customer stops wondering whether it went through, which is most of what support anxiety actually is. Swap Gmail for Brevo or Outlook at install.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
