I was wonder what others were doing to license the National Do Not Call Registry? It seems I cannot license the data set and give access to multiple customers? Ryan
It appears that Ryan Finnesey <ryan.finnesey at conovence.com> said:
I was wonder what others were doing to license the National Do Not Call Registry? It seems I cannot license the data set and give access to multiple customers?
Items 36 through 38 in the FTC's FAQ appear to address this question. https://www.ftc.gov/tips-advice/business-center/guidance/qa-telemarketers-se... R's, John
Hi John How have you been? So, I did see the information on the site I just did not know if there was a different licensing model for carriers. It looks like if we were going to offer an API for customers to check if a number is in the data base before they complete a call they would each need a license or subscription. We are not able to aggregate the data. Ryan -----Original Message----- From: John Levine <johnl at taugh.com> Sent: Sunday, October 10, 2021 10:35 PM To: voiceops at voiceops.org Cc: Ryan Finnesey <ryan.finnesey at conovence.com> Subject: Re: [VoiceOps] National Do Not Call Registry" It appears that Ryan Finnesey <ryan.finnesey at conovence.com> said:
I was wonder what others were doing to license the National Do Not Call Registry? It seems I cannot license the data set and give access to multiple customers?
Items 36 through 38 in the FTC's FAQ appear to address this question. https://www.ftc.gov/tips-advice/business-center/guidance/qa-telemarketers-se... R's, John
They can delegate their access to you, and you can use that to verify they have legitimate access to the areas in charge, and then maintain your data by compositing the entire list all of your customers have access to and adding their SAN to your client list. I think they have to do something to verify the relationship, then you can download their data with your account and everything's nice and legal and shiny. You just have to have a mechanism to make sure they maintain an active subscription for the data they are trying to access (so for example, you don't return data in texas if they only subscribe to 5 area codes in illinois). I looked at doing this for telcodata.us a while back and it was a LOT of effort to go through and I didn't have time to code it at the time, but it's a valuable service and I'm sure there's a way to make a go of it. Same with LNP data use for wireless scrubbing - your carrier rules don't actually allow it to be used for telemarketing list washing, you have to do something similar with iconnectiv. They have a similar arrangement where each customer has to pay for access to the DB for that particular purpose. It wasn't wholly unreasonable and you could make a go of it if you had 5 or so customers out of the gate (my math) but you'd think this would just be something easy you could do with the data you have, and it's just never that easy because someone found a way to monetize the everliving shit out of data they handle on the behalf of the nation. -Paul On 10/11/21 10:04 AM, Ryan Finnesey wrote:
Hi John
How have you been? So, I did see the information on the site I just did not know if there was a different licensing model for carriers. It looks like if we were going to offer an API for customers to check if a number is in the data base before they complete a call they would each need a license or subscription. We are not able to aggregate the data.
Ryan
-----Original Message----- From: John Levine <johnl at taugh.com> Sent: Sunday, October 10, 2021 10:35 PM To: voiceops at voiceops.org Cc: Ryan Finnesey <ryan.finnesey at conovence.com> Subject: Re: [VoiceOps] National Do Not Call Registry"
It appears that Ryan Finnesey <ryan.finnesey at conovence.com> said:
I was wonder what others were doing to license the National Do Not Call Registry? It seems I cannot license the data set and give access to multiple customers? Items 36 through 38 in the FTC's FAQ appear to address this question.
https://www.ftc.gov/tips-advice/business-center/guidance/qa-telemarketers-se...
R's, John _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thanks Paul We have some extra development cycles so we may look to build something. LNP data would also be interesting to include. Ryan -----Original Message----- From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Paul Timmins Sent: Monday, October 11, 2021 10:45 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] National Do Not Call Registry" They can delegate their access to you, and you can use that to verify they have legitimate access to the areas in charge, and then maintain your data by compositing the entire list all of your customers have access to and adding their SAN to your client list. I think they have to do something to verify the relationship, then you can download their data with your account and everything's nice and legal and shiny. You just have to have a mechanism to make sure they maintain an active subscription for the data they are trying to access (so for example, you don't return data in texas if they only subscribe to 5 area codes in illinois). I looked at doing this for telcodata.us a while back and it was a LOT of effort to go through and I didn't have time to code it at the time, but it's a valuable service and I'm sure there's a way to make a go of it. Same with LNP data use for wireless scrubbing - your carrier rules don't actually allow it to be used for telemarketing list washing, you have to do something similar with iconnectiv. They have a similar arrangement where each customer has to pay for access to the DB for that particular purpose. It wasn't wholly unreasonable and you could make a go of it if you had 5 or so customers out of the gate (my math) but you'd think this would just be something easy you could do with the data you have, and it's just never that easy because someone found a way to monetize the everliving shit out of data they handle on the behalf of the nation. -Paul On 10/11/21 10:04 AM, Ryan Finnesey wrote:
Hi John
How have you been? So, I did see the information on the site I just did not know if there was a different licensing model for carriers. It looks like if we were going to offer an API for customers to check if a number is in the data base before they complete a call they would each need a license or subscription. We are not able to aggregate the data.
Ryan
-----Original Message----- From: John Levine <johnl at taugh.com> Sent: Sunday, October 10, 2021 10:35 PM To: voiceops at voiceops.org Cc: Ryan Finnesey <ryan.finnesey at conovence.com> Subject: Re: [VoiceOps] National Do Not Call Registry"
It appears that Ryan Finnesey <ryan.finnesey at conovence.com> said:
I was wonder what others were doing to license the National Do Not Call Registry? It seems I cannot license the data set and give access to multiple customers? Items 36 through 38 in the FTC's FAQ appear to address this question.
https://www.ftc.gov/tips-advice/business-center/guidance/qa-telemarket ers-sellers-about-dnc-provisions-tsr
R's, John _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (3)
-
johnl＠taugh.com -
paul＠timmins.net -
ryan.finnesey＠conovence.com