Timer Management

Hold & Pause

Pause ticket timers when waiting for user responses or external information. SLA tracking stays accurate.

ticket-1234
Online
Moderatorused4:22 PM

/tickethold

Support BotBOT4:22 PM

⏸️ Ticket On Hold

This ticket has been placed on hold. Auto-close timers and SLA tracking are paused.

Held By

Moderator

Timers

All paused

Channel

Locked for user

Use /ticket hold again to resume this ticket

Message #ticket-1234

Illustration only — actual interface and behavior may differ

How Hold Works

Three Steps to Pause

Put a ticket on hold, pause all timers, and lock the channel — all with a single command.

1

Staff Runs /ticket hold

A staff member uses the /ticket hold command. The ticket is instantly marked as on-hold.

2

Timers Pause

Auto-close timers, inactivity warnings, and SLA tracking all pause automatically. No manual intervention needed.

3

Channel Locks

The user can still read the channel but cannot send messages. Staff retain full access to coordinate internally.

Ticket System

Hold Tickets

Place a ticket on hold to pause inactivity timers and SLA tracking. The ticket remains accessible but won't be auto-closed.

Hold with an optional reason visible to the user
Resume with a single click or command
Track hold duration in analytics
Configurable hold notification messages

Active Tickets

ticket-1234

On Hold — Waiting for internal approval

2h ago

ticket-1235

Active

5m ago

ticket-1236

On Hold — Escalated to dev team

1d ago

ticket-1237

Active

12m ago
In Action

Hold Notifications in Channel

When a ticket is placed on hold, a clear notification is sent to the ticket channel. The user knows exactly why their ticket is waiting and that staff is still working on it.

ticket-1234
Online
Support BotBOT2:10 PM

⏸️ Ticket placed on hold by Sarah — Escalated to development team for bug investigation.

Sarah2:11 PM

The dev team is looking into this. We will get back to you within 24 hours.

Support BotBOT2:11 PM

🔒 This channel is now locked. Only staff can send messages while the ticket is on hold.

Message #ticket-1234

Illustration only — actual interface and behavior may differ

Ticket System

Timer Pause

When a ticket is on hold, all timers freeze — auto-close, reminders, and SLA counters. They resume the moment the hold is released.

Auto-close timers freeze instantly
Inactivity warnings suppressed
Hold time excluded from SLA metrics
Timers restore exactly where they paused

Auto-Close Timer

Paused

Timer ProgressPaused at 12h / 48h
Inactivity WarningPaused
SLA Response TimerPaused at 45m / 2h
In Action

Seamless Resume Flow

When the wait is over, resume the ticket with a single click or the /resume command. The channel unlocks, timers restart from where they paused, and a notification informs the user that their ticket is active again.

ticket-1234
Online
Sarahused10:30 AM

/tickethold

Support BotBOT10:30 AM

▶️ Ticket Resumed

This ticket is now active again. All timers have been restored.

Hold Duration

20h 19m

Resumed By

Sarah

Timers

Restored

Channel

Unlocked

Sarah10:31 AM

Good news! The development team found and fixed the issue. Let me know if everything works now.

Message #ticket-1234

Illustration only — actual interface and behavior may differ

Ticket System

Channel Lock

Optionally lock the ticket channel while on hold, preventing new messages until a staff member releases the hold.

Permission Matrix

Staff
Full access
Ticket Creator
Read only
Added Members
Read only
ticket-1234
Online
Support BotBOT3:00 PM

🔒 Channel Locked

This ticket is on hold. The channel has been locked so only staff can send messages. The user can still read the conversation.

Reason

Waiting for third-party response

User Access

Read only

Staff Access

Full access

Click Resume Ticket when ready to continue

Message #ticket-1234

Illustration only — actual interface and behavior may differ

Impact

Why Hold Matters for Metrics

Without hold, legitimate waiting time inflates your response metrics. Here is the difference.

Without Hold

Avg. Resolution Time26h 45m
SLA Compliance62%
False Auto-Closes12 / week

Wait time from users and third parties skews all metrics.

With Hold

Avg. Resolution Time4h 12m
SLA Compliance97%
False Auto-Closes0 / week

Hold time tracked separately. Only active support time counts.

Hold & Pause at a Glance

Everything you need to manage waiting tickets professionally.

1 cmd

To Hold a Ticket

100%

Timer Accuracy

Instant

Channel Lock Speed

Full

Audit Logging

Use Cases

When to Use Hold

Waiting for User Input

The user needs to provide screenshots, logs, or additional details. Hold the ticket so it does not auto-close while they gather information.

Third-Party Escalation

The issue requires input from a developer, external team, or service provider. Hold while you wait for their response.

Scheduled Follow-Up

You need to check back later — after a deployment, update, or event. Hold prevents false inactivity warnings.

Frequently Asked Questions

Any staff member with access to the ticket can place it on hold. Hold/unhold actions are logged.

No, users can still send messages by default. When they do, the ticket can automatically resume from hold. Channel lock is an optional setting.

Ready to Transform Your Support?

Set up professional support in minutes. No coding required. Start with a free trial and explore all features.

This offer is only available for selected servers that have never purchased a plan and never used a free trial before. You do not need to enter any payment information to start the trial and the trial automatically expires after 14 days. Servers that have been deleted from SCNX previously are not able to participate.