Setting up your SMS provider
Connect SparrowSMS or a custom gateway, set your sender ID, and turn on dispatch.
Updated
To send SMS from Rentrovia, configure a provider under Settings → SMS Provider. Without a ready provider, messages are logged but not delivered.
Before you start
You need the CRM SMS module on your plan. Demo workspaces cannot use SMS.
Only users with permission to edit role settings can save provider changes. Viewing the page needs View SMS templates & logs.
Choose a provider
Open Settings → SMS Provider. Pick one of three options:
- Console (dev / no-op) — writes to server logs only. Useful for testing.
- SparrowSMS — paste your API token from the SparrowSMS dashboard.
- Custom HTTP — any HTTPS endpoint with headers and a body template.
Enter your Sender ID. This is what recipients see. SparrowSMS requires an approved sender for your account.
SparrowSMS setup
Paste your token in API token. Leave the field blank to keep a stored token. Use Clear stored token to remove it.
The SMS credits card shows your Sparrow balance when a token is saved. Click refresh to update it.
Custom HTTP setup
Set Endpoint URL (HTTPS only), Method, and optional Headers.
Write a Body template using placeholders like {{to}}, {{body}}, and {{from}}. Add Enc or Json suffixes for encoded values inside JSON bodies.
Header values are never shown back after saving. Re-enter them when you update settings.
Enable dispatch
Turn on Enable SMS dispatch. This is the master switch for real delivery.
Check the status badge:
- Ready — SMS will reach recipients through this provider.
- Not ready — messages are logged only until configuration is complete.
Click Save changes. Rentrovia confirms with SMS provider updated.
What Console mode is for
Console is safe for staging. Switch to SparrowSMS or Custom HTTP before going live.
Next: turn on automated triggers under automated booking and expiry SMS, or edit wording in SMS templates and variables.
Your workspace Contact phone from setup is used when owner alerts have no override.
