A caller asks for an SMS code
Check which action the code authorises before treating it as delivery confirmation or identity verification.
A one-time code may approve a login, reset a password or authorise a payment. Its short lifetime does not make it harmless. Identify the sending service and the exact action described in the message before deciding what to do.
Read the actual authorisation
A login code does not become a cancellation code because a caller describes it that way. If you did not initiate the action, do not approve it or read its digits aloud. A screenshot can expose the same secret. A plausible sender label alone does not explain why another person needs access.
Distinguish a real collection code
Example: a parcel may have a handover code used when it is physically delivered. That does not justify giving a caller a password-reset code from another service. Open the real order and read its instructions. If they do not match the request, end the conversation and contact support through the retailer’s existing app.
Respond to the affected service
If you disclosed a code, use the original notification to identify the account. Follow its official recovery guidance, review sessions and check recovery methods. Notify the bank promptly if bank access or a payment was involved. A public number report does not revoke an account session or reverse a transfer. Keep the message privately, without posting the code in a review.
Quick checklist
- Identify the service and action.
- Do not relay codes or screenshots.
- Check actual order instructions.
- Secure the affected account if exposed.
Sources and editorial responsibility
Prepared by the KtoTam.to team. Examples are illustrative, not user reports. Number lookups and reviews do not verify a caller’s identity. Check service terms and device instructions with the original provider.
Found an error? Tell our team which guide needs correcting and include a supporting source.
Report a correction