Choosing the right support space
Open support from your user space. The central personal support and the Local Helpdesk are two distinct spaces. The local helpdesk appears only if your profile allows it; otherwise the central space is presented directly.
In the central support, Refresh reloads your requests. More requests loads the next batch. Open a ticket to view its messages; Previous messages loads older exchanges.
Creating a personal request
- Click New.
- Fill in the subject, priority, and message.
- Click Send.
- Check the created ticket and its content.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Subject | Summarizes the request | Required, 255 characters maximum | Call interrupted this morning |
| Priority | Indicates urgency | Low, normal, high, or urgent depending on the options; normal initially | Normal |
| Message | Describes the issue | Required; input limited to 32,000 characters, with an additional limit of 32,768 bytes after formatting | Time, screen, and exact message |
To reply, open the request, complete the message, and send. Attachments are added to a message after it is saved, via the message's commands. Requests and messages wait for the previous operation to complete.
"Message too long (32768 bytes maximum)." requires shortening the text. If sending status is uncertain, check your requests before resending.
Viewing local helpdesk tickets
Select Local Helpdesk. The status filters select tickets; the Open, Urgent, and To follow up counters help organize work.
- Select a ticket.
- Read the requester, exchanges, and attachments.
- Modify Priority or Status if needed: each selection immediately sends a change.
- Write Your reply…, optionally attach files, then click Send.
Text or at least one file is required for the reply. Attach adds files; dropping files also adds them. Remove clears the entire selection or a single file depending on the button chosen. Clicking on the name of an already received attachment downloads it.
Creating a local email
New opens New email.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Sending mailbox | Sending identity | Authorized mailbox; the first one is proposed | Reception |
| Recipient | Person contacted | Non-empty email address | camille@example.test |
| Subject | Subject of the ticket and email | Non-empty text | Follow-up on your request |
| Content | Message sent | Non-empty text | Prepared reply |
| Attach | Adds files | Files accepted by the service | Sample document |
Review the mailbox, recipient, and attachments, then click Send. Cancel closes without creating anything. The button waits for required fields and remains unavailable while the request is in progress.
"Ticket saved locally — no email was sent." means the ticket exists but external sending is not confirmed. Only the delivery response provides the Email sent confirmation.
Tracking an email reply
The email reply panel has its own text and attachments. It accepts up to ten files and 8 MiB combined; each file can be removed. The text is limited to 60,000 characters and must be non-empty.
After sending, check the delivery status: queued, sending, sent, failed, or undetermined. Retry is only offered for statuses that allow it, notably queued or failed. An undetermined status requires verification before resending. A read error on these deliveries offers Retry.
Verifying the result
Review the ticket and the re-read message. For an email, also check the delivery; the existence of a saved exchange is not sufficient on its own.
If it doesn't work
Refresh reloads central support. An unavailable central link should be checked by the person who manages telephony. Errors in the list, detail, and local mailboxes have their own retry mechanism. Before resending a failed message, check the history to determine whether it has already been created.
