<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article What opt-in documentation is required for Toll-Free sender verification? in Toll-Free Numbers (TFN)</title>
    <link>https://community.sinch.com/t5/Toll-Free-Numbers-TFN/What-opt-in-documentation-is-required-for-Toll-Free-sender/ta-p/10251</link>
    <description>&lt;DIV class="p-rich_text_section"&gt;
&lt;DIV class="__unstyled paragraph alignment--left block--focussed" contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="a2hlq-0-0"&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&lt;SPAN data-offset-key="a2hlq-0-0"&gt;A compliant opt-in process (also called a "Call to Action") is required to get your toll-free number (TFN) verified. A compliant opt-in process means the way you get people’s consent to send them messages.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;You can only use a business messaging service to send messages to people who've given their explicit consent to receive those messages from you. This applies to all business messaging, including sending to employees.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="image008.png" style="width: 999px;"&gt;&lt;img src="https://community.sinch.com/t5/image/serverpage/image-id/6604i208AB5D8A6EEE98A/image-size/large?v=v2&amp;amp;px=999" role="button" title="image008.png" alt="image008.png" /&gt;&lt;/span&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="__unstyled paragraph alignment--inherit block--empty" contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="83td-0-0"&gt;
&lt;DIV&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="83td-0-0"&gt;&lt;SPAN data-offset-key="4nie8-0-0"&gt;If you don’t provide evidence of a compliant opt-in process, your TFN cannot be verified and you won’t be able to keep sending messages.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;If you don’t currently have a compliant opt-in process, you’ll need to create one to in order to get your TFN verified.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="__unstyled paragraph alignment--left " contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="fkule-0-0"&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="fkule-0-0"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;STRONG data-stringify-type="bold"&gt;Opt-in language in Terms &amp;amp; Conditions or Privacy Policy is NOT considered compliant opt-in.&amp;nbsp;TFNs used for Marketing/Promotional use cases MUST include &lt;EM&gt;visual documentation&lt;/EM&gt; (i.e. screenshot, live URL) of a compliant opt-in process in order to get verified. O&lt;SPAN class="markcj63f95ma" data-markjs="true" data-ogac="" data-ogab="" data-ogsc="" data-ogsb=""&gt;pt-in&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;has to be branded with the name of the business,&amp;nbsp;so the end user knows whose opt-in they are agreeing to.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;Examples of accepted methods of opt-in documentation include:&lt;/DIV&gt;
&lt;UL class="p-rich_text_list p-rich_text_list__bullet" data-stringify-type="unordered-list" data-indent="0" data-border="0"&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Website opt-in: Screenshot or URL of webform where the client adds number and agrees to receive messaging.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Website Posting: Screenshot or URL of where the number is advertised or where the customer finds the number to text in.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Keyword or QR Code Opt-in: Screenshot or copy of material showing where customer finds the keyword in order to opt-in to receive messages.
&lt;UL&gt;
&lt;LI&gt;If a QR code is provided, please include the URL that the QR code redirects to (ex. opt-in webform or webpage) &lt;SPAN&gt;where the end user provides their phone number with SMS disclosures&lt;/SPAN&gt;.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;There’s a legal requirement for businesses to obtain written consent before sending customers promotional text messages when using a keyword as a business must do a double Opt-in process.&lt;/LI&gt;
&lt;LI&gt;The customer provides their phone number on a form on a business’ website in exchange for a discount on their first purchase (first opt-in).&lt;/LI&gt;
&lt;LI&gt;The business sends them a text message that includes the instruction “Reply YES to receive promotional messages.”&lt;/LI&gt;
&lt;LI&gt;The customer replies “YES” (second opt-in).&lt;/LI&gt;
&lt;LI&gt;The business now has explicit written consent to send the customer promotional messages.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Voice/IVR opt-in: Verbal script and detailed description of process to opt-in.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;2FA/OTP: Screenshot of process to receive the initial text.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Paper form: Screenshot or copy of form.&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Wed, 18 Jun 2025 14:57:52 GMT</pubDate>
    <dc:creator>Meredith_W</dc:creator>
    <dc:date>2025-06-18T14:57:52Z</dc:date>
    <item>
      <title>What opt-in documentation is required for Toll-Free sender verification?</title>
      <link>https://community.sinch.com/t5/Toll-Free-Numbers-TFN/What-opt-in-documentation-is-required-for-Toll-Free-sender/ta-p/10251</link>
      <description>&lt;DIV class="p-rich_text_section"&gt;
&lt;DIV class="__unstyled paragraph alignment--left block--focussed" contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="a2hlq-0-0"&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&lt;SPAN data-offset-key="a2hlq-0-0"&gt;A compliant opt-in process (also called a "Call to Action") is required to get your toll-free number (TFN) verified. A compliant opt-in process means the way you get people’s consent to send them messages.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;You can only use a business messaging service to send messages to people who've given their explicit consent to receive those messages from you. This applies to all business messaging, including sending to employees.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="a2hlq-0-0"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="image008.png" style="width: 999px;"&gt;&lt;img src="https://community.sinch.com/t5/image/serverpage/image-id/6604i208AB5D8A6EEE98A/image-size/large?v=v2&amp;amp;px=999" role="button" title="image008.png" alt="image008.png" /&gt;&lt;/span&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="__unstyled paragraph alignment--inherit block--empty" contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="83td-0-0"&gt;
&lt;DIV&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="83td-0-0"&gt;&lt;SPAN data-offset-key="4nie8-0-0"&gt;If you don’t provide evidence of a compliant opt-in process, your TFN cannot be verified and you won’t be able to keep sending messages.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;If you don’t currently have a compliant opt-in process, you’ll need to create one to in order to get your TFN verified.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="__unstyled paragraph alignment--left " contenteditable="true" data-block="true" data-editor="2ci6m" data-offset-key="fkule-0-0"&gt;
&lt;DIV class="DraggingRow" data-testid="block-wrapper"&gt;
&lt;DIV class="public-DraftStyleDefault-block public-DraftStyleDefault-ltr" data-offset-key="fkule-0-0"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;STRONG data-stringify-type="bold"&gt;Opt-in language in Terms &amp;amp; Conditions or Privacy Policy is NOT considered compliant opt-in.&amp;nbsp;TFNs used for Marketing/Promotional use cases MUST include &lt;EM&gt;visual documentation&lt;/EM&gt; (i.e. screenshot, live URL) of a compliant opt-in process in order to get verified. O&lt;SPAN class="markcj63f95ma" data-markjs="true" data-ogac="" data-ogab="" data-ogsc="" data-ogsb=""&gt;pt-in&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;has to be branded with the name of the business,&amp;nbsp;so the end user knows whose opt-in they are agreeing to.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;Examples of accepted methods of opt-in documentation include:&lt;/DIV&gt;
&lt;UL class="p-rich_text_list p-rich_text_list__bullet" data-stringify-type="unordered-list" data-indent="0" data-border="0"&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Website opt-in: Screenshot or URL of webform where the client adds number and agrees to receive messaging.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Website Posting: Screenshot or URL of where the number is advertised or where the customer finds the number to text in.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Keyword or QR Code Opt-in: Screenshot or copy of material showing where customer finds the keyword in order to opt-in to receive messages.
&lt;UL&gt;
&lt;LI&gt;If a QR code is provided, please include the URL that the QR code redirects to (ex. opt-in webform or webpage) &lt;SPAN&gt;where the end user provides their phone number with SMS disclosures&lt;/SPAN&gt;.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;There’s a legal requirement for businesses to obtain written consent before sending customers promotional text messages when using a keyword as a business must do a double Opt-in process.&lt;/LI&gt;
&lt;LI&gt;The customer provides their phone number on a form on a business’ website in exchange for a discount on their first purchase (first opt-in).&lt;/LI&gt;
&lt;LI&gt;The business sends them a text message that includes the instruction “Reply YES to receive promotional messages.”&lt;/LI&gt;
&lt;LI&gt;The customer replies “YES” (second opt-in).&lt;/LI&gt;
&lt;LI&gt;The business now has explicit written consent to send the customer promotional messages.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Voice/IVR opt-in: Verbal script and detailed description of process to opt-in.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;2FA/OTP: Screenshot of process to receive the initial text.&lt;/LI&gt;
&lt;LI data-stringify-indent="0" data-stringify-border="0"&gt;Paper form: Screenshot or copy of form.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 18 Jun 2025 14:57:52 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Toll-Free-Numbers-TFN/What-opt-in-documentation-is-required-for-Toll-Free-sender/ta-p/10251</guid>
      <dc:creator>Meredith_W</dc:creator>
      <dc:date>2025-06-18T14:57:52Z</dc:date>
    </item>
  </channel>
</rss>

