<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Use &#039;1600xx&#039; number series to call customers for transactions: RBI to banks</title>
    <link>https://www.taxtmi.com/news?id=30620</link>
    <description>REs must use the 1600xx series for transactional/service calls and the 140xx series for promotional calls, follow TRAI commercial communication guidelines, utilise the Mobile Number Revocation List on the Digital Intelligence Platform to clean customer databases, develop SOPs for fraud-risk monitoring, verify and update registered mobile numbers, and apply enhanced monitoring to accounts linked to revoked numbers to prevent misuse; compliance is required by March 31, 2025.</description>
    <language>en-us</language>
    <pubDate>Fri, 17 Jan 2025 19:46:03 +0530</pubDate>
    <lastBuildDate>Fri, 17 Jan 2025 19:46:03 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=789857" rel="self" type="application/rss+xml"/>
    <item>
      <title>Use &#039;1600xx&#039; number series to call customers for transactions: RBI to banks</title>
      <link>https://www.taxtmi.com/news?id=30620</link>
      <description>REs must use the 1600xx series for transactional/service calls and the 140xx series for promotional calls, follow TRAI commercial communication guidelines, utilise the Mobile Number Revocation List on the Digital Intelligence Platform to clean customer databases, develop SOPs for fraud-risk monitoring, verify and update registered mobile numbers, and apply enhanced monitoring to accounts linked to revoked numbers to prevent misuse; compliance is required by March 31, 2025.</description>
      <category>News</category>
      <law>-</law>
      <pubDate>Fri, 17 Jan 2025 19:46:03 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/news?id=30620</guid>
    </item>
  </channel>
</rss>