Help Desk Testing Scenarios

Get Started. It's Free
or sign up with your email address
Rocket clouds
Help Desk Testing Scenarios by Mind Map: Help Desk Testing Scenarios

1. Reporting

1.1. Tickets closed

1.1.1. by Month

1.1.2. by Category

1.2. Agent metrics

1.3. Open tickets

2. System Setup

2.1. Import agent information

2.2. Import end user information

2.3. Ticket flow process

2.3.1. Unassigned & Assigned

2.3.2. Status

2.4. Change Control

2.4.1. Views

2.4.1.1. Adding & Managing

2.4.1.2. Agent views

2.4.1.3. Customer fields

2.4.2. Tags

2.4.2.1. Adding & Managing tags

2.4.2.2. Automatic ticket tagging

2.4.2.3. Tagging users or orgs

2.4.3. Ticket fields

2.4.3.1. Adding & Managing Fields

2.4.3.2. Requried

2.4.4. Site customization

2.4.5. Widgets and add ins

2.5. Rule based categorization

2.5.1. based on identity ( known end user portal )

2.5.2. based on identity ( known end user email )

2.5.3. based on selected category ( portal )

2.5.4. based on email subject

2.6. Assignment

2.6.1. Agent assign to different agent from an unasigned view

2.6.2. Triggers

2.6.2.1. Auto assign based on selected category

2.6.2.2. Auto assign based on incoming address

2.6.3. Agent assign to different agent from after they have take ownership

2.7. Service Level Agreements Configuration

2.7.1. SLA based on category

2.7.2. SLA based on identity

2.7.3. SLA based on timing

2.7.4. Escalate based on SLA rules

2.7.4.1. Notify Agents

2.7.4.2. Notify Supervisor(s)

2.7.4.3. Notify End User

3. Ticket Management

3.1. Ownership

3.1.1. Agent take ownership from unassigned view

3.1.2. Agent take ownership from another agent

3.1.3. Agent assigns ownership to another agent from their queue

3.1.4. Agent assigns ownership to agent 2 from another agent's view

3.2. Create Tickets

3.2.1. Known end user via email

3.2.2. Known end user via portal

3.2.3. New user via email

3.2.4. New user via portal

3.2.5. Create ticket using mobile device app

3.3. Working Open Ticket

3.3.1. Attach documents to a ticket

3.3.2. Send com to other agents ( private )

3.3.3. Add screen shots to tickets

3.3.4. Send com to other agents ( public )

3.3.5. Make notes about actions taken

3.4. Database Searching

3.4.1. Full text

3.4.2. Additional meta data

3.4.3. Are Attachments indexed

3.5. End User Communication

3.5.1. Email conversation threading

3.5.2. Appropriate from address in reply

3.5.3. Using macros for canned responses

3.5.4. Triggering canned responses based on conditons

3.5.5. Using automation to notify end users of ticket status

3.6. SLA Escalation

3.6.1. Escalate based on a single SLA setting

3.6.1.1. Category

3.6.1.2. Identity

3.6.1.3. Timing

3.6.2. Escalate based on multiple SLA settings

4. Vocabulary

4.1. End User = Customer

4.2. Agent = Someone who works tickets

4.3. Admin = Agent with rights to configure environment

4.4. Organization = Collection of end users

4.5. Group = Collection of agents

4.6. Macro = Predefined action, manually initiated

4.7. Automation = Predefined action, time based initiation

4.8. Trigger = Condition based actions that occur during processing

4.9. Default Ticket Statuses

5. Forum / Knowledge base

5.1. Restricting access

5.2. Publishing content

5.3. Importing existing content

6. Challenges / Concerns

6.1. Limited workflow / approvals

6.2. 2 Security Levels

6.3. System availibility

6.4. System performance

7. External System Integration

7.1. Social Media Integration

7.1.1. Yammer

7.1.2. Twitter

7.2. SugarCRM

7.3. Other links into our systems

7.3.1. Password Resets

7.3.2. Different Types of Inquires

8. New node