Communication and Professionalism practice questions

Continue using technical terms to educate the user.

Why wrong: This can overwhelm and frustrate the user further, hindering progress.

Ask the user to share their screen so the technician can do it remotely.

Why wrong: While efficient, it doesn't teach the user and may not be allowed by policy.

Send the user a written guide and end the call.

Why wrong: Abandoning the user without support is unprofessional and may not resolve the issue.

Tell the user they must have clicked on a phishing link and it's their fault.

Why wrong: Blaming the user without investigation is unprofessional and may be incorrect.

Ignore the complaint because spam is common.

Why wrong: Ignoring a security incident could lead to further compromise and violates policy.

Ask the user to change their password and not worry about it.

Why wrong: While password change is good, it's not sufficient without investigating the cause.

Agree to the manager's request and rush the installation to avoid conflict.

Why wrong: Rushing may lead to errors and unmet expectations, damaging professional credibility.

Install the software and let the users figure out the rest on their own.

Why wrong: Ignoring training and data migration leads to user frustration and potential data loss.

Tell the manager that training is not part of the technician's job.

Why wrong: This is unhelpful and fails to address the user's needs; a good technician coordinates with other resources if needed.

Tell the customer to buy a new battery immediately.

Why wrong: Jumping to a conclusion without verification wastes the customer's time and money.

Say that the motherboard is likely dead and needs replacement.

Why wrong: This is an extreme assumption without any diagnostic steps.

Tell the customer to bring the laptop to the shop without further questions.

Why wrong: This avoids remote troubleshooting and may inconvenience the customer unnecessarily.

Proceed with the installation without asking any questions to respect their time.

Why wrong: This could lead to incorrect configuration if assumptions are wrong.

Insist on a full meeting to discuss requirements.

Why wrong: This ignores the manager's stated time constraint and may cause frustration.

Install the software and leave a note with questions for later.

Why wrong: This delays resolution and may result in rework.

Reply with a detailed technical explanation proving the fix was right.

Why wrong: This can come across as dismissive of the user's feelings and escalates conflict.

Ignore the email to avoid an argument.

Why wrong: Ignoring a complaint is unprofessional and leaves the issue unresolved.

Forward the email to the user's manager to complain about the user's tone.

Why wrong: This escalates unnecessarily and violates professional discretion.

Tell the employee that their router is probably cheap and needs replacement.

Why wrong: This is insulting and will increase defensiveness.

Ask the employee to run a command prompt command without explanation.

Why wrong: This may confuse the employee and feels like a test, increasing frustration.

Escalate the issue to a senior technician without further attempts.

Why wrong: This avoids the problem and doesn't develop the technician's communication skills.

Tell the user to uninstall the antivirus immediately.

Why wrong: This dismisses the user's concern without investigation and may leave the system unprotected.

Explain that antivirus programs always slow down computers and there's nothing to be done.

Why wrong: This is dismissive and unhelpful; it fails to address the specific issue or offer a solution.

Immediately remote into the computer to check CPU usage.

Why wrong: While technically valid, doing so without acknowledging the user's frustration can damage trust and is less professional.

Tell the customer that Windows updates often break things and they should avoid updates.

Why wrong: This blames the software without offering a solution and discourages important security updates.

Ask the customer to try unplugging the printer and plugging it back in.

Why wrong: While a simple step, it doesn't address the likely driver issue and may frustrate the customer further.

Immediately remote into their computer and start checking settings without explaining.

Why wrong: Lack of communication can confuse the customer and violate their sense of control.

Implement the configuration as requested to keep the manager happy.

Why wrong: This violates security best practices and could lead to data breaches.

Refuse to do the work and walk away.

Why wrong: While security is important, walking away without explanation is unprofessional and doesn't solve the problem.

Secretly implement a secure configuration and tell the manager it's what they asked for.

Why wrong: Lying to a client is unethical and damages trust.

Tell the user to calm down and that losing data is not a big deal.

Why wrong: This dismisses the user's feelings and is unprofessional; it will likely escalate the situation.

Raise your voice to match the user's tone to show you are taking it seriously.

Why wrong: Matching an angry tone can escalate conflict; the technician should remain composed.

Transfer the call to a manager immediately.

Why wrong: This avoids responsibility; the technician should attempt to resolve the issue first.

Tell the user that the network changed the printer's address and it is not your fault.

Why wrong: This shifts blame and does not help the user understand; it is unprofessional.

Use technical jargon like 'DHCP lease expiration' and 'subnet mask misconfiguration' to sound authoritative.

Why wrong: Jargon can confuse the user; the explanation should be tailored to their level of understanding.

Say that the printer is faulty and needs to be replaced.

Why wrong: This is dishonest and avoids the real issue; it could lead to unnecessary costs.

Proceed with the installation as requested to respect the executive's time.

Why wrong: This risks installing the wrong software or missing dependencies, leading to more delays.

Install the software that is most commonly used by other executives.

Why wrong: This assumes needs without verification, which can lead to dissatisfaction.

Tell the assistant that you cannot proceed without talking to the executive directly.

Why wrong: This is inflexible; the assistant may have the necessary information.

Tell the user that you will fix it and they should not worry about the details.

Why wrong: This lacks transparency and may cause frustration if the user's work is interrupted unexpectedly.

Use technical terms like 'PST file corruption' and 'registry repair' to sound knowledgeable.

Why wrong: Using jargon can confuse and intimidate the user; communication should be tailored to the audience.

Rebuild the profile without informing the user to avoid worrying them.

Why wrong: This violates the principle of informed consent and can lead to loss of trust if the user notices changes.

Agree not to tell the manager and remove the PUP quietly.

Why wrong: This may violate company policy on reporting security incidents; the technician should follow protocol.

Tell the user that this is a serious security breach and you have to report it immediately.

Why wrong: This may overstate the severity and cause unnecessary panic; a PUP is often low-risk but still needs documentation.

Ignore the request and report the user to HR for violating IT policy.

Why wrong: This is overly harsh and does not consider that the user made an honest mistake; a more measured approach is appropriate.

Ask the user to log in with an administrator account and install the software.

Why wrong: This is a valid method, but it requires the user to know an admin password, which may not be appropriate or secure.

Temporarily add the user to the Administrators group, install, then remove them.

Why wrong: This is overly complex and introduces security risks; the simpler 'Run as administrator' method is preferred.

Cancel the installation and escalate to a senior technician.

Why wrong: This is unnecessary; the technician can handle the situation with standard tools.

Tell the customer that the screensaver is likely the problem and they should uninstall it.

Why wrong: This is presumptuous and may offend the customer; the technician should first gather evidence.

Blame the screensaver and suggest the customer stop using decorative software.

Why wrong: This is unprofessional and may damage the customer relationship.

Ignore the screensaver and run a full virus scan.

Why wrong: This dismisses the customer's report and may waste time if the screensaver is indeed the cause.

Ignore the user's comment because it is hearsay and proceed with the installation.

Why wrong: Dismissing user input can lead to problems; the technician should investigate potential conflicts.

Disable the antivirus temporarily and install the software.

Why wrong: Disabling security software without proper justification is a security risk; a better approach is to check for known issues.

Tell the user that the coworker is mistaken and install the software anyway.

Why wrong: This dismisses the user's concern and may damage trust if a conflict occurs.

Remotely reinstall the wireless adapter driver.

Why wrong: This is premature; the technician has not yet confirmed the driver is the issue and may cause unnecessary changes.

Tell the user to bring the laptop to the IT office for a physical inspection.

Why wrong: This may be unnecessary and inconvenient; remote troubleshooting should be attempted first.

Escalate the ticket to the network team immediately.

Why wrong: Escalation should only occur after basic troubleshooting has been performed and the issue is identified as network-related.

Pretend to understand and hope the issue becomes clear during troubleshooting.

Why wrong: This can lead to misunderstandings and wasted time; it is better to clarify early.

Transfer the call to a different technician who might understand the accent better.

Why wrong: This may be seen as avoidance; the current technician should attempt to resolve the issue first.

Tell the user that their accent is hard to understand and ask them to email the problem instead.

Why wrong: This is disrespectful and could be perceived as discriminatory; a more tactful approach is needed.