If a recipient decides to opt back in, you can select their number and click "opt in" so they can receive messages from you again. This will show a list of numbers that have opted out from receiving SMS messages. This list can be managed in your AWS account in the SNS section at Text messaging (SMS)->View opted-out phone numbers. By replying "stop" to the message sent, AWS will put their number on the opt-out list and they will no longer receive any messages from you even if they are sent. Some carriers may break long messages into separate, shorter messages.ĪWS also has a mechanism for recipients to opt out of receiving messages from you. Your function call should look something like this:ĮmailSMSSend("AccessKeyHere" "SecretKeyHere" "17702349293" "Your Message Here"] If you want to send to multiple numbers, separate them with commas like so "17702349293,16781234567." The plugin will strip out any other characters besides 0-9 so phone numbers could also be put in the format +1(770)234-9293. For example the country code for the United States is +1 so any number that originates in the US needs to have "1" in front of it like so: 17702349293. Recipient numbers need to have the phone number's country code in front of it. It is best practice to create a dedicated user with these permissions only and then use the key set for this user in the EmailSMSSend function The IAM user associated with these keys will specifically need the Simple Notification Service (SNS) permissions CreateTopic, Subscribe, and Publish. Directions for creating these keys can be found here. The SMS functionality of the plugin requires that you have an AWS account and have generated an access key and secret key. Make sure that you set the correct region prior to submitting the support request. Please note that moving into production mode is done on a per region basis. Documentation for how to do so can be found here. While you can still use the SMS functionality of the Email plugin while in sandbox, we recommend that you move into production mode. When your account is moved out of the sandbox, these restrictions are removed, and you can send SMS messages to any recipient. You can delete destination phone numbers only after 24 or more hours have passed since verification or the last verification attempt. You can send SMS messages only to verified destination phone numbers (up to 10 verified destination phone numbers). SMS sandbox has the following restrictions: NOTE: While P2P long codes associated with your account may work, effective June 1, 2021, US telecom providers no longer support using person-to-person (P2P) long codes for application-to-person (A2P) communications to US destinations.īy default the SNS module's SMS functionality will be in SMS sandbox. To make the best decision on which origination number type is best for your use case you can find information about them and how to provision them here: There are stipulations and processes in regards to 10DLC and Toll Free numbers as well. Short codes are comparatively more expensive (in the US a $650 set up fee and $995 per month for each short code, cost varies by country) and it can take several weeks for short codes to become active on all carrier networks. For most use cases, a 10-DLC or Toll Free number is probably the best choice. There are 3 types of origination numbers that can be used: short codes, 10DLC, and toll-free (there are also sender-IDs if you are in a country that supports and/or requires them). You will need to have an origination number associated with your AWS account in order to use the SMS functionality of the Email plugin. You can specify different origination numbers by use case. When you send an SMS message using an origination number, the recipient's device shows the origination number as the sender's phone number. Please note that 2-way communication is currently not supported Requirements Origination NumberĪn origination number is a numeric string that identifies an SMS message sender's phone number. The Email plugin leverages Amazon AWS / SNS to send SMS messages world wide. 6.7 Saving attachments to a container field.6.6 Fetch unread messages and create new records for each.6.2 Lower the chances of your email being identified as spam.6.1 Overview: Adding HTML with Inline Attachments.5.7 Office365 Authentication unsuccessful.5.4 Downloaded emails are not decoded properly.5.3 EmailConnectX method error: "PKIX path building failed".5.2 EmailSend error: "Invalid Addresses".4.2 Office 365 OAuth Worflow: Automated Example.4.1 Office 365 OAuth Workflow: Manual Example.3.2 Google OAuth Worflow: Automated Example. 3.1 Google OAuth Workflow: Manual Example.2 Sending with Amazon Web Services Simple Email Service.1.7 Promotional vs Transactional messages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |