{"id":491,"date":"2019-10-09T12:01:48","date_gmt":"2019-10-09T12:01:48","guid":{"rendered":"https:\/\/staging.txtbox.in\/docs\/salesforce-quickstart\/?post_type=lsvr_kba&p=491"},"modified":"2020-04-24T05:20:50","modified_gmt":"2020-04-24T05:20:50","slug":"configure-sender-id-inbound-number-and-assign-it-to-your-users-campaigns-and-programs","status":"publish","type":"lsvr_kba","link":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/knowledge-base\/configure-sender-id-inbound-number-and-assign-it-to-your-users-campaigns-and-programs\/","title":{"rendered":"Configure Sender ID and Assign it to your Users, Campaigns, and Programs"},"content":{"rendered":"\n

Sender ID is an alphanumeric name or number that appears on the mobile device and helps to identify the sender of the message. It can be a long code or shortcode that you assign to a single user, multiple users, or a profile. Inbound numbers should be used as the Sender Id to receive replies to your outbound messages. <\/p>\n\n\n\n

There are some countries that allow you to send SMS with Alphanumeric Sender ID. To get replies you\u2019ll need to procure an Inbound number and give reply instructions in the text of the SMS you send. For example, Dear Customer, Enjoy the Rewardz Festival on your Credit Card. To know more, SMS \u2018JOIN\u2019 to 5676756 and register now. For TnC, please visit http:\/\/bit.ly\/6463nf\u2019.<\/p>\n\n\n\n

Alphanumeric sender ID is not allowed in some countries including US, Canada, and Brazil because of carrier regulations. Therefore, non-compliance to these local carrier regulations may prevent your messages from getting delivered.
<\/br>\nYou need to reach out to sales@screen-magic.com to get the sender ID added to your org. The sender ID will then be populated in the Sender ID & Assigment section in th configuration steps.<\/div>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

You can configure Sender IDs for different organizations, teams, or individuals or Campaigns or Messaging Programs to appear as you want on the customer\u2019s mobile device. <\/p>\n\n\n\n

You can configure the default templates you wish to use to notify the User assigned to a Sender ID on any incoming message.<\/p>\n\n\n\n

In case the Sender ID is assigned to multiple users or a profile, the incoming message notification is sent as per the rules defined in the Sender ID assignment settings page.<\/p>\n\n\n\n

For example, if the Notification Recipient field displays Last Sender as its value, then the incoming message goes to the last user (within the profile or group of users) who sent the message.<\/p>\n\n\n\n

In the Manage Notification pop-up window, you can configure the notification of a Sender ID. You set the recipient of the notification as well as select the email template to be used for notifying the recipients.<\/p>\n\n\n\n

To know more about email templates and how to create them, see Email Templates<\/a>.<\/p>\n\n\n\n

You can associate an incoming number to a Sender ID only if it is defined for outgoing messages. Country-wise restrictions determine if the same Sender ID can be used for both incoming or outgoing messages.<\/p>\n\n\n\n

Guidelines for Choosing Sender ID\u2019s<\/strong><\/p>\n\n\n\n


<\/td>		Manual SMS<\/strong><\/td>Campaigns<\/strong><\/td>Automations \/ Services<\/strong><\/td><\/tr>
Key Considerations<\/td>Better to give reps or agents dedicated numbers for personalized conversations (Similar to a dedicated phone line)
Use one Sender ID for one type of conversation with a recipient (Do not use many senders because it will confuse the recipients)<\/td>		Keep dedicated numbers for campaigns (Do not mix service numbers and manual SMS\u2019)<\/td>One Service One Number \u2013 It helps in easy recall for recipients, makes compliance management easier (Think of it as a sales or support service line) <\/td><\/tr>
Exceptions<\/td>
<\/td>		Sales campaigns (Must use the lead or contact owner\u2019s sender ID)<\/td>No-Response Automations \/ Services (Must have an auto-responder telling user about the same)<\/td><\/tr>

<\/td>		If a rep or agent is absent (Share conversations, messages, and sender IDs for someone else to respond)<\/td>The campaign generated responses handled by reps should use the same campaign ID (for familiarity)<\/td>Preferable to have someone monitor automation or service responses (Key indicator of user satisfaction)
<\/td><\/tr>
Inbox<\/td>Give dedicated inbox<\/td>Filter campaign responses in inbox for sales handling<\/td>If you handle responses, then filter the Converse App in inbox<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Configure User Notification on Incoming SMS<\/strong><\/p>\n\n\n\n

You can configure User Notification on new incoming messages. You can configure the default email templates that you wish to use to notify the User assigned to a Sender ID on any incoming message. In case the Sender ID is assigned to multiple users or a profile, the incoming message notification is sent as per the rules defined in the Sender ID assignment settings page. For example, if the Notification Recipient field displays Last Sender as its value, then the incoming message goes to the last user (within the profile or group of users) who sent the message.<\/p>\n\n\n\n

In the Manage Notification pop-up window, you can configure the notification of a Sender ID. You set the recipient of the notification as well as select the email template to be used for notifying the recipients. <\/p>\n\n\n\n

For more information about configuring the sender ID, see Configure and Assign Sender ID<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Sender ID is an alphanumeric name or number that appears on the mobile device and helps to identify the sender of the message. It can be a long code or shortcode that you assign to a single user, multiple users, or a profile. Inbound numbers should be used as the Sender Id to receive replies […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"lsvr_kba_cat":[33],"lsvr_kba_tag":[],"class_list":["post-491","lsvr_kba","type-lsvr_kba","status-publish","format-standard","hentry","lsvr_kba_cat-users-and-sender-id-management"],"_links":{"self":[{"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba\/491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/comments?post=491"}],"version-history":[{"count":6,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba\/491\/revisions"}],"predecessor-version":[{"id":897,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba\/491\/revisions\/897"}],"wp:attachment":[{"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/media?parent=491"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba_cat?post=491"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/sf-quickstart\/wp-json\/wp\/v2\/lsvr_kba_tag?post=491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}