Request
Validate input and authenticate first.
An infrastructure guide
How SMS infrastructure works
Understand the journey from application to SMS gateway, operator and handset: acceptance, delivery receipts, message parts and delays before choosing a Jordan provider.
Submission
Route acceptance is not delivery.
Outcome
Correlate the receipt with its message.
Before the network
From business event to submission queue
Sending starts with an event such as order confirmation or sign-in. The application validates destination, template and contact purpose, then submits an authenticated request. Approval, scheduling or segmentation may precede submission. Keep an internal business reference even if connectivity fails.
Messages wait in a queue according to service settings and route limits. Campaign size and peak periods therefore affect waiting time. Plan time-sensitive OTP requirements separately from bulk campaigns.
From network to receipt
Why submission and delivery are different
The agreed route carries the submission to the network. Delivery depends on number validity, handset state, coverage and policy. A DLR reports the available status and can arrive late or more than once. Client systems reconcile by message reference and terminal state, not arrival order alone.
Delivered means that the route reported delivery, not that the recipient read the message. If an API request times out, check its status before resending to avoid duplicates. Integration documentation explains the available states and how to handle them.
Implementation steps
How we prepare and launch the service
We review the use case and requirements, then test the setup before production sending begins.
- 01Validate
Authentication, destination, template and reference.
- 02Prepare
Encoding, parts, queue and limits.
- 03Submit
Submit to the route under account settings.
- 04Reconcile
Store and correlate receipts without resending.
Information we need
Share these details for an accurate proposal
These details help us confirm pricing, requirements, and the right operating model from the first conversation.
- 01A sample without personal data
- 02Destinations and sender IDs
- 03Peak volume and submission window
- 04States your system needs
Frequently asked questions
Straight answers about the service
Does HTTP 200 prove delivery?+
No. Check the connector's documented response meaning and follow available delivery reporting. HTTP success alone is not a delivery state.
Is an Arabic message always one part?+
Not always. A short Arabic message typically fits 70 text units in one part. Longer messages usually allow 67 units per part. Some emoji use multiple units; the calculator helps estimate the total.
Related services