Questions, answered.
The basics of sending, integration, and message status in one place.
Can I send from the dashboard and the API?
Yes. Both are designed around the same organization, wallet, sender IDs, and message history.
Do I need a branded sender ID to start?
An available public sender may be used for some accounts and use cases. A custom sender ID needs approval before it can be used.
Does an accepted message mean it was delivered?
No. Acceptance means the upstream provider received the submission. A delivery receipt provides the later delivered or failed result.
What happens when my message is long?
A long message can be split into multiple SMS segments. Textly calculates the segment count and estimated charge before sending.
Can I schedule a campaign?
The dashboard and API are designed to support scheduled messages. Your workspace will show the scheduled time and current status.
Can I import contacts from a CSV file?
Yes. Import an existing contact list from a CSV file into your Textly workspace, organize recipients into groups, and select the right audience for a bulk SMS campaign.
How do I avoid duplicate API sends?
Send an Idempotency-Key header with a unique value for each request. Reuse the same key and payload when retrying after a timeout.
Need more technical detail? Explore the documentation →