{"id":4942,"date":"2020-07-06T07:52:39","date_gmt":"2020-07-06T07:52:39","guid":{"rendered":"https:\/\/staging.txtbox.in\/docs\/salesforce\/?post_type=lsvr_kba&p=4942"},"modified":"2020-07-06T08:49:09","modified_gmt":"2020-07-06T08:49:09","slug":"facebook-tagged-sender-ids-templates-messages","status":"publish","type":"lsvr_kba","link":"https:\/\/staging.txtbox.in\/docs\/salesforce\/knowledge-base\/facebook-tagged-sender-ids-templates-messages\/","title":{"rendered":"Facebook Tagged Sender ID\u2019s, Templates & Messages"},"content":{"rendered":"\n

Facebook Sender ID<\/strong><\/h3>\n\n\n\n

After completing the configuration steps, you would be able to see Facebook senderID added into the \u2018Sender ID & Assignment\u2019 table in Converse settings along with one new column as \u2018Channel Type\u2019 showing channel type to which the respective senderID belongs. While sending messages, whenever a marketing or sales user goes into the selection of \u201cFrom\u201d number i.e. while selecting the senderID from the list, He will be able to understand senderID to channel tagging based on text UI identifier added in front of senderID as 4M0WHS76V6GR (Facebook).<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Facebook Templates<\/strong><\/h3>\n\n\n\n

When a sales or marketing user is trying to send a Facebook message, he will have to first select the senderID tagged with Facebook channel & based upon the senderID selected by the user, the system will load the list of templates having respective channel tagging available in the list of templates dropdown. Along with the list, he should be able to see one more tag on UI as \u201cMTM Template\u201d in front of the template name for all the templates which are marked as Facebook registered templates. With this tag, the user would be able to identify Facebook registered templates separately. <\/p>\n\n\n\n

Please note that Facebook 24 hr window condition would be applicable on top of this & according to the recipient session (Inside or outside of the active window), the templates list will be displayed for selection.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Facebook Outgoing & Incoming Messages<\/strong><\/h3>\n\n\n\n

When a marketing or sales user sends an outgoing message using the senderID tagged to Facebook channel or receives an incoming message on the senderID tagged to the Facebook channel, he will be able to see a Facebook channel icon tagged with both the messages in the conversation view at the Converse desk. Also we have introduced one more column in SMS History as \u2018Channel Type\u2019 displaying the communication channel using which he will be able to identify the Facebook outgoing & incoming messages in SMS History.<\/p>\n\n\n\n

In the case of package upgrade scenario, you would see \u2018SMS\u2019 channel icon tagged for all existing messages in the Converse desk but the channel type field value for all existing messages in SMS History will remain blank.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n
\"\"\/<\/figure>\n","protected":false},"excerpt":{"rendered":"

Facebook Sender ID After completing the configuration steps, you would be able to see Facebook senderID added into the \u2018Sender ID & Assignment\u2019 table in Converse settings along with one new column as \u2018Channel Type\u2019 showing channel type to which the respective senderID belongs. While sending messages, whenever a marketing or sales user goes into […]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"lsvr_kba_cat":[567],"lsvr_kba_tag":[],"class_list":["post-4942","lsvr_kba","type-lsvr_kba","status-publish","format-standard","hentry","lsvr_kba_cat-facebook-messaging"],"_links":{"self":[{"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba\/4942","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/comments?post=4942"}],"version-history":[{"count":1,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba\/4942\/revisions"}],"predecessor-version":[{"id":4943,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba\/4942\/revisions\/4943"}],"wp:attachment":[{"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/media?parent=4942"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba_cat?post=4942"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/staging.txtbox.in\/docs\/salesforce\/wp-json\/wp\/v2\/lsvr_kba_tag?post=4942"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}