Troubleshooting process

Use this page to understand how to troubleshoot when customers have service or device issues.

Review what you handle

  • Owns all initial troubleshooting in Atlas FIX-Flows under Fundamental Troubleshooting – Account Care.
  • These steps prevent call disconnections and avoid requiring customer callbacks, though performing a reconcile may be necessary.
  • Account Care troubleshooting includes:
    • Understanding the issue by asking probing questions (SDL).
    • Performing account and coverage checks.
  • The VEA (Virtual Engineering Assistant) tool allows you to deliver network insights in under 30 seconds, reduce transfers to tech support, and resolve issues faster. Complete all fundamental troubleshooting to resolve customer concerns before escalating. 

  • Responsible for Advanced Troubleshooting in Atlas FIX flows.
  • Tech Care never transfers to Account Care regardless of call type.

  • Owns the full scope of troubleshooting. 
  • Manages all incoming conversations and transfers to ESC only when directed by policy. 
  • Line of businesses assisting Social Media Care follow their scope of support before transferring in Khoros.

Before transferring to Tech Care

  • Is the caller escalated and requesting a supervisor? Yes, engage team leadership and do not transfer to Tech.
  • Verify if customer is calling from device experiencing the issue. Review Troubleshooting with customer on device.
  • Confirm customer has access to the device experiencing issues, including HSI and coverage devices.
  • Follow the Fundamental Troubleshooting - Account Care section.
    • Use VEA to check for open outages and emerging issues if issue is location specific.
    • If a VEA query is completed, save the VEA Report ID in memos.
  • If the caller is unverified, set appropriate support expectations. Review Unable to verify account troubleshooting.   
  • Capture a callback number and save it in memos in case of disconnection during transfer.
  • Save the token in account memos. 

Get the complete picture of what the customer is seeing. Fully understand the situation to determine the root cause.

  • What shows on the device screen when you have the problem? 
  • Do you get any error messages? 
  • What were you doing with the device when this started happening? 
  • What devices are having the issue? Are other devices not having the issue? 
  • For Dual SIM with eSIM devices, which line is having the problem? 

 

Learn when an issue started and if it is repeatable, which helps you match the problem with other events like upgrades, app downloads, or known issues.

  • When did you first notice it?
  • How often does it happen?
  • Can you repeat the same steps and always get the same problem? Or is it sporadic?

 

Locations where the issue happens can help you understand if the issue is related to coverage. If issue is in one or two locations, move straight to network root causes.

  • Where do you normally experience these issues? Home, work, school?
  • How many bars of signal do you have? Do the signal bars fluctuate?
  • Do you see 3G, 4G, LTE, or 5G on your screen?
  • Are you inside or outside?

 

Ask questions

To start the troubleshooting process, ask clarifying questions so you fully understand the issue. Ask specifics about the situation, duration, and location. 

  1. Verify the account. 
    • Unverified accounts will have limited troubleshooting support. 
    • If the customer cannot verify, you can still open the account in Unauthorized state and troubleshoot. Review Unable to verify account troubleshooting
  2. Ask the customer to describe the issue and how it started. 
  3. If the customer visited a T-Mobile store, ask what steps were taken and check account notes. Continue with troubleshooting and skip those steps. 
  4. Ask open-ended and close-ended probing questions to clearly define Situation, Duration, and Location beyond the customer’s initial description.

Get the complete picture of what the customer is seeing. Fully understand the situation to determine the root cause.

  • What shows on the device screen when you have the problem? 
  • Do you get any error messages? 
  • What were you doing with the device when this started happening? 
  • What devices are having the issue? Are other devices not having the issue? 
  • For Dual SIM with eSIM devices, which line is having the problem? 

 

Learn when an issue started and if it is repeatable, which helps you match the problem with other events like upgrades, app downloads, or known issues.

  • When did you first notice it?
  • How often does it happen?
  • Can you repeat the same steps and always get the same problem? Or is it sporadic?

 

Locations where the issue happens can help you understand if the issue is related to coverage. If issue is in one or two locations, move straight to network root causes.

  • Where do you normally experience these issues? Home, work, school?
  • How many bars of signal do you have? Do the signal bars fluctuate?
  • Do you see 3G, 4G, LTE, or 5G on your screen?
  • Are you inside or outside?

 

Locate a solution

Use the answers you received from asking the questions above to identify potential root causes and solutions. The issue may be related to the customer's account, device, or network. 

  1. Check the account and services are all set up correctly.
  2. Open The Fix. In Atlas, click the Troubleshooting tab. Find the relevant FIX Flow to begin troubleshooting and follow the outlined steps.
  3. To go back, click START OVER at the top of the page.
  4. Hover over the (i) icon (Atlas) to see instructions and details for the step.
  5. Pop out troubleshooting so you can use other tools or maps while troubleshooting. In Atlas Troubleshooting, a window pops out when you open The Fix flow.
  6. Click the check box next to a step when you complete it. This adds it to the troubleshooting history, the memo builder, and allows you to file a ticket if the step is mandatory.
  7. Atlas Troubleshooting Dashboard can automatically check device diagnostic data for:
    • Airplane mode OFF
    • Data or packet data ON
    • APNs set to default
    • Wi-Fi OFF
    • Data Roaming OFF
    • Wi-Fi Calling
    • Device Rooted
    • Bluetooth OFF
  8. Device diagnostics
    • Apple: Data for Apple devices is retrieved from Apple products and displayed using the iOS GSX tool, an Apple diagnostic product. The information is stored for 14 days, but you can refresh it anytime.
    • Find My iPhone indicator: Summary tab > Find My iPhone status. Three possible statuses.
      • Lost or stolen: Icon is red and indicates the device is lost or stolen.
      • Not lost or stolen: Icon is green and indicates if Find My iPhone is on or off.
      • Unavailable: Icon is gray and indicates the information is not available.
    • Request and use diagnostics.
    • Customer must be able to access the internet and device must not be lost or stolen for these steps to work.
  9. Ensure device is updated to the most recent software version. If not, update it for diagnostics to work properly.
  10. On the Device tab, view the last updated date under each section to see if it was updated recently.
  11. Click Request Diagnostics.
  12. Tap Settings > Privacy > Analytics > Start Diagnostics with Apple Support.
  13. Review the Diagnostic Terms and Conditions, and tap Agree.
  14. The Running Mobile Resource Inspector screen appears.When finished, the device shows “Waiting” until the customer closes out of the session.
  15. Select the above steps that have been completed on the customer's device checkbox, and click Check Device Data.
  16. The updated time stamp appears and the customer can exit out of the session.
  17. If you see an alert on the diagnostic screen, click the link for further instructions.
  18. If none of the articles resolve the issue, continue with standard troubleshooting.

  • In Atlas Troubleshooting  >  The Fix  flows, you can click a dropdown to bring up tools to complete the step:
    • Known and Emerging Issues
    • Call Forwarding for Voice
    • ESIM/SIM Status
    • Voicemail
    • OTA General Download
    • Reconcile
  • Do not perform a Last Resort (master reset, exchange, complaint) until previous steps are complete. If a previous Expert completed the steps, click Skip to Last Resort.
  • Check for known issues and outages:
    •  Atlas: Troubleshooting > Tech Tools tab > Quick Links > Known Issues
    • Review System Issues
    • Check for device known issues.

  1. Refer to any outages, system issues, emerging issues, or known issues.
    • You may not be able to troubleshoot or resolve these, but you can advise the customer of workarounds or details.
    • Review Network outage advisements.
  2. Follow the troubleshooting steps as a process of elimination, to find and resolve the root cause.
    • Complete all relevant steps in The Fix, and click the check box for each step you complete.
      • Check each step in order to use the memo builder later.
      • In Atlas Troubleshooting, checking some steps is mandatory in order to file a ticket. These steps show a ticket icon.
    • If you're not in one of the Tech queues, you can skip the steps listed under the "Tech Care" title.
    • You may change the order of steps, based on how the customer answered your probing questions.
    • If you find a system issue or emerging issue, you can advise your customer of the problem.
    • Do not perform a master reset, exchange, or file a complaint until all other steps have been completed.
  3. Use these tips:
    • If the customer is on the device with the issue or doesn't have it with them, you might only be able to try some steps. See Troubleshooting process with customer on device.
    • Always restart the device. It can fix device and network issues.
    • Always install device software updates. That also fixes device and network issues.
  4. Test your work. Have the customer repeat what they did before, and make sure it doesn't cause an issue again.
  5. If not resolved, try other troubleshooting steps and solutions. Consult your coach for help.
  6. If not resolved and you've followed all the troubleshooting and issues you can, then consider a transfer to Tech support queues.

  • After resolving the issue, educate customers about what you've done to fix things and close. Explain why the issue happened and how to avoid it in the future.
  • Recap the call, so the customer understands the resolution.
    • Memo the account with the steps you completed using The Fix Memo builder.
    • Atlas The Fix automatically builds memos as you complete troubleshooting steps, making account memos.
      • When you select the step check box, it adds it to the account memo.
      • If a memo is longer than 1,978 characters, Atlas Memo builder automatically removes all document names. If you still have too many characters, a pop-up requests you reduce it to the 1,978 character limit.

Troubleshooting when unable to verify account

When troubleshooting for customers who cannot verify the account, open the account as unauthorized. The Atlas troubleshooting tool is not available for unverified accounts otherwise.

Troubleshoot technical problems following the troubleshooting process above. Answer device or feature questions.

  • Troubleshooting includes fixing services/features already included on the account.
    Example: Troubleshooting cannot make or receive calls or help with device common procedures (such as how to master reset, clear memory, and update software).
  • Use Atlas and other tools to fix problems with a service/feature that is already provisioned. In Atlas HLR Profile, you may only do the following:
    • Configure WAP, MMS, and Internet settings using the T-Mobile Device Configuration Tools.
    • Reconcile in Samson & Atlas (but not Reset).
  • If required, transfer to the next tier of support or file a trouble ticket in Atlas.
  • If a call drops after you started troubleshooting, call the customer back.

    When the caller is not verified, do not make changes that would impact service or cause charges.

    • Do not exchange devices, batteries, or chargers.
    • Do not make a change in Samson, Atlas, or other tools that are not specifically in the Allowed section above, including:
      • Add or remove a service/feature.
      • Make a change that would incur any charges.
      • Change how a service/feature works, such as modifying call forwarding settings or resetting the voicemail password.
      • Change anything that would cause a customer to lose data, such as:
        • Deleting an email account from a My T-Mobile account
        • Deleting or resetting a My T-Mobile user or password
        • IMEI unclaiming for SyncUP DRIVE
        • Reset (Resend to Switch) in Samson & Atlas
        • Removing a voicemail box
        • Requesting voicemail recovery
      • Cancel location.
      • Provide a PUK code.
      • Resend any T-Mobile partner and third-party purchases.
      • Update the SIM status.

    Reminder: Never release CPNI & PII during troubleshooting, even if the caller claims to be a T-Mobile employee or can verify account information. Never release the following to an unauthorized caller:

    • Payment amount (amount customer actually paid) and date of payment
    • Amount of last payment or most recent payment
    • IMSI, IMEI, or other unique device identifiers (Provide self-service options to retrieve IMEI from device.)
    • Roam Area Name
      Example: INTL under the heading Roam Area Name indicates a customer’s plan allows international roaming.