Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • Long SMS Mode
  • Setup
  • SMS history
  • Replace non-GSM7-characters
  • How It Works
  • Benefits
  • Examples of Character Replacement
  • When to Use This Feature

Was this helpful?

  1. Portal
  2. Billing

SMS Credits

Last updated 1 month ago

Was this helpful?

In order to send SMS messages using the Rules Engine, you need SMS credits. You can buy prepaid bundles of SMS credits. If you send an SMS message, the credit will decrease accordingly.

Long SMS Mode

When you send an SMS message over 160 characters, the message will be split and result in multiple messages. You can choose if you want to truncate the message to 160 characters to make sure only at max one credit is deducted per message from your balance or if you always want to receive the full message which can result in multiple message credits being deducted.

The SMS standard says that large messages are segmented into 153 character segments and sent individually then rebuilt on the recipients device. This means that a 161 character message would result in two segments being deducted.

If you include non-GSM characters in your message, those messages have to be sent using the so-called UCS-2 encoding. Messages containing any non-GSM-character are limited to 70 characters. See a list of all GSM characters here:

Unfortunately, our beloved emojis are not part of the GSM character set. Messages containing emojis are thus limited to 70 characters 😭

Setup

In order to set up the truncation mode simply navigate into the billing section of your Datacake Workspace using the Side Bar.

In here you find the settings for truncation mode as shown on the above screenshot.

SMS history

You can see a list of the last up to 100 SMS messages including their segment count in the billing administration.

Replace non-GSM7-characters

The SMS Character Replacement feature automatically substitutes special characters, symbols, and accents with their standard alternatives to optimize your message delivery.

How It Works

When enabled, this feature replaces non-standard characters (such as emojis, accented letters, and special symbols) with their closest standard equivalents that conform to the GSM7 character set.

Benefits

  • Reduced Costs: Messages containing non-standard characters require more segments to send, increasing costs. By replacing these characters, your messages use fewer segments.

  • More Efficient Delivery: Standard GSM7 characters are more reliably delivered across all mobile networks.

  • Predictable Billing: Avoid unexpected increases in SMS segments due to special characters.

Examples of Character Replacement

Original character
Replaced with

ê, ë, ĕ

e

ħ

h

â„¢

(tm)

When to Use This Feature

Enable this option if:

  • You want to minimize SMS costs

  • Your messages frequently contain non-Latin characters, emojis, or special symbols

  • You prioritize delivery efficiency over exact character preservation

Leave it disabled if:

  • Exact character preservation is critical to your communication

  • Your brand identity requires specific symbols or characters

  • You communicate primarily in languages requiring non-GSM7 characters

https://en.wikipedia.org/wiki/GSM_03.38#GSM_7-bit_default_alphabet_and_extension_table_of_3GPP_TS_23.038_.2F_GSM_03.38
Character replace mode toggle