November 19, 2026
Holiday Tech Support Can Wait Until After Dinner
A little help, a clear boundary, and no surprise evening-long repair project.

By John Miller
3 min read
"While you're here, could you look at my laptop?" is a reasonable question. It can also turn a holiday visit into an evening of updates, password recovery, and a printer that has apparently been broken since March.
I'd rather set an honest boundary than agree to a quick look and spend the rest of dinner wishing I hadn't. You can care about someone's problem and still choose a better time to work on it.
Offer a time you can actually give
Something as simple as "I can look at that tomorrow afternoon, but I'm taking tonight off" is enough. There's no need to invent an excuse or turn the conversation into a lecture about how much IT work you already do.
If you want to help immediately, keep the scope small: identify the issue and decide what should happen next. Agree on a stopping point before starting. Don't promise a complete fix before you know whether you're dealing with a setting, failing hardware, or an account-recovery problem.
And if you can't follow up, say so. A clear referral to the manufacturer's official support is more useful than a promise you won't have time to keep.
Separate an inconvenience from a possible scam
A printer can usually wait. Someone saying they just gave remote access to a caller claiming to be technical support deserves a different response. I'd pause the casual troubleshooting and help them find the official guidance for that situation.
The FTC describes tech-support scams that begin with unexpected calls or frightening pop-ups. Its advice includes avoiding the contact details in suspicious messages and using a company's independently verified contact information instead.
If someone has already shared credentials or granted access, use the FTC's recovery guidance and the affected provider's official support. Don't assume closing a pop-up means the problem is resolved. Avoid turning a family conversation into an improvised investigation of a device you haven't assessed.
Let the owner stay in control
When helping with an account, I'd have the person enter their own password and verification codes. Explain what you're changing and ask before changing it. Helping shouldn't require taking over someone's accounts or collecting their credentials.
For ordinary maintenance, the FTC recommends software updates, strong passwords, and two-factor authentication. Those are useful topics for a calm follow-up session. Trying to teach all of them between dinner and dessert is probably too much.
Let the person perform the steps while you explain. A short note in their own words may be more useful later than watching you move through six menus at full speed. Keep private account information out of the note.
Turn "a quick look" into a clear agreement
Imagine a relative hands you a slow laptop while everyone is getting ready to eat. I'd first ask what "slow" means: starting up, opening one application, or loading websites. Then I'd decide whether I can identify a next step without starting a repair I can't finish.
A useful answer could be, "I can help narrow it down now. I can't promise to fix it tonight." That keeps a small favor from quietly becoming an open-ended commitment. If the next step involves a long update or moving important files, choose another time and confirm what needs protecting before doing it.
The same approach works when the request expands. You agree to help connect a printer, then discover a forgotten account password and a request to reorganize years of photos. Pause and agree on which problem you're actually solving. You don't have to accept the entire list because you accepted the first item.
If you do arrange a follow-up, ask them to have the device, charger, and a description of the problem ready. They should have access to their own account-recovery methods without sending you passwords or verification codes.
Keep the handoff simple
At the end, I'd leave a short note with three things: what changed, what still needs attention, and where to get official help. "We connected the printer; the account-recovery issue is still open" is clearer than "Everything should be fine now."
Explain any remaining limitation in ordinary language and have the person show you the task once. If the fix only works when you're holding the device, there may still be a teaching or usability problem to solve.
The conversation examples below are options, not lines you have to memorize. Pick wording that sounds natural to you. A friendly boundary is easier to keep when it is specific and you mean it.
Leave something useful behind
Before finishing, agree on what was resolved and what still needs attention. Save a link to the official instructions, check that the person knows how to get support, and avoid making yourself the only recovery plan.
If a suspicious message was involved, the FTC's phishing guide is a useful reference for recognizing the pattern and knowing where to report it.
The goal is to help without making the whole visit about technology. A smaller, clearly agreed favor leaves more room to enjoy the people you came to see.