Creating Tickets

Tickets can be created by clients through the portal or by internal team members on behalf of clients or for internal escalations.

​

Who can create tickets

​

Clients

Through the client portal:

• Submit support requests
• Ask questions
• View and track their tickets
• Add comments and attachments

​

Internal team members

All team members can create:

• Support tickets (on behalf of clients)
• Internal escalations
• Questions (on behalf of clients)

​

Creating internal tickets

​

Starting a new ticket

​

Ticket type selection

Choose the appropriate type: Support:

• Technical issues
• Bugs or problems
• Something broken
• Need a fix

Escalation:

• Client relationship concerns
• Delivery issues
• Quality problems
• Service complaints

Question:

• Information requests
• How-to questions
• Clarification needed
• No work required

​

Support ticket fields

​

Required fields

All support tickets need:

• Client - Which client this affects
• Title - Brief, clear description
• Priority - P1 through P4 based on impact

​

Recommended fields

For better context:

• Description - Full details of the issue
• Stores affected - Which client sites/stores impacted
• Desired outcome - What resolution looks like

​

Optional fields

Additional information:

• Attachments - Screenshots, logs, references
• Contact users - Specific client contacts to involve

​

Priority guidelines

Choose priority based on impact:

​

Escalation ticket fields

​

Purpose

Internal escalations flag concerns:

• Scope creep
• Delivery delays
• Quality issues
• Service complaints

​

Required fields

All escalations need:

• Client - Which client this concerns
• Title - Brief summary of concern
• Escalation type - Select one or more types
• Priority - Severity of concern
• Description - Full context
• Action taken - Steps already attempted

​

Escalation types

Select all that apply: Scope Creep:

• Client requesting work beyond retainer
• Unclear boundaries
• Expanding requirements

Delivery Delay:

• Work falling behind schedule
• Missed commitments
• Unrealistic expectations

Quality Issue:

• Work not meeting standards
• Repeated bugs
• Client dissatisfaction with output

Service Complaint:

• Communication problems
• Relationship concerns
• Client expressing frustration

​

Question ticket fields

​

Purpose

Simple information requests:

• How does X feature work?
• Where can I find Y?
• What is the status of Z?
• Can you clarify something?

​

Required fields

All questions need:

• Client - Who is asking
• Title - The question
• Priority - Urgency of answer

​

Recommended fields

For context:

• Description - Additional details
• Contact users - Who to respond to

​

Quick workflow

Questions have a simplified workflow:

• New → Accepted → Resolved
• No scheduling or assignment needed
• Answer provided directly
• Resolution summary contains the answer

​

Client portal submission

​

How clients submit

Through the client portal:

​

Client ticket fields

Clients provide:

• Title (required)
• Description (optional but recommended)
• Priority (required, P1-P4)
• Stores affected (optional)
• Desired outcome (optional)
• Attachments (optional)

​

After submission

When client submits:

• Ticket created with “New” status
• Origin marked as “client”
• CSM for that client notified
• Managers notified
• Appears in Help Desk list

​

Notifications

​

Who gets notified

New client ticket:

• CSM assigned to client
• Managers
• On-call PM (if configured)

New internal ticket:

• Depends on type and priority
• High priority → broader notification
• Escalations → management team

Ticket assigned:

• Assigned team member
• PM who assigned it

Ticket resolved:

• Client (if client-submitted)
• Relevant team members

​

Notification channels

Notifications sent via:

• Email
• In-app notifications
• Visible in notifications panel

​

Best practices

​

Common mistakes

​

Mistake 1: Wrong ticket type

Problem: Creating support ticket for a question Impact:

• Goes through full workflow unnecessarily
• Takes longer to get answer
• Wastes scheduling capacity

Solution: Use Question type for information requests

​

Mistake 2: P1 for everything

Problem: Marking all tickets as P1 Impact:

• Teams ignore priority
• Real emergencies not recognized
• Boy-who-cried-wolf effect

Solution: Reserve P1 for true emergencies only

​

Mistake 3: Insufficient detail

Problem: Title only, no description Impact:

• PM can’t understand issue
• Back-and-forth in comments
• Delays resolution

Solution: Provide context upfront in description

​

Mistake 4: Creating task instead

Problem: Creating ticket for planned work Impact:

• Loses scheduling benefits of tasks
• Not integrated with roadmap
• Harder to track against quotes

Solution: Use tickets for reactive support, tasks for proactive work

​

Troubleshooting

​

Next steps