1. Reducing response time: Common questions are answered instantly, so customers don’t have to wait in queue.
2. Maintaining consistency: Every interaction follows the same tone, style, and quality.
3. Freeing up human agents: Repetitive tasks are automated, allowing agents to focus on complex or sensitive issues.
4. Providing accurate resolutions: Ticket resolutions are documented automatically, with clarity and knowledge sharing.
5. Lesser SLA violation: Faster responses and proactive resolution updates help teams in meeting their deadlines.

1. Support Specialist
1. Drafts smart and empathetic replies for incoming tickets.
2. Uses the Knowledge Base to provide accurate answers to common customer queries.
3. If no relevant article is found, leaves a private comment, and un-assigns itself so a human agent can take over.
2. Resolution Expert
1. Automates the documentation of ticket resolutions once a ticket is closed.
2. Summarizes key details such as the issue, root cause, fix applied, and customer confirmation.
3. Updates the resolution each time the ticket is reopened and closed again.

1. High-priority tickets can be routed directly to the Support Specialist for faster replies.
   
2. When a ticket status changes to Closed, it can automatically be assigned to the Resolution Expert for resolution text generation and the generated text will be added as resolution every time the ticket has been closed.
   

1. Analyzes incoming tickets using the Knowledge Base.
2. Drafts empathetic replies for standard queries.
3. Un-assigns itself and notifies human agents if it cannot find a suitable answer.

1. Reviews closed tickets to summarize the query, root cause, solution, and fix applied.
2. Updates the resolution tab automatically for future reference.
3. Handles reopened tickets and update resolutions each time.

Zia agents are autonomous. They function as AI teammates embedded into the ticket handling flow, not as separate queues. They do not replace human agents; they augment the existing ticket owners and queue logic.

They primarily focus on performing the following actions:

• Drafting replies for routine queries.

• Capturing and adding resolutions once a ticket’s solution is clear.

Role of support specialist in the ticket lifecycle

1. A ticket enters a department (e.g., General, Billing, Technical). This will depend on the ticket routing rules configured in the department.

2. It is assigned to the Support Specialist as per the configuration in the Zia agent setup.

3. Support Specialist performs the following actions:

• Analyzes the ticket content (subject, description, recent threads).

• Consults your knowledge base and prior context.

• Drafts an empathetic, knowledge‑based reply for common or routine issues.
  

f the information is unavailable in the KB, the following action will take place:

• If the Support Specialist cannot confidently construct a valid answer due to missing or unclear information in the available knowledge base:

• It steps back or unassigns itself from the ticket.

• The ticket renters the routing cycle and is assigned to a human agent depending on the ticket auto-assignment configuration that is setup.

This prevents wrong or low‑quality automated responses. Also, maintains business integrity by looping in human assistance when needed to provide timely support.

Impact on ticket queues

• Once Support Specialist is setup, the ticket will be directly assigned to the Zia agent. Only if it is unable to draft a suitable response the ticket is assigned to a human agent. So the queue and routing logic appears like this:

• Ticket received > assigned to support specialist > KB found > answered.

• Ticket received > assigned to support specialist > KB not found > unassign itself > tickets renters the queue > assigned to human agent.

• You can design processes so that:

• Certain queues (e.g., FAQ or low‑complexity queues) rely heavily on Support Specialist drafts.

• Other queues (e.g., Escalations) rarely use it, focusing on deep human expertise.

Role in the lifecycle

1. After conversations progress and a clear solution emerges, the ticket reaches a resolution stage.

2. The Resolution Expert:

• Identifies the root cause implied by the conversation.

• Captures the final solution in structured form.

• Automatically adds the resolution into the ticket.

Operational effect

• Agents don’t need to spend time writing detailed resolution notes for every case.

• Resolutions become consistent and complete, which benefits:

• Future reporting and analytics.

• Training for new agents.

• Article generation and self‑service improvement.

In relation to queues

• Works across any queue where tickets are resolved.

• Especially valuable in queues with:

• High volume of similar cases.

• Strong need for reporting and analytics based on root cause and resolution.

Zia Agents optimize the work inside the queue, while your existing configuration still controls:

• Which tickets go to which queue.

• Which agent/teams own those tickets.

• How SLAs and escalations are applied.