Planned timing
Send when the reminder is useful, rather than merely when it is convenient to produce.
SMS reminders
Send appointment reminders from the portal, or let a documented event in your booking system trigger SMS through the API. Pay only for the messages you send.
Send when the reminder is useful, rather than merely when it is convenient to produce.
Schedule manually in the portal, or connect delivery to an event in your system through the REST API.
State the time, place and expected action. Replies require a sender and receiving setup suited to the need.
Practical overview
A useful reminder helps someone arrive prepared, remember a deadline or find the right practical information. It should arrive early enough for the recipient to act and be concise enough for its purpose to be understood immediately.
In the portal, a member of staff can select recipients and schedule delivery. This suits manageable volumes or a list prepared as a batch. Through the SMS API, a booking or line-of-business system can ask Intellipush to send when a documented event occurs. Your system continues to own the business rule and timing.
Portal and API serve different working methods. Choose the portal for human-controlled scheduling, the API for automated workflows, or combine them where the organisation needs both.
Workflow
Build in control before a message leaves.
Decide what triggers the reminder, who should receive it and which system is the source of the time and contact details.
Consider whether SMS is the right channel and how long the recipient needs to confirm, change or cancel.
Include essential practical details but avoid sensitive information. Link to a secure signed-in service if more information is required.
Test with your own recipients and a low volume. Decide who responds to failures, replies and changes to the underlying appointment.
Responsible use
An appointment reminder is not automatically marketing. Assess the purpose and content, and do not hide promotional wording inside a practical message. Apply marketing rules where the message genuinely promotes a sale.
Telephone numbers, times and appointment details must be current. Establish a routine for wrong numbers, changed appointments and recipients who should no longer be contacted. The customer is the controller for its recipient data, while Intellipush normally processes that data on the customer’s behalf.
If recipients should be able to reply, decide how the response is received and who will handle it. Do not promise two-way dialogue until an appropriate setup has been selected.
Next steps
Product, preparation tools and pricing belong in the same decision.
See more working methods for alerts and practical messages.
Learn more →Plan events, authentication and technical failure handling.
Learn more →Check data and message length before the first delivery.
Learn more →Pay for usage
Cost depends on the length and content of the message, and the destination country. Current prices are shown in the portal.
Get started
Create an account for free and use the portal or API. Buy SMS credits when you are ready to send — with no monthly platform fee or lock-in.