Have something to say?
execute ussd codes remotely
Something like: #144* 38 * customer number *amount#, for mobile phone credit top-up
Make Delivery Reports Optional
Some countries charge users extra for deliver reports. Add the ability for httpSMS to send messages without requesting for delivery reports back.
Reprocess expired messages
Reprocessing expired messages in bulk is essential, as queued messages can time out. An option to requeue them via HTTP API would be fantastic. Currently, this option can only be done manually and one at a time.
New Word Needed to Send sms
Can you guys add the word “Activate” to the set of words someone can send with sms ? Thanks
Automatic SMS reply
It would be very very beneficial if I could choose an SMS text to automatically reply with if someone messages my phone number. Bonus: Choose some regex when to (or not to) automatically reply, for example when the user just likes the message and I get the SMS text “xxx liked your message…” I don’t want to auto-reply
Contacts support
Thanks for your amazing work on this. It's very welll documented and easy to use. Would be a good addition if we can add contact name to each number. This will make it easy to chat with existing customers in the Web UI. Ability to add and update fields like first name, last name, email to the contact If those fields are not possible just an extra name field should be great!
Bulk Delete Threads from the Web App
For those who have enabled incoming messages, I don't like to see the list of threads in the web app that are mostly from spam numbers., So, there should be an option to bulk select and delete the threads. Right now, have to delete one by one which is time consuming.
API Development
It would be useful to build integrations for 3rd party software like CRM and other tools, for now the API is very much MVP. Future development could consider the following: API key verification (Simple /hello endpoint that would reply 2XX if key is valid, 4XX if API key is wrong) Creating webhooks via API calls (often required when integrating with CRM or automation platforms like Make.com / Zapier) Bulk Campaigns via API with support to distribute the queue between multiple SIM/numbers (specify array of phone numbers in "from" field). Personalization of messages with %tokens%. Endpoint to list all available/online SIM/numbers. The list would probably go on, but these would be some of the bare basics to get started with integrations which are crucial for any successful service nowadays.
Queue Scheduling (Business Hours)
Allow setting up schedules for SMS queue processing. @Different SMS queues with different priorities should also be considered, basically it could be simple as "transactional" and "promotional" queues. Where transactional is always highest priority and processed all times 24/7/365. Where as promotional queue could be processed as set schedule, for example 9am to 8pm, weekdays mon-fri. Schedules should be configured on queue/number level, depending how queues would be configured.
USSD code support (call forwarding)
Would be great to have option to remotely change call forwarding settings by issuing USSD codes on gateway devices.
Blacklisting (manual + via API + keyword)
Option to blacklist number to avoid ever sending (bulk) messages to that number. This could be done through contact editor, in the thread, via simple API call or by monitoring predefined keywords such as "STOP" or "DND" in incoming messages. Blacklisting would ensure outdated CSV/Excel lists won't bother customers.
MMS Support
Support for multimedia messages to gain support for images, videos and vcf files.
Contacts API / Simple CRM
A basic CRM style contacts feature would be useful to keep bulk lists updated all times via API. Tagging users to groups could be used to split contacts into segments (different bulk sms lists, events, customer segments). API could be used to create/update/delete or mark contact as "blacklisted" to avoid ever sending SMS to that number. Support for custom fields would be great for personalization. These contact lists could be used to send out bulk SMS campaigns in few clicks. Added bonus, have message history displayed for each contact (perhaps linking to contact thread).
Send a webhook when phone goes offline and when comes back online (after it being offline)
Copy from email: “I think if you are listening and checking for heartbeat (which you probably do in order to send the offline email), then you can set status of the phone in the DB to 0 when phone goes offline “WENT_OFFLINE”. Then when next heartbeat happens you can check if the phone previous status was 0 and if it is, trigger the “BACK_ONLINE” event and set the status to 1 in order for the next heartbeat to not trigger this event. To be honest, WENT_OFFLINE event would be really enough for me in this moment, but it will be really useful to know when the phone comes back online again as well :)” Looking forward to this. Thank you for your consideration. Cheers
Send Webhook Notification When the phone has an incoming call
Wend a webhook on an incoming phone call (so I could reply with a SMS that the number is not callable and the user should call another number)?
Different SMS queues with different priorities
Hello, thank you for the awesome work you've been doing in httpSMS. A feature request I'd like to propose is to be able to prioritize queues for sending SMS-es. For example, I have a normal queue and there are 100 SMS waiting to be sent. If I have another SMS that needs to be sent urgently I'd need to wait for those 100 SMS to be sent. I'd be really useful if we have an "urgent queue" where we will be able to send SMS that needs to be sent ASAP, or give a "priority" number from 1 to 10 when sending an SMS. As far as I am aware there is no solution for that now. Thank you!