About Text Messaging

 

 

 

 

LIMITATION: Before considering using H2OS text messaging please be advised that in order to send text messages from H2OS you will need to enter (1x) the recipients mobile telephone number and service provider (e.g. AT&T, Verizon, etc.)

 

 

 

 

 

 

 

A simple form of text messaging has been added to H2OS with build 11.40 in August, 2012.

 

Text messaging in H2OS is based on the use of a specific method to send text messages: the message is sent to the recipients cell phone carrier, formatted in such a way as to be interpreted as an SMS  (text) message

 

In order to send a text message, the recipient's mobile telephone number AND carrier name must be available, either in the customer (or other) record, or key-entered during the send text message process

 

An example of the email address used to send a text message is  5162732999@att.msg.  The telephone number must be exactly 10 characters (with hypens removed), and the carrier name must be valid.

 

On the Send SMS message screen (below), the CARRIER pulldown contains a list of known carrier names. If you have one or more carrier names that do not appear on this list, and have been tested okay, please provide them to us and we will add them to the list.

 

We are not aware at this time of any exceptions to the availability of the mobile carrier name information and the ability to send text messages using this method, but it is possible there are exceptions and it's also possible this method will not be available "forever".  Obviously, we have no control over the cell phone carriers and their methods, so we will make this method available to you for as long as it is available.

 

To the best of our knowledge, messages sent at this time are not charged to the sender, but the recipient is charged for each message received. This can change over time and is based on the carriers.

 

This example shows an employee name is selected using the EMPLOYEE pulldown menu, and the carrier name and mobile telephone number for the selected employee.

 

 

 

 

 

About how  text messaging works in H2OS

 

H2OS's text messaging takes advantage of a facility provided by most/all cell carriers for transmitting text messages via the carrier's SMTP (email) interface (which each carrier happens to have - which is opposed to sending the text message via the cellular network, which H2OS cannot reach (for free anyway, if it can at all, but I have to assume it's possible, but cellular and the Internet aren't the same technology (well, they actually are, but they are packaged and sold differently). When you send a text message from a cell phone, it's sent over the cell carriers network, but when H2OS sends a text message its sent over the Internet, not the target carrier's cell network (of course), so a 'bridge' is needed to get around this problem.

 

In more detail - the reason you can send me a text message from your cell phone to mine is that you're already logged onto a cellular network, and so am I, but H2OS is not, so it needs an alternative method (a bridge) to transmit to a cell phone, which is what we're doing, but it has the requirement that we know the recipient's cell carrier name as well as the cell telno.  

 

I imagine there are other ways of doing this now or will exist in the future, but I'd also expect such a service would not be free, i.e. a monthly bill, probably based on usage. So we may have a limitation, but it's better than not having the capability at all, simpler for us to provide and support, and probably avoids a monthly bill. 

 

Also note: the sender (operator) must have a valid email ID (registered in SETUP->OPTIONS->INTERNET) for sending email and text messages. Replies to text messages are sent to this email address as email format notes,

 

The recipient's Carrier and mobile TEL # are required (e.g. 5162732999@att.msg for this mobile number using AT&T).  The only way to get around this, as I understand it, is basically to pay for a service.  In fact there is money involved - the recipient (not the sender) pays for the message, at least that's what I've seen in doc so far.