Expertque

The lifeguard team - Ticketing

Every ticket has an owner, a priority and a timer.

Assignment rules send each ticket to the right person. Priorities and SLA timers decide what comes next. Escalations step in before a promise is broken.

Tickets - My queue
Priya is viewing #48207
#48213

Payment debited twice

Billing

Urgent

06:12

#48207

Damaged on delivery

Returns

High

14:40

#48196

Invoice GST number wrong

Billing

Normal

1:42:00

#48188

Warranty claim - LED TV

Service

Normal

3:05:00

SLA policy - Priority

  • First reply15 min
  • Next reply1 h
  • Resolve8 business hours

Escalate to team lead at 80% of the timer

0

priority SLA breaches on sale day

8,400

tickets handled by 42 agents

80%

default escalation point

24/7

timers that respect your hours

What you get

The rules a great support lead would set, running every second.

Set them once. Expertque applies them to every ticket on every channel, day and night.

Assignment rules

Route tickets by topic, channel, language, customer tier, skill or brand.

  • Round-robin or load-balanced
  • Skip agents who are away or at capacity
  • Telugu tickets to Telugu speakers

SLA policies

First reply, next reply and resolution targets per priority, with business hours and holidays.

  • Different targets for VIP customers
  • Timers paused while waiting on the customer
  • Live countdown on every ticket

Escalations

At 80% of a timer, the ticket moves up the queue and the team lead is alerted.

Collision detection

See who is viewing or typing so two agents never reply to the same customer.

Priorities and tags

Urgent, high, normal and low, set by rules, keywords or the AI's reading of the message.

Parent and child tickets

Link many customer tickets to one outage or courier delay and update all of them at once.

Merge and split

Combine duplicates or split one message with two problems into two tickets.

Automations

If-this-then-that rules for tagging, closing, follow-ups and reopen on reply.

Custom fields and forms

Capture order IDs, product models or policy numbers as required fields before a ticket closes.

CSAT after every resolution

A one-tap rating on the same channel the customer used, with comments sent back to the ticket.

How it works

How a ticket moves from wave to shore.

1

Arrives and is tagged

The message is read, tagged by topic and language, and given a priority.

2

Goes to the right agent

Assignment rules pick an available agent with the right skill and lightest load.

3

The timer runs

SLA countdown is visible to the agent and the lead. At 80% it escalates.

4

Resolved and rated

The customer gets a CSAT question and the ticket closes, or reopens on reply.

Questions

Common questions

Yes. Each team can have its own hours and holiday calendar, including regional festivals. Timers pause outside those hours and while you wait on the customer.

Sunset on the beach

No ticket left drifting.

Set up teams, priorities and SLA targets in an afternoon and see every ticket's timer before the next rush.

  1. Day 1

    Connect email, WhatsApp, chat and social

  2. Day 2

    Import policies and help articles

  3. Day 3

    Set SLAs and go live

Beach board

18:42 - end of shift

EVERYONESAFE

0

in queue

0

SLA breaches

4.6

CSAT