Closing Ticket Due to No Response Templates: Sample Wording for Every Attempt and Every Channel

You asked the requester a question twelve days ago. The ticket has gone silent, and it's still one of the oldest in your queue. Every message you could send feels either too soft to work or too blunt to send to a coworker. Close it quietly and the person may write back next month to say they never saw your question, or your report may credit you with a fix nobody checked. A closing ticket due to no response template helps most when the message, the status and the report all say the same thing about what happened.

Below you'll find copy-ready wording for each attempt by email, chat and phone, along with the closure message and the ticket note. After that come how many days to wait, how to word a follow-up so people answer, the closure label that keeps your reports accurate, and the tickets you shouldn't close this way.

Help Desk Agents Contacting Customers for Ticket Responses

Key Takeaways

• Two kinds of silence need different wording and labels: Silence after a fix you delivered can end as resolved, and silence while you wait for information can't.
• Three attempts is a published pattern: Most published schedules use three attempts by email, chat or phone and close a ticket anywhere from three business days to a week or more.
• The closure label decides what your reports say: Closing a ticket as resolved while you were still waiting on information can raise First Contact Resolution (FCR), the share of tickets fixed on the first contact. It can also add a resolution time for a ticket nobody resolved, so give those closures their own label and keep them out of your count of first-contact fixes and your average resolution time.
• Some tickets shouldn't close on a timer: Five kinds of ticket, among them security issues, referrals and tickets where IT owes the next move, need a person's decision.

Closing Ticket Due to No Response Template: Copy-Ready Example Messages for Each Attempt

A no-response closure, sometimes called closing a ticket due to inactivity, can run on three attempts, one closure message and one ticket note. Every attempt repeats the same three facts:

1. The ticket
2. The one thing you need
3. The date the ticket will close

Every sample message below is free to copy into a Word document, an Excel sheet or your ticketing system's macro library. If you delivered a fix and heard nothing, skip to "When You Delivered a Fix and Heard Nothing." If you only need the closing ticket email, go straight to "The Closure Message" below.

Which Situation Are You In?

Match your ticket to a row first, because each situation gets different wording and a different label.

The Sequence at a Glance

The following table counts business days from the day you asked the question, so a question asked on Monday gets attempt 1 on Wednesday. Before you send attempt 1, check the ticket against the five kinds listed later in this article, which we call the exemption list, because attempt 1 promises a closing date. Pick the closing date when you send attempt 1 and use it in every attempt that follows. If a step slips, move the closing date and say so in the next message.

These days are a starting point, and the schedules section below shows how to adjust them. Counting each part of attempt 3 separately, the requester hears from you up to five times by business day 5, or three times if email is your only channel.

• Attempt 1: The Email Nudge

  Send this email template on business day 2 as a friendly reminder. When you first ask the question, set a follow-up date on the ticket for that day. The subject line names the ticket and the one thing you need, and the body restates the ask and gives the closing date.

  Subject: Ticket #[ticket number]: still need [the one thing you need] to keep going

  Hi [name],

  I'm following up on ticket #[ticket number] about [short description]. To keep working on it, I need [the one thing you need, such as the error message or a good time for a short call].

  Could you please reply to this email with it by the end of the day on [day, date]? If I haven't heard from you by then, I'll go ahead and close the ticket, and you can { reply to reopen it | open a new ticket and mention #[ticket number] }. If you need more time, or you've already taken care of it, tell me and I'll adjust the date or close it right away.

  Thanks,

  [Your name]

  [Service desk phone number and portal address]

  Formatting notes:

  • Text in square brackets is yours to fill in. [day] means a weekday, [date] a calendar date and [day, date] both, such as Tuesday, October 20. [team name] is your desk's name, whether your requesters are employees or customers.
  • A bracket that holds an instruction, such as [phone number again], tells you what to say, and "Teams" stands for whichever chat tool you used. Where a template offers two options in braces ( { } ) with a bar ( | ) between them, keep one of the phrases and delete the other.

  Naming the closing date in attempt 1 keeps every message consistent, but if you'd rather open gently, drop the "I'll go ahead and close the ticket" sentence from attempt 1 and let attempt 2 use it.

• Attempt 2: The Teams or Chat Message

  A day or two after the email, move to chat and pick a different time of day. Two or three lines are enough, and the same wording works in Slack or any other chat tool.

  Hi [name], it's [your name] from [team name]. I emailed on [day] about ticket #[ticket number] ([short description]). Could you please send me [the one thing you need]? If a quick call is easier, please tell me a good time. If I don't hear from you by the end of the day on [day, date], I'll be planning to close the ticket then. Thanks!

• Attempt 3: The Phone Call, Voicemail and Final Reminder (Pre-Closure Warning)

  Make the third attempt a phone call. Before you dial, look for an automatic out-of-office reply to your earlier messages and check the requester's calendar if your tools let you see it. If you still can't tell whether they're away, ask their manager.

  If you reach the person, agree on a date while you're on the line and confirm it in a short email. If you reach voicemail, leave a message of under a minute along these lines:

  Hi [name], this is [your name] from [team name], calling about ticket number [ticket number, read one digit at a time]. I need [the one thing you need] to keep working on it. Please reply to my email or call [team name] at [phone number]. That's [phone number again]. If I don't hear from you by the end of the day on [day, date], I'll be planning to close the ticket then. The details are in my email. Thanks!

  Keep three things out of the voicemail:

  1. The details of the problem
  2. Any account information
  3. Any request for a password or a code

  If you have no phone number for the requester, ask their manager for one. If you still have none, make attempt 3 a second chat message plus the final reminder. In the final reminder, the closure message and the ticket note, replace the phone mention with the second chat message so each lists only the channels you used. If email is all you have, see "If Email Is Your Only Channel" below.

  Unless the call connected and you agreed on a date, send the final reminder by email right after the call so the voicemail and the written record match.

  Subject: Ticket #[ticket number]: final reminder, closing on [date]

  Hi [name],

  This is my final reminder about ticket #[ticket number] ([short description]). I emailed on [day], messaged you on Teams on [day] and called on [day].

  I still need [the one thing you need] to keep working on this. If I don't have it by the end of the day on [day, date], I'll go ahead and close the ticket. If you need more time, please reply with a date within the next [number, such as 3] business days and I'll hold the ticket open until then.

  Thanks,

  [Your name]

  [Service desk phone number and portal address]

  The extension offer in that last paragraph comes from Bowdoin College's guidelines, which tell requesters they can ask for more time by replying before the seven-day window closes.

• The Closure Message (Closing Ticket Email Template)

  At the end of business day 7, if there's still no answer, close the ticket under your no-response label and send this closing ticket email, which some desks call the final notice. The email lists the attempts and says plainly that the outcome hasn't been confirmed, without guessing why the person went quiet. The closure label section below explains the label.

  Subject: Ticket #[ticket number] closed: I couldn't reach you

  Hi [name],

  I've gone ahead and closed ticket #[ticket number] ([short description]) because I couldn't reach you after three attempts (email on [date], Teams on [date] and phone on [date]), plus a final reminder by email on [date]. I haven't confirmed that your [issue or request] is taken care of, and I still need [the one thing you need] to move it forward.

  If you still need help, please { reply to this email by the end of the day on [last date to reply] with what you still need and the ticket will reopen | open a new ticket at [portal address] and mention #[ticket number] }. No need to reply if you're all set.

  You can read how the desk handles quiet tickets at [address of your published schedule].

  [Your name]

  [Service desk phone number and portal address]

  If the conversation started in chat, also post a shorter closure in the same thread:

  Hi [name], just so you're aware, I'm going ahead and closing ticket #[ticket number] ([short description]) because I couldn't reach you after three attempts, and I haven't confirmed that your [issue or request] is taken care of. If you still need help, please { reply here by the end of the day on [last date to reply] | open a new ticket and mention #[ticket number] }.

• Choose Your Reopen Rule

  Choose your reopen rule before you send attempt 1, because every message that tells the requester how to come back has to match what your tool actually does. If your rule is a window, add "within [number] days of closing" after "reply" in each of those messages. Three published examples show the range:

  1. Reply Reopens: A reply to the resolution email reopens the ticket right away, according to UNC Asheville's IT service desk page.
  2. Reply Within a Window: The University of Arkansas help desk reopens a ticket when the requester replies within three days of resolution, and after that a new ticket references the old one.
  3. Portal Only: Adobe Commerce Support, which serves external customers, lets them reopen a closed case on its Experience League site within 14 days, and a reply to an email about a closed ticket won't reopen it.

  Some of these describe resolved tickets and some describe closures after no response, and the same choice applies to your no-response closures. A thank-you or an out-of-office reply to your closure message can reopen a ticket in some tools, and our article on ticket reopen rate causes covers the email filters that stop it.

• The Internal Ticket Note

  Write the note for someone who wasn't there, because it protects you if the ticket is reopened or reviewed later (our article on ticket resolution notes best practices covers how to structure one for the next agent). Memorial University of Newfoundland's guidelines say its team includes a clear explanation in the resolution notes whenever it closes a ticket.

  Closed, no response. Waiting on [the one thing you needed] since [date]. Attempts: [date] email,#[date] Teams message,#[date] phone call ({ reached them | left a voicemail }), plus a final reminder email on [date] stating a closing date of [date]. No reply as of [date, time]. Exemption check on [date]: [result]. Out-of-office check on [date]: [result]. Closure message sent [date]. Reopen rule: [rule].

If the Requester Replies Before the Ticket Closes

Any reply from the requester takes the ticket out of the no-response sequence that day, except an automatic out-of-office reply, which only tells you to pause. What you do next depends on what the reply says:

• Full Answer: Move the ticket back to work and tell the requester what happens next.
• Already Taken Care of: Close the ticket right away, as attempt 1 promises, under a label such as "Closed, Resolved by Requester" that doesn't credit the desk with a fix, and note that the requester fixed it.
• Partial Answer or Acknowledgment Only: Thank them, make what's still missing the new question for them, and give a new closing date, with attempt 1 going out two business days later.
• Request for Time: Record a date within the extension you offer in your final reminder. If it's later, ask your help desk lead before you agree. If the date passes with no answer, send the final reminder again with a closing date two business days out.
• Call That Connects: Put the agreed date in the ticket note, and send the final reminder only if that date passes. If the ticket then closes, change the closure message to say you agreed on a date when you spoke on [date] and didn't hear back.
• Repeated Delay: If the requester stalls again, restart the sequence one more time at most, then hand the ticket to your help desk lead.

When You Delivered a Fix and Heard Nothing

Sometimes you did the work, asked whether it's fixed, and got silence. Mark the ticket resolved when you send the first message below, or use the nearest status your tool has, such as a work-completed status, and check whether your reports stop the clock there. Then move the ticket to closed on the date you named if nobody replies. In your reports, this is an ordinary resolution, so it counts toward FCR only if the first contact delivered the fix.

Published grace periods run from three days at the University of Arkansas to more than a week at Memorial University, and our reopen rate article says most platforms default to three to five days. Pick a number and publish it with your schedule. Send the confirmation by email and add a reminder the day before the closing date, by chat or, if email is your only channel, as a short second email, and check whether logging that reminder restarts your auto-close timer. The exemption list later in this article applies here too, so a security fix nobody confirmed doesn't close on a timer.

If the date passes with no reply, move the ticket to closed and send this message:

Store the Messages as Macros and Automate the Reminders

Store each email as a macro (a ready-made reply, often called a canned response or ticket response template) with the requester's name and the ticket number filled in automatically, and keep the chat messages in the same library to paste. That keeps the messaging consistent from one agent to the next. A macro usually can't know the one thing you need or the closing date, so leave the square brackets in place, keep one option from each pair of braces and read each message before you send it.

Check whether your tool's rules can also send the follow-up reminders and apply the closure label on a schedule. Some vendors now sell Artificial Intelligence (AI) agents that send the follow-ups and close the ticket themselves, and some let a person review each message first. Until you have your own reopen-rate and satisfaction numbers for automated closures, keep the exemption list and the wording under a person's control, and see our service desk automation article for what not to automate.

Our article on help desk scripts has the acknowledgment and resolution messages that come before a ticket goes quiet.

If Your Requesters Are External Customers

Customers need the same three facts in the same order, with three changes:

1. Replace the Teams message, and every other mention of Teams, with the channel the customer already uses with you, such as a text message or in-app chat.
2. Skip the calendar check and the manager step.
3. For a suspected account takeover, call the number already on the customer's record, because a number that arrives in a suspicious message could belong to the attacker.

If Email Is Your Only Channel

If email is the only way you can reach requesters, make each of the three attempts a different email:

1. Attempt 1: Send the attempt 1 template above on business day 2.
2. Attempt 2: Send the short email template below on business day 3 or 4, with a new subject line and at a different time of day.
3. Attempt 3: Look for an out-of-office reply to your first two emails, then send the final reminder on business day 5 with its sentence about Teams and phone replaced by the dates of your earlier emails. For employees, copy the requester's manager if your policy allows it and the ticket holds nothing sensitive.

Send this closure message instead of the standard one:

Use this ticket note instead of the standard one:

How Many Attempts and How Many Days Before You Close a Ticket for No Response?

Most published schedules make three attempts and put the closing point anywhere from three business days to a week or more, and none of them is the standard. The right schedule is the one you write down and publish.

Published Schedules From Five Organizations

All five schedules give the requester several chances before the ticket closes.

Note that the East of England item is an archived staff notice that announces the policy in the future tense and gives no publication date (the "last updated" line on the archived page matches the archive's capture time), so treat it as one example of how a desk designed its schedule.

A Starting Schedule and How to Adjust It

Which schedule should you pick? Start with the one in the Sequence table near the top, which makes three attempts by business day 5 and closes the ticket on business day 7. That sits close to Bowdoin College's seven days and runs longer than Memorial University's one-week minimum, and the two days between the final reminder and closure match the two Bowdoin leaves after its last reminder. Adjust it for your service desk with these recommendations:

• Weekends and Holidays: Count business days, and put a calendar date in every notice. Some tools count calendar days, and some restart their auto-close timer every time an agent updates the ticket, so check yours. If yours does either, close by hand on the date in your notice.
• Out of Office: If the requester is away, pause the sequence, note the date they're back and send a fresh attempt 1 that morning. If the absence runs longer than any wait you'd accept, ask the manager whether someone else can answer.
• Shift Workers and Clinicians: Someone who isn't at a keyboard may not see email for days. Ask their department lead how best to reach them and stretch every date in the schedule, for example by doubling the days between steps. If the ticket blocks their work and those steps don't reach them, see the exemption list below.
• High-Impact Tickets: A ticket that blocks someone's work shouldn't close on a timer, so treat it as a blocked requester under the exemption list below. Send attempt 1 the next business morning without a closing date, call sooner and let your desk lead decide when it closes.
• Low-Impact Tickets: Shorten the schedule when the ticket isn't blocking anyone's work.

Publish the schedule, with its pauses for leave and its exemptions, where requesters can read it, as Memorial University does for its attempts and exemptions, and link to it from your closure message. Karen Ferris, in an ITSM.tools roundup of practitioner views, said the most important point is that the approach is clearly agreed with the customer and communicated to them.

How to Word a No-Response Follow-Up So People Reply

To write an email for no response, or to professionally email someone who hasn't responded, lead your follow-up email with the ticket number and the one thing you need, name a date, and keep the message short enough to read at a glance. Six rules cover most of it:

1. Ask for One Thing: A message with five questions reads like a form. Pick the one thing that unblocks you, and if that thing is a how-to step, link a knowledge base article and don't describe it in the message.
2. Name a Date: Use a real day, such as "by Thursday, October 22." A Cochrane review of randomized trials of research questionnaires found, in one trial of about 8,600 people, that stating a deadline raised the odds of an online response (odds ratio 1.18, meaning 18% higher odds), while six postal trials found no evidence of an effect. None involved a help desk, so test it on your own tickets.
3. Keep It Short and Skip the Apology: A few lines is plenty, and there's no need to apologize for checking in. Following up is part of the job. In the same review, a postal trial of 500 people found no evidence of a difference between a brief and a detailed letter, but an online research survey of 1,250 people found the brief one had over three times the odds of a response (odds ratio 3.26).
4. Call It an Attempt: Many desks call this the three-strike rule internally. Stephen Cull, in the same roundup above and about desks that chase users to confirm a closure, said that the phrase can, in some cases, signal contempt for users. Memorial University's page says "attempts." Keep "strike" out of anything the requester sees.
5. Switch Channels Before You Resend: Resending the same message to the same inbox gives the requester nothing new. Move to chat and then to the phone, and treat voicemail as one of several contact methods. Roy Atkinson, as summarized in that roundup, cautioned that voicemail is often ineffective. If email is all you have, change the subject line, shorten the message and bring in the manager where your policy allows it, as "If Email Is Your Only Channel" describes.
6. Make the Message Safe to Trust: Give your name and the ticket number, and point to the desk's published phone number or portal. Write the portal address out so people can type it instead of clicking, and never ask for a password or a one-time code, since that's what an impersonator asks for. A joint advisory on the Scattered Spider group from the Cybersecurity and Infrastructure Security Agency, the Federal Bureau of Investigation and other agencies, citing public reporting, says the group posed as company IT or help desk staff by phone calls and text messages to get employees' credentials. It also says the group posed as IT staff to get employees to share one-time passcodes.

Which Closure Label to Use: What Each Choice Does to FCR, Resolution Time and Reopen Rate

Close a ticket that was waiting on information under a no-response label, since resolved would say you fixed it and canceled would say the requester withdrew the request. A closure label is whatever your tool lets you attach to a closed ticket so reports can find it, such as a status, a reason code or a tag. A no-response label is a closure label whose name says why the ticket closed, such as "Closed for No Response."

Which Label Fits Which Silence?

Silence comes in two kinds, and each gets its own label:

1. Silence After a Delivered Fix: You did the work, asked whether it's fixed, and the requester never answered. Mark the ticket resolved, then close it on the date you named in your confirmation message. In many desks, resolved means the fix is in and awaiting confirmation, while closed means the ticket is finished.
2. Silence While Waiting on Information: You asked for something you need, and the requester never sent it. Nothing was resolved, so it takes the no-response label.

Silence after a fix can simply mean the person moved on. Daniel Breston, in the ITSM.tools roundup above, said that after a fix he doesn't always respond, and that doesn't mean he's unhappy. Silence while you wait for information says nothing about whether the person still needs help, so it can't be treated as agreement.

The practitioners in that ITSM.tools roundup split on how to close tickets that were waiting on information. James Gander advised resolving such tickets under a category such as "Unable to contact user" and closing them if the requester hasn't come back within about ten days. Stephen Cull argued that a ticket that was never resolved should go straight to closed and shouldn't carry a resolution time. We recommend Cull's approach for those tickets, and Gander's approach still works if his category keeps them out of your FCR and resolution time figures.

Our reopen rate article describes a three-contact approach that ends by resolving the ticket with a note. Read that as moving the ticket out of your queue, and file it under a no-response label so you can filter it later.

What Each Closure Choice Does to Your Metrics

The table below shows what each choice does to the reports most tools run when a ticket was waiting on information, and the second row is the one we recommend. Silence after a delivered fix is an ordinary resolution, so it isn't in the table. Confirm each cell in your own tool. The last column covers the Service Level Agreement (SLA) clock and the satisfaction survey.

A ticket that closed because the requester never replied isn't a first-contact fix, whatever status it closed under. Our article on how to improve first call resolution rate warns about closing tickets prematurely to keep the number high.

Keep No-Response Closures Easy to Filter

To make the no-response label useful in your reports, set these up:

• Use one no-response label for every ticket closed this way.
• Make sure your report doesn't count them as fixed on first contact, and leave them in the total number of tickets. Each one is a ticket you didn't fix on first contact, and taking them out would flatter your FCR.
• Keep them out of average resolution time, and report the age at close on its own.
• Report their survey responses on their own line instead of folding them into your satisfaction score. Check what the survey email says too, because a request to rate how your issue was resolved contradicts a closure message that says the outcome isn't confirmed.
• Count them each month, and track how many reopen or come back as a new ticket about the same issue. Use the reopen window your closure message states, or a window you choose if your message offers only a new ticket.

To see how the second bullet plays out, suppose a desk closes 200 tickets and 100 were fixed on first contact, an FCR of 50%. If 20 of the other 100 were silent tickets, counting them as fixed on first contact would read 60% (120 of 200), and removing them from the total would read 56% (100 of 180). Leaving them in as not fixed keeps the month at 50%.

How much does this matter? It depends on how many tickets you close this way, and you'll only know once you start counting. A monthly export filtered on your no-response label, plus a pivot table by requester, is enough to spot the new tickets that formal reopen counts miss.

Our FCR article and time to resolution article define both metrics, and our first response time article makes a similar case for filtering system-closed tickets out of its metric.

The SLA Clock

Whether a waiting status pauses the SLA timer varies by tool and by metric, so check each metric your reports use. Pause only for a genuine wait on the requester and record a reason every time. A pause that hides a stalled ticket makes your numbers look better than your service is.

A ticket waiting on IT or a vendor keeps its clock running under that rule. If your SLA allows an exception for vendor waits, write it into the SLA instead of borrowing the waiting-on-requester status. Our SLA breach root cause analysis explains how a hidden pause develops.

5 Kinds of Tickets to Keep Out of No-Response Closure

Memorial University of Newfoundland's guidelines name three kinds of tickets as exempt from automated closure when a requester doesn't respond (security-related issues such as virus or malware concerns, software installations bought through its IT Procurement team and tickets referred from other IT support groups). The five kinds below adapt those three and add two of our own:

1. Security-Related Tickets: Silence tells you nothing about the risk, so your security contact or desk lead decides when the ticket closes, and a desk of two should name that person in advance. Don't wait on the requester's reply to secure an account that may be compromised.
2. Tickets Referred to or From Another Team or Vendor: When another group owns part of the wait, a timer built for a silent requester may measure the wrong one. Memorial exempts tickets referred from other IT support groups, though not from its own service desk or procurement team, and its page doesn't say why. An equipment request waiting on a manager's approval fits here too.
3. Tickets Where IT Owes the Next Move: Hardware on order, a change window not yet reached or a promised callback means the next move is yours. Memorial's exemption for software installations bought through its procurement team looks like the same case.
4. Requests From Someone Who's Blocked or Hard to Reach: A person in the middle of an outage, or a nurse between patients, won't answer a third email.
5. Tickets Linked to a Major Incident: The incident owner decides when the issue ends.

In three of these five, someone other than the requester owns the wait. Memorial's page calls its exempt tickets "not subject to automated closure," which implies the other tickets can close automatically and these need a person's decision. The page doesn't say who decides or how.

Tickets kept out of no-response closure still get follow-ups, but no closing date goes in the message and no timer decides when they close. For a follow-up, reuse attempt 1 and replace its closing-date paragraph with "Could you please reply to this email with it when you can? If you've already taken care of it, tell me and I'll update the ticket." Whether requests from executives go on the exemption list depends on whether your leadership expects a person to handle them, so ask once and write the answer into your published schedule. Tickets under a legal hold stay open or close only as your legal or records team directs.

Where Each Ticket Goes Instead

A Message for Tickets Waiting on IT or a Vendor

Send this when you move a ticket out of the waiting-on-requester status, and set the follow-up for the date you promised. If you have no expected date, delete the clause about it and keep the update date.

How to Enforce the Exemption List

Statuses enforce an exemption list better than a rule an agent has to remember, as long as your tool can act on them. Keep "waiting on the requester" separate from "waiting on someone else," and use your own plain labels, because "pending," "waiting on customer" and "awaiting reply" mean different things in different ticketing systems.

For example, take a docking station on back order from a vendor. If its ticket sits in the waiting-on-requester status, the auto-close rule will time it out on someone who did nothing wrong, and the requester gets a closure message for a delay that was never theirs.

Some auto-close rules act on resolved tickets only. Check what the rule in your ticketing system watches and whether it can skip a category, a priority or a tag. If it can't, treat the exemption as a status someone sets by hand.

For referrals, our IT help desk escalation rules article covers how the handoff should work.

Closing Ticket Due to No Response Template FAQs

• How do you say "no response" professionally?

  Say what you did and what you need, and leave out why the person hasn't answered. Four phrasings work in most situations:

  1. About ticket #[ticket number], I haven't been able to reach you.
  2. I still need [the one thing you need] to keep working on ticket #[ticket number].
  3. If I don't hear from you by the end of the day on [day, date], I'll plan to close ticket #[ticket number].
  4. I'm closing ticket #[ticket number] because I couldn't reach you after three attempts.

  Skip "I haven't heard back from you," which opens with the requester's silence instead of the ticket.

• How do I write a closing ticket email?

  For a ticket that was waiting on information, write a closing ticket email in four parts, in this order:

  1. The ticket and the reason it's closing
  2. The attempts, by day and channel
  3. A plain statement that the outcome hasn't been confirmed, and what you still need
  4. How to come back

  Keep the last part to one sentence that matches what your tool does when someone replies.

• What's the difference between resolved and closed?

  Resolved means the fix is in and the requester hasn't confirmed it yet, while closed means the ticket is finished. A ticket that was waiting on information was never resolved, so close it under a label that says no response. A ticket where you delivered a fix and heard nothing is marked resolved first and closed on the date you named.

• Should a ticket closed for no response count as First Contact Resolution?

  No, a ticket that needed information and then went quiet doesn't count as First Contact Resolution. Say a desk closes 200 tickets in a month and 100 were fixed on the first contact, an FCR of 50%. If 20 of the other 100 were silent tickets that had been waiting on the requester's information, closed as resolved and counted as first-contact fixes, the same month would read 60% (120 of 200), although nobody had delivered a fix for any of those 20 tickets.

  Count them as not fixed on first contact and leave them in the 200-ticket total, since our FCR formula divides by all tickets. That keeps the month at 50%, while removing them would read 56% (100 of 180) and flatter the rate.

• What should happen when someone replies "thanks" to the closure message?

  A thank-you shouldn't reopen the ticket. In some tools any reply to a resolved or closed ticket reopens it, which inflates your reopen rate.

  Filter acknowledgments and auto-replies where your tool allows it, and have an agent read any reply a filter holds back so "thanks, but it's still broken" doesn't disappear. Treat a "thanks" in answer to an "is this fixed?" message as a probable yes and have an agent read it before the ticket closes.

• What if the requester is on vacation or out sick?

  Look for an out-of-office reply or a calendar entry before the last attempt, and pause the sequence if the requester is away.

  If you can't tell, ask in your first email, for example "If you're away, tell me the day you're back and I'll pick this up then."

  Put the return date in the ticket note and set a follow-up for the day they're back, then send a fresh first attempt. If the absence has no end date, ask their manager whether someone else can answer.

• Can you auto-close a silent ticket without warning first?

  You can, but a closure with no earlier notice is one way a ticket gets closed on someone who was out of the office. If your auto-close rule counts days without an update, check whether each attempt you log restarts the count and whether it counts calendar days. Then close by hand on the date in your final reminder. If you let the rule close it, set the number to the longest gap you'd accept so it never fires before that date, and expect the ticket to close on or after the date in your notice.

  Send a final reminder that names the date, and send the closure message when the ticket actually closes. For tickets where you delivered a fix, our article on ticket reopen rate causes covers the confirm-or-auto-close process.

Related Giva Resources

• IT Support for Non-Technical Users: How to Make the Help Stick
• First Call Resolution Formula (Free Excel Template)
• 12 Help Desk Ticket Examples and Responses for Busy IT Managers

Closing Ticket Due to No Response: Pick a Schedule and Use One Label

A ticket that goes quiet doesn't resolve itself. It ages in your queue, and a careless closure either strands the requester or inflates your reports. What works is:

• A short written routine built from a published schedule
• The same three facts in every attempt
• A label that matches what happened
• Exceptions kept off the timer

Before the next quiet ticket shows up, save the messages above as macros and add a no-response label, so the first closure is already one you can find in a report.

Ready to Save These Messages as Macros in a Help Desk Ticketing System?

A template only saves time when it's a few clicks away at the moment a ticket goes quiet, and a closure label only helps when every agent applies it the same way.

Giva's Help Desk Software lets you save the email and closure messages as macros, each with a public note and dynamic text such as the requester's name and the ticket number.

You can set an auto-close rule that counts calendar days since the last update from the requester or an agent, so set it for the longest gap you'd accept after your final reminder. The rule applies a closing status, such as the "Auto-Closed by Rules" example on Giva's auto-close page or a no-response status of your own, and a public note can tell the requester what happened.

You can also keep an "Awaiting Customer Response" ticket status separate from closed.

Giva's Re-Opened Tickets and First Contact Resolution reports give you numbers to watch as you change how you close tickets.

Your free 30-day trial comes with free setup help. You can try the macros and the closing status in a working system before you change anything for your team.

For more, get a demo to see Giva's solutions in action, or start your own free, 30-day trial today!