Ticket resolver
Drafts an answer to a ticket from your policies and similar solved tickets, with its sources and how sure it is.
How it works
For a new or open ticket, the agent drafts an answer for the person working it. It uses your company's policies, how similar solved tickets of your company were answered and, when the question needs it, the requester's own records such as leave balances, only if you are allowed to see them. Each draft shows its sources and a confidence (high, medium or low). You send it as it is or edit it first; the agent never replies to the requester by itself. Employees asking the assistant on WhatsApp or the web can see what the policies say before they raise a ticket.
A few credits per draft
What it reads
- The ticket and its messages
- Your company's policies
- Answers given on similar solved tickets of your company
- The requester's leave balances, when you may see them
When it starts
- When someone working a ticket asks for a draft
- When an employee asks the assistant before raising a ticket
What it can do
- Draft an answer with its sources and confidence
- Send the answer to the requester (after you confirm)
What it never does
- Reply, close or change a ticket by itself
Safe by design
- One assistant, many agents. Ask the Employee assistant in the app or on WhatsApp; it calls the agents your company has hired that you may use.
- Hired, not switched on. Your admin hires each agent from the catalogue and chooses who can use it.
- Agents propose, people confirm. Anything that changes data, like a leave request, waits for a person to confirm it.
- Same access as the user. An agent sees only what the person asking is allowed to see.
- AI processing in India. Agents run on models hosted in India (AWS Mumbai).
- Budgets and a hard stop. Set a monthly credit limit per agent; agents stop when credits run out.
- Every run recorded. Admins see each run, the credits it used and what it did.
Frequently asked questions
What does the Ticket resolver do?
For a new or open ticket, the agent drafts an answer for the person working it. It uses your company's policies, how similar solved tickets of your company were answered and, when the question needs it, the requester's own records such as leave balances, only if you are allowed to see them. Each draft shows its sources and a confidence (high, medium or low). You send it as it is or edit it first; the agent never replies to the requester by itself. Employees asking the assistant on WhatsApp or the web can see what the policies say before they raise a ticket.
Can the Ticket resolver change data on its own?
No. It asks a person to confirm before it will: send the answer to the requester. It never does the following: reply, close or change a ticket by itself.
How much does the Ticket resolver cost?
A few credits per draft. Credits are a paid add-on to any flowwork.ai plan at ₹100 (US$ 1.19) per 1,000 credits, and new companies get 500 free trial credits for 30 days.
Where is the data processed?
Agents run on AI models hosted in India and see only what the person using them is allowed to see. Admins see every run and the credits it used.
Other agents
Suggests category, priority and group for a ticket and drafts a first reply from similar solved tickets.
Finds the questions your helpdesk keeps getting and drafts FAQ articles for them, from your policies and solved tickets.
Tell it about your company in plain words; it plans departments, offices, holidays, leave, work week, payroll and expenses for you to confirm.