When resolution requires another team, professionalism means clear communication , setting expectations, and explaining what will happen next. Quentin Docter describes escalation: when you don’t have the answer, “this process is called escalation,” and when a ticket is escalated, someone must “be responsible for communicating with the user.” He emphasizes “Clear Communication,” stating the problem description must be understandable to others because “the problem may have to be escalated,” and you should communicate work-arounds and progress transparently.

The All-in-One guide and Mike Meyers Lab Manual both stress empathy and respectful communication with frustrated users—use statements that acknowledge feelings and keep a nonaccusatory tone.

Option D best matches these best practices: explain what’s happening (app crashing), why another department must be involved, and what the user should expect (timeline/next steps/work-around if available). Transferring without explanation (A) increases frustration; a complaint (B) isn’t a solution; and working alone (C) ignores the required collaboration.