You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most SMS apps have an option to report spam and SMS fishing. I think such a functionality could be added to AirMessage in the form of a context option to report the sender of a message. See the following idea on a potentially simple method of implementation.
Selecting the suggested "Report Phishing" option in AirMessage could open a new message thread window and auto-populate the recipient as "7726" (The FTC's official SMS number for reporting fraud) . The messages body could also be auto-populated with the fraudulent sender's SMS number and a default message indicating the intention to report said number.
At that point the AirMessage user is left with a new thread, a pre-typed message, and the recipient as 7726. They then can then decide to send, make additional edits , or just close without sending like any other new message being drafted in the app.
The text was updated successfully, but these errors were encountered:
Most SMS apps have an option to report spam and SMS fishing. I think such a functionality could be added to AirMessage in the form of a context option to report the sender of a message. See the following idea on a potentially simple method of implementation.
Selecting the suggested "Report Phishing" option in AirMessage could open a new message thread window and auto-populate the recipient as "7726" (The FTC's official SMS number for reporting fraud) . The messages body could also be auto-populated with the fraudulent sender's SMS number and a default message indicating the intention to report said number.
At that point the AirMessage user is left with a new thread, a pre-typed message, and the recipient as 7726. They then can then decide to send, make additional edits , or just close without sending like any other new message being drafted in the app.
The text was updated successfully, but these errors were encountered: