Today Skycore has spun off our email solution into a new service called MailPact. The service features an unlimited email and subscriber solution where you only pay for how fast you would like to send. No more paying per subscriber or per message for your email marketing or transactional email. The solution works as a campaign management tool where you need to connect your own SMTP server or use an SMTP service like Sendgrid, MailGun or Mandrill.
Existing email customers on Skycore.com will continue to be able to use Email within the Skycore platform pricing however new customers will not have access to the Email capabilities and must sign up with Mailpact.com. Skycore platform customers are encouraged to move their subscribers and API calls to Mailpact.com so that they no longer will be paying transaction fees per message.
Step 1: Create a campaign in your Skycore.com account. We suggest that you use the following settings.
- Set the campaign name to “Delivery Status Notifications” or something similar. The campaign name will appear in the Opt-in message. This will ensure that the customer is aware of what they are agreeing to.
- Set the “Re-Subscribe Opt-in SMS Flow” to OFF. This means that if a customer is already subscribed they will not receive the opt-in message flow again.
- Set the “Re-subscribe Auto-responders” to OFF. This means that if the customer is already subscribed they will not receive any auto-responders again.
Step 2: At checkout provide customers with an optional checkbox to receive SMS delivery status updates. When checked, make sure to request their mobile phone number and disclose they will be receiving text messages to their phone and that it is not a required part of the purchase.
Step 3: After customers submit their order, your server will need to call the subscribe API function. Within this API call below you to change the “API_key=”, “mobile=” and the “campaignid =”sections of the API.
- “api_key=” is your account’s API key.
- “mobile=” is the customer’s phone number including the country code.
- “campaignid=” is the campaign ID can be found on the “SMS/MMS Campaigns” page.
Step 4: Once the Subscribe API is called, the customer will be sent an opt-in message requesting their ‘written consent’ to receive text messages from you. Affirmative written consent is a FCC mandate which is why we ask the customers to reply “YES”. Your customers will then be segmented into three groups in your Audience Manager.
- Subscribed Users – Customers who reply “YES” or “Y” and have not unsubscribed.
- Unconfirmed Users – Customers who did not reply “YES” or “Y” but who checked your checkbox to receive delivery notifications.
- Unsubscribed Users – Customer who unsubscribed themselves by replying “STOP”, “QUIT”, “CANCEL” or “UNSUBSCRIBE”.
Step 5: All messages you send out will automatically start with your brand name as they did in the double opt-in message above. To send messages, use the SendSMS API call. In the SendSMS API call below, you will need to change the “api_key=”, “to=”, “text=” and “campaignref=” sections.
- “api_key=” is your account’s API key.
- “to=” is the customer’s phone number. Make sure to include the country code.·
- “text=” is the actual message you will be sending out.
- “campaignref=” is the campaign ID of the campaign that you are sending the message from.
Step 6: When you call the API – you should receive one of two messages depending on if the customer is subscribed into the campaign or not:
- A “Success” message, and the customer should be receiving your SMS very shortly.
- A “Failure” message which means the customer has not opt-in. They will not receive any SMS message and we recommend that you flag the user as opt-out in your internal database.
Example of an API Success Message and an API Failure Message:
As we kick off 2015, it is looking like this year is going to be all about visual marketing and brand recall. Brands will be sponsoring messages in applications like Facebook, Instagram and Twitter with interesting pictures in order to increase a metric called ‘brand recall’ which is used to measure their success. Brands who have built up SMS lists will be sending MMS messages to their lists for that same reason.
The question we are often asked is what the best image size is for delivering an MMS message. Each year, screen dimensions change as popularity shifts to larger, taller screens. Over 96% of consumer devices on the market have phones with screens that are in portrait mode (tall). If you check out the Tier 1 US carrier’s websites even the old school flip phones are all portrait mode nowadays. The only phone being sold by the Tier 1 US carriers that is still landscape(wide) is the Blackberry 9930. Even the Blackberry Z10 and Q10 are not landscape. The Z10 is portrait and the Q10 is square at 720×720. Therefore you should focus your effort on delivering a beautiful portrait image that is compelling to your audience.
We’ve created a number of different images and delivered them as an MMS to a number of popular phones on the market today of various sizes. Here are our results.
After completing these tests we found that an aspect ratio of 9:16 worked best across all devices. We suggest using images that are 640px by 1138px, or 1080px by 1920px if you want a larger version.
When you upload an image above 640px by 1138px and over 100Kb the Skycore platform will transcode and optimize your image and adapt the markup to fit the screen width. Images 640px by 1138px and below may have higher file sizes but will still be transcoded on delivery if required.
When we tested the different devices we found that the iPhone 5s and iPhone 6 would first open up to a preview screen and then would display a full screen version of the image if you tapped again. In that preview screen there is a border on both the top and the bottom that cuts off some pixels. We did some research and were able to find the exact number of pixels for the suggested screen sizes that are being cut off for both the iPhone 5s and the iPhone 6. We suggest that when creating your MMS images that you refrain from putting any logos, barcodes or important information in these temporarily covered areas. You can see in the image below the red area that represents the covered area. Due to the popularity of the iPhone 5 and 5s that you keep important information far enough from the bottom and top edge.
We went on to test the 640×1138 and 1080×1920 files sizes on the Blackberry Bold 9900 to see how the image would be viewed on their landscape screens. Here you can see our results of how the image normally looks as well as how it would appear if you zoom in. Both looked exactly the same and the zoom was no issue at all for an everyday blackberry user. Just pinch the screen outwards similar to how an iPhone works.
Go To Market Recommendation:
Create an image that is 640px by 1138px or 1080px by 1920px at any file size up to 1.5Mb . For 640px by 1138px do not put any “content of interest” in the top 129px and the bottom 89px, and for 1080px by 1920px do not put any “content of interest” in the top 218px and the bottom 150px. The Skycore platform will transcode your content to the appropriate file sizes for each carrier and device.
You are set for 2015!
On Nov 1st, with feedback from the industry, the CTIA released a new Short Code Monitoring Handbook which governs the approval and audit standards of short codes and the advertising of short code campaigns. Whether you have a short code in market or you are considering registering a code there are a number of key changes that all brands should be aware of. Here are a few that I feel are pretty substantial.
1) Brands can now provide a generic ‘recurring’ message frequency disclosure instead of an exact frequency of messages when they opt a customer into a campaign. A number of brands face lawsuits because the CTIA guidelines had previously required an exact frequency of messages to be disclosed and some of these companies delivered slightly more than their stated frequency. To prevent lawsuits, conservative brands started disclosing frequencies 10 times that of what they would actually send to be on the safe side. For example a brand might have disclosed 30/month when in fact they sent 1/week. This previous compliance policy created a bad customer experience and significantly more liability for both brands and marketing service providers. With the recent change to the rules a brand can simply state that the messages are ‘recurring’. I believe this is a fantastic improvement for both customers and brands because it removes liability, makes the opt-in advertising more accurate, and allows more flexibility and personalization with each campaign based on appropriateness rather than some arbitrary message limit.
2) “Message & Data Rates May apply” is no longer required in the “Opt-in Message”. It is now only required in the “Confirmation Message” and in the “Advertising Disclosures”. This is a great benefit as well. Brands will now have more characters to describe what the customer is signing up for in the very first message. In the past, since there had been so many required discloses in the Opt-in Message, a brand would hardly have much room for their own text. It made for a poor customer experience and likely lowered opt-in rates.
3) “Reply STOP to opt-out” is no longer required in the ongoing message flow as long as it is provided at least once a month in a service message or within content delivered. Horray! Customers will no longer wonder why the brand is telling them to opt-out in every message they receive. This was obviously an awkward requirement for both customers and brands. Not to mention it took valuable space in each message.
4) “Reply STOP to opt-out” is no longer required to be disclosed in the “Advertising Disclosures” as long as it is in BOLD letters in the Terms and Conditions page. The Reply STOP to opt-out requirement was always awkward for advertisers who wondered why we would provide opt-out instructions IN ADVERTISING to someone who had not yet opted-in.
5) No more shared short code restrictions on Point of Sale vendors. This will enable small and medium sized businesses to afford to SMS message their customers. While there are additional compliance requirements for Point of Sale call-to-actions by the FCC, this CTIA rule will help open up text messaging to SMBs who cannot afford $500/month to lease their own short code.
Great job CTIA.
The Update: You can now deliver vCards(.vcf) and iCalendar(.ical) through both the MMS API as well as through the Campaign Manager User Interface. The process is as simple as adding an image or video using the same structure and flow that you are used to. We have also enabled text to be delivered alongside the ical/vcard since not every phone supports .vcf and .ical in 2014. You can use this space to provide a fallback/download link to the object until vcard/icalendar MMS transcoding is available in 2015 and more devices have the capability.
Benefits of the Update: There are many useful reasons to send contact information via MMS. Often adding contact information to your phone is not quick and easy. Other times it is awkward to ask for it in person from a service provider. The use cases for vcards is most obvious for business who rely on phone calls to either order something regularly, call in an emergency or conduct business primarily by phone.
The Update: Email addresses can now be collected via SMS data collection. Email data is collected when an SMS data collection message is sent out to customers requesting their email address in the reply. When customers respond, that data is both added to their Audience profile and subscribed to an email campaign. Once the email is added to an email campaign a sequence of email auto-responses can be sent to the customer.
Benefits of the Update:
You are now able to take customers who already subscribed to an SMS/MMS campaign, and subscribe them into an email campaign. By doing so, you will be able to transition your SMS/MMS marketing campaign into a cross-platform strategy.
Cross-platform mobile marketing campaigns give companies the option to present a larger variety of content by taking advantage of multiple mediums. Different mobile marketing mediums have different advantages.
Once customers are opted into an email campaign, you can send email auto-responders and scheduled email messages to them. By creating an auto-responder for your email campaign, customers can receive a confirmation email message from you almost instantly after they submit their email address through SMS. There is no API integration required.
The Update: Menu Response Actions (MRA) and SMS Data Collection have been added as new features. MRA allows you to create quizzes and surveys with open ended or multiple choice answers. Data from customer answers are then collected and stored as subscriber data. Later in your messaging campaign, you can use this data as within messages using dynamic merge tags. You can also simply export the data as a CSV file for analysis. These special SMS questions can be scheduled as message blasts during a campaign. The response actions that are carried out after a customer replies are set up when creating the SMS MRA.
Benefits of the update:
Improved Customer Information: Before this update you were limited to gathering information during opt-in time, import or through the API. With SMS Menu Response Actions you can continuously gather customer information throughout a campaign and store it into simple variable names. Using dynamic merge tags you can create personalized SMS, MMS and emails using information gathered from many data sources throughout the campaign.
Data Collection: Recognizing who your customers are and what they are interested in is critical for any business. Through Menu Response Actions you can easily send surveys out to your audience to gather opinions about your products and services. Using this information you can better allocate your marketing resources.
Customized Responses: For each question in your SMS you can provide an automatic response for each possible answer. The response can either be another SMS or MMS. This can be a great way to create interactive message flows or be a way to redirect customers with links to specific products.
The Email Design Tool now supports adding “Background Images” to email templates. Before this update email templates could only have a colored background. The background option only allowed you to use a single color to fill the blank background space in emails. This update allows you to use images with the jpg, png, and gif extensions to serve as the background of the email template. Adding beautiful images to the background will make your emails more appealing to readers. You can also overlay text, buttons or other images on top of this background.
Benefits of the update
Adding images to your email gives it emotion and substance. The problem is that not all email clients display images by default. Therefore placing any text within your image means that many people will not be able to read it unless they ‘allow images’. The benefit of using background images are that you can still put html, text and buttons in the email over the background image. By doing so the recipient will be able to read your textual message with or without ‘allowing Images’. Placing the image as the background will free up space for your message and other buttons or links. If you have any questions on email backgrounds please visit the Email Help Section for Email Design Tool.
The security team at Skycore has been working to assess the impact for our customers following April 7th’s disclosure of CVE-2014-0160, also known as Heartbleed. This is a critical vulnerability in OpenSSL which can compromise the secret keys used for SSL encryption.
We have not discovered any intrusions or unauthorized use of our systems but it is important to ensure that the vulnerabilities are patched in a timely manner.
We have performed the following updates to our systems and procedures on the following dates:
* We have patched all OpenSSL libraries on all servers April 8th
* Skycore leverages Amazon Elastic Load Balancing infrastructure. This was patched by Amazon on April 8th
* We have reissued all internal SSH keys April 8th and renewed SSL Certificates April 11th
We recommend our API customers review the security of their own servers to ensure they are not vulnterable:
* Refresh API Keys if applicable
* Verify that any of your public and private SSL endpoints are not still vulnerable
Further background on the Heartbleed vulnerability: http://heartbleed.com/
To confirm our Heartbleed status visit: http://filippo.io/Heartbleed/#skycore.com
We hope this answers your questions about the impact of CVE-2014-0160. If you have any follow up questions, don’t hesitate to ask at firstname.lastname@example.org
All the best,
The Skycore Team
The Update: SMS Concatetenation now lets SMS hold up to 300 characters. Normally SMS are limited to roughly 160 characters. Messages longer than 160 characters are sent as multiple messages. SMS Concatenation will send these smaller messages with a special flag to combine into one long message on the device. For billing purposes concatenated messages will be charged as multiple messages.
Benefits of the update:
Organization: When an SMS is sent as multiple small messages it has the potential to be sent in the incorrect order. With this update you can send those longer messages knowing they will be read in the proper order.
More Information: SMS can now hold nearly double the amount of characters than before. Your messages now have more space allowing you to add crucial content. Adding more App information and SMS links will help promote your campaign.
How to access this feature: You can schedule SMS through the SMS/MMS Campaign’s “Message Scheduling” tab. Select a date so that the message select window appears. Choose the SMS tab and create the message with up to 300 characters in the text area.
The message will be received as one long fluid message.