Make the issue and requested action clear

Use the team’s approved escalation route when an unresolved customer issue needs action from another role or team, or when you are unsure who should own the next step. Record and manage customer-specific context in Mango CS, following the access and handling rules that apply to the account.

This fictional example does not define urgency thresholds, response times, or a Northstar escalation roster. For an urgent or sensitive issue, follow your manager’s and organization’s established route rather than relying on this sample page.

Prepare a useful handoff

A clear summary helps the receiving role decide what to do next.

  1. 1

    State the customer impact

    Describe what the customer cannot do or what outcome is at risk, using the customer’s reported facts.

  2. 2

    Separate facts from assumptions

    Include what was observed, when it occurred, and any exact error or reproducible behavior. Label an unconfirmed cause as unconfirmed.

  3. 3

    List actions already taken

    Note checks completed, results, and any customer update already sent.

  4. 4

    Name the requested decision or action

    Explain what help is needed and which role or team you believe should take the next step; confirm routing through the approved escalation process.

  5. 5

    Record and follow up

    Update the customer issue in Mango CS, hand it to the confirmed next owner, and keep the customer informed through the agreed communication route.

Before handing an issue over

Check that the receiving colleague can understand the situation without guessing.

Customer and impact

Identify the relevant account in Mango CS and describe the practical effect on the customer.

  • State what is blocked or affected.
  • Include the customer’s requested outcome.

Evidence and next step

Share the facts needed to assess the issue and make ownership visible.

  • Include observed behavior and actions tried.
  • Name the requested action and confirmed next owner.