Help Center | Twilio Setup Guide

Please Note: Although you can see the menu on the right, clicking anywhere outside the helpfiles (for security) will result in your browser being directed elsewhere. Once you activate a workspace, the system will detect your signup IP and white list the login page and all other pages.

If you want to talk to someone directly from Efkolos.com (makers of this Texting App) please click the "Join Us On Discord" blue button there to get in. =)

Below you'll fine a list of other pages beyond the basic F.A.Q.'s listed on this page. Addtionally, the Provider's and CRM systems that Texting App is compatiable with are listed under the Provider Guides and CRM Setup guides columns, although I don't quite have those guides complete yet, I'm working on them.

Provider Guides
  • TWILIO
  • Primevox
  • Vonage Business
  • Telnyx
  • Plivo
  • Five9
CRM App Guides
  • UISP
  • Splynx
  • VISP
  • Jira CRM Plus
  • WHMCS
  • Sugar CRM
  • ZenDesk
  • Sonar ( In the works )
Other Guides & Plugins
  • Wordpress Plugin
  • Jira Project Manager
  • Asana Project Manager
  • Drupal Plugin
  • Zoho Projects
  • Monday.com
  • Android Mobile App
  • iOS Mobile App
  • Windows 11 App

Text Attachment Considerations

For any MMS/Media message (in other words, any file you attach to a text) must be under 5MB in size. If you attach one over or receive over that size the MMS will fail. In most cases, if any text is sent along with it, the text will still send.

In most cases, Twilio will take any of the valid/supported image types and reformat them for delivery based on the destination device limitations, if any.

Any attachment that's not an image, such as a video, vcard, pdf, or most any other file, all carriers have a rather small limit of between 1 MB and 1.5 MB for 10digit long code texting.

Yes, Twilio limits text attachments to 10. Additionally, no matter how many attachments there are in a given text, Twilio counts it as a single segment message.

There is no size limit for incoming MMS to your Twilio numbers. Twilio does not perform any transcoding or resizing on incoming media attachments, but the handset or sending carrier will likely apply transcoding before the file reaches Twilio. In the rare case that an inbound MMS message contains more than 10 media attachments, Twilio's /Messages API will currently only surface the first 10 media attachments in the MediaUrl parameters. However, the Twilio Console will display all media attachments associated with that message record. Typically, mobile handsets will restrict the number of attachments on an MMS message, or the total size of the message; because of this, messages with more than 10 attachments are uncommon.

The Texting App accepts all incoming text attachments in the state that we receive them and storm them within your account. If our system detects the incoming media attachment as an image, our system will sense if the attachment is under 4MB, if its over 4MB, a thumbnail that's under 4MB in size will be created as well as the higher resolution file being stored within your worksapce and counting against your storage. The non-image attachment will be stored locally untouched and a public URL provided for any non-image file.

Twilio Supported File and Size limits for MMS Media Messages: CLICK HERE

Twilio's Complete Listed of accepted mime-types (filetypes/extentions): CLICK HERE

Yes, right now, there are only certain file types (listed below) which we download from Twilio and store locally on our system which of course you can access under your attachments section of the web GUI app, or with in the standard texting screen or archived texts screen.

Any image over 5MB however, what we do with our system, is create a smaller version at under 4MB and then include a public URL within the text for your receiver to click on to get the "full resolution" version downloaded to their device, or the URL copy and pasted into an email perhaps.

Any non-imgage file regardless that you attempt send will be saved in an untouched format and a public URL made available for your receiver to download, stream, add a vCard what ever they with to their device.

Additionally, all files you attach to any texts (which includes images, their generated thumbnails, and all non-image files) are counted against your plans included storage space based on file size. We have a "soft limit" of 100,000 "in nodes" (or files) given our file system. Once this limit is reached we will first delete the oldest file, and then plug in the newer file. We will be building in a feature that will allow you to "download & purge" attachments, as well as we'll be working on Google Drive support for simply storing all your attachments there instead of locally on our platform.

Steps for Twilio Setup

  1. Sign up for a new Twilio account and load it with at least $50 USD. The Texting App will NOT work with a trial account.

  2. Begin your A2p-10DLC registration ( This step is only required for US based numbers at this time ) with Twilio by CLICKING HERE. There are 3 steps to completing your A2P-10DLC setup. This step is REQUIRED in order for Twilio to process your texts.
    1. Creating your first customer profile
    2. Registering your brand
    3. Registering your first campaign

  3. Purchase a Twilio Phone Number by CLICKING HERE. Once you've purchased your phone number, navigate to the configuration and scroll by CLICKING HERE and clicking on the phone number you purchased. Then scroll down until you find Messaging Configuration and under "A message comes in" select webhook, and in the URL enter "https://texting.efkolos.com/ears/twilio.php" and make sure HTTP has "HTTP POST" selected and then hit the blue "Save Configuration" button.

  4. Next your going to need to visit the "General Message Settings" page by CLICKING HERE and you want to make sure that MMC Converter is set to enabled. This creates links for the other party to download attachments if they are too big or not of a valid file type according to Twilio's system. It's a very hand feature. SMS Pumping Protection is untested as of yet and costs money if you Enable it. For the purposes of the Texting App, its optional and you can safely leave it disabled. Set your HTTP Basic Authentication for media access to Disabled. Finally with Message records Data Access and Backup, we recommend leaving the default of 400 days, but of course this is optional for the Texting App to work.

  5. Finally, make sure you visit the Messaging -> Geo Permissions page by CLICKING HERE and you MUST select ONLY the US and Canada. If any other countries are selected it will break the Texting App GUI and it will not work. We will be building support in for other countries very soon.

Steps for Texting App Setup

  1. Activate your account. | After you sign up for service, check out, and successfully pay, with in 1 to 4 hours you'll receive an activation email with an activation URL in it. Open that in any browswer and then you'll want to use the activation screen to select a workspace name and password. Your initial username is formed automatically by using your first name and last name, taking out the space and making the first letter of your first name and last name lower case. So if you rname is John Smith your initial admin username for your workspace will be "johnsmith".

  2. Activate Twilio Link | Once you get logged in visit the Settings Page and scroll down until you find Twilio Settings. Once there, plug in your Twilio Account SID and Twilio Auth Token and click the "Test Twilio Link" button. If its successful it will return all the phone numbers under that account in the humber drop down list. Select the number you wish to text from. ( Optionally, you can set a prepend which adds what ever you put in the box in front of every outgoing text or an Auto-reply which automatically gets texted back to ALL incoming texts).

  3. Select Provider | Now that your Twilio account is linked visit your Workspace Page and select your provider to Twilio.