It's ideal for asset tracking - you can fit a GPS fix, timestamp, and accuracy estimate (based on # of satellites visible) into 12 bytes, which is enough to ping once per minute and still only use half your allocated bandwidth. If your asset tags call in every 5 minutes or once per hour lots of options open up.
2 way communications aren't much more demanding because most of what you need can be done with lookup tables, and there aren't that many different commands you would need to send to an asset tag for local scanning. If you want to do person-to-person, 2 bytes per word is sufficient for a fairly large vocabulary (especially a tightly specified one like military brevity codes) - not exactly chatty but sufficient for many operational/emergency purposes.
2 way communications aren't much more demanding because most of what you need can be done with lookup tables, and there aren't that many different commands you would need to send to an asset tag for local scanning. If you want to do person-to-person, 2 bytes per word is sufficient for a fairly large vocabulary (especially a tightly specified one like military brevity codes) - not exactly chatty but sufficient for many operational/emergency purposes.