September 2019 PACE CPC Meeting 

PACE has sponsored industry-wide Communication Protection Coalition (“CPC”) meetings in the past that addressed mitigating robocall blocking/labeling errors in an analytics-based framework.  PACE held another CPC meeting on Wednesday, Sept. 25 in Washington D.C.   The focus of the meeting was centered around addressing mitigating blocking errors in a SHAKEN/STIR environment.  This issue is one of the current topics addressed in a pending FCC proposed rule making.  Many of the initial comments submitted noted the importance of protecting legal callers. Thus, if you commented on this topic, you may find attendance at the CPC meeting useful.

The meeting will be held in the same hotel hosting the PACE Washington D.C. Summit, which is the Intercontinental Washington D.C., 801 Wharf Street, SW Washington D.C., 20024.   The CPC meeting will be from 8:30 a.m. – 12:00 p.m.  Registration will help us get an accurate count for logistics purposes.

An agenda will be forthcoming, and we expect to have all segments of the industry, including various regulators, attending.  Given the various legislative proposals and regulatory proceedings addressing this topic, it is a timely opportunity for you to attend.

If you are also attending the PACE Washington Summit, you may add the CPC session to your registration to help facilitate meeting logistics.  If you have already registered for Summit, please contact Kayci Vincent to add this meeting to your current registration.

Further questions can be directed to Karl Koster, of Noble Systems, at 404 851-1331 (x1397) or at

September, 2018 PACE CPC Meeting 

The last meeting of the Communication Protection Coalition (“CPC”) task force, sponsored by PACE, was held in Washington, D.C., on September 26th following the PACE Summit.  We are working to determine the next meeting of the CPC for the 1st quarter of 2019.  Communications regarding that meeting will be posted immediately when finalized. 

August 2018 PACE Communication Protection Coalition Meeting

The next PACE Communication Protection Coalition meeting will be held at 8:00 A.M. – 5:00 P.M., Friday, August 3, 2018.

Kelley Drye & Warren, LLP
Washington Harbour, Suite 400
3050 K Street, NW
Washington, DC 20007

Registration is required for this event. If you do not register for this event, you will not be allowed to attend.

Please consider making a $150 donation to the PACE Communication Protection Coalition to help defray meeting expenses.*** 

Agenda for August 3, CPC Meeting includes:

  1. Reporting Results of Number Registry Sampling
  2. Trusted Call Originator  – definition and discussion
  3. SHAKEN and STIR’s Proof of Possession (“POP”)– overview and discussion 

More details regarding the meeting will be forthcoming in the next few weeks.


UPDATE: April 2018 CPC Meeting Date

Updated Best Practices Document as of April 4th, 2018 (click here)

The Communication Protection Coalition (“CPC”) task force, sponsored by PACE, will hold its second meeting on April 4, 2018 in Washington, D.C.  
The venue is located at 601 New Jersey Ave., N.W. 5th Floor, Washington, D.C. 

The sign-in begins from 8:00 AM – 8:30 AM, along with breakfast. 

Please note that pre-registration is required in order to gain entry to the facility, so please register in advance at the link provided below. 

Unlike like last time, PACE will NOT be broadcasting this meeting live.  The session presentation and minutes will be available a week or two after the meeting.

Main topics of discussion will focus on mechanisms for checking on the status associated with a number and mitigation mechanisms.

Click here to register.

CPC Meeting, April 4 2018

• 8:00-8:30am – Breakfast
• 8:30am – 8:40 – Welcome/Introductions
• 8:40 – 9:30 – Update from last meeting
• Action items, Industry, Resolutions, New Challenges
• 9:30 – 11:00 – STIR/SHAKEN – presented by ATIS
• 11:00 – 11:15 – Break
• 11:15 – 12:30 – Beyond the Call Originator for Best Practices
• 12:30- 1:30 – Lunch
• 1:30 – 3:00 Panel Discussion with Analytics/Data Providers
• Progress, Challenges, Future Steps
• 3:00-3:30 – Wrap up, Next steps

Click here to download the agenda

January 2018 CPC Meeting Date

The next PACE Communication Protection Coalition meeting will be held at 8:15 a.m. – 4:30 p.m., Thursday, January 25, 2018.

Kelley Drye & Warren, LLP
Washington Harbour, Suite 400
3050 K Street, NW
Washington, DC 20007

Registration is required for this event. If you do not register for this event, you will not be allowed to attend.

  • Please consider making a $150 donation to the PACE Communication Protection Coalition to help defray meeting expenses.***
  • Space is limited, so only one (1) person per company is allowed to register.***

The Government Affairs Committee encourages PACE members to participate in regulatory processes that may affect their business. Until January 23rd, the FCC is accepting comments in its proceeding related to Advanced Methods to Target and Eliminate Robocalls. Specifically, the FCC seeks comments on methods for carriers to unblock erroneously blocked numbers and measure the effectiveness of call blocking techniques. The full text of the FCC’s request is in paragraphs 57-59 of its recent Report and Order.

Many PACE members regularly provide comments to the FCC on upcoming matters. While some use the services of a law firm, this is not required and members often submit comments on their own. If your organization has not commented before to the FCC, the process is not difficult and can be completed online. To help you get started, the Government Affairs Committee put together a short tutorial that will walk you step-by-step through the commenting process. You can find the tutorial here.

The comment process is your opportunity to be heard on issues that matter greatly to your business and we encourage you to take advantage of it. 


UPDATEPlease click here for an update on the latest FCC action on this important issue

Have you noticed a significant decrease in your contact rates over the last several months? 

Has your company seen a depression in contact rates lately? Have your customers been asking why your calls show as “Scam Likely” or “Fraud Alert”?

As a result of the FCC’s Robocall Strike Force initiatives, the carriers and their associated analytics companies are making decisions about your calls. These unregulated analytics companies apply their own algorithms to determine if a call should be blocked from ringing your customer’s phone or replace your Caller ID with a label such as “Scam Likely”, “Robocaller”, “Fraud Call”, “Telemarketer” or “Debt Collector”.

The issue that is very concerning to PACE and our members is that the algorithms do not take into account legal entities delivering legal calls for which consent has been provided. The analytics companies are merely applying their algorithm without knowing all the facts regarding the call. Essentially, your calls could be going into a blackhole to which you have no visibility.

PACE is not taking a passive look at this issue. This is the most significant issue for our members, who use the telephone to communicate with their customers, since Do Not Call legislation. The reason that this call blocking and labeling issue came up is that the FCC wants to stop illegal robocalls. We all want that. No “ifs”, “ands” or “buts”. Unfortunately, as implemented without careful thought about unintended consequences, legal communication between companies and their customers has been affected greatly. 

PACE’s end goal is to make sure that every legal call that a company places to its customers gets to the customer unencumbered without false labels or never getting there at all because it was blocked. The tactics of how we get there are now being considered. Our first step is to get all the stakeholders to agree that this is an issue.  By organizing a coalition led by PACE, we can solve this in the short term before a long-term solution that has been proposed by the FCC Robocall Taskforce is implemented.  

On Wednesday September 20, 2017, PACE convened a meeting of stakeholders which included carriers, analytic companies, app developers, trade associations and regulators. Each constituency presented their side of the story, so that there were no wrong assumptions still in play. The meeting was very well attended and there were different points of view that may or may not come together in a solution. There are some next steps already set.

PACE has formed a task force that will be driving not only PACE’s strategy, but also the leadership of the coalition. In the next few weeks, we will have a webinar for all PACE members on this topic. Our membership will be updated on the issue, PACE’s strategy and the coalition efforts. 

As discussed during the CPC meeting that was held on Wednesday, September 20th in Washington, D.C., a best practices “working document” has been generated for mitigating robocall processing impacts on wanted and legitimate communications. 

The downloadable Best Practices Word working document provides you the opportunity to review the best practices as it stands now.
The Template for Edits document allows you to suggest or propose additions/edits.  Once completed, please submit to Karl Koster at and Rebekah Johnson at  The comments will be collected/summarized, and potentially incorporated into the next draft.

These will also be discussed, as well as any other submissions received, at the January 2018 meeting.  The date/venue of the January meeting will be forthcoming.

September 2017 Meeting Minutes
Powerpoint presentation

Best Practices Documents
Template for Edits

Contact PACE if you have questions or comments.