Are all MT messages originating from your Production short code and not the mblox test code (28444)?

Transcription

1 mblox Certification Checklist PLEASE NOTE: These guidelines are not intended to supersede or replace any requirements in the MMA or Carrier Guidelines. They are merely to aid providers and their clients in testing their campaigns prior to submitting them to mblox for certification. If a campaign fails in any one of these points, do not submit the campaign for certification until the problem has been resolved as this will result in a failure. When you request certification in mopt, you have agreed that you have tested your service and you are ready to go live. If you need additional assistance to supplement your in-house testing capabilities, please see your mblox Account Manager who can provide information on mblox s additional service capabilities. 1.1 General Questions Have you connected to mblox servers? Are all MT messages originating from your Production short code and not the mblox test code (28444)? Have you tested your service on a handset from each US carrier requested within the mopt order to ensure the entire service is working properly? If not, please contact your mblox Account Manager to discuss other options. Do you have the keywords and/or the URL required for opt-in to the service ready for carrier and mblox certification testing? Please Note: You must provide a way to test each approved price point within the mopt order on each carrier. For example, if an approved price point is not available on the opt-in website, you will need to set up and provide a keyword for that tariff for certification purposes. Have you implemented a STOP MT (Standard Rate)? This is required regardless of whether your application is a transaction or subscription service and must be working at all times. All MMA opt-out keywords must return the carrier approved MT response: STOP, CANCEL, QUIT, END, UNSUBSCRIBE, STOP ALL. STOP commands must be recognized regardless of the text case or subsequent text within the users MO STOP message. Example: StOp it Now, QUIT SENDING, or STOP sdswsds should all return the same opt-out message. Does the STOP MT include confirmation that the user has been opted out of service and no further messages will be received + Customer care/support contact information (URL or toll free#)? Please Note: If the end user is opted into multiple subscription services on the same short code and an MO of STOP is received, an MT with a list of services to which the end user is currently subscribed may be sent. This MT should let the end user know how to opt out of each individual service. If no such MT message is sent, the MO STOP must function as a STOP ALL command and the end user must be unsubscribed from all existing subscription services. Have you implemented a HELP MT (Standard Rate)? This is required regardless of whether your application is atransaction or subscription service and must be working at all times. The Help MT message must include customercare/support contact information, the pricing/billing frequency, the program sponsor name, how to opt-out via SMS, current compliance wording regarding standard carrier charges, and the type of service (i.e., alerts, trivia, ringtones, etc). Page 1 of 7

2 Does your message flow match the approved mopt order you are requesting certification on? If not, your order will not pass the carrier certification. In addition, all support numbers, URL s and s must match the original submission. Are the initial double opt-in MT s standard rate? Are alerts being sent out following the opt-in to subscription services? An alert will need to be tested on all alerts-based campaigns. After the opt-in confirmation MT s, please ensure that a sample alert is being sent or direction is provided in the mopt certification request on how to test said alert. An alert should be sent in a timely fashion after an end user has opted into your service. If an alert is not sent in a timely fashion, this could delay your certification or cause an unnecessary failure. Are your premium billed MT s flagged with the correct tariff? Does the opt-in MT state the program sponsor/service name, the cost of service, the billing frequency (where applicable), how to get help, and how to opt out? Does your initial MT (initial response to keyword) include the following: program name, service type (ex: alerts), pricing, frequency of messages (where applicable), and how to obtain help via SMS. If double opt-in is being requested on a premium service, the pricing MUST come before any requested opt-in confirmation responses (Ex: reply Y or enter PIN ). Are your premium MT s being sent promptly after the double opt-in confirmation is received on premium services? Confirmation that the end user has been billed, the message frequency (where applicable), type of service, program sponsor name, HELP wording, and STOP wording should be included in this message. The Premium MT should be sent within a timely fashion. If a premium MT is not sent in a timely fashion, this could delay your certification or cause an unnecessary failure. Do your MT s state Msg&Data Rates May Apply, Message and Data Rates May Apply, or Msg&data rates may apply? Does the end user have a clear understanding of what he/she is purchasing? 1.2 Carrier-Specific Requirements: AT&T Your orders must be submitted within the timeframes outlined below: Certification requests for new campaigns must be received by mblox no more than 120 calendar days from the date your campaign has been provisioned by mblox. In the event the certification does not pass AT&T s testing, the request for retest must be received by mblox no more than 120 calendar days from initial submission. The first MT must include the location of SMS terms and conditions, product being sold, Msg&Data Rates May Apply wording, pricing/billing frequency (as applicable), message frequency (as applicable), HELP wording, and STOP wording(stop - only if double opt-in is not required). Premium confirmation MT s must include the product being sold, Msg&Data Rates May Apply wording, pricing/billing frequency, message frequency (as applicable), HELP wording, and STOP wording. Page 2 of 7

3 PREMIUM ONLY: Are your STOP & HELP MT s flagged as <free> for the tariff value (tariff=free instead of tariff=0)? Have you removed the term Free, No Cost or Zero Charge from your advertising? Have you removed alternate billing methods as an option? Example: credit card billing Have you removed the AT&T logo from your advertising? Only plain-text AT&T is supported. PREMIUM ONLY: AT&T Premium Interface Solution Service IDs must be implemented and tested. You can check that billing posted properly by going to Current subscription status and details of your charges will be accessible from this site. PREMIUM ONLY: When MO: STOP is sent to the short code, it is required that: A response STOP MT must be sent. The user must indeed be opted out. The opt-out must be communicated to AT&T via the AT&T Premium Interface Solution /QPASS. Both the Service ID and Session ID in the STOP MT must match the Service ID and Session ID that starts the subscription. PREMIUM ONLY: Are you using Tag-Exempt=true? If not, this implementation is highly recommended. Opt-in MT message must be complete and not truncated. WEBSITE: Must clearly disclose that all purchases (if premium rated) must be authorized by the account holder. WEB OPT-IN: Mobile phone submit page must disclose Messaging and Data Rates May Apply. Are terms and conditions readily available? SMS Ts&Cs are required and must be manually checked prior to the end user proceeding through the Opt-in web page? This must be in place on the cell submit or Pin Entry page. AT&T recommends that a link to Ts&Cs be available in a side bar, header, or footer. Price, billing, and frequency must be clearlydisclosed next to the cell phone submit page. Do your Terms include Messaging & Data Rates May apply? Are the Termination and help instructions in BOLD? Chat services must be moderated and cannot allow prohibited words. If a user sends a prohibited word, an MT must be sent stating that the message is not appropriate. WAP sites must include FAQ for customer support and must have a functional hyperlink to terms and conditions. 1.3 Boost Unlimited & Prepaid WEB OPT-IN: Pricing must be clearly written near the mobile phone submit field (not only within the summary of SMSTerms & Conditions or full Ts&Cs). Services do not exceed $6.99. When replying to messages, some Boost handsets will treat SMS messages like s. RE: will be in front of any message replies followed by the previous message. If a user is opting into a service with Page 3 of 7

4 yes, it will come through as, RE:YES (previous message). You will need to assure messages still respond accordingly. 1.4 Sprint Within days of Sprint provisioning a short code, the program is subject to an Audit. If Sprint tests your service and it fails an audit, the short code could be suspended for a minimum of 30 days. It is important that you assure you match your approved program brief for any live traffic. WEBSITES: If a Sprint mobile number can be entered onto a website and work, the website must be Sprint compliant. Sprint Logo or Sprint in plain text must be listed on the website. Terms and Conditions on the web site must state that the user must send or text HELP, STOP, and any other MO commands to the short code. The phrase Reply STOP to cancel must appear in the: First MT, Confirmation MT, and HELP MT. HELP MT must be compliant in the following ways: A MO of HELP must return information about the most recent program the user opted into. If an end user is subscribed to multiple programs, a help menu is OK if you only provide information on the subscribed programs. Price ranges are not allowed. The HELP MT must contain the most recent transaction or subscription pricing. information. Example: If the user s most recent purchase on a short code was a ringtone transaction for $1.99 thehelp must state the $1.99 price. If a user is not opted into any programs, the HELP MT must provide information about the short code including. support contact information, pricing, billing frequency, program sponsor name, type of service, and opt out information. WEBSITE: On web opt-in, the pricing must be within 125 pixels directly above or below cell-submit field, with no intervening text. WEBSITE: Display T&Cs containing message and data rates and customer cancellation, opt-out, billing method, pricing, and subscription disclosures with at least three lines above the fold at screen resolution 1024x768 pixels BINARY: When sending your WAP push your content must point to a GCD file. PREMIUM: All premium messages must have the appropriate content type. o Example: Operator=31005, Tariff=999,ContentType=10 ALL CAMPAIGNS: Help MT must contain a toll free support phone number. Subscription Alerts: Help MT must contain total number of alerts end user will receive. Page 4 of 7

5 1.5 T-Mobile Premium Subscription: Monthly renewal date must be listed in your help MT. Premium applications must include the toll free number in the HELP MT. Premium opt-in MT s must include program name, price and billing frequency, and frequency of alerts. Pricing must be displayed before your confirmation keyword. Billing MT s must include confirmation that billing has occurred, HELP, and STOP information. BINARY: Are you sending a billable message after content has been delivered to the handset? Device discovery has been implemented either by WAP or handset selector on a webpage. T-Mobile games must be certified through True North prior to requesting for certification with mblox. A copy of True North s certification certificate will be required upon requesting mblox certification. Premium Campaigns: Product description tags and approved Service ID s must be present; subscriptions must also have both of these in the STOP command. Premium Campaigns: Testing of premium service before certification will cause an error code 72 to be returned on the billable MT. The MT will not hit the handset. If you get an error 72 only, you should consider this a successful test. All Campaigns: The Service ID parameter needs to be implemented for all MTs both standard rate and premium. PSMS accounts and Direct + accounts will have different Service IDs. The correct Service IDs are found in the details section of mopt for each order. 1.6 US Cellular Do you have the Service ID s implemented for premium transactions? Do you have the product description tag implemented for premium services? Any Opt-in commands or PIN codes must be after the pricing and message frequency for the program. 1.7 Verizon Wireless Campaign submitted for certification must match final approved program in mopt. This includes URL s, customer care information including support number, and message flows. Have you provided the most recent VZW Content Certification Test Plan & Handset Compatibility document to the certification engineer, Account Manager, or uploaded it to your mopt order? If game downloads are offered on your website, you must disclose that they are not available for Verizon Wireless subscribers everywhere pricing information is displayed. Web Opt-in must have the following implemented: - Customer care info on website must match customer care info in MT s (customer care number, support , etc) - Verizon Wireless must be listed as a supported carrier. Cannot put just Verizon. Page 5 of 7

6 - When entering PIN/Password to confirm your purchase, end user must be informed that they are agreeing to the Ts& Cs. - Customer care number must have a valid voic or is answered by a member of the clients support team. - Pricing and Billing period disclosure must be clearly disclosed with specific charges, duration of subscriptions, optout details listed o Verizon Requirements: 12 point font and have a 125 color contrast value. - The price point must be numerical and must include the dollar sign. - A summary of the terms and conditions, or the full text of the terms and conditions, must be displayed, with a minimum of three lines of text above the fold (if there are more than three lines of text to the terms and conditions) on the page where the user enters their cell phone number AND on the PIN code page (if PIN is used). It is not acceptable to have only a link to the terms and conditions. All Campaigns: The Service ID parameter needs to be implemented for all MTs both standard rate and premium. PSMS accounts and Direct + accounts will have different Service IDs. The correct Service IDs are found in the details section of mopt for each order. Premium Campaigns: Price ranges are not allowed. The HELP MT must contain the most recent transaction or subscription pricing information. Example: If the user s most recent purchase on a short code was a ringtone transaction for $1.99 the HELP must state the $1.99 price. Your STOP Service ID needs to match the Service ID in the START MT. 1.8 Virgin Mobile All test numbers must be white listed with Virgin Mobile in order to test a campaign on the production short code before the campaign has been certified live. BINARY: You will need to provide a list of supported and unsupported handsets to the certification department for each binary application. You can go to for an updated list of the required in market handsets. BINARY: Does the WAP push you are sending point to a GCD file? BINARY: Are you billing the end user before delivering content? Virgin Mobile is a prepaid carrier and you want to assure that the end user has enough funds before providing your services. STOP and HELP information must be clearly written in MT messages. Abbreviations of the words Reply, Cancel, Help, or Stop are not allowed. Acceptable variations of HELP & STOP instructions: Reply HELP for help. Reply STOP to cancel Reply HELP for help, reply STOP to cancel. Reply HELP for help, STOP to cancel. (must be a comma separating commands) WEB OPT IN: The first line of the Terms and Conditions must be viewable without scrolling when viewing on Windows Internet Explorer with screen resolution set at 1024 X 768 and within 2 inches of action button or MDN/PIN field. Page 6 of 7

7 PREMIUM: Help MT messages must display remaining credits and/or renewal date, whichever is applicable. DOUBLE OPT IN: Any Opt-in commands or PIN codes must be after the pricing and message frequency for the program. Have you implemented the cross-carrier Content Type Identification? All Other Carriers For any carrier not mentioned specifically above, please ensure that your service complies with all guidelines mentioned for that carrier in the mblox Supplemental US Carrier Guidelines Document and the MMA Consumer Best Practices Guide. More information on all of these requirements is located in the public documents Please contact your mblox Account Manager with any questions. Page 7 of 7