It answers on email and your site, looks up the order, remembers the customer, closes what your rules allow, and hands you the calls that are yours.
One support agent that resolves tickets on email, web chat and inside your product. Plain-English rules decide what asks you first.
It answers on the inbox and website you already have, resolves the ticket within rules you wrote in plain English, remembers the customer next time, and asks you only when the call is yours.
Most AI support tools are a smarter FAQ. They answer what they can find in your help center and route everything else to a queue you still have to clear.
Fasrad's support agent reads the ticket, looks up the customer and the order in your records, decides the right outcome, and carries it out inside rules you wrote in plain English. That might be the refund, the reissued invoice or the plan change. The customer gets an answer and an action. You get a one-line summary, or nothing at all when nothing needed you.
It works on the channels you already run. Give it a support inbox and it answers every email in the thread it arrived in, in the customer's language. Drop it on your website and it handles the same questions in chat, captures who it's talking to, and follows up by email if the answer needs a lookup. It's one agent with one memory, so the customer who wrote in about a late delivery in May gets recognized in September, and the reply reads like someone who remembers.
What it does with a typical night's tickets:
The approval flow is what makes it safe to run unattended. Rules like 'refunds over $50 ask me,' 'never promise a delivery date we can't see,' or 'anything legal goes to me untouched' become standing instructions it applies to every ticket. When a rule fires, you get the prepared action and a button (Approve, Offer exchange, Let me reply) on Telegram or in chat. One tap and the customer has their answer.
Every ticket lands in the built-in CRM as a contact, a summary and a category, so it can answer 'why are we getting so many size refunds?' with real counts.
Buyers usually compare these adjacent jobs before choosing an AI agent.
Email and web chat out of the box. It can run a support inbox itself, or work in your own inbox where it drafts and you approve, and there's an embeddable chat for your site. It's one agent across all of them, so the customer who chatted yesterday is recognized when they email today. Telegram and phone are the same agent too.
It acts. It looks up orders and accounts in your records or through your API, issues refunds and credits within the limits you set, reissues invoices, changes plans, books calls, and files bugs to your team. Answering from your help docs is where it starts.
You write the rules in plain English: 'refunds over $50 ask me,' 'never promise dates,' 'legal threats come straight to me.' When a rule fires, the agent prepares the action and holds it, and you get a summary and an Approve button on Telegram or in chat. It closes everything else on its own and logs every ticket so you can review what it did.
Yes. Every conversation is filed in the built-in CRM as a contact with a summary, and the agent keeps memories about people: the credit you gave in May, that they prefer short replies, that their last three orders were all size M. The next reply reads like it came from someone who remembers, because it did.
It hands the ticket to you on Telegram, email or chat with the full context: who, what, and what it already tried. The customer hears who has it and when they'll hear back. You reply in your own words, or tap the draft it prepared, and the customer gets a real answer from a real person.
Yes. It can run alongside Zendesk, Freshdesk, Help Scout, or Gorgias through their APIs, reading tickets, posting replies and updating status. For a small team it can replace the helpdesk entirely, since it keeps its own contacts, ticket log, and categories. Most customers start with the inbox and add the connection later.
Start with a 7-day free trial. Full access, no card needed. Then $49 per month. There are no per-resolution fees, per-seat charges or conversation caps, so the price is the same whether it closes ten tickets or a thousand. It's in public beta and takes about four minutes to connect.