<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tahir Almas|ICTBroadcast</title>
	<atom:link href="https://www.ictbroadcast.com/author/admin/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ictbroadcast.com</link>
	<description>Unified Auto Dialer and Predictive Dialer Software</description>
	<lastBuildDate>Sun, 15 Nov 2026 17:43:35 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://www.ictbroadcast.com/wp-content/uploads/2021/07/cropped-download-1-32x32.png</url>
	<title>Tahir Almas|ICTBroadcast</title>
	<link>https://www.ictbroadcast.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The FCC Just Cut Off Eight Voice Providers. Could Your Call Center Software Lose Its Carrier Next?</title>
		<link>https://www.ictbroadcast.com/fcc-traceback-cutoff-eight-providers-call-center-software/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Sun, 15 Nov 2026 17:43:35 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/fcc-traceback-cutoff-eight-providers-call-center-software/</guid>

					<description><![CDATA[<p>The FCC removed eight providers from the Robocall Mitigation Database on 13 November for ignoring traceback requests, with two business days for everyone else to stop taking their calls. Five carrier checks for your call center.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-traceback-cutoff-eight-providers-call-center-software/">The FCC Just Cut Off Eight Voice Providers. Could Your Call Center Software Lose Its Carrier Next?</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>On 13 November 2026 the FCC removed eight voice providers from the Robocall Mitigation Database because they ignored traceback requests. Every other carrier now has two business days to stop taking their calls. If your call center software sends traffic through one of them, even several hops upstream, your campaigns stop too, and you didn&#8217;t do anything wrong.</p>
<p>That&#8217;s the part of robocall enforcement most outbound teams never plan for. You picked a carrier, you signed a contract, the trunk registered and the calls went out. What you probably didn&#8217;t pick is the chain of providers your carrier hands calls to. This order is a reminder that any link in that chain can be cut on very short notice, and that the fastest way to get cut is to go quiet when someone asks where a call came from.</p>
<h2>What the FCC ordered on 13 November</h2>
<p>The Enforcement Bureau&#8217;s order, DA 26-1226, was adopted and released on 13 November. It removes the certifications of eight companies from the Robocall Mitigation Database (RMD): Advantage Investors llc, sunstreamnetwork, Quantum Link VOIP, Summit Industries, Scissortail Communications LLC, Globe Tech Solutions, Alpha Stream and MMN Tech LLC.</p>
<p>The history is short. On 27 August the Bureau sent a show cause order to nine companies, telling each one to fix its RMD filing or explain why it shouldn&#8217;t be removed. The eight named this week did neither. According to the order, each had failed to respond to multiple traceback requests from the industry traceback consortium, which contradicts what they&#8217;d certified in the database.</p>
<p>Here&#8217;s what the order says happens next:</p>
<ul>
<li><strong>Removal is immediate.</strong> The eight are out of the RMD as of the release date.</li>
<li><strong>Two business days to stop the traffic.</strong> All intermediate providers and voice service providers must stop accepting traffic directly from these companies within two business days of release. The only exceptions are calls to 911 and calls from public safety answering points and government emergency numbers.</li>
<li><strong>No quick comeback.</strong> None of the eight can file again without the consent of both the Wireline Competition Bureau and the Enforcement Bureau.</li>
</ul>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/11/bc-cutoff-chain.png" alt="Diagram showing a call path from call center software to a SIP carrier to an upstream provider to the called party, and the timeline from traceback request to 24-hour deadline to FCC removal order to traffic blocked two business days later" /></p>
<h2>Why a missed traceback is enough to get cut off</h2>
<p>A traceback is the industry&#8217;s way of following a suspicious call back through every network it crossed until it reaches the provider that let it in. Each provider in the path gets asked the same question: who handed you this call?</p>
<p>Since 26 February 2024, every provider filing in the RMD has certified, under penalty of perjury, that it will respond to traceback requests from the FCC, law enforcement and the industry traceback consortium within 24 hours. The order spells that out. So ignoring a traceback isn&#8217;t a paperwork slip. It makes the provider&#8217;s certification inaccurate, and an inaccurate certification is grounds for removal.</p>
<p>For you, the important thing is how that pressure flows downhill. When a traceback lands on your carrier and the call came from your account, your carrier will ask you. If you can&#8217;t answer quickly, the carrier has a choice between protecting its own listing and keeping your business. You already know which one it&#8217;ll pick.</p>
<h2>The states want the database much tighter</h2>
<p>Three days before the order, on 10 November, the National Association of Attorneys General sent reply comments to the FCC on behalf of a bipartisan group of 49 attorneys general. They back the FCC&#8217;s plan to rebuild the database and want it to go further. Among their asks:</p>
<ul>
<li>Verify provider information before a filing shows up in the RMD.</li>
<li>Require disclosures about related businesses, third-party service providers and company principals.</li>
<li>Make providers certify that their filings are accurate and that they follow the FCC&#8217;s robocall rules.</li>
<li>Make it harder for removed providers to come back under a new name.</li>
<li>Keep historical filings and publish provider status for law enforcement and industry oversight.</li>
</ul>
<p>That lines up with the FCC&#8217;s own proposal, which we covered when it hit the Federal Register: it lists <a href="https://www.ictbroadcast.com/fcc-robocall-mitigation-database-overhaul-call-center-software/">dialing platforms and call centers by name</a> as the kinds of entities the rules should reach. None of the proposal is law yet. The direction is clear, though, and this week&#8217;s order shows the Bureau is already removing providers under the rules it has today.</p>
<h2>Five carrier checks for your call center</h2>
<p>None of this needs a lawyer to start. It needs an afternoon and a short list.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/11/bc-carrier-checklist.png" alt="Five carrier checks for call center teams: look up your carrier in the Robocall Mitigation Database, ask who carries your calls upstream, keep a second trunk configured and tested, answer a traceback in minutes, only send authorized caller IDs" /></p>
<ol>
<li><strong>Look your carrier up in the RMD.</strong> Search the public database by company name. Check that a current filing exists and that a robocall mitigation plan is attached. If your carrier isn&#8217;t there, nobody else is allowed to take its calls.</li>
<li><strong>Ask who carries your calls upstream.</strong> Your contract is with one company, but your calls may cross two or three more before they reach the person you&#8217;re calling. Ask your carrier which providers it uses for your traffic, and check them too. A good carrier will tell you. A vague answer is useful information.</li>
<li><strong>Keep a second trunk ready.</strong> Two business days isn&#8217;t long enough to find, sign, provision and test a new carrier from scratch. In ICTBroadcast you can add trunks under Settings > Trunks, so keep a second one registered and run a small test campaign through it every month or so. Then a cut-off becomes a configuration change rather than an outage.</li>
<li><strong>Be ready to answer a traceback in minutes.</strong> When your carrier asks about a call, you want the campaign, the caller ID, the contact list it came from and the consent record for that number, pulled from your own system. Campaign reports and call records in your call center software should get you most of the way there. Write down who answers these requests and how, before the first one arrives.</li>
<li><strong>Only send caller IDs your carrier has authorized.</strong> ICTBroadcast&#8217;s own setup guide says it plainly: the caller ID on a campaign must be a number registered with your SIP trunk provider. Numbers you don&#8217;t control are the quickest route to a traceback, and to the <a href="https://www.ictbroadcast.com/stir-shaken-still-spam-likely-number-reputation-2026/">&#8220;Spam Likely&#8221; label</a> that follows.</li>
</ol>
<p>One more habit is worth adding. Keep your Do Not Call lists and opt-outs clean. ICTBroadcast checks campaigns against master and user DNC lists before it dials, and a list that&#8217;s honored on every campaign is the best answer you can give when someone asks why a person got called.</p>
<h2>What this means for self-hosted and cloud setups</h2>
<p>It doesn&#8217;t matter much where your software runs. Whether you host ICTBroadcast yourself or use a cloud instance, your calls still leave through a SIP trunk, and the trunk still belongs to a carrier that&#8217;s listed in the RMD or isn&#8217;t. What self-hosting does give you is direct access to your own call records, which makes the traceback question easier to answer fast. If you&#8217;re setting up a new trunk, the <a href="https://www.ictbroadcast.com/how-to-set-up-voice-broadcast-campaign/">campaign setup guide</a> walks through trunk registration, caller ID and a safe starting call rate.</p>
<p>The short version: you can&#8217;t control every network your calls cross, but you can know who they are, keep a way out ready, and make sure you&#8217;re never the reason a traceback goes unanswered.</p>
<h2>Frequently asked questions</h2>
<h3>Which providers did the FCC remove on 13 November 2026?</h3>
<p>Order DA 26-1226 removed Advantage Investors llc, sunstreamnetwork, Quantum Link VOIP, Summit Industries, Scissortail Communications LLC, Globe Tech Solutions, Alpha Stream and MMN Tech LLC from the Robocall Mitigation Database, each for failing to respond to multiple traceback requests.</p>
<h3>How long do other carriers have to stop taking their calls?</h3>
<p>Two business days from the order&#8217;s release on 13 November. After that, intermediate and voice service providers must refuse traffic directly from those companies, except calls to 911 and calls from public safety answering points and government emergency numbers.</p>
<h3>What is a traceback request?</h3>
<p>It&#8217;s a request to identify the provider that handed a particular call to your network, so a suspicious call can be followed back to its source. Every provider in the RMD has certified that it will respond within 24 hours to requests from the FCC, law enforcement and the industry traceback consortium.</p>
<h3>Does my call center have to file in the Robocall Mitigation Database?</h3>
<p>Today the filing duty sits with voice service providers, gateway providers and intermediate providers. The FCC has proposed rules that name dialing platforms and call centers, but they aren&#8217;t final. Even if you don&#8217;t file, your carrier does, and its listing decides whether your calls get through.</p>
<h3>How do I check whether my carrier is in the RMD?</h3>
<p>Search the FCC&#8217;s public Robocall Mitigation Database by company name. Confirm the filing is current and has a mitigation plan attached, then ask your carrier which upstream providers handle your traffic and check those as well.</p>
<h3>Can ICTBroadcast use more than one SIP trunk?</h3>
<p>Yes. Trunks are managed under Settings > Trunks, so you can keep a second carrier configured and tested alongside your main one, ready for the day your primary route goes away.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-traceback-cutoff-eight-providers-call-center-software/">The FCC Just Cut Off Eight Voice Providers. Could Your Call Center Software Lose Its Carrier Next?</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>FTC Warns Health Plan Callers: 5 Checks for Your Call Center Software</title>
		<link>https://www.ictbroadcast.com/ftc-health-plan-warning-letters-call-center-software/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 19:51:17 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/ftc-health-plan-warning-letters-call-center-software/</guid>

					<description><![CDATA[<p>FTC staff sent warning letters to 25 health plan marketers and lead generators on 29 October 2026, citing prerecorded call consent, Do Not Call rules and penalties of up to $53,088 per call. What the letters say and five checks for your call center software.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/ftc-health-plan-warning-letters-call-center-software/">FTC Warns Health Plan Callers: 5 Checks for Your Call Center Software</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>The FTC has sent warning letters to 25 companies that market health plans or generate leads for them, just as ACA open enrollment got going. The letters remind them that prerecorded sales calls need express, informed consent, that Do Not Call numbers are off limits without consent, and that each unlawful call can cost up to $53,088. If your call center software runs health plan campaigns this season, check your lists and recordings now.</p>
<p>FTC staff announced the letters on 29 October 2026 and said more will go out on a rolling basis. The agency didn&#8217;t name the recipients, and the letter itself says it isn&#8217;t a finding that anyone broke the law. It&#8217;s a warning, sent at the moment when calling volume for health plans is at its peak.</p>
<h2>What the letters say</h2>
<p>The press release focuses on deceptive claims. It lists the patterns FTC staff keep seeing in complaints:</p>
<ul>
<li>misrepresenting what a plan covers or what it doesn&#8217;t</li>
<li>presenting a limited benefit plan or medical discount program as comprehensive health insurance</li>
<li>misrepresenting what the plan costs</li>
<li>promising free offers, cash rewards or rebates for enrolling</li>
</ul>
<p>The letter template, which the FTC published alongside the release, goes further, and this is the part call center operators should read. It says consumers have also reported unsolicited calls promoting healthcare products, and then cites the Telemarketing Sales Rule. In the letter&#8217;s words, the TSR prohibits sellers and marketers from making outbound calls that deliver prerecorded messages &#8220;to induce the purchase of products, including health insurance&#8221; without express, informed consent. It also prohibits calling numbers on the National Do Not Call Registry, &#8220;absent consent or other narrow exceptions&#8221;.</p>
<p>The third rule in the letter is the Impersonation Rule, 16 CFR Part 461. It bans posing as a government agency, such as the Department of Health and Human Services, or as a business such as an insurance carrier. It also bans implying that you&#8217;re affiliated with or endorsed by one.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/11/bc-ftc-letter-three-rules.png" alt="Diagram of the three rules in the FTC warning letter to health plan marketers: deceptive claims, the Telemarketing Sales Rule and the Impersonation Rule, with penalties of up to 53,088 dollars per violation for call center software users" /></p>
<h2>Why &#8220;per call&#8221; is the number to remember</h2>
<p>The letter says violations can bring a federal court injunction that halts the business, plus civil penalties of up to $53,088 per violation. It then adds the line that matters most for anyone running a dialer: &#8220;each unlawful call, advertisement, or misrepresentation may constitute a separate violation&#8221;.</p>
<p>That changes the maths of a bad list. A voice broadcast to 10,000 numbers that lacked consent isn&#8217;t one mistake. It&#8217;s 10,000 of them. Some compliance blogs still quote an older figure of $51,744. The current letter says $53,088, so use that.</p>
<p>The FTC also listed past cases to show it means it. They include a $145 million settlement with Assurance IQ and MediaAlpha, a $195 million judgment against Simple Health Plans and $100 million in refunds from Benefytt. One case from this year, FTC v. Top Healthcare Options in the Southern District of Florida, is still being litigated, and the court has issued a preliminary injunction. Several of those cases involved lead generators who sold consumer details to telemarketers, which is exactly the supply chain behind many health plan call lists.</p>
<h2>What this means for your dialing operation</h2>
<p>If you run outbound campaigns for insurance agencies, brokers or lead buyers, the letter is a checklist in disguise. Here&#8217;s how we&#8217;d read it.</p>
<h3>Know where every number came from</h3>
<p>Health plan lists often pass through two or three lead sellers before they reach a dialer. The FTC has gone after lead generators before, and its letter asks recipients to review what&#8217;s said &#8220;through third-party distributors, marketing affiliates, and sales agents&#8221;. If you can&#8217;t trace a number back to the form or call where the person gave it, you can&#8217;t show consent for it.</p>
<h3>Treat prerecorded campaigns as a separate category</h3>
<p>A voice broadcast that plays a recorded sales message needs express, informed consent under the TSR, whatever the list looks like. Scrubbing against the Do Not Call Registry doesn&#8217;t fix a missing consent. Keep prerecorded sales campaigns to numbers with a consent record you can produce, and run everything else as live-agent calling.</p>
<h3>Scrub every list, every time</h3>
<p>Load a fresh copy of the National Do Not Call Registry, no more than 31 days old, and apply your own internal opt-out list on top. Check that both run against every campaign, including the small test batches people forget.</p>
<h3>Listen to the recording and the script</h3>
<p>The deceptive claims in the release come straight out of call scripts. &#8220;Full coverage&#8221;, &#8220;free plan&#8221; and &#8220;cash back when you enroll&#8221; are phrases worth searching for in every recording and agent script before a campaign starts. If the plan is a limited benefit or discount product, the message has to say so.</p>
<h3>Say who&#8217;s calling</h3>
<p>Under the Impersonation Rule, the greeting and caller ID can&#8217;t suggest you&#8217;re Medicare, HHS or a named insurer unless you are. &#8220;Calling about your health benefits&#8221; from an unnamed caller is the kind of opening that invites a complaint.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/11/bc-ftc-campaign-gate.png" alt="Five checks before a health plan campaign starts in call center software: number source, written consent, Do Not Call scrub, script review and caller identity" /></p>
<h2>How ICTBroadcast fits in</h2>
<p>ICTBroadcast is call center software that runs voice broadcasts, predictive and progressive dialing, SMS and email campaigns from one system. For this kind of campaign, a few parts matter.</p>
<ul>
<li><strong>Two DNC lists.</strong> The Master DNC list holds registry data, such as numbers you download from the FTC&#8217;s registry, and each user&#8217;s own opt-outs go on the User DNC list. Numbers on either list are skipped automatically when a campaign runs. The <a href="https://www.ictbroadcast.com/amd-dnc-support-autodialer-software-voice-broadcastng-do-not-call-list-appliction/">DNC support page</a> explains both.</li>
<li><strong>Recorded and live calling kept apart.</strong> A voice broadcast campaign plays a recorded message with no agents involved, while predictive dialing connects answered calls to live agents. Because they&#8217;re different campaign types, you can keep recorded messages to the lists that have consent for them. Our <a href="https://www.ictbroadcast.com/how-to-set-up-voice-broadcast-campaign/">voice broadcast setup guide</a> walks through it.</li>
<li><strong>Opt-out by keypress.</strong> In a voice broadcast, people who press the opt-out key are added to the DNC list automatically and won&#8217;t get future calls.</li>
<li><strong>Time zones.</strong> A campaign can apply a time zone per contact from your CSV, or one time zone for the whole campaign, so calls land inside allowed hours. See <a href="https://www.ictbroadcast.com/time-zone-based-restrictions-on-telemarketing-campaigns-ictbroadcast-autodialer-scheduling/">time zone restrictions on telemarketing campaigns</a>.</li>
</ul>
<p>What the software can&#8217;t do is decide whether a lead seller&#8217;s consent is real, or rewrite a misleading script. Downloading the registry on schedule, keeping consent records and reviewing recordings are your jobs, and each user is responsible for following federal and state law. If you&#8217;ve been following the TCPA side of consent too, our post on <a href="https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/">the robocall consent case everyone is quoting wrong</a> covers it.</p>
<p>A quick test before your next health plan campaign: pick ten numbers from the list and try to show, for each one, where it came from and what the person agreed to. If you can&#8217;t do that from your own records, don&#8217;t load the recording yet.</p>
<h2>Frequently asked questions</h2>
<h3>Who got the FTC warning letters?</h3>
<p>FTC staff sent letters to 25 companies that market ACA Marketplace plans, limited benefit plans or medical discount programs, or generate leads for them. The FTC didn&#8217;t name them, and it says more letters will follow.</p>
<h3>Does a warning letter mean a company broke the law?</h3>
<p>No. The letter says it doesn&#8217;t reflect a conclusion that the recipient did anything illegal. It&#8217;s a reminder of the rules, with a note that FTC staff are watching the market and will act where needed.</p>
<h3>Can I play a prerecorded message to health plan leads?</h3>
<p>Only with express, informed consent for prerecorded sales calls, according to the Telemarketing Sales Rule as described in the letter. Being off the Do Not Call Registry isn&#8217;t enough on its own.</p>
<h3>How much can each violation cost?</h3>
<p>Up to $53,088 per violation, and the letter says each unlawful call, ad or misrepresentation may count separately. A federal court can also order a business to stop operating or pay refunds.</p>
<h3>Does this apply only to ACA plans?</h3>
<p>No. The letter covers ACA Marketplace insurance and other healthcare products such as limited benefit plans and medical discount programs, and the TSR and Do Not Call rules apply to telemarketing generally.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/ftc-health-plan-warning-letters-call-center-software/">FTC Warns Health Plan Callers: 5 Checks for Your Call Center Software</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>$251 a Number: What Teleflora&#8217;s Text Settlement Means for Your Call Center Software</title>
		<link>https://www.ictbroadcast.com/teleflora-text-dnc-settlement-call-center-software/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Tue, 20 Oct 2026 10:22:02 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/teleflora-text-dnc-settlement-call-center-software/</guid>

					<description><![CDATA[<p>Teleflora agreed to pay $6M, about $251 per number, over promotional texts sent to phones on the Do Not Call Registry. Who is in the class, why texts count, and the four checks your call center software should run before every SMS send.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/teleflora-text-dnc-settlement-call-center-software/">$251 a Number: What Teleflora&#8217;s Text Settlement Means for Your Call Center Software</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>Teleflora has agreed to pay $6 million, about $251 per phone number, to settle claims that it sent promotional texts to people on the National Do Not Call Registry. If your call center software sends SMS campaigns, the settlement is a clear price tag on a check that takes minutes to run before every send.</p>
<p>The case is Carter v. Teleflora LLC, filed on 26 June 2026 in the Circuit Court for Miami-Dade County, Florida (case 2026-012979-CA-01). The court gave preliminary approval on 26 August, the notice went out this month, and the final approval hearing is set for 25 November 2026. Teleflora denies doing anything wrong. It settled anyway, and the reasons it did are worth reading if you run outbound messaging.</p>
<h2>Who is in the class</h2>
<p>The class definition is short, and every word in it is a test your own campaigns can fail. A phone number is in if all three of these are true:</p>
<ul>
<li><strong>The person never gave Teleflora their number.</strong> That phrase points at numbers that came from somewhere else, such as a bought list, a data append or a partner.</li>
<li><strong>The number had been on the National Do Not Call Registry for at least 30 days</strong> when the texts arrived.</li>
<li><strong>Teleflora sent more than one promotional text to it within 12 months.</strong> The class period runs from 9 May 2021 to 26 August 2026.</li>
</ul>
<p>About 23,844 numbers qualify. Six million dollars across that many numbers is where the $251 estimate comes from, before fees and administration costs come out of it.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/10/bc-teleflora-class.png" alt="Diagram of the three tests that put a phone number in the Teleflora text message Do Not Call class settlement, relevant to SMS campaigns in call center software" /></p>
<h2>Why texts count as calls here</h2>
<p>The TCPA&#8217;s Do Not Call section, 47 U.S.C. 227(c), lets a person sue when they get more than one telemarketing call within 12 months while their number is on the registry. Damages are up to $500 per violation, and a court can triple that if the violation was willful or knowing.</p>
<p>The FCC said in December 2023, in order FCC 23-107, that it was codifying the registry&#8217;s protections for text messages as well as calls. So the federal regulator&#8217;s position is plain: a marketing text to a registered number is treated the way a marketing call would be.</p>
<p>Some courts have read the statute differently. Eric Troutman of TCPAWorld, writing about this settlement on 19 October, pointed to recent decisions holding that texts fall outside the DNC rules, that cell phones aren&#8217;t covered, or that there&#8217;s no private right of action under those rules at all. His view is that Teleflora paid more than it had to. That may be right, but it&#8217;s a split, not a settled rule. Plenty of defendants decide that $251 a number is cheaper than finding out which side of the split their judge lands on.</p>
<p>For a business sending texts, the practical reading is simple. Don&#8217;t build your campaign on the hope of winning that argument. Scrub as if texts are covered, because the FCC says they are.</p>
<h2>The defense Teleflora could have used</h2>
<p>The DNC rules carry a safe harbor. Under 47 CFR 64.1200(c)(2), a seller that shows it followed routine business practices can defend a call or text that slipped through by mistake. The rule lists what those practices are:</p>
<ul>
<li>written procedures for complying with the national Do Not Call rules</li>
<li>training for staff on those procedures</li>
<li>a list of numbers the seller may not contact</li>
<li>a process that checks the registry using a version no more than 31 days old</li>
<li>records showing all of this happened</li>
</ul>
<p>The safe harbor protects a business that made an error despite doing the work. It doesn&#8217;t help a business that never scrubbed in the first place, and it only works if you can prove the process with records.</p>
<h2>Four checks before a marketing text goes out</h2>
<p>Here&#8217;s the order we&#8217;d run them in on every SMS broadcast. Any &#8220;no&#8221; drops the number from that send, and the reason gets logged.</p>
<ol>
<li><strong>Is there consent or a relationship on file?</strong> Know where each number came from and when. &#8220;The person gave us this number&#8221; is a very different position from &#8220;a vendor sold us this number&#8221;, and the class definition turns on that difference.</li>
<li><strong>Is the number clear of the national registry?</strong> Check against a registry copy that&#8217;s no older than 31 days. If a number joins the registry, you have up to 31 days to honor it, not forever.</li>
<li><strong>Is it clear of your own DNC and STOP list?</strong> Every opt-out counts, whether it arrived as a STOP reply, a keypress on a voice call, an email or a word to an agent. It should block every channel, not just the one it came in on.</li>
<li><strong>Is it inside your sending window?</strong> Federal rules allow telephone solicitations between 8am and 9pm in the recipient&#8217;s local time. Many states set tighter hours and add days of the week.</li>
</ol>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/10/bc-sms-presend-check.png" alt="Flowchart of four checks to run before sending a marketing text message: consent, national Do Not Call registry, internal DNC and STOP list, and sending hours, in call center software" /></p>
<p>Count texts per number, too. The statute&#8217;s trigger is more than one message in 12 months, so a business that sends one promotional text a week to a registered number crosses it in the second week.</p>
<h2>How ICTBroadcast handles DNC for SMS</h2>
<p>ICTBroadcast runs voice, SMS, email and fax campaigns from one system, and it keeps two kinds of Do Not Call list. The <strong>Master DNC</strong> list holds country-wide registry data, such as numbers you download from the FTC&#8217;s registry, and the <strong>User DNC</strong> list holds each user&#8217;s own opt-outs. Any number on a DNC list is skipped automatically when a campaign runs. The <a href="https://www.ictbroadcast.com/amd-dnc-support-autodialer-software-voice-broadcastng-do-not-call-list-appliction/">DNC support page</a> explains both lists.</p>
<p>On SMS campaigns, when someone replies STOP, the platform adds them to your do-not-contact list so they drop out of every future campaign. The <a href="https://www.ictbroadcast.com/sms-broadcasting/">SMS broadcasting guide</a> covers throttling, delivery reports and opt-out handling in detail.</p>
<p>What the software can&#8217;t do is decide where your numbers came from or keep your registry copy fresh for you. Downloading the registry, loading it on a schedule that keeps it inside 31 days, and keeping consent records are your jobs. As our DNC page says, it&#8217;s up to each user to follow federal and state law. If you&#8217;re unsure what consent your campaign needs in the first place, we covered the latest consent ruling in <a href="https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/">the robocall consent case everyone is quoting wrong</a>.</p>
<p>A good test is to pick ten numbers from your last SMS campaign and try to answer two questions for each one. Where did this number come from, and when did we last check it against the registry? If you can&#8217;t answer both from your records, that&#8217;s the gap a class action would find.</p>
<h2>Frequently asked questions</h2>
<h3>How much is the Teleflora settlement per person?</h3>
<p>The fund is $6 million for about 23,844 phone numbers, so the estimate is up to $251 per number, before attorney fees and administration costs are taken out.</p>
<h3>Do Do Not Call rules apply to text messages?</h3>
<p>The FCC says yes. In December 2023 it codified that National Do Not Call Registry protections extend to texts. Some courts have recently disagreed, so the question isn&#8217;t fully settled, but the safest course is to treat marketing texts like marketing calls.</p>
<h3>How often do I need to scrub against the Do Not Call Registry?</h3>
<p>The FCC&#8217;s safe harbor requires a registry version obtained no more than 31 days before the call or text. In practice that means refreshing your copy at least monthly and scrubbing before each campaign.</p>
<h3>Does a STOP reply count as a Do Not Call request?</h3>
<p>Treat it as one. A STOP reply should go on your internal do-not-contact list straight away and block that number across every channel you use, not just SMS.</p>
<h3>Does ICTBroadcast scrub against the national registry automatically?</h3>
<p>ICTBroadcast skips any number on its Master DNC or User DNC lists. You load the registry data into the Master DNC list yourself and keep it current. STOP replies to SMS campaigns are added to the do-not-contact list automatically.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/teleflora-text-dnc-settlement-call-center-software/">$251 a Number: What Teleflora&#8217;s Text Settlement Means for Your Call Center Software</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Robocall Consent Ruling Everyone Is Quoting Was Decided on a Phone in the Mississippi</title>
		<link>https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Tue, 22 Sep 2026 19:32:21 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/</guid>

					<description><![CDATA[<p>A Maryland court suggested that giving a business your number is consent for prerecorded calls. Read the order and the certification was denied because the plaintiff threw his phone in a river.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/">The Robocall Consent Ruling Everyone Is Quoting Was Decided on a Phone in the Mississippi</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>A ruling out of Maryland is being passed around as though prior express consent just got much easier. The line people are quoting is that a consumer consents to <em>the call</em>, not to the prerecorded voice used to make it. Before you touch your consent capture, read what the court actually decided. It denied class certification because the plaintiff threw his phone into the Mississippi River.</p>
<h2>The case</h2>
<p>Smith v. ExamWorks, 2026 WL 2823260, decided in the District of Maryland on 21 September 2026, case number 8:21-cv-02746-PX. Filed back in October 2021, it was a two-count class action against GEICO and ExamWorks over non-emergency prerecorded calls placed by a GEICO vendor to schedule independent medical examinations.</p>
<p>The court refused to certify the class. The reason given most attention in the write-ups is adequacy: to represent a class you have to show you are in the same position as its members, and this plaintiff was not, because at some point during the litigation he destroyed the single most important piece of evidence. With the handset gone, the defence could not examine it to establish who had been messaging him, what he had been doing, or even that the calls had landed on that phone at all.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/bc-ruling-vs-quote.png" alt="Comparison of what Smith v. ExamWorks decided, namely class certification denied on adequacy after evidence destruction, against the consent findings it is being quoted for" width="1000" style="max-width:100%;height:auto;"></p>
<h2>Where the consent language comes in</h2>
<p>Along the way the court made some observations that would help callers if they stand. One is that consent can be conveyed by conduct, so handing a business your phone number can itself amount to prior express consent. The other is the reading being quoted everywhere: that the statutory phrase about a call made with prior express consent attaches to the call, not to the use of a prerecorded voice. On that reading a consumer does not have to agree to the technology, only to being contacted.</p>
<p>That is genuinely interesting, and it may matter later. It is also not what the case was decided on. The certification denial did not rest on it, which is the textbook definition of a remark a later court is free to ignore.</p>
<p>The lawyer who broke the story is blunt about it himself. His write-up describes the court&#8217;s other findings as likely driven by its irritation at the destruction of evidence. When the person arguing your side says the reasoning was coloured by the plaintiff&#8217;s behaviour, that is a signal about how much weight it will carry.</p>
<h2>Why we are not changing anything, and nor should you</h2>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/bc-consent-hold.png" alt="Four reasons not to loosen consent capture: a single district court that disagrees with itself, nationwide exposure, separate state law, and the value of good consent records" width="1000" style="max-width:100%;height:auto;"></p>
<p>Start with the fact that the same district pointed the other way six months ago. A March 2026 decision in the District of Maryland suggested consent has to reference the regulated technology. Two orders, one courthouse, opposite directions, and no appellate ruling tidying it up. A split like that is a reason to sit still, not to move.</p>
<p>Then there is geography. A <a href="https://www.ictbroadcast.com/">call center software</a> operation places calls into every state, and the plaintiff picks the forum. A helpful reading in Maryland does nothing for you in a district that has never considered the question.</p>
<p>State law is the third problem, and the one people forget. Florida, Oklahoma and Washington run their own telemarketing statutes with their own consent standards and their own private rights of action. A federal court&#8217;s reading of the TCPA does not move any of them. Plenty of operators who are clean federally have been sued under a state statute instead.</p>
<p>And this is also single-source for now. One specialist blog has written it up, in two posts on the same day. That is not a criticism of the reporting, it is a statement about how much confirmation exists. Before rebuilding a consent flow on the strength of it, wait for other lawyers to read the order.</p>
<h2>What is actually worth doing this week</h2>
<p>The useful lesson in this case is not about consent at all. It is that the defence won because it could point at missing evidence, and the plaintiff lost because the record was gone.</p>
<p>That cuts both ways, and your side of it is the consent file. For every number you dial you want to be able to produce where it came from, what the person was looking at when they gave it, the exact wording they agreed to, and the timestamp. Not a flag in a column saying consent equals yes, but the underlying record.</p>
<p>Three things make that real in a dialling platform:</p>
<ul>
<li><strong>Store the form as it appeared, not just the answer.</strong> Consent language changes. If you cannot show what the page said in March, you cannot prove what somebody agreed to in March.</li>
<li><strong>Keep the provenance with the record.</strong> Numbers arrive from web forms, imported lists, partner feeds and inbound calls, and those carry very different weight. Merge them into one field and you have thrown away the distinction a court will ask about.</li>
<li><strong>Retain long enough to survive the limitation period.</strong> A four year old claim needs a four year old record. Retention policies written for storage cost tend not to account for that.</li>
</ul>
<p>None of that depends on how this consent question resolves. It is what turns a lawsuit into an early exit regardless of which way the reading goes.</p>
<h2>Frequently asked questions</h2>
<h3>Does this mean giving out my number is now consent to robocalls?</h3>
<p>No. One district court suggested it might be, in a case decided on other grounds, and another judge in the same district suggested otherwise earlier this year. Nothing has changed about what you are required to do.</p>
<h3>Is the ruling binding anywhere?</h3>
<p>District court decisions bind nobody, not even other judges in the same district. They carry persuasive weight, and a point the decision did not rest on carries less of it again.</p>
<h3>Should we stop asking for technology-specific consent?</h3>
<p>No. Asking somebody to agree to prerecorded or automated calls costs you a line of text and removes an argument. Dropping it to chase a favourable reading that might not survive is a poor trade.</p>
<h3>What about informational calls like appointment scheduling?</h3>
<p>That was the setting here, and informational calls have always had a different consent posture from marketing. The distinction is worth keeping clear in your campaign configuration, because it decides what a revocation covers.</p>
<h3>How long should consent records be kept?</h3>
<p>Long enough to cover the limitation period for every claim you could face, federal and state, which is longer than most retention defaults. Work backwards from the longest one that applies to you.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/tcpa-prior-express-consent-call-center-software/">The Robocall Consent Ruling Everyone Is Quoting Was Decided on a Phone in the Mississippi</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The FCC&#8217;s Robocall Database Overhaul Names Dialing Platforms and Call Centers</title>
		<link>https://www.ictbroadcast.com/fcc-robocall-mitigation-database-overhaul-call-center-software/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Sun, 13 Sep 2026 05:14:21 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/fcc-robocall-mitigation-database-overhaul-call-center-software/</guid>

					<description><![CDATA[<p>The FCC's Robocall Mitigation Database proposal hit the Federal Register on 9 September 2026, with comments due 9 October. It says the rules should reach an entity by what it does with voice traffic, and it names dialing platforms and call centers directly.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-robocall-mitigation-database-overhaul-call-center-software/">The FCC&#8217;s Robocall Database Overhaul Names Dialing Platforms and Call Centers</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>The FCC&#8217;s proposal to rebuild the Robocall Mitigation Database was published in the Federal Register on 9 September 2026. Comments are due 9 October, replies 9 November. The line that matters for anyone running outbound: the Commission wants the rules to reach an entity by what it does with voice traffic, and it names dialing platforms and call centers as examples.</p>
<p>That is a change in kind, not degree. For five years the database has been a place where carriers file a description of how they fight illegal robocalls. The proposal turns it into a vetting file that decides whether you get to hand traffic to anyone.</p>
<h2>What the proposal actually says</h2>
<p>The Further Notice was adopted 22 July and released 23 July 2026, under WC Docket Nos. 24-213 and 17-97 and CG Docket No. 17-59. None of it is law yet. Read what follows as the direction of travel rather than a checklist you owe anybody in October.</p>
<p>The scope language is the part worth reading twice. The FCC proposes clarifying that the rules apply across the voice ecosystem regardless of how an entity describes its service, and it lists VoIP resellers, MVNOs, PBX providers, dialing platforms and call centers. If you have spent years confident that the database was your carrier&#8217;s problem, that sentence is aimed at you.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/rmd-who-files.png" alt="Diagram showing who files in the Robocall Mitigation Database today versus the VoIP resellers, MVNOs, PBX providers, dialing platforms and call centers named in the FCC proposal" width="1000" /></p>
<p>I want to be careful not to overstate this, because plenty of compliance blogs will. The proposal asks questions. It does not yet impose a filing duty on every call center in the country, and a lot of comment filings between now and November will argue about exactly where that line lands. But the Commission has been widening this net steadily since the gateway provider rules, and I would not bet on it narrowing.</p>
<h2>Four certifications, and one with a clock on it</h2>
<p>Filers would certify four things: that they have not submitted false, misleading or inaccurate information to the FCC, that they comply with the robocall, caller ID authentication and numbering rules, that they meet STIR/SHAKEN attestation requirements, and that they respond to traceback requests within 24 hours.</p>
<p>That last one is the operational item. Twenty four hours is not long if traceback requests land in a shared inbox that somebody checks when they get a minute. The Industry Traceback Group typically wants to know which customer originated a specific call at a specific second, and if your platform cannot answer that from a CDR in a few minutes, the clock is already against you.</p>
<p>Run a drill. Pick a call from last Tuesday out of your own logs and see how long it takes someone who is not you to produce the originating tenant, the source IP, the caller ID presented, and the consent record. Most teams find the answer is somewhere between twenty minutes and never.</p>
<h2>The disclosures are about people, not technology</h2>
<p>The proposed filing would carry principals&#8217; contact details and citizenship, every affiliate and subsidiary, a US registered agent, prior regulatory actions, and identification of third party vendors. Any STIR/SHAKEN exemption you claim would have to name the specific rule that allows it and explain why it applies using facts about your own network.</p>
<p>Read that list again and notice what the FCC is building. It is a map of who is behind an entity, so that a provider removed under one name cannot reappear the following month under another. The database stops being a description of your mitigation and becomes a description of you.</p>
<p>For an honest operator this is mostly paperwork. For anyone who has ever quietly stood up a second company to carry traffic the first one could not, it is the end of that trick.</p>
<h2>How a stale filing becomes blocked traffic</h2>
<p>The enforcement side is where the proposal has teeth. Staff would be able to hold a filing in pending status, withhold publication, or reject it outright, particularly where it looks connected to a previously removed provider. Grounds for suspension or removal get codified: a deficient filing, inconsistencies with what the Commission can see elsewhere, failure to update on time, carrying illegal calls, mitigation that does not work in practice, and caller ID authentication violations. Serious cases get an expedited process with five days to cure or respond before removal.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/rmd-removal-clock.png" alt="Flow from filing or update through FCC staff screening, a five day cure window, and removal, with the codified grounds for suspension alongside the routine obligations that avoid them" width="1000" /></p>
<p>Removal from the database is not a fine. It means downstream providers are required to stop accepting your traffic. You do not get to appeal your way back into service while your campaigns keep dialing. That asymmetry is the whole point, and it is why the existing obligations are worth more attention than they usually get: recertify by 1 March every year, and update the entry within ten business days of a change to your address, ownership, registered agent or officers.</p>
<p>The ten day rule catches more people than the annual one. Nobody forgets 1 March twice. Plenty of companies change a registered agent in June and update the database the following spring.</p>
<h2>What this asks of your call center software</h2>
<p>Strip out the filing mechanics and four capabilities decide whether you can live with rules like these. They are worth auditing whatever happens to this proposal.</p>
<p><strong>Per-tenant attribution that survives a year.</strong> When a traceback arrives you need to name the customer, not the platform. On a multi-tenant deployment that means CDRs that carry the tenant identity, the campaign, and the caller ID presented, retained long enough to answer a request about a call from eight months ago.</p>
<p><strong>Consent you can produce, not just claim.</strong> The certification about complying with the robocall rules is only as good as the record behind it. If consent lives in a CRM nobody exports and the dialer only holds a phone number, you have an assertion rather than evidence.</p>
<p><strong>Controls that actually stop a campaign.</strong> Your mitigation description has to match what the platform enforces. Do not write that you throttle suspicious traffic if the only throttle is a person watching a dashboard. <a href="https://www.ictbroadcast.com/how-predictive-dialers-work-2026-pacing-abandonment-compliance/">Pacing, abandonment and calling window controls</a> that are configured at the tenant level are the difference between a description and a control.</p>
<p><strong>Somebody who owns the traceback queue.</strong> This is a staffing answer, not a software one, but the software decides how painful it is. A named person, a monitored address, and a documented lookup that takes minutes.</p>
<p>Self-hosted platforms have a real advantage on the first two, and I say that as someone with an obvious interest. When the CDRs and the consent records sit in your own database you can answer a traceback without opening a vendor ticket. When they sit in a hosted platform you are waiting on somebody else&#8217;s support queue while a 24 hour clock runs. We made a similar argument about <a href="https://www.ictbroadcast.com/fcc-upstream-provider-vetting-outbound-calling/">upstream provider vetting</a> last year, and this proposal is the same pressure arriving one layer closer to you.</p>
<h2>What I would do before March</h2>
<p>Not much of this requires a decision from the FCC first.</p>
<p>Check whether your company or any affiliate has an entry in the database, and read what it says. A surprising number of entries were written by someone who left, describe a stack that has since been replaced, and have not been touched since the original filing. If the description does not match what your platform does today, that is an inconsistency under the proposed grounds for removal, and it is also just bad practice.</p>
<p>Then write down your affiliates. Every entity that touches the traffic, every reseller relationship, every white label tenant operating under their own brand. The proposal wants that list and most operators cannot produce it in an afternoon.</p>
<p>Last, if the scope language worries you, file a comment. The window is open until 9 October and the record is genuinely thin on what these rules cost a twenty seat call center as opposed to a carrier. Regulators write the rule they have evidence for. Nobody is going to make that argument on your behalf.</p>
<h2>FAQ</h2>
<h3>Does my call center have to file in the Robocall Mitigation Database today?</h3>
<p>Today the filing obligation sits with voice service providers and intermediate and gateway providers. If you buy origination from a carrier and do not hold numbering resources yourself, you are most likely not a filer. The proposal asks whether that line should move, and names call centers and dialing platforms while asking.</p>
<h3>What happens if a provider is removed from the database?</h3>
<p>Downstream providers are required to stop accepting its traffic. In practice that is an outage rather than a penalty, which is why filings and updates deserve more attention than their tedium suggests.</p>
<h3>When are the comment deadlines?</h3>
<p>Comments are due 9 October 2026 and reply comments 9 November 2026, in WC Docket Nos. 24-213 and 17-97 and CG Docket No. 17-59. The Further Notice was adopted 22 July and published in the Federal Register on 9 September 2026.</p>
<h3>Is the 24 hour traceback response a new rule?</h3>
<p>Responding to traceback has been expected for years. What the proposal adds is a certification, signed by you, that you do it within 24 hours. Certifying something you cannot demonstrate is a worse position than not certifying it.</p>
<h3>Does STIR/SHAKEN exemption paperwork change?</h3>
<p>Under the proposal, claiming an exemption would mean naming the rule that authorises it and explaining why it applies with facts about your own network. A generic exemption claim would not survive screening.</p>
<h3>How does ICTBroadcast help with any of this?</h3>
<p>It is not a compliance product and I would not sell it as one. What it gives you is the underlying evidence: per-tenant CDRs on your own server, recordings, calling window and pacing controls set per tenant, and a REST API to pull all of it out when someone asks. Our <a href="https://www.ictbroadcast.com/tcpa-stir-shaken-compliance-outbound-calling-checklist/">TCPA and STIR/SHAKEN checklist</a> covers the rest of the routine. The filing is still yours to write.</p>
<p>If you are sizing up whether your current stack could answer a traceback inside a day, that is a good test to run this week rather than next March. Take ICTBroadcast for a look and try the lookup on your own data.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-robocall-mitigation-database-overhaul-call-center-software/">The FCC&#8217;s Robocall Database Overhaul Names Dialing Platforms and Call Centers</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Your Calls Pass STIR/SHAKEN and Still Say Spam Likely. Here Is Why</title>
		<link>https://www.ictbroadcast.com/stir-shaken-still-spam-likely-number-reputation-2026/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Tue, 01 Sep 2026 18:00:07 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/stir-shaken-still-spam-likely-number-reputation-2026/</guid>

					<description><![CDATA[<p>STIR/SHAKEN proves a number is really yours, but carriers still decide the label from how you dial. Here is what drives number reputation in 2026 and how to protect it.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/stir-shaken-still-spam-likely-number-reputation-2026/">Your Calls Pass STIR/SHAKEN and Still Say Spam Likely. Here Is Why</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>If your outbound numbers pass STIR/SHAKEN with A-attestation and still show up as &#8220;Spam Likely,&#8221; you are not doing anything wrong with the standard. Attestation proves the number is really yours. It says nothing about how you dial it. The label comes from a separate carrier reputation model, and that model watches your call patterns, not your signature. Fix the patterns and the label follows.</p>
<h2>Attestation and reputation are two different things</h2>
<p>A lot of teams treat STIR/SHAKEN as a spam-label fix. It isn&#8217;t one. The framework lets a carrier vouch that the caller ID hasn&#8217;t been spoofed. A-attestation means your provider knows you and confirmed you own the number. That&#8217;s real value, and you want it. But the phone that rings is a mobile handset running its own screening, fed by the carrier&#8217;s analytics engine, and that engine scores every number on behavior.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/ictb-number-reputation-pipeline.png" alt="Diagram showing how a STIR/SHAKEN attested call still passes through carrier analytics that decide whether it rings clean, shows Spam Likely, or is blocked" /></p>
<h2>What the carrier model actually looks at</h2>
<p>Every carrier keeps its own recipe, but the signals overlap. High call volume from one number in a short window reads like a spam run. A large share of very short calls, the kind that end in a second or two, looks like people declining a robocall. Complaint reports weigh heavily, and so do repeated hits against numbers that have gone quiet or landed on do-not-call lists. Roll those together and you get a rolling reputation score. Cross a threshold and the label flips.</p>
<h2>Six habits that keep numbers clean</h2>
<p>Reputation is earned by how you run campaigns, day after day. These are the levers that matter, and good <a href="https://www.ictbroadcast.com/">call center software</a> should make each one easy rather than manual.</p>
<p><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/09/ictb-protect-number-reputation.png" alt="Six habits that protect call center number reputation: healthy pacing, clean lists, branded caller ID, spreading load across numbers, watching complaints, and respecting calling windows" /></p>
<p>Start with pacing. Keep abandonment low and close the silent gap between an answer and an agent, because that gap is the single clearest robocall tell. Scrub your lists against do-not-call and known-litigator data before the campaign runs, not after a complaint arrives. Add branded caller ID through Rich Call Data so your name and logo show on the screen, which lifts answer rates and shortens the guessing that leads to declines. Spread volume across numbers sensibly instead of burning one line. Track spam-label and complaint rates per number so you can pull a number before it drags the rest down. And respect calling windows and per-day contact caps by region.</p>
<p>None of this replaces STIR/SHAKEN. It sits alongside it. The standard gets you in the door with the carrier, and clean dialing keeps you welcome. For the mechanics of pacing and abandonment specifically, our guide on <a href="https://www.ictbroadcast.com/how-predictive-dialers-work-2026-pacing-abandonment-compliance/">how predictive dialers work in 2026</a> goes deeper.</p>
<h2>Recovering a flagged number</h2>
<p>If a number is already labeled, rest it. Move active campaigns to healthier lines, stop the behavior that triggered the score, and let the rolling average recover, which usually takes weeks rather than days. Some carriers and analytics providers accept remediation or registration requests, and branded caller ID registration can help re-establish trust. What does not help is rotating to a fresh number and repeating the same pattern, because you&#8217;ll just train the model again.</p>
<h2>FAQ</h2>
<p><strong>Does A-attestation guarantee my calls connect?</strong> No. It confirms the number is yours and unspoofed. The carrier&#8217;s reputation model still decides the label based on your calling behavior.</p>
<p><strong>Why do short calls hurt me?</strong> A high ratio of one or two second calls looks like people rejecting a robocall, which is one of the strongest spam signals a carrier tracks.</p>
<p><strong>Is branded caller ID the same as STIR/SHAKEN?</strong> No. STIR/SHAKEN authenticates the number. Branded caller ID, delivered through Rich Call Data, displays your name and logo. They work best together.</p>
<p><strong>How long until a flagged number recovers?</strong> Reputation is a rolling average, so plan on weeks of clean, low-volume dialing rather than an overnight reset.</p>
<p><strong>Should I just keep buying new numbers?</strong> No. If the dialing pattern doesn&#8217;t change, new numbers get flagged too. Fix the pattern first.</p>
<p>The short version: STIR/SHAKEN is table stakes, not a shield. Your numbers stay clean when your dialing looks like a business talking to people who want to hear from it.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/stir-shaken-still-spam-likely-number-reputation-2026/">Your Calls Pass STIR/SHAKEN and Still Say Spam Likely. Here Is Why</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Your AI Caller Must Now Say It Is a Machine. What Call Center Software Has to Change</title>
		<link>https://www.ictbroadcast.com/ai-disclosure-rules-call-center-software-2026/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Sat, 22 Aug 2026 07:07:54 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/ai-disclosure-rules-call-center-software-2026/</guid>

					<description><![CDATA[<p>EU AI Act Article 50 took effect on 2 August 2026 and requires a spoken AI disclosure at the start of a call. Here is what it changes inside a dialer, and why the FCC is heading the same way.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/ai-disclosure-rules-call-center-software-2026/">Your AI Caller Must Now Say It Is a Machine. What Call Center Software Has to Change</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>Since 2 August 2026, an AI voice calling into the EU has to announce itself. Article 50 of the EU AI Act asks for a spoken, plain-language disclosure at the first interaction, covering both the fact that the caller is a machine and the business it calls for. For call center software teams, that is a configuration job, not a legal memo.</p>
<h2>What Article 50 actually asks for</h2>
<p>The obligation is short, which is exactly why it slips past people. If a person interacts directly with an AI system, they have to be told. On a phone call, that means audio, at the start, in words a caller understands without hiring a lawyer.</p>
<p>Two facts have to land. First, that the caller is a machine. Second, on whose behalf it is calling. A watermark buried in call metadata does not clear the bar. Neither does a clause in your terms of service, which nobody hears while a phone is ringing. My honest read is that the second half will catch more operators than the first, because resellers and white-label teams habitually name the platform instead of the client whose campaign is running.</p>
<p>Penalties reach 15 million euros or 3% of worldwide annual turnover, whichever is higher. There is a separate December 2026 deadline for certain content-marking duties, but the phone disclosure date did not move with it.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/08/bc-aiact-flow.png" alt="Decision flow showing when call center software must play an AI disclosure on an outbound call under EU AI Act Article 50" /><figcaption>The disclosure test applies per call leg, and it has to carry two separate facts.</figcaption></figure>
<h2>The uncomfortable number sitting behind the rule</h2>
<p>A 2026 blind study found that 71% of callers could not reliably tell an AI voice agent from a human. That single figure is most of the justification for Article 50. Back when synthetic speech was obviously synthetic, disclosure was redundant. It stopped being obvious somewhere around the point where end-to-end response latency dropped into the 250 to 800 millisecond band and the pauses started sounding like someone thinking.</p>
<p>Volume moved too. Voice AI went from 6% of inbound contact center traffic in 2024 to 19% in 2026, with banking and telecom leading. Regulators do not write disclosure rules for fringe use cases.</p>
<h2>Where this breaks in a real dialer setup</h2>
<p>Picture a twelve-seat outbound team running EU campaigns. A bot qualifies, a human closes. The bot discloses and the human does not need to, which sounds simple until the same audio prompt gets reused on a campaign where a person is doing the dialing. Now you have a recording announcing an automated system on calls that are not automated. Wrong in the other direction, but still wrong.</p>
<p>Language is the second trap. Plain language means the caller&#8217;s language, not yours. One English prompt on a campaign dialing Belgium and Poland does not satisfy anything, and this is the failure I would expect to see most often in audits over the next year.</p>
<p>Placement is the third. &#8220;At the first interaction&#8221; is not a synonym for &#8220;somewhere in the first minute.&#8221; If your script opens with a two-sentence hook and discloses afterwards, the interaction already happened. Answering machine detection complicates this further, because a disclosure that fires before detection resolves ends up on voicemail, and a disclosure that fires after it may land several seconds into a live conversation. Pick the order deliberately rather than inheriting whatever the flow does by default.</p>
<h2>The FCC is walking the same road, just slower</h2>
<p>US operators are not exempt from this thinking. The FCC ruled back in February 2024 that calls using AI-generated voices count as &#8220;artificial&#8221; under the TCPA, which pulls them under prior express written consent. A final rule dealing specifically with AI-generated calls is expected around Q4 2026 or Q1 2027, though the Commission under Chairman Carr has signaled a lighter regulatory posture than the previous one.</p>
<p>The likely shape is familiar: an explicit AI identification requirement at call open, consent language that names AI directly, and a formal definition of an AI-generated call. That overlaps enough with Article 50 that building two separate implementations would be wasted effort. Build one, then relax it per region if the FCC lands somewhere softer.</p>
<p>The money is not theoretical. TCPA class actions in 2025 and 2026 have settled in the $5M to $20M range, and statutory damages sit at $500 to $1,500 per unauthorized call. If your team is still working through the basics here, our guide to <a href="https://www.ictbroadcast.com/autodialer-laws-and-regulations-tcpa-compliant-auto-dialer/">autodialer laws and TCPA compliance</a> covers the consent side that these AI rules attach to. Teams dialing across borders should also read the <a href="https://www.ictbroadcast.com/country-wise-regulations-about-auto-dialers/">country-wise auto dialer regulations</a> before assuming one script works everywhere.</p>
<h2>Proving it happened, six months later</h2>
<p>This is the part almost everyone underinvests in. A complaint lands long after the campaign has been archived, and &#8220;we configured it correctly&#8221; is not evidence of anything. What you need is a call record that can be read back by someone hostile.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/08/bc-aiact-log.png" alt="Table of call detail record fields that evidence AI disclosure compliance in predictive dialer software" /><figcaption>Six fields that turn a policy claim into something a regulator can verify.</figcaption></figure>
<p>If you only add one field, make it the offset. Whether the disclosure played at all is usually easy to establish from audio. When it played, relative to the first word of the conversation, is the thing that actually gets argued about. Keep these fields for as long as you keep call detail records generally, because the complaint window outlasts the campaign by a wide margin.</p>
<p>One more practical note: version your disclosure text. Campaign wording changes mid-flight more often than teams admit, and a log entry pointing at &#8220;the standard disclosure&#8221; is useless if the standard disclosure was edited twice in March.</p>
<h2>Doing this in ICTBroadcast</h2>
<p>ICTBroadcast integrates with Google Dialogflow for building conversational agents, so the disclosure does not need a separate compliance module. It belongs in the call flow, ahead of the handoff. A few things worth setting up deliberately:</p>
<ul>
<li>Place the disclosure as the first prompt in the <a href="https://www.ictbroadcast.com/ivr/">IVR flow</a>, before control passes to the Dialogflow agent, so it always precedes the first conversational turn.</li>
<li>Keep one prompt per language and bind it to the campaign&#8217;s target country rather than to a global default.</li>
<li>Run AI campaigns as their own campaigns, separate from plain voice broadcast lists, so the opening prompt cannot leak onto human-dialed calls.</li>
<li>Name the client business in the prompt text, not the platform. If you resell, this needs to be a per-tenant value, not a shared one.</li>
<li>Export call detail records with the campaign identifier attached so the disclosure version can be reconstructed later.</li>
</ul>
<p>None of this is heavy engineering. It is an hour of prompt work and a decision about where the boundary between bot and agent sits.</p>
<h2>A short checklist before your next EU campaign</h2>
<ul>
<li>Does the disclosure play before the first substantive sentence, not after it?</li>
<li>Does it name a business, and is that business the client rather than the dialer vendor?</li>
<li>Is there a prompt in every language the campaign targets?</li>
<li>Does answering machine detection run before or after the disclosure, and did you choose that on purpose?</li>
<li>Can you pull a call from four months ago and show when the disclosure played?</li>
<li>Is the AI campaign isolated from lists that humans dial?</li>
</ul>
<h2>Frequently asked questions</h2>
<h3>Does Article 50 apply if a human agent uses AI assistance during the call?</h3>
<p>The trigger is direct interaction between a person and an AI system. A human agent reading AI-suggested text to a caller is not the caller interacting with the AI. A synthetic voice speaking to the caller is. The grey zone is real-time voice cloning of an agent, and I would disclose in that case rather than argue about it later.</p>
<h3>Do we need consent as well as disclosure?</h3>
<p>They are separate duties and both apply. Article 50 governs transparency. Consent for the call itself comes from other law, and in the US the TCPA requires prior express written consent for AI-voiced marketing calls regardless of what you announce at the start.</p>
<h3>What if the caller hangs up during the disclosure?</h3>
<p>That is a compliant outcome, not a failure. Log it as a disclosure played with an early disconnect. Teams sometimes try to shorten the notice to reduce these drops, which is the wrong optimisation to run.</p>
<h3>Does this apply to inbound calls too?</h3>
<p>Yes. The obligation follows the interaction, not the direction of dialing. An inbound AI receptionist handling EU callers needs the same spoken notice at the top of the call.</p>
<h3>We only dial the US. Can we ignore this?</h3>
<p>For now, mostly. But the FCC rule expected in late 2026 or early 2027 points in the same direction, and retrofitting disclosure into a live campaign under deadline is worse than building it now. Most teams we talk to are treating the EU wording as the template.</p>
<h3>Is a disclosure needed on every call in a campaign, or once per contact?</h3>
<p>Per call. There is no concept of a caller remembering last week&#8217;s notice, and building that assumption into your flow creates a record you cannot defend.</p>
<h2>Related resources</h2>
<ul>
<li><a href="https://www.ictbroadcast.com/autodialer-laws-and-regulations-tcpa-compliant-auto-dialer/">Autodialer laws and regulations: TCPA compliant auto dialer</a></li>
<li><a href="https://www.ictbroadcast.com/country-wise-regulations-about-auto-dialers/">Country-wise regulations about auto dialers</a></li>
<li><a href="https://www.ictbroadcast.com/press-1-campaign-for-interactive-voice-broadcasting/">Press 1 campaigns for interactive voice broadcasting</a></li>
<li><a href="https://www.ictbroadcast.com/ivr/">IVR features in ICTBroadcast</a></li>
<li><a href="https://www.ictbroadcast.com/free-asterisk-based-auto-dialer/">Free Asterisk based auto dialer</a></li>
</ul>
<h2>Getting this configured</h2>
<p>If you are running EU campaigns and want the disclosure wired into the flow properly rather than bolted on, take a look at what <a href="https://www.ictbroadcast.com/">ICTBroadcast</a> ships with, and at the <a href="https://www.ictbroadcast.com/packages/">edition comparison</a> if you need the Dialogflow integration specifically. Questions about a particular campaign setup are best raised through our <a href="https://service.ictinnovations.com" target="_blank" rel="noopener">support portal</a>, where they reach the engineering team directly.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/ai-disclosure-rules-call-center-software-2026/">Your AI Caller Must Now Say It Is a Machine. What Call Center Software Has to Change</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>88% of Call Centers Have AI. Only 25% Use It Daily. Here Is What Is In the Way</title>
		<link>https://www.ictbroadcast.com/call-center-ai-adoption-gap-integration-2026/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Sun, 09 Aug 2026 05:09:27 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/call-center-ai-adoption-gap-integration-2026/</guid>

					<description><![CDATA[<p>Almost every contact center has bought AI. Only a quarter run it in daily operations. New 2026 research points at the same cause every time, and it is not budget or training. It is that the average team runs 3.9 separate systems and only 3% have them joined up.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/call-center-ai-adoption-gap-integration-2026/">88% of Call Centers Have AI. Only 25% Use It Daily. Here Is What Is In the Way</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>Here is a pair of numbers worth sitting with. Around 88% of contact centers now have some form of AI in place. Only about 25% have it running in daily operations. Almost everyone has bought it. Three quarters are not really using it.</p>
<p>That gap is usually explained as a training problem or a change management problem. The 2026 research points somewhere else, and it is a much more boring answer: the AI cannot see enough of the business to be useful.</p>
<h2>The number that explains the other numbers</h2>
<p><img src='https://www.ictbroadcast.com/wp-content/uploads/2026/08/call-center-ai-adoption-gap.png' alt='Chart contrasting 88 percent of contact centers having some form of AI against 25 percent running it in daily operations, with 3.9 separate contact center technologies per team and only 3 percent on a unified platform' width='1000' height='600' /></p>
<p><em>Bought is not the same as running, and the distance between them has a cause.</em></p>
<p>Puzzel&#8217;s State of Contact Centres 2026 research found that the average team runs 3.9 separate contact center technologies, and only 3% operate on a single unified platform. Three percent. That is the number that makes the adoption gap make sense.</p>
<p>Think about what four disconnected systems does to an AI feature. The dial outcome lives in the dialer. The customer history lives in the CRM. The recording lives in a third system, and the ticket lives in a fourth. Any task that needs two of those at the same time either fails or gets handed back to a person.</p>
<p>So the AI ends up confined to the things one system can do alone. Transcribe this recording. Summarise this ticket. Those are real conveniences and nobody minds them, but they are not what anyone approved the budget for, and they are not enough to change how a day runs.</p>
<p>Meanwhile the pressure to show something keeps building. Gartner found 91% of customer service leaders under executive pressure to implement AI. Pressure plus a fragmented data path produces exactly what the numbers show: fast purchasing, slow adoption.</p>
<h2>Why a tool that is usually right gets ignored</h2>
<p>There is a second failure mode that follows straight from the first, and it is the one that quietly kills pilots.</p>
<p>When a model can only see part of the picture, it guesses at the rest. It is right most of the time, because most cases are ordinary. Being right most of the time sounds fine until you look at what it does to the person using it.</p>
<p>A tool that is right most of the time gets checked every time. The agent reads the suggestion, then opens the CRM to confirm it, then acts. That is slower than just opening the CRM. So after a few weeks they stop reading the suggestion, and the feature is technically live and functionally dead. It is in the 88% and not in the 25%.</p>
<p>Trust here is not a soft factor. It is a straightforward calculation the agent is making about whether verification costs less than doing it manually. Fix the data path and the calculation flips.</p>
<h2>The research keeps landing on agent workflow, not self-service</h2>
<p><img src='https://www.ictbroadcast.com/wp-content/uploads/2026/08/call-center-ai-integration-order.png' alt='Comparison of the usual call center AI rollout order starting with self-service deflection against an order starting with unified call outcome and customer data, plus three questions to ask before buying' width='1000' height='600' /></p>
<p><em>The order most teams buy in, and the order the returns actually show up in.</em></p>
<p>Verint&#8217;s 2026 research found the highest returns in agent workflow rather than customer self-service. That finding keeps recurring across different studies, and it keeps getting ignored, for a reason that is easy to understand.</p>
<p>Self-service is the part that looks like a headcount saving. It has a clean business case you can put on one slide. Agent workflow improvements look like helping people do their existing jobs slightly better, which is a much harder thing to write a number next to before you have done it.</p>
<p>But the self-service case has a measurement trap in it. Deflection is easy to count and easy to misread. A call the bot handled without a transfer counts as deflected, whether or not the customer called back an hour later, gave up, or emailed instead. Teams declare a win on the deflection number, then find total contact volume did not move, then blame the model and start shopping for a better one. That is how you end up with a fifth system to integrate.</p>
<p>The agent workflow route starts smaller. The AI drafts the summary, suggests the next action, and pulls the relevant history in before the agent asks. It needs less autonomy to be useful, and crucially it fails safely, because a person is reading everything it produces. But it needs the joined-up data that self-service also needs, which is why doing it first is the right order rather than a compromise.</p>
<h2>Get the order right</h2>
<p>Three steps, in this sequence.</p>
<p><strong>First, put the call outcome and the customer record somewhere a tool can read them together.</strong> That is not a platform migration and it does not mean ripping out four systems. It means one place where a query can join what happened on the call to who the person is. If that place does not exist, nothing you buy next will work properly, no matter how good the model is.</p>
<p><strong>Second, point AI at the agent&#8217;s work.</strong> Summaries, next-action suggestions, quality scoring across the whole call volume instead of the two calls a supervisor had time to listen to. These pay quickly and they generate the labelled outcome data you need for anything more ambitious.</p>
<p><strong>Third, automate the calls that never needed a person</strong>, once you can prove from your own data which ones those are. By then you are automating a category you have measured, not a category a vendor deck told you exists.</p>
<p>Done in that order you finish with fewer moving parts than you started with. Done in the usual order you finish with more.</p>
<h2>Three questions before the next purchase</h2>
<p>These are worth asking any vendor, and worth asking about tools you already own.</p>
<p><strong>Can it read the outcome?</strong> If the tool cannot see how the last call ended, it is guessing at the next one. Ask specifically how it gets the disposition, not whether it integrates.</p>
<p><strong>Can it write back?</strong> A tool that only reads produces a report. A tool that writes back changes what happens on the next contact. This is the difference between an analytics product and an operational one, and the demo rarely makes it obvious.</p>
<p><strong>Who owns the join?</strong> If the only place your call data and customer data come together is inside the vendor&#8217;s platform, you have rented your data path along with the model. Switching costs then grow every month, and the thing you would be switching away from is not the AI, it is the integration.</p>
<p>That last question is where self-hosting earns its keep. When the dialer runs on your own infrastructure, the call records, dispositions and recordings sit in a database you control, and you decide what reads them. Our write-up on <a href="https://www.ictbroadcast.com/cloud-call-center-software-open-source/">open source cloud call center software</a> covers what that looks like in practice.</p>
<h2>Where ICTBroadcast fits</h2>
<p>Worth being precise here, because vague AI claims are part of the problem this article is about.</p>
<p>ICTBroadcast integrates with Google Dialogflow. That means you build the conversational agent in Dialogflow, with its intents and flows, and ICTBroadcast handles the telephony side: placing the calls, managing the campaign, and recording what happened. The integration is the connection between the two, not a separate AI engine bundled into the dialer.</p>
<p>Why that matters for everything above: the campaign data, call outcomes and recordings stay in your ICTBroadcast installation on your own server. The conversational layer is a component you chose and can replace. Nobody else owns the join between what the agent said and what your business knows about the customer.</p>
<p>ICTBroadcast also ships a REST API by default, which is the practical mechanism for step one. If the outcome data needs to reach your CRM, or your CRM needs to feed the dial list, that is an API call rather than a support ticket. We covered the API in more detail in the <a href="https://www.ictbroadcast.com/ictbroadcast-sp-edition-rest-api-included-by-default/">SP Edition REST API</a> post.</p>
<h2>What to do this week</h2>
<p>Count your systems. Just count them. Dialer, CRM, ticketing, recording, quality, reporting. If the number is around four, you are average, and the average is where the adoption gap lives.</p>
<p>Then pick one question your team asks often that needs two of those systems to answer, and time how long it takes to answer today. That number is your integration debt, expressed in a unit anyone can understand. It is also the thing your next AI purchase will run into.</p>
<h2>Frequently asked questions</h2>
<h3>Why do most contact centers have AI but not use it daily?</h3>
<p>Because the data the AI needs is split across separate systems. Research puts the average team on 3.9 different contact center technologies with only 3% on a unified platform, so anything requiring two systems at once either fails or gets escalated to a person. The tool then gets used only for single-system tasks like transcription.</p>
<h3>Is agent-facing AI really a better first step than self-service?</h3>
<p>Verint&#8217;s 2026 research found the highest returns in agent workflow rather than customer self-service, and that finding shows up repeatedly. Agent-facing tools need less autonomy to be useful, fail safely because a person reviews the output, and produce the outcome data that later automation depends on.</p>
<h3>What is wrong with measuring call deflection?</h3>
<p>Deflection counts calls the bot finished without a transfer. It does not count the customer who called back later, gave up, or switched to email. Check total contact volume over the same period instead, because that is the number that reflects whether work actually went away.</p>
<h3>Does ICTBroadcast include an AI voice agent?</h3>
<p>ICTBroadcast integrates with Google Dialogflow, so you build the conversational agent there and ICTBroadcast handles call placement, campaign management and recording. The AI capability comes from the Dialogflow side, and the integration connects it to your telephony.</p>
<h3>What does it mean to own the join between call data and customer data?</h3>
<p>It means the place where a call outcome gets matched to a customer record is infrastructure you control, rather than a vendor&#8217;s platform. If only the vendor can perform that join, replacing them means rebuilding the integration, which is usually a larger job than replacing the AI model itself.</p>
<h3>Do we need one unified platform to get value from AI?</h3>
<p>No, but you do need one place where the call outcome and the customer record can be read together. That can be achieved with an API and a shared datastore. The point is a readable join, not a single vendor.</p>
<h2>Related resources</h2>
<ul>
<li><a href="https://www.ictbroadcast.com/gartner-80-billion-call-center-ai-fine-print/">Gartner&#8217;s $80 Billion Call Center AI Forecast: The Fine Print</a></li>
<li><a href="https://www.ictbroadcast.com/cloud-call-center-software-open-source/">Open Source Cloud Call Center Software</a></li>
<li><a href="https://www.ictbroadcast.com/self-hosted-auto-dialer-software/">Self-Hosted Auto Dialer Software</a></li>
<li><a href="https://www.ictbroadcast.com/ictbroadcast-sp-edition-rest-api-included-by-default/">ICTBroadcast SP Edition: REST API Included by Default</a></li>
</ul>
<h2>Where to go next</h2>
<p>If counting your systems produced an uncomfortable number, the first move is a readable join between call outcomes and customer records, not another platform. <a href="https://www.ictbroadcast.com/">ICTBroadcast</a> runs on your own infrastructure with a REST API included, so the campaign data stays somewhere you can query and connect. Tell us which systems you are trying to join and we will help you work out the shortest path. Open a ticket at <a href="https://service.ictinnovations.com/contact.php" target="_blank" rel="noopener">service.ictinnovations.com</a>.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/call-center-ai-adoption-gap-integration-2026/">88% of Call Centers Have AI. Only 25% Use It Daily. Here Is What Is In the Way</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Your Upstream Carrier Just Became Your Problem: The FCC&#8217;s Next Robocall Move</title>
		<link>https://www.ictbroadcast.com/fcc-upstream-provider-vetting-outbound-calling/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Wed, 29 Jul 2026 06:54:05 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/fcc-upstream-provider-vetting-outbound-calling/</guid>

					<description><![CDATA[<p>The FCC is pushing robocall responsibility up the call path, asking providers to vet whoever hands them traffic. Here is what changes for outbound teams and the four checks worth running now.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-upstream-provider-vetting-outbound-calling/">Your Upstream Carrier Just Became Your Problem: The FCC&#8217;s Next Robocall Move</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>The FCC&#8217;s robocall strategy has quietly changed shape. Instead of chasing the people placing bad calls, it is putting pressure on the providers who carry them, and asking those providers to look at whoever handed them the traffic in the first place. If you run outbound campaigns on your own <strong>call center software</strong>, that shift reaches you through your carrier, not through a new rule aimed at you.</p>
<p>Reply comments on the numbering proceeding closed on 7 July 2026, so this is live policy rather than speculation. The direction is clear enough to plan around even before the final text lands.</p>
<h2>What the FCC is proposing</h2>
<p>The core idea is that a voice service provider should know the upstream providers it accepts traffic from, in a specific and documented way. The proposal spells out what that looks like: confirm the upstream provider has a filing in the Robocall Mitigation Database, actually read that filing and its mitigation plan for completeness, confirm the provider holds a Service Provider Code token where it claims full or partial STIR/SHAKEN implementation, and check whether the provider appears on certain national security or enforcement related lists.</p>
<p>Read that list again and notice what it is not. It is not a technical standard. It is a due diligence obligation, closer to what a bank does before opening an account than anything in a SIP specification.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/07/fcc-upstream-accountability.png" alt="Diagram comparing the old robocall accountability model with the FCC proposal where responsibility runs backwards down the call path to upstream providers" /><figcaption>Signing your own traffic was the old bar. Vetting who hands you traffic is the new one.</figcaption></figure>
<h2>Why this reaches your call center software even though it targets carriers</h2>
<p>Most outbound teams read &#8220;provider obligation&#8221; and assume it is somebody else&#8217;s paperwork. That assumption held for a few years. It is getting weaker.</p>
<p>Carriers that are told to vet upstream sources will pass that scrutiny down, because the cheapest way to satisfy a regulator is to tighten who you accept. Wholesale voice is a chain, and every link that gets squeezed squeezes the next one. In practice that means the questions on your next carrier onboarding form get longer, and the tolerance for vague answers gets shorter.</p>
<p>The other reason it reaches you is that the Commission has been willing to cut providers off entirely rather than fine them. Losing a route with no notice is an operational problem, not a legal one, and no compliance budget fixes a dialer that suddenly cannot complete calls. If your campaigns run through a single upstream, that is concentration risk you can measure today.</p>
<p>Teams running a self-hosted stack have a real advantage here, because the call detail records and campaign logs sit on hardware you control. Producing six months of evidence is a query rather than a support ticket. That is not a small thing when someone asks you to prove what you sent and when.</p>
<h2>The four checks, and the part people skip</h2>
<p>If you resell, aggregate, or hand traffic to anyone downstream of you, the four checks below are the ones the proposal describes. Even if you only buy termination and never sell it, running them on your own carrier is a reasonable way to judge whether that carrier is about to have a bad year.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/07/upstream-provider-vetting-checks.png" alt="The four upstream provider checks for robocall compliance covering RMD filing, mitigation plan review, Service Provider Code token and enforcement list screening" /><figcaption>Four checks, four artefacts. The artefact is the half people forget.</figcaption></figure>
<p>The part people skip is the evidence. Checking the Robocall Mitigation Database takes two minutes and leaves no trace unless you deliberately keep one. A dated screenshot and a three line review note, filed somewhere you can find it in eighteen months, is the difference between having done the work and being able to show it. I would treat that filing habit as the actual deliverable here.</p>
<p>One honest caveat: none of this is a substitute for the consent and suppression work you already owe. Vetting your carrier does nothing for a campaign calling numbers it should not. Our <a href="https://www.ictbroadcast.com/autodialer-laws-and-regulations-tcpa-compliant-auto-dialer/">guide to autodialer laws and regulations</a> covers that side, and it has not become less important.</p>
<h2>What to do in the next month</h2>
<p>Start by writing down which upstream providers your traffic actually touches. A surprising number of operators cannot answer that quickly, especially where a reseller sits in the middle. You cannot vet a chain you have not drawn.</p>
<p>Then check your own filing. If you appear in the Robocall Mitigation Database, reread what you filed. Plans written two or three years ago often describe a system that no longer matches how the business runs, and an out of date plan reads worse than a modest one that is accurate.</p>
<p>After that, look at attestation levels on your own outbound. If your calls are going out with anything less than full attestation, find out why. Sometimes the answer is a number the carrier does not believe you own, which is fixable in an afternoon and quietly costs you answer rate every day it stays broken.</p>
<p>Finally, add a second termination route if you only have one. Not because your current carrier is doing anything wrong, but because enforcement in this area is fast and does not care about your campaign calendar.</p>
<h2>Where this is heading</h2>
<p>My read is that STIR/SHAKEN has stopped being a caller ID feature and become the paperwork trail for an accountability regime. The signature was never the point on its own. The point is that a signature ties a call to a provider, and a provider to a filing, and a filing to a name somebody can act against.</p>
<p>For legitimate outbound operations that is mostly good news, because the traffic it squeezes is the traffic that has been degrading answer rates for everyone. The cost is a bit more diligence and a lot more record keeping. That is a trade most serious teams should take, and the ones who set up the record keeping early will find the next rule change much less disruptive than the ones who wait for a carrier to demand it.</p>
<h2>Frequently asked questions</h2>
<h3>Does this apply to me if I am not a carrier?</h3>
<p>The obligations described in the proposal sit with voice service providers. If you only originate your own campaigns, you are not the direct target, but your carrier&#8217;s new diligence will show up as tougher onboarding and faster disconnection for accounts that look risky.</p>
<h3>What is the Robocall Mitigation Database in plain terms?</h3>
<p>It is the FCC&#8217;s public register where providers state how far they have implemented caller ID authentication and describe the steps they take to prevent illegal robocalls on their networks. Anyone can look up an entry, which is what makes it usable as a vetting tool.</p>
<h3>What is a Service Provider Code token?</h3>
<p>It is the credential a provider needs in order to sign calls under STIR/SHAKEN. Claiming implementation without holding one is exactly the mismatch the FCC wants downstream providers to catch, which is why confirming the token appears as a separate check.</p>
<h3>Will full attestation stop my calls being labelled as spam?</h3>
<p>Not by itself. Attestation tells the terminating carrier who vouched for the call, but analytics engines also weigh complaint rates, call duration patterns and how many numbers you rotate through. Good attestation with bad calling behaviour still gets labelled.</p>
<h3>How long should I keep vetting records?</h3>
<p>Longer than feels necessary. Investigations look backwards, and the useful answer is usually about a relationship that ended a year ago. Keeping dated evidence for the life of the relationship plus a couple of years is a sane default.</p>
<h2>Related resources</h2>
<ul>
<li><a href="https://www.ictbroadcast.com/autodialer-laws-and-regulations-tcpa-compliant-auto-dialer/">Autodialer laws and regulations for TCPA compliant calling</a></li>
<li><a href="https://www.ictbroadcast.com/country-wise-regulations-about-auto-dialers/">Country wise regulations about auto dialers</a></li>
<li><a href="https://www.ictbroadcast.com/custom-caller-id-with-personalized-name/">Custom caller ID with a personalised name</a></li>
<li><a href="https://www.ictbroadcast.com/voice-broadcast/">Voice broadcasting with ICTBroadcast</a></li>
<li><a href="https://www.ictbroadcast.com/packages/">ICTBroadcast editions and pricing</a></li>
</ul>
<p>Compliance gets easier when the records live on your own server instead of a vendor&#8217;s. ICTBroadcast is <a href="https://www.ictbroadcast.com/free-asterisk-based-auto-dialer/">an Asterisk based auto dialer</a> you host yourself, with campaign and call detail data you can query directly. Have a look at the <a href="https://www.ictbroadcast.com/packages/">available editions</a> if you are weighing a move off a hosted platform.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/fcc-upstream-provider-vetting-outbound-calling/">Your Upstream Carrier Just Became Your Problem: The FCC&#8217;s Next Robocall Move</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Gartner Puts an $80 Billion Number on Call Center AI. Here&#8217;s the Fine Print</title>
		<link>https://www.ictbroadcast.com/gartner-80-billion-call-center-ai-fine-print/</link>
		
		<dc:creator><![CDATA[Tahir Almas]]></dc:creator>
		<pubDate>Fri, 24 Jul 2026 08:37:48 +0000</pubDate>
				<category><![CDATA[call center]]></category>
		<guid isPermaLink="false">https://www.ictbroadcast.com/gartner-80-billion-call-center-ai-fine-print/</guid>

					<description><![CDATA[<p>Gartner says conversational AI will cut contact center labor costs by $80 billion in 2026, yet only one in ten agent interactions will be fully automated. Here's where the savings actually come from.</p>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/gartner-80-billion-call-center-ai-fine-print/">Gartner Puts an $80 Billion Number on Call Center AI. Here&#8217;s the Fine Print</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></description>
										<content:encoded><![CDATA[<p>Gartner&#8217;s projection made headlines across the industry this month: conversational AI will trim contact center labor costs by $80 billion during 2026. Impressive number. The same research carries a detail most coverage skipped, and it changes what the figure means for anyone running call center software: only about one in ten agent interactions will be fully automated this year.</p>
<p>So nine out of ten calls still need a person. Where does $80 billion come from, then? That gap between the headline and the mechanism is worth understanding before you sign anything, because vendors will quote you the big number while selling you the narrow slice.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/07/gartner-80b-fine-print.png" alt="Diagram contrasting the Gartner 80 billion dollar contact center labor savings projection with the fine print that only one in ten agent interactions will be fully automated in 2026" width="1200" height="675" /><figcaption>The headline number and the fine print sit side by side in the same research.</figcaption></figure>
<h2>Where the Call Center Software Savings Actually Come From</h2>
<p>Full automation gets the attention, but it&#8217;s the smallest contributor. The savings pile up in less glamorous places. Shorter handle times account for a big share: when an agent gets a live transcript, caller history, and a suggested answer on screen, a six minute call becomes a four minute call. Multiply that across a 50 seat floor and you&#8217;ve cut the equivalent of a dozen positions without automating a single conversation end to end.</p>
<p>After-call work is the second quiet winner. Agents have historically spent 30 to 60 seconds per call typing notes. Auto-generated summaries wipe most of that out. Then there&#8217;s QA: instead of a supervisor sampling 2% of calls, AI scoring covers every call, which means coaching happens where it&#8217;s needed rather than where the sample happened to land.</p>
<p>The mid-market reality check matters here. The contact center AI market hit roughly $4.89 billion this year, and enterprises like Cigna and Comcast are running voice AI at serious scale. But those firms have data teams tuning the systems weekly. If you run a 20 seat operation, your savings come from the assistive layer first, and I&#8217;d argue that&#8217;s the right place to start anyway.</p>
<figure><img decoding="async" src="https://www.ictbroadcast.com/wp-content/uploads/2026/07/where-ai-saves-call-centers.png" alt="Diagram of where AI saves money in call center software before during and after each call including routing pacing live transcripts summaries and QA scoring" width="1200" height="675" /><figcaption>The wins cluster around the agent before, during, and after each call.</figcaption></figure>
<h2>What This Means for Outbound Campaigns</h2>
<p>Most of the AI coverage focuses on inbound support, but outbound teams have their own version of this math. Predictive pacing is decades old and still delivers the single biggest efficiency gain in outbound calling: agents talk instead of waiting for someone to answer. Layer AI on top and the picture improves further. Answering machine detection gets sharper, so fewer agent seconds burn on voicemail. Campaign analytics tell you which lists, scripts, and time windows convert, so tomorrow&#8217;s dialing plan is better than today&#8217;s.</p>
<p>You don&#8217;t need a Fortune 500 budget for any of that. <a href="https://www.ictbroadcast.com/free-asterisk-based-auto-dialer/">An Asterisk based auto dialer</a> paired with sensible campaign design captures most of the assistive-layer gains at a fraction of the licensed-seat pricing the big CCaaS vendors charge. The honest answer is that the software matters less than the discipline: track connect rates, listen to failed calls, and adjust weekly.</p>
<h2>The One-in-Ten Rule Should Shape Your Buying</h2>
<p>Here&#8217;s the practical takeaway. If a vendor pitch centers on replacing agents, be skeptical: the research says that slice stays small through 2026. If the pitch centers on making each agent 20 to 30 percent more productive, the numbers back it up.</p>
<p>That framing also protects you from overbuying. Voice AI minutes, LLM API fees, and per-seat AI add-ons stack quickly. Start with what pays back fastest: automated summaries, full-coverage QA, smarter routing, and <a href="https://www.ictbroadcast.com/voice-broadcast/">voice broadcasting</a> for the messages that never needed a live agent in the first place. Appointment reminders, payment notices, and service alerts are automation that has worked for years, no LLM required.</p>
<p>Then pilot one AI voice agent use case with clear exit criteria. Measure containment and the 7 day recontact rate, not just deflection. A deflected call that comes back angry tomorrow saved you nothing.</p>
<h2>FAQ</h2>
<h3>Will AI replace call center agents in 2026?</h3>
<p>Not at any meaningful scale. Gartner expects only about one in ten agent interactions to be fully automated in 2026. The bigger effect is assistive: AI shortens calls, automates notes, and covers QA, which changes how many agents you need per thousand calls rather than eliminating the role.</p>
<h3>Where does call center AI save the most money?</h3>
<p>Handle time reduction, after-call work automation, and full-coverage QA scoring deliver the most reliable savings. Full call automation helps for narrow, high-volume intents like order status or appointment confirmation, but it&#8217;s the smallest slice of the total.</p>
<h3>Can small call centers benefit from AI without enterprise budgets?</h3>
<p>Yes. Open source call center software with predictive dialing, answering machine detection, and campaign analytics captures most of the productivity gain. Add AI summaries and QA scoring through affordable APIs rather than per-seat platform fees.</p>
<h3>What should I measure in an AI voice agent pilot?</h3>
<p>Containment rate, escalation quality, and the 7 day recontact rate. If callers the AI &#8220;resolved&#8221; call back within a week, the automation moved the work instead of removing it.</p>
<h3>Is voice broadcasting still relevant when AI voice agents exist?</h3>
<p>Very much so. One-way notifications like reminders and alerts don&#8217;t need conversational AI, and broadcasting them costs a fraction of an interactive AI call. Use the cheap tool where the job is simple.</p>
<h2>Related Resources</h2>
<ul>
<li><a href="https://www.ictbroadcast.com/free-asterisk-based-auto-dialer/">Free Asterisk Based Auto Dialer</a></li>
<li><a href="https://www.ictbroadcast.com/voice-broadcast/">Voice Broadcasting</a></li>
<li><a href="https://www.ictbroadcast.com/autodialer-laws-and-regulations-tcpa-compliant-auto-dialer/">TCPA Compliant Auto Dialer: Laws and Regulations</a></li>
<li><a href="https://www.ictbroadcast.com/packages/">ICTBroadcast Packages</a></li>
<li><a href="https://www.ictbroadcast.com/difference-between-multi-user-multi-tenant-software/">Multi User vs Multi Tenant Software</a></li>
</ul>
<p>&lt;p&gt;The post <a rel="nofollow" href="https://www.ictbroadcast.com/gartner-80-billion-call-center-ai-fine-print/">Gartner Puts an $80 Billion Number on Call Center AI. Here&#8217;s the Fine Print</a> first appeared on <a rel="nofollow" href="https://www.ictbroadcast.com">ICTBroadcast</a>.&lt;/p&gt;</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
