The helpdesk publishes a reception number and an after-hours line. Knowing when to call vs. when to type a ticket means you get help faster.

Open a ticket when

  • The issue can wait an hour
  • You can describe it in writing
  • You'd benefit from a record of the conversation
  • It affects only you or a small group

Tickets create a paper trail. A future technician — including you, three months from now — can read the history and understand what happened.

Call when

  • You can't reach the web form (the helpdesk is the broken thing)
  • It's a confirmed P1 outside business hours
  • You've already submitted a ticket and want to add context the technician needs right now
  • You're not sure if it's a P1 and you need someone to triage it verbally

Don't call to "make a ticket move"

Tickets aren't faster because someone calls about them. Calling the duty desk to ask "any update on TKT-…?" pulls a technician off another ticket — usually yours, since they're now answering a phone instead of working. The right way to push is to comment on the ticket noting any urgency change. The system flags long-quiet tickets automatically.

What to say when you call

Keep it under 30 seconds for the opening:

  1. Your name and site
  2. Existing ticket number if any
  3. The one-sentence summary: "We can't print from Reception" or "Pikasha can't get into her email this morning"
  4. What outcome you need: a callback, a remote session, a tech on site, just an update

The duty desk will either resolve it, escalate it, or open a ticket for the right tech and call you back.

After-hours

Out of business hours, the reception number rolls over to voicemail. The P1 line stays answered. Use it only for genuine emergencies — wrong-numbering it delays response when real emergencies hit, and we audit the call log monthly.