You are on page 1of 3

February 10, 2014

Marlene H. Dortch, Secretary Federal Communications Commission Office of the Secretary 445 12th Street, SW Washington, D.C. 20554 RE: EB Docket No. 06-36 Annual CPNI Certification

Dear Ms. Dortch: In accordance with FCC Enforcement Advisory DA 10-91, attached is the annual CPNI certification filing covering the year of 2013, pursuant to 47 C.F.R 64.2009(e), for Sancom, Inc. dba Mitchell Telecom.

Sincerely,

Ryan Thompson General Manager/CEO Sancom, Inc. dba Mitchell Telecom

Attachment

1801 North Main Street Suite 25 Mitchell SD 57301 ~ Phone 605-990-1000 ~ Fax 605-990-1010

Annual 47 C.F.R. 64.2010(e) CPNI Certification Template EB Docket 06-36


Annual 64.2009(e) CPNI Certification for 2014 covering the prior calendar year 2013 1. Date filed: February 10, 2014 2. Name of company(s) covered by this certification: Sancom, Inc. dba Mitchell Telecom 3. Form 499 Filer ID: 807865 4. Name of signatory: Ryan Thompson 5. Title of signatory: CEO 6. Certification: I, Ryan Thompson, certify that I am an officer of the company named above, and acting as an agent of the company, that I have personal knowledge that the company has established operating procedures that are adequate to ensure compliance with the Commissions CPNI rules. See 47 C.F.R. 64.2001 et seq. Attached to this certification is an accompanying statement explaining how the companys procedures ensure that the company is in compliance with the requirements (including those mandating the adoption of CPNI procedures, training, recordkeeping, and supervisory review) set forth in section 64.2001 et seq. of the Commissions rules. The company has not taken actions (i.e., proceedings instituted or petitions filed by a company at either state commissions, the court system, or at the Commission against data brokers) against data brokers in the past year. The company has not received customer complaints in the past year concerning the unauthorized release of CPNI. The company represents and warrants that the above certification is consistent with 47. C.F.R. 1.17 which requires truthful and accurate statements to the Commission. The company also acknowledges that false statements and misrepresentations to the Commission are punishable under Title 18 of the U.S. Code and may subject it to enforcement action.

Signed __________________________________

Attachments:

Accompanying Statement explaining CPNI procedures

ATTACHMENT Customer Proprietary Network Information (CPNI) Documentation for: Sancom, Inc. dba Mitchell Telecom 1801 N Main St Ste 25 Mitchell, SD 57301

Per the FCC CPNI rules, Sancom certifies that we are in compliance with the CPNI rules and we have taken the following steps to protect CPNI: The companys CPNI manual to account for CPNI handling. A compliance officer is designated to oversee all CPNI training and activity. All employees have been trained on when they are, and are not, authorized to use or disclose CPNI. o Authentication steps are in place for handling customer requests in person and over the phone. o Passwords are established for customers requesting call detail records. If no password is present, Sancom will use other approved methods of authentication before proceeding. Customers are notified in writing of account changes within 48 hours of a qualifying change. We use the opt-out method to request approval of CPNI use for marketing campaigns. o We notify customers bi-annually of their CPNI rights. o We notify new customers as a part of our customer sign-up process. Their opt-out notification is included in our terms & conditions reviewed at sign-up. o Customer records within our billing system display their opting status for their account. o The companys compliance officer retains CPNI notification and opting records for two years. Maintain record of any marketing campaigns that use customers CPNI. These records are maintained for a minimum of one year. An outbound marketing supervisory review process has been established. Defined disciplinary process in place for violations and/or breaches of any customer records containing CPNI. Proper authorities will be notified of any CPNI breaches.

CPNI Breaches and Customer Complaints for 2013 o o o Number of CPNI breaches for 2013 none. Number of CPNI customer complaints for 2013 none. Actions taken against data brokers in 2013 none.

We are unaware of current processes pretexters are utilizing for attempted CPNI access. At this time, we have not encountered known pretexting.

You might also like