Add attachments to a ticket

Support Tickets and Chat

Add attachments to a ticket

Upload screenshots or files so support can see exactly what you see.

What this function does and why it matters

Add attachments to a ticket is part of the Support Tickets and Chat workflow in ClassRoom.Study. The function exists to help the right stakeholder move from intention to action without guessing which page, button or record controls the outcome. Upload screenshots or files so support can see exactly what you see. In daily use this means a learner can understand what to do next, a creator can prepare learning material with fewer support questions, a company admin can manage people and evidence with a cleaner audit trail, and a platform admin can see whether the process is working at scale. For users, support manuals show the fastest route to help: self-serve the assistant, then raise a tracked ticket with attachments when a human is needed. For support teams, structured tickets and escalation keep evidence and ownership clear.

The benefit is not only convenience. This area protects operational consistency. It makes status visible before a person acts, keeps related records connected, and gives teams a repeatable way to train new users. When a company has many learners, courses, invoices, schedules or live sessions, small navigation mistakes become expensive. A clear manual gives every person the same mental map: where to start, what to check, what each control changes, and what proof should exist after the action is complete. Use this page as the plain-language reference when onboarding new staff, answering support tickets, checking compliance, or preparing screenshots for a branded internal guide.

Benefits and features

• Shares visual evidence that speeds up diagnosis.

• Supports common image and document types.

• Keeps everything attached to the ticket record.

Visual flow

The high-level path from start to finish. Each box is a stage; the arrows show the order. Use this as a quick mental map before the detailed steps below.

Open ticket

→

Attach file

→

Confirm upload

→

Submit

Mind map

The feature at the centre, with the related toggles, settings and sub-controls branching out. Use it to see everything this area touches at a glance.

Ticket attachments

◆Use for

• Screenshots

• Documents

◆Benefit

• Faster diagnosis

◆Stored

• On the ticket

Upload a screenshot for the Add attachments to a ticket overview here.

Video placeholder

In Admin Settings > System Manuals, edit this article and use the video button to paste a YouTube URL. The saved article will render the video inline for visitors.

Step-by-step navigation

Follow the steps in order the first time. After you understand the flow, you can jump directly to the control you need. For training purposes, replace every screenshot placeholder with the exact screen your users will see in production, including the correct company, role or learner context.

1. Step 1: Open your ticket or the new-ticket form.

   

2. Step 2: Use the attach control to add a screenshot or file.

   

3. Step 3: Confirm the file uploaded.

   

4. Step 4: Submit or reply with the attachment included.

   

Good operating habits

Work from the smallest panel that gives you the control you need, confirm status chips before acting, and use exports or detail pages when you need an audit trail. If an action changes billing, access, certificates, AI usage, invitations, public content, or live session attendance, pause long enough to confirm the company, learner, course and date context. Add notes where the interface provides them. Use filters before exporting so the exported CSV answers a specific question. When training a novice, ask them to say what changed after each step; if they cannot explain the result, they should return to the record and check the status, timestamp, or linked activity before moving on.