Free demo: bring the process that lives in a spreadsheet today and watch Tali build it in 30 minutes. Schedule now

Every request with an owner, a deadline and an answer

Email, WhatsApp, website chat, portal and forms land in a single queue, for external customers and for your own team. Every ticket gets an owner and a deadline, and the requester follows it in the portal until it is answered.

Tickets · Support queue

  • #1042 · Duplicate boleto Routed to Finance
  • #1043 · System down Priority raised to urgent
  • #1044 · Password reset Answered with an article
  • #1045 · Invoice question SLA due in 40 business min

2 tickets with SLA at risk

Where support gets lost

  • The request came in through three channels

    Email to one person, WhatsApp to another, a chat message. Three people answering the same thing, or nobody.

  • Nobody knows who has the ticket

    With no owner, the request waits. With two owners, each one thinks the other replied.

  • The deadline is a matter of opinion

    Without SLA by priority and business hours, the customer is the one who notices the delay.

  • The same question, every day

    The answer exists, but every agent writes it again from scratch.

What the service desk does

From the incoming message to the satisfaction rating, for customers and for your own team.

  • Channels

    Every request comes in through the same door.

    • An email address for your inbox to forward to
    • WhatsApp on the company number and website chat
    • Requester portal and public form
  • Queues and SLA

    Deadlines by priority, counted in business minutes.

    • Round-robin or least-load assignment
    • First response and resolution targets
    • Clock paused while the requester has not replied
  • Replies

    Agents answer quickly and in the right tone.

    • Macros with ready replies and actions
    • Suggested articles added as links
    • Internal notes only the team sees
  • Automation

    Rules act without anyone watching.

    • Routing that picks the queue on arrival
    • Triggers on ticket created or updated
    • Time-based automations that remind, escalate and close
  • Help center and portal

    Customers find the answer and follow up without an account.

    • Articles shown before a ticket is opened
    • Portal sign-in with a code sent by email
    • 1 to 5 rating when the ticket is solved
  • Reports

    Support results in numbers.

    • Volume by channel, queue and agent
    • First response time and SLA met
    • Satisfaction, backlog and most-read articles

One ticket, from message to rating

Each step shows who does it: a rule, AI or a person.

Who runs the step Rule AI Person
  1. 1

    Opening Person

    The requester writes by email, WhatsApp, chat, portal or form.

  2. 2

    Routing Rule

    Rules pick the queue and assignment gives the ticket an owner.

  3. 3

    Classification AI

    AI reads the text, raises the priority when the request calls for it and records the type.

  4. 4

    Reply Person

    The agent replies with a macro, an article or the suggested draft, and reviews it before sending.

  5. 5

    Deadline Rule

    The SLA counts in business minutes and pauses while the requester has not replied.

  6. 6

    Rating Rule

    Once solved, the requester is invited to rate it from 1 to 5.

Ask Tali

Everything the service desk screens do, Tali does in conversation, with your permission and confirming before saving.

  • Which tickets in the Support queue have no agent?
  • Summarize ticket 1043 and suggest a reply.
  • Reply to ticket 1042 saying the duplicate boleto was sent by email.
  • How did SLA and satisfaction look this month?

Examples of what you can ask. Tali uses your permissions and confirms before saving.

Where the service desk connects

Questions about the service desk

Does the customer need a TAI account to open a ticket?
No. They write by email, WhatsApp, website chat or the form, and follow up in the portal by signing in with their email and a code sent on the spot.
Does it work for internal support?
Yes. Staff open requests in My tickets, under My space, and the ticket lands in the IT, HR or any other team's queue, with a deadline and a recorded answer.
How is the SLA counted?
By priority, in business minutes within the queue's business hours. The clock pauses while the ticket is waiting on the requester.
Does Tali answer customers?
In the help center, she answers the question with published articles before a ticket is created. On a ticket, she prepares the draft and the reply goes out after a person reviews it.
How do I measure support?
Reports show volume by channel and queue, first response time, resolution, SLA met, satisfaction and the current backlog.

Turn your support inbox into a queue with deadlines

In 30 minutes you see your channels arriving in a single queue, with owners, SLA and Tali classifying what comes in.

👋 Want to see Tali executing a real process from your company?

Schedule a free demo