Select Page

Frequently Asked Questions

Legal Disclaimer: All the information provided in this document by Flimp Media, Inc. d/b/a Flimp Communications (“Flimp”) is intended only to guide and educate. Any and all information may be updated for accuracy at any time. The information provided does not cover all potential questions and answers nor provide complete details to make an informed decision to subscribe to Flimp’s WorkforceTXT™️ solution and associated products, services, and tools. For questions and more complete information about any aspect of WorkforceTXT, please contact a Flimp representative. This is not a sales document.

Platform Overview

What is WorkforceTXT™?

WorkforceTXT™️ is an easy-to-use text messaging platform available for Flimp Communications clients with options for Flimp Managed Campaigns, Annual Employer Self-Service Accounts, or the Multi-Tiered and Multi-Tenant Accounts for brokers, enrollers, or carriers.

Key Features:

  • Simple – Intuitive user interface and quick results
  • Compliant – HITRUST (The Health Information Trust Alliance) and HIPAA compliant
  • Trackable – Detailed reporting dashboard to view engagement metrics

Key Benefits:

  • High Engagement – Our text messaging solutions drive an average 95% employee engagement rate compared to open rates of 15-20% for traditional email communication
  • Accessible Information – As mobile smartphones become a part of everyday life, text messaging continues to become the preferred method of communication by employees 

Reliable Distribution – Internet isn’t required as text messages are delivered via mobile carrier networks (International text messaging is also available within specific countries)

Who Is It For?

Employers / Healthcare Brokers / Benefit Consultants – Employers, Brokers, and Benefit Consultant groups are constantly addressing the digital communication deficit and how to successfully communicate benefits information to clients and/or employees.

Platform Levels & Pricing

Managed Campaigns for Employers

Pricing*: $500 Annual Fee + $0.08 per SMS Text Message ($0.10 for MMS texts)

Flimp Communications allows employers to be completely hands-free of contact management, campaign creation, and message distribution while still having access to engagement metrics within the WorkforceTXT platform. After all service order estimates have been accepted, the intake process can be completed with text messages ready to be distributed within 24-48 hours.

Annual Employer Self-Service Accounts

Pricing*: $2,400 Annual Fee + $0.05 per Text Message + Complimentary 30,000 SMS Texts Messages ($0.10 for MMS texts)

Annual Employer Self-Service Account allows all authorized users under the account to manage administration, update contact information, create message campaigns, schedule message distribution, and have access to the metrics dashboard. After all service order estimates have been accepted, our team will create your account and schedule a demonstration of the platform. During this demonstration, we will cover all platform features, answer any questions, and introduce you to our dedicated technical support team for the WorkforceTXT platform. 

Multi-Tiered and Multi-Tenant Self-Service Platform License

Pricing*: Annual Fee + $0.04 per SMS Text Message

(Annual fee is TBD until scoping the project and needs are completed and $0.10 for MMS texts)

Multi-Tiered and Multi-Tenant Self-Service Platform License is ideal for large-scale employers, brokers, and enrollers that handle texting messaging and IVR campaigns for clients. The Multi-Tiered and Multi-Tenant system allows a limitless business-to-business relationship to be established with the primary account administration operationally managing all accounts. After all service order estimates have been accepted, our team will create the primary account, schedule an initial demonstration, and give the option for an additional demonstration for any potential users of the platform (clients, regional offices, etc.). During these demonstrations, we will cover all platform features, answer questions, and record each training while providing you with support to further your team’s familiarization with the WorkforceTXT platform.

* For foreign-language translation services contact your account manager for pricing.

Compliance

Clarifying Key Points:

We are not lawyers nor do we provide legal advice.

This is a very complex and regulated field of digital communication.

Our intention is to help you understand the basics of compliance and regulations.

When in doubt, speak with your organization’s or legal team or consult outside legal counsel.

Links for Regulation and Compliance

Mobile communication is a complex and regulated field. Most compliance is based on protecting people against unwanted calls or messages from unsolicited sources. Included below are links for regulation and compliance reference:

Is an Employer Allowed to Text Their Employees?
  1. Texting employees is not considered “Commercial” texting
  2. Federal and State-by-State text regulations are intended to cover and protect people from “Commercial” texting and its abuse therein
  3. Flimp Communications WorkforceTXT texting solution used by an employer to text their employee(s) falls under the below allowable rules and is not considered “Commercial” texting under BOTH: 1. the Federal Communications Commission (FCC) – CAN-SPAM Act of 2003 and 2. the Telephone Consumer Protection Act (TCPA), passed by the USA Congress in 1991 and State-by-State follow-on regulations since that time. Allowable rules for employer to text their employees:
Implied vs. Explicit Consent
  1. Individuals who wish to receive your scheduled messages must give implied or explicit consent.

    1. Implied Consent
    • Implied Consent is an established relationship between an employee and employer. Upon accepting a role within an organization, an employee will either willingly provide or not provide their employer with their phone number, while under the impression of future communication between both parties.
    • Initial Warning Message – Our product team suggests when sending your first text message, that your initial message includes the option to “Opt-Out”. Example: “Reply STOP to Opt-Out. HELP for more info”
    1. Explicit Consent
    • In any instance where employees are signing a document in which they agree to be contacted by their employer via phone or text message.
    • Optional “Opt-In” Campaign – In this scenario, the text message recipients who choose to receive messages from the WorkforceTXT platform must take the call to action and send a specific keyword to the correct short-code (5 Digit Number) to “Opt-In” and receive any further text messages.
      • We see significantly lower engagement rates with this option.

    Here’s a quick summary overview we wrote for legal, compliance, and security teams that might also be helpful to consider: Can You Text Your Employees? A Quick 101 on SMS Rules

Short Codes

What Is a Short Code?

A short code is a unique 5-digit or 6-digit phone number used by organizations as a secure two-way communication method when text messages are being sent at scale. A short code is important when distributing any text message campaign for both security and recognition purposes. These 5-digit and 6-digit numbers are licensed, regulated, and follow compliance with the Telephone Consumer Protection Act (TCPA), Cellular Telecommunications Industry Association (CTIA), Federal Communications Commission (FCC), and other mobile communication authorities.

Short code numbers offer the fastest possible send speeds, up to 1,000,000 mph (messages per hour). They’re great for organizations with sizable opt-in lists or campaigns that are planning large-scale engagement. With being shorter than a usual long-digit phone number they offer the chance to be more memorable, the best options for branding, and are also more trusted among individuals that are receiving messages from these 5 or 6-digit numbers.

Short Code: Verification Time Period

Short Code applications are reviewed and approved by each carrier on a specific step-by-step basis. Plan ahead for a 3-5 week processing time before your number is verified, licensed, and ready to use for distribution.

Short code: Estimated Cost
  1. In the United States, short codes can be leased for 3, 6, or 12-month terms. Dedicated Short Codes cost up to $2,500 a month. Short Codes are a limited resource. As more Short Codes are created and leased, the more the price increases.

10 Digit Long Codes (10DLC)

What is a 10DLC?

A 10 Digit Long Code, or a “10DLC”, is a 10-digit phone number used by smaller organizations as an alternative option to using a licensed Short Code. These 10-digit numbers are very limited to being secure during distribution while also having a less confident recognition process when being sent from an employer to an employee. In comparison to the regulations and compliance standards that surround Short Codes, the requirements and setting of SMS best practices for 10 digit numbers are still in the beginning stages of implementation. As more major carriers begin to support application-to-person distribution (A2P) for 10DLCs, new guidelines and fees are being created to try and contain the abuse of text messaging while protecting consumers.

10 Digit Long Code numbers have much slower send speeds, about 36,000 mph (messages per hour). This type of text message communication is better for smaller organizations with the need to only contact a small list of contacts. Carriers such as AT&T, T-Mobile, and Verizon will be the ones to ultimately determine your organization’s campaign’s send speeds. Along with this sense of throttling distribution performance, the capabilities of 10DLC phone numbers also depend on which mobile carriers your recipients use.

10DLC: Verification Time Period

10 Digit Long Codes are typically registered and created on a by need basis. This process usually takes about 3-5 business days. Afterwards, you can expect to be able to distribute text messages in about 5-7 business days. With this being said, new compliance is being released by the TCR which now requires additional details for existing registrations and implemented new limits on organizations entering the text messaging world.

10 DLC: Estimated Cost
In the United States, 10DLCs come with two categories of costs. Registration fees and Per-Message carrier fees. Both fees differ by carrier. Due to this, prices and fees may vary while depending on the volume of message distribution.

Application-to-Person Messaging (A2P)

A2P SMS

Application-to-Person messaging (A2P) is any kind of text message traffic in which a person is receiving messages from an application (WorkforceTXT) rather than receiving messages from another individual or device. These applications are used in the anticipation of not replying to a message sent from the recipient. A2P messaging can include, but is not limited to, any and all marketing communications, appointment reminders, chat bots, notifications, and any one-time passwords (OTPs) or PIN codes. Wireless carriers treat A2P and Person-to-Person (P2P) traffic differently in terms of the type and volume of traffic that they allow. It is important to understand your use case so you can use the correct tools, such as verified phone numbers, licensed short codes, or a registered Alphanumeric Sender ID.

Carriers in the US and Canada have a strict interpretation of A2P, and consider all messaging that passes through WorkforceTXT — or other messaging application platforms — to be A2P.

Person-to-Person Messaging (P2P)

P2P SMS

Person-to-Person messaging (P2P) is any kind of text message traffic in which two or more people communicate over text messaging. For example, when you send a text message from your phone to another person’s phone. Under some circumstances, this may also include traffic that goes through an API to connect two people, however some countries (including the US and Canada) do not consider any application-mediated traffic to be P2P. Wireless carriers treat P2P and A2P traffic differently in terms of the type and volume of traffic that they allow. It is important to understand your use case so you can use the correct tools, such as verified phone numbers, licensed short codes, or a registered Alphanumeric Sender ID.

Carriers in the US and Canada have a strict interpretation of P2P. All messaging that passes through WorkforceTXT is considered to be A2P and not P2P.

Implementation, Subscription Agreements, & Legal Guidance

Do I Need to Sign a Contract?

Flimp Communications does not require clients to execute a contract to use our WorkforceTXT solution. However, we do have a contract to execute, as may be required, because we realize that some clients and their legal, compliance, and procurements teams do require a contract to ensure that both Flimp, the supplier of WorkforceTXT, and the client sending text messages to their employees and contacts (defined as the “end-client”) are both in accord as to its use and ensuring all parties associated are in compliance at all times with both CTIA’s “Messaging Principles and Best Practices” and the Telephone Consumer Protection Act (TCPA) and only implement and use WorkforceTXT and the associated services for end-client, approved communications.

NOTE: If a contract is required then only the end-client may execute it with Flimp, not an intermediary acting on behalf of an end-client. If applicable, please contact your account manager to review our “WorkforceTXT™ Messaging Subscription Agreement”.

Is a Flimp Communications Service Order Needed to Begin Using WorkforceTXT?

Yes, before moving forward with the set-up of and use of the WorkforceTXT solution (the “Project”) the client using WorkforceTXT must agree to a Flimp Communications Service Order (“SO”). Our SO acts similarly to an SOW (Statement of Work) where we include all details that may be required by your team. To make it easier to review, edit as necessary, and approve the SO, a Flimp Communications Account Manager sends you the SO accessible via an online link that will update in real-time with edits and directions to approve and accept the SO. Once the SO is officially “accepted”, we can start the Project and will send an associated invoice to the entity paying, which might be the client, carrier, or an associated broker or consultant of the client using the WorkforceTXT solution.

Is there a Flimp Communications Contact Available for Further Contractual Questions?

Yes, your Account Manager will put your team in touch with our EVP and Head of Legal & Compliance to answer any questions and updates to the agreement, as may be required, to ensure we are in accord with your legal, compliance, and procurement teams. We respond to all inquiries and strive to come to an agreement that satisfies both parties within 24-48 hours.

Disclaimer to all legal-related answers below:

Flimp Media, Inc. d/b/a Flimp Communications (“Flimp”) and our employees are not lawyers and in answering these questions we are NOT providing legal advice that is binding or accurate. Rather we are providing our basic understanding of laws, which can vary from US state to US state, and NOT providing legal interpretation of the laws or laws that govern texting by employers to employees. Therefore, if you have questions about the legal use of texting by employers to their employees you must consult a legal professional to ensure you get the exact legal position. Flimp’s answers to the following questions are to provide guidance only on Flimp’s understanding of how employers can and should text their employees.

Are employers legally allowed to send mobile text messages to employees after working hours?

Currently, in the United States (Europe and Canada are more strict), it is legal to text your employees – both “exempt” and “non-exempt” – after hours for employer communications on benefits, important events, emergencies, and more related to work that would help the employee, including information regarding open enrollment deadlines. As long as the text does not require or ask a non-exempt employee to take immediate action or perform tasks outside of their normal working hours (see example below) and is informational, there is no violation within the Fair Labor Standards Act (“FLSA”) guidance. For exempt employees, we believe that an employer can text their employees anytime an employer desires and that there are no issues if asking exempt employees to take immediate action or if just informational; it’s up to the exempt employee to manage expectations and to take immediate action or not. Here is a helpful website explaining this: https://www.textline.com/blog/texting-employees-off-the-clock

Unless you operate in one of the few countries that have already made it illegal, you can text your employees during, before, and after business hours. But before you do, a note of caution and we suggest doing this as part of your business best practices: text your employees after “working hours” only in an emergency or to provide critical information to make their lives easier, better, and fun. A good rule of thumb for managers sending texts; put yourself in your employee’s shoes for a moment and ask yourself: “Does an employee need to receive a text message after their designated working hours unless it’s an emergency? Can my non-emergency text messages wait to be sent during “normal working hours”?

  • Examples: Texting Non-Exempt Employee vs. Exempt Employee

    1. Non-Exempt Employee: If a text message requires a “non-exempt employee”, defined as an hourly employee with a maximum work week of 40 hours with at least minimum wage payment and eligible for overtime pay, to work beyond their regular rate for time worked of over 40 hours in a workweek, if that is their arrangement with their employer, then compensation may be required. FLSA mandates that employers pay non-exempt employees for all overtime they work. This includes time spent responding to e-mails, texts, and voicemails. An emergency help text should not be an issue.
    2. Exempt Employee: If a text message requires an “exempt employee”, defined as salaried and not eligible for overtime pay, to work beyond their normal work day hours defined with their employer there should be no issues as it is up to the employee if and when they want to reply or not to the text message received. Note – laws are murky because the FLSA does not define full-time employment or part-time employment clearly. This is a matter generally to be determined by the employer and the agreed hours defining a “full work week” with their exempt employee. More can be found on the US Department of Labor website related to FLSA here: https://www.dol.gov/agencies/whd/flsa/faq

 

Does Flimp Communications sell or release any phone numbers which are provided and captured during the mobile communication process to any other entity?

Users of Flimp Communications Products, Solutions, and Services will never be asked for or be allowed to enter information considered PII, PHI, or HIPAA-related. However, pursuant to the use of Flimp’s WorkforceTXT® Employee-Texting Solution, if a client chooses to use this solution, a person’s/employee’s mobile phone number is provided by the client to Flimp and used only within the solution to send out text messages on behalf of the Flimp clients and ONLY AFTER the client provides the mobile phone numbers (not names or email addresses or any other identifiers) and permission to Flimp to send text messages on behalf of the client to the provided mobile phone number(s).

These mobile phone numbers are considered PII and because of this are used for no other purpose but to provide the client with options to text employees their own client-configured messages via Flimp’s WorkforceTXT® Employee-Texting Solution, which is both HITRUST and HIPAA compliant and PEN tested annually. Flimp never uses, stores, accesses, sells/re-sells, markets, shares, or contacts the mobile phone numbers provided by clients and these mobile phone numbers are solely used on behalf of the client choosing Flimp’s WorkforceTXT® Employee-Texting Solution to send text messages. We only upload these phone numbers via a csv/excel/similar file provided by the OPPD HR team into the WorkforceTXT® Employee-Texting Solution and do not use them for any other purposes but to text OPPD HR team-approved texts. The phone numbers are secure and the associated files can be deleted anytime per client request and/or upon the termination of using the solution; we only keep the files containing mobile phone numbers on file pursuant to managing the OPPD HR team’s instructions, requests, and to ensure we keep proper records of past texting campaigns for compliance reasons. Moreover, all text messages themselves include an opt-out option for compliance reasons.

Furthermore, as noted the WorkforceTXT platform is both HIPAA compliant and HITRUST certified and PEN tested annually. In order to retain our HITRUST certification, our platform is required to stay up-to-date with the latest security and privacy standards to ensure that sensitive data is effectively and efficiently safeguarded. This certification requires Flimp Communications to follow guidelines in coordination with and beyond regulations set forth by the Telephone Consumer Protection Act (TCPA), Cellular Telecommunications Industry Association (CTIA), Federal Communications Commission (FCC), and other mobile communication authorities including the annual PEN test.

 

Are there unique and/or Washington, USA, state-based rules/regulations regarding employers sending text messages to their employees beyond what is covered under Telephone Consumer Protection Act (TCPA), passed by the US Congress in 1991?

Yes, in addition to the federal TCPA act referenced herein, the State of Washington has this follow-on law for more clarity and specific rules: Law: “RCW 19.190.060 – Commercial electronic text message—Prohibition on initiation or assistance—Violation of consumer protection act” – https://app.leg.wa.gov/rcw/default.aspx?cite=19.190.060

Important Take-Aways

  1. This law was written to take into consideration “Commercial” texting and in Flimp Communications’ opinion would not apply to an employer texting their employees for the aforementioned reasons stated per “Is an employer allowed to text their employee”?
  2. Critical language to clarify and reinforce our understanding of the State of Washington law is this language from the law as written: “The legislature intents [intends] to limit the practice of sending unsolicited commercial text messages to [a] cellular telephone or pager numbers in Washington.”

 

Are there unique and/or California, USA, state rules/regulations regarding employers sending text messages to their employees beyond what is covered under Telephone Consumer Protection Act (TCPA), passed by the US Congress in 1991?

Yes, in addition to the federal TCPA act referenced herein, the State of California uses as its basis to govern texting the same rules from TCPA.

SPECIAL NOTE: While, California in 2022 did enact the California Consumer Privacy Act (CCPA), which oversees consumer privacy and protections in general to cover all types of information related to a “person”, whereby under CCPA, California customers have the right to request a report on the personal information (mobile phone number included) a company has on them and a list of other companies it’s shared that data between, CCPA is intended to cover “commercial/marketing” type of texts.

Key Take-Aways from the law:

  1. This CCPA law is intended to protect people from marketers/spammers/unwanted commercial texts and NOT an employer texting their employees
  2. To comply with CCPA, SMS marketers must inform California customers about the personal information they are collecting, provide an option to request data access, update privacy policies with California rights, and offer opt-out methods. Marketers must not send an opt-in request for at least 12 months if a customer opts out of the text messaging program.

Relevant Links to Review:

  1. S.1462 – Telephone Consumer Protection Act of 1991 from Congress (TCPA) – https://www.congress.gov/bill/102nd-congress/senate-bill/1462
  2. Federal Communications Commission (FCC) – CAN-SPAM Act of 2003: Unwanted Commercial Electronic Mail – https://www.fcc.gov/general/can-spam
  3. Federal Communications Commission (FCC) – “FCC Actions on Robocalls, Telemarketing” – https://www.fcc.gov/general/telemarketing-and-robocalls
  4. State of Washington – “RCW 19.190.060 – Commercial electronic text message—Prohibition on initiation or assistance—Violation of consumer protection act” – https://app.leg.wa.gov/rcw/default.aspx
  5. California Consumer Privacy Act (CCPA) – State of California Department of Justice – https://oag.ca.gov/privacy/ccpa

WorkforceTXT: Getting Started

What Are The First Steps In Using the Platform?

The first steps in using WorkforceTXT will depend on which licensing option is chosen through WorkforceTXT. Our Flimp Communications support team for WorkforceTXT will require specific information for this implementation process.

Flimp Communications Managed Campaign

  1. Contacts: Our team will request all contact phone numbers to be populated in a CSV file, which we will initially provide during the intake process.
  2. Text Message Content: Our team will request a 160-character count message that is considered to be an SMS or MMS. The character count limit for a single text is 160 characters. Anything that exceeds this limit will be considered 2+ segments.
  3. Distribution Specifics: Our team will request the specific date(s) and time(s) for which each separate message is to be sent. A specific time zone will be required as well.
  4. Optional Media: It is optional to include any working website URL can be inserted into texting but be aware that we must receive the full URL before shortening it. This URL can be a Flimp Communications-created live page or any specific URL of your choosing.

Annual Self Service Account & Annual Multi-Tenant Accounts

  1. Implementation: Our team will request new user information prior to the respective account becoming operational. The information needed would include the Users First Name, Users Email Address, and the desired 8 character first time password.
  2. Platform Training: Our team will schedule and provide step-by-step training for any number of attendees which will cover the entire WorkforceTXT platform. This training is able to be recorded and broken into separate segments if the situation permits.
  3. Collateral Exchange: Our team will follow up the Platform Training with all collateral created for processes to perform certain tasks within the WorkforceTXT tool.
  4. Support: Our team is dedicated to specific needs through the process of implementing our communication tools and methods. If there are any particulars needed which are not already provided by Flimp Communications, a request for those materials can be made.

WorkforceTXT Collateral

WorkforceTXT: Capabilities

What Capabilities & Features Does the WorkforceTXT Platform Include?
  • Dashboard:
    • Metric Reporting
      • Attempted Messages, Delivered Messages, Error Messages, Received Responses, Scheduled Messages, Undelivered Messages 
    • Consent Management / Engagement Rate
      • Total Contacts Opted-In (95% avg) vs. Total Contacts Opted-Out (5% avg)

✶ Additional Reporting is available when using media created by Flimp Communications including views, touches, time spent on content, device type used to view, response rates, etc…

  • Admin Administration / Tenant Administration:
    • Tenant Management
      • User Management: Activate, Deactivate, Password Creation, Login Stats
      • Tenant Tiering Management: Activate, Deactivate, Tenant Specific Metrics
  • Contact Management:
    • Contact Book
      • Group Creation, Sub-Group Creation, Contact Card Details (First Name, Last Name, Phone Number, Email Address, Group Membership/Identifier, Consent Management, Contact Status), Single Contact Upload, Multiple Contact Upload, CSV File Download, Excel Export Customized Census
  • Campaign / Message Management:
    • Campaign Creation
      • Campaign Creation Template Assistance (Naming, Character Count, GSM Encoding Tool, Keyword Response Tool, Consent Management Response Tool, First Name Personalization Tool)
      • Keyword Response Campaigns, Chain / Tree Response Campaigns 
    • Short Link Manager
      • Redirect Link Manager (This tool will redirect and shorten your original URL’s to be used effectively in text messaging by reducing character count. Using branded links will also enhance your campaign’s visibility and reach by deterring carrier network filtering)
      • Campaign Trigger Link Manager (This tool will trigger the delivery of a campaign text message when a recipient clicks or navigates to the URL link. This is ideal whenever you have a list of phone numbers and want to provide a unique URL link to capture text consent via an email)
  • Distribution Management:
    • Delivery Date Selection (Real Time vs. Future Scheduling), Recipient Selection (Single Number, Contact Group, Contact Field Match), Campaign / Message Selection, Short Code Identifier, Time Zone Identifier, Verification Message

WorkforceTXT: General Questions

What’s the Difference Between Attempted Messages vs. Delivered Messages?
  • Attempted Message – Any outbound text message that is successfully sent from the WorkforceTXT platform in anticipation of reaching any one or multiple contacts.
  • Delivered Message – Any outbound text message that has been successfully delivered to a phone number and verified as “received” from a carrier produced “received receipt”.
What is an Error Message?
  • Any text message that has been classified as an “Error” is a message that…

    • Has been sent to a landline and deemed undeliverable.
    • Has successfully reached a contacts cell phone that has service through a carrier who does not provide “received receipts” for Application-to-Person delivery systems (this often happens with pre-paid phones and smaller carriers on unrecognized networks).
    • Has unsuccessfully reached a contacts cell phone. If this happens, once the contacts phone is turned on and the text message is delivered, the categorized “Error” message will be transferred from the “Error” classification to the “Delivered” classification.
    • Has unsuccessfully reached a contacts cell phone due to the phone number no longer being in service. We currently do not have systems available to pre-verify whether a phone number is in service or disconnected prior to attempting to send a text message.

What if our organization does not want to respond to any Received Messages?
Users do not have to respond to any received messages sent to the WorkforceTXT platform. In order to abide by compliance and regulatory requirements set forth by the CTIA, we must allow recipients to reply with “STOP” to opt-out or “HELP” for more info. All inbound text messages will populate in the “Received” metric organizer which may include a text message with information that is not “STOP” or “HELP”. In this case, users have the option to ignore that specific response, reply to that specific contact response with the WorkforceTXT platform, or utilize other tools outside of the workforceTXT platform to communicate with that contact specifically.
Is the WorkforceTXT Platform Able to Schedule Multiple Messages Ahead of Time?

Users are able to schedule as many text messages ahead of time as needed. After scheduling a message to be sent on a specific date and at a specific time, users can view their scheduled messages by clicking on the “Scheduled” metric organizer tile in the Dashboard. While viewing  the messages in the “Scheduled” metric organizer, users are able to view scheduled messages by customizing the date range and clicking “Refresh” on the left hand side of the platform.

If I have messages scheduled ahead of time, will WorkforceTXT remind me about them?

WorkforceTXT will deliver an automatic email notification to the user who scheduled a message the day before that specific text message is to be sent. This email notification will come from the noreply@workforcetxt.net email domain and contain the delivery date, delivery time, campaign title, assigned contact group, and the number of contacts within that group.

What is the “Undelivered” Metric Classification?

Flimp Communications successfully has licensed and taken ownership of a verified Short Code from the U.S. Short Code Administration. With this licensing, we have overcome the possible instance of any message being sent from the WorkforceTXT platform being identified as spam. When sending a mass amount of text messages from an A2P or P2P 10-digit long code or any other singular cellular device, there is a high chance that carriers such as AT&T, T-Mobile, or Verizon, will automatically identify those messages as spam since the messages are not being sent from a licensed and verified Short Code from an A2P application such as WorkforceTXT.

Why does Consent Management not match up with my current Contact List Consent?

Consent Management, which contains both the metric organizers that display “Total Opted In” and “Total Opted Out” can be misunderstood when using Implied Consent and Explicit Consent (Implied Consent vs. Explicit Consent: Page 4). These two metric organizers will only display the Explicit Consent within the contact library for both Opted-In and Opted-Out contacts. When initially using Implied Consent, there will be an aggregate of “0” in these metric organizers as a user begins to message all contacts using Implied Consent. If a recipient does Opt-Out, the “Total Opted Out” metric organizer will then begin to populate as those who Opt-Out are now explicitly denying consent to contact them by text message. The “Total Opted In” metric organizer will populate if using an “Opt-In Campaign ” in which users use Keywords to Opt-In.

Glossary

Common Texting Phrases/Terms + Definition:
  • Alphanumeric Sender ID – An Alphanumeric Sender ID is your company name or brand name used as the Sender ID in one-way SMS messages sent to supported countries. An Alphanumeric Sender ID may be up to 11 characters long. Accepted characters include both upper- and lower-case Ascii letters, the digits 0 through 9, and the space character. They may not be only numerals.
  • API – An Application Programming Interface (API) is provided by a service owner so that others may use the features and functions enabled by the service. APIs describe how a consumer will make requests of the service, and what they will receive in return.
  • API Key – An Application Programming Interface (API) Key is a unique identifier that is used to authenticate a developer or program to an API.
  • Application – An Application, often shortened to ‘app’, is a program, or set of programs, that allows end-users to perform particular functions. For example, ecommerce companies provide applications to customers to facilitate purchases and services.
  • Application-to-Person Messaging – Application-to-Person messaging (A2P) is any kind of message traffic in which a person is receiving messages from an application rather than another individual, and which is not expected to receive a reply. A2P message includes, but is not limited to, marketing communications, appointment reminders, chat bots, notifications, and one-time passwords (OTPs) or PIN codes.
  • Campaign – Text campaigns are campaigns sent via text message or short message service (SMS). Text campaigns rely on SMS messages to send information directly to end users mobile devices.
  • Click-to-Call – Click-to-call, sometimes called click-to-talk or click-to-dial, is a way to let people connect with a company by phone when receiving a text message.
  • CTIA – Cellular Telephone Industries Association (Carrier enforcement).
  • Custom Field – A custom field is a database field that is created to allow for data to be appended to an email or cell phone number record. Defining the field allows for the database to be customized for data collection or integration with other systems.
  • Dedicated Short Code – A “dedicated” short code is a short code that is managed by a provider that is leased from the Common Short Code Administration for dedicated uses by a brand or company.
  • GSM Encoding – A character encoding standard most commonly used with letters and numbers. GSM-7 encoded SMS messages can carry up to 160 characters.
  • Keyword – Keywords are typically 2-10 characters without spaces that are texted-in by an end user to opt in to a Short Code program or to receive a response.
  • Long Code – A long code number is a standard phone number used to send and receive voice calls and SMS messages. Phone numbers are typically called “long codes” (10-digit numbers) when comparing them with SMS short codes (5-6 digit numbers).
  • MMS – Short for Multimedia Messaging Service, is a standard way to send multimedia such as pictures, videos, and other attachments over text messaging channels.
  • Opt-In – The end user action of giving “express written consent” to a brand or company to receive SMS messages utilizing a method compliant with current best practices, carrier guidelines and the Telephone Consumer Protection Act (TCPA). Typically this is done by the end user initiating a keyword text-in to a short code and replying “YES” to a compliant opt-in message.
  • Opt-Out – The end user action of revoking consent from a brand or company to receive SMS messages. Typically this is done by the end user initiating a keyword text-in to a short code with the word “STOP”.
  • Person-to-Person Messaging – When two or more people communicate over text messaging. For example, when you send a text message from your phone to another person’s phone, that’s P2P. Under some circumstances, this may also include traffic that goes through an API to connect two people, however some countries (including the US and Canada) do not consider any application-mediated traffic to be P2P.
  • Personally Identifiable Information (PII) – Personally Identifiable Information, or personal data, is data that corresponds to a single person. PII might be a phone number, national ID number, email address, or any data that can be used, either on its own or with any other information, to contact, identify, or locate a person.
  • Platform – A platform is any combination of hardware and software used as a foundation upon which applications, services, processes, or other technologies are built, hosted, and/or run. Platforms offer the ability to build within an existing technical framework, decreasing both development time and cost.
  • Push Notification – A push notification (also known as a server push notification) is the delivery of information to a computing device from an application server where the request for the transaction is initiated by the server rather than by an explicit request from the client. While ‘push notification’ is most often used to refer to notifications on mobile devices, web applications also leverage this technology.
  • Short Code – A short code is a special telephone number designed for high-throughput, two-way messaging. Short codes are used to send and receive SMS and MMS messages to and from mobile phones.
  • SMS – SMS stands for Short Message Service and is another name for a text message. An SMS is generally sent from one mobile device to another over the cellular network. SMS is a text-only standard first formalized in 1985 in the Global System for Mobile Communications (GSM) standards.
  • SMS Character Limit – A single SMS message technically supports up to 160 characters, or up to 70 if the message contains one or more Unicode characters (such as emoji or Chinese characters). However, modern phones and mobile networks support message concatenation, which enables longer messages to be sent. Messages longer than 160 characters are automatically split into parts (called “segments”) and then re-assembled when they are received. Message concatenation allows you to send long SMS messages, but this increases your per-message cost, because SMS are billed per segment. The 160-character limit is for messages encoded using the GSM-7 character set. Messages not encoded with GSM-7 are limited to 70 characters.
  • SMS Delivery – SMS Delivery is a measure of the percentage of outgoing SMS and MMS messages which are received at their intended destination.  While sometimes referring to the status of a single message, SMS delivery usually is a rate of delivered versus intended messages and summarized as an ‘SMS Delivery Rate.’
  • SMS Gateway – An SMS Gateway enables a computer to send and receive SMS text messages to and from a SMS capable device over the global telecommunications network (normally to a mobile phone). The SMS Gateway translates the message sent, and makes it compatible for delivery over the network to be able to reach the recipient.
  • SMS Notification – SMS Notifications are out-of-band text messages sent in response to events or transactions which occur somewhere else. While often used as a marketing tool to increase the percentage of returning visitors, SMS notifications are very useful for organization and public safety purposes as well.
  • String Identifier (ISD) – A unique key used to identify specific resources.
  • Subscriber – A recipient of email and/or SMS/MMS text messages.
  • Tenant – Within the WorkforceTXT Portal, an individual user may be managing one or several brands, creating different tiered accounts called “Tenants”.
  • Unicode – An international character encoding standard that provides a unique number for every character across languages and scripts, making almost all characters accessible across platforms, programs, and devices.
  • User – A user is a person who has account credentials to access the WorkforceTXT platform for one or multiple tenants within a specific account. 
  • Virtual SMS – Virtual SMS enables you to send and receive SMS text messages over the internet without having to use a physical phone. This is especially useful when you want to use software to communicate with telephone networks that would be impossible on a physical phone.
  • Webhook – Webhooks are user-defined HTTP callbacks. They are triggered by some event in a web application and can facilitate integrating different applications or third-party APIs