Start with the real requirement
Look for unexpected changes in payment instructions, urgency and requests for credentials. A familiar display name or logo does not establish that the sender is authorized.
Make the process repeatable
Verify through a known independent channel. Open the service directly or use a saved contact, not the phone number or link supplied in the suspicious message.
Manage risk while making changes
Create a simple reporting process that staff can use without embarrassment. Early reporting helps contain incidents, especially when a person has already clicked or approved a request.
A practical example
For example, an invoice that changes bank details should trigger a verification step with the established contact. Replying to the message may simply reach the same attacker.
Conclusion
If credentials were entered, follow the provider’s recovery process from a clean device. Preserve relevant details and review sessions and access rather than deleting the message and hoping nothing happened.
Use this guidance as a planning aid rather than a promise of a particular outcome. Technical decisions depend on the environment, available access and existing safeguards. When requesting assistance, describe the business goal and confirm the service scope before work begins.