Understand the decision

If a verification prompt arrives when you are not signing in, pause instead of approving it to make the notification disappear. Check whether you or an authorised colleague started a legitimate action through the expected account process. Do not share a code with someone who contacts you claiming to resolve the problem. Open the service through a route you already trust, and use its official support and security guidance to investigate the unexpected request.

A practical workflow

For a business account, tell the responsible administrator what happened, including the approximate time and service involved. Avoid posting codes or unnecessary personal information in the report. Review account activity using the service’s available controls and follow its recommended recovery steps if anything is unfamiliar. If a team routinely approves prompts without understanding them, change that operating habit. The important outcome is a clear connection between a requested approval and an action the account holder actually intended.

Imagine this

Hypothetical example

A profile administrator receives a sign-in approval while in a meeting. They decline the request, open the service through their saved route and report the event to the account owner. The team reviews activity instead of treating the prompt as an inconvenient notification to dismiss.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Further reading: CISA: Require multifactor authentication ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.