Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
How-to guide

How to Create Support Groups in an ERP: Teams, Queues and Fair Assignment for Your Service Desk

For service heads and support leads: organise the desk into groups so every ticket reaches a team that can solve it, and work is shared fairly.

A support lead handing out work to her team at a service desk

Knowing how to create support groups in an ERP decides whether your service desk is one noisy inbox or a set of teams that each own their work. A group is a named team with its own queue, its own members and its own way of handing out tickets.

Many Indian service desks start with everyone reading everything. The fastest person answers the easy tickets, a billing question waits because the engineers ignore it, and the one person who speaks Tamil gets every Tamil caller whether or not she is free.

This guide covers how to design groups, an illustrative setup at a Chennai air conditioning service company, and how Apragya's support app runs them.

How to create support groups, step by step

A support group is a named team that owns a queue of tickets. Each group has members, a way of handing out new tickets, and a description of what it handles. Routing puts each new ticket into exactly one group.

Design groups around the work, not the org chart. Breakdown service, installation, billing and spares each need different skills and have different response expectations. Keep a front desk group for tickets that cannot be classified yet, and empty it every day.

Then decide how tickets are shared inside each group. Round robin is fair by count. Least loaded is fair by open work. No automatic assignment suits a small team that picks work together. Tag each group with the skills and languages it covers, so routing can find it.

  1. List the kinds of request your desk receives and who handles each.
  2. Create one group per kind of work, plus a front desk.
  3. Add members in rotation order.
  4. Choose round robin, least loaded or no automatic assignment for each group.
  5. Tag skills, languages and a time zone where they matter.
  6. Write routing rules that send each ticket to the right group and review misroutes weekly.

What a desk without groups costs

Everyone reads everything

Tickets are skimmed many times and owned by nobody.

Uneven load

Quick responders carry the desk while others wait.

Wrong-team delays

A billing query sits with engineers until someone notices.

Language gaps

Callers in a regional language wait for the one person who speaks it.

An example: a Chennai air conditioning service company

Take an illustrative company that installs and services split and cassette units across Chennai and Coimbatore. Its ten-person desk shared one inbox, and customers writing in Tamil about billing often waited two days.

One desk, organised into groups

Incoming tickets

Email, portal and logged calls.

  • Breakdown service

    Least loaded engineer gets the next ticket.

  • Installation

    Round robin across the site team.

  • Billing

    Tagged for billing, Tamil and English.

  • Spares

    Part enquiries, dispatch and returns.

  • Front desk

    Anything not yet classified.

Each ticket lands in one group's queue, and the group decides who picks it up.

Within a month billing tickets in Tamil were answered the same day, because routing sent them to the group tagged for billing and Tamil. The breakdown team's least loaded rule stopped one engineer from carrying half the queue, and the front desk held only what was still unsorted.

Five baskets holding equal piles of folded tickets
Each group's basket held a fair share, and billing tickets went to the team that could answer them.

How helpdesk team setup works in Apragya

Step 1 of 5

Create groups

Name each team, describe what it handles and keep it active or inactive.

  1. Create groups: Name each team, describe what it handles and keep it active or inactive.
  2. Add members: Add people in order; one person can sit in more than one group.
  3. Pick a strategy: None, round robin or least loaded decides how a new ticket finds its owner.
  4. Tag skills and languages: Routing rules can ask for a skill or language instead of naming a team.
  5. Set a time zone: Routing can prefer a team whose working hours are open.

Ticket assignment round robin or least loaded

Round robin shares tickets evenly by count, which suits teams whose tickets take similar time. Least loaded gives the next ticket to the member with the fewest open tickets, which suits teams where some jobs run for days. Leaving assignment off suits small teams that pick work together.

A shared inbox, compared with Apragya

FeatureShared inboxApragya support groups
Who sees a ticketEveryoneThe group's members
Who owns itWhoever replies firstSet by the group's strategy
FairnessBy speedBy count or by open load
Skills and languageKnown informallyTagged on the group
Staff on leaveStill sent ticketsPaused without losing history

Checked against public information on 16 September 2026.

Support queue management that holds up

Rename without breaking

Groups can be renamed or deactivated while old tickets keep their link.

Leave without disruption

A member can be paused and returns to the same place in the rotation.

Shift handoff

Unresolved tickets can move to the next shift's group on a schedule.

Access by role

Role-based access decides who may reassign, reopen or raise priority.

AI you can put to work

Agents run on ticket events and save their output on the ticket.

Audit log

Owner and group changes are logged.

Groups work with routing rules and SLA policies. Read the support groups software page, and for an AI view of routing, AI agent for support ticket routing.

Getting started

  1. Write down the teams that already exist on your desk.
  2. Create a group for each, plus a front desk for unsorted tickets.
  3. Add members in the order you want the rotation to run.
  4. Choose an assignment strategy for each group.
  5. Tag skills and languages, then point routing rules at them.

Two or three groups are enough for most small desks. Add more only when a queue clearly needs its own people.

What it costs to start

INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus Support and Ticketing
2,000
AI Credits a month
Included on Starter
Free
Up to 3 users
CRM, HR and Vendor Onboarding

Creating support groups, answered

How many groups should a small desk have?
Usually the two or three teams that already exist, plus a front desk for anything not yet classified.
Can one person belong to more than one group?
Yes. They work both queues, and each ticket still records its group.
What happens when a member goes on leave?
Mark the membership inactive. They leave the rotation, keep their history and return to the same position.
Can routing ask for a skill instead of a team?
Yes. A rule can name a required skill, so it keeps working when teams are reorganised.
What does it cost to start?
Support and Ticketing is available from the Starter plan, INR 3,999 a month for up to 10 users, which includes CRM and HR plus a choice of enterprise apps and 2,000 AI Credits a month. Pro, at INR 7,999 a month, covers 25 users and every enterprise app.

Give every queue a team behind it

Create your groups, add members and choose how tickets are shared.