Feature Requests

I would be a great addition to an already existing functionality to be able to delete a number from Opt-out list depending on some inbound rule. Like if customer replies with 'STOP' we added a rule to add the number in opt-out list, we should also have a rule where if customer replies with 'START', the same number should be deleted from opt-out list (or any other list).

Hello, In the ClickSend service "Email-SMS", when you send the converted source email as an SMS it is apparently currently not possible to select from our list of Clicksend-registered phone numbers to be used as outgoing number, depending on a text string contained in the original email. So what we would need id that Clicksend should check if the original email subject is containing key words we pre-defined in the portal, and based on that it should send the SMS by one of our registered phone numbers (For example if the email subject contains "warning", the outgoing generated SMS should have our Clicksend-registered phone number +12345678 as sending number, and if it contains "success", the SMS should have (use) the also registered second phone number +98765432). Ideally it should also be possible to not only to select the outgoing sender cell phone number based on the email subject, but also to send the SMS to a different target CellPhone number , depending on a text string contained in the original email. For example if the email subject again contains "warning", the SMS should go to +12345678, and if it contains "success", the SMS should go to +98765432) As support told us, exactly this second option is already possible if the soure is an SMS, but not if the input comes from an email (for using the ClickSend Email-SMS service as mentioned). As these 2 features are real important for us and other services already have this, but we don't want to be forced to move to another sevice because of this small feature, as we like ClickSend very much, and as you already have implemented this if the source is an SMS, is it possible to implement this also for the Email-SMS service in a forseeable time frame? And can you give us a short feedback? Thank you very much, this would help a lot, surely not only for us, but for many other customers. Regards Tom

to add friends and family manually to thread

Update or change a scheduled SMS before it is due to be sent.

Hello, I attempted to send a large volume of SMS and most messages were marked as Failed. I would like to understand: • What is my current per-second sending limit? • Is there a daily or monthly sending limit on my account? • Were the messages blocked due to content restrictions or carrier filtering? • Are there any compliance requirements for high-volume SMS in the US? • Can you provide the exact rejection reason for these failed messages? Thank you.

Today there isnt a sms package that suits my need. The first package is for 3000 Norwegian krone and the second is for 35 000 . Thats a VERY big difference. Over 1000% difference between the first and second sms package. I wish there was the option to buy for 6000, 12000 norwegian krone etc.

Many users send automated reminders and notifications via the ClickSend REST API (e.g. appointment systems and transactional messaging). Currently, API-sent SMS do not appear as threaded conversations in Messenger, forcing users to rely on the SMS History page, which requires manual refresh and limits real-time visibility of replies. Please consider enabling optional Messenger threading for API-sent SMS, with safeguards such as opt-in per sender number, per request flag, or volume limits. Competing platforms (e.g. Twilio, MessageBird) support threaded conversations for API-sent messages. This would be a significant UX improvement for customers using ClickSend for automated, two-way messaging at scale.

For some unfortunate reason, download urls in SMS messages are broken up when received by our endpoint. For example, we see the following in our SMS History on your website https://clicksend-api-downloads.s3.ap-southeast-2.amazonaws.com/_private/AF6A4AC9-5A78-41F7-89EC-990D00FFB98A.jpg?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAWKMIV4OKATYVXFML%2F20260130%2Fap-southeast-2%2Fs3%2Faws4_request&X-Amz-Date=20260130T170025Z&X-Amz-SignedHeaders=host&X-Amz-Expires=600000&X-Amz-Signature=d50a18c110b45706e6b50da19b5e395067a0bbfc4967faeaf51106c41429c4ce Selected and paid. Due in 3 weeks However, what we receive is shown below. Note that it has multiple fields starting with "X-Amz-" that came from the original body. PLEASE do not break up the body like this. Instead, please send as in the SMS History as it is easy to extract the urls from there. Thanks. {"originalsenderid":"[redacted]","body":"https:\/\/ clicksend-api-downloads.s3.ap-southeast-2.amazonaws.com \/_private\/AF6A4AC9-5A78-41F7-89EC-990D00FFB98A.jpg?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD","X-Amz-Algorithm":"AWS4-HMAC-SHA256","X-Amz-Credential":"AKIAWKMIV4OKATYVXFML\/20260130\/ap-southeast-2\/s3\/aws4_request","X-Amz-Date":"20260130T170025Z","X-Amz-SignedHeaders":"host","X-Amz-Expires":"600000","X-Amz-Signature":"d50a18c110b45706e6b50da19b5e395067a0bbfc4967faeaf51106c41429c4ce\nSelected and paid. Due in 3 weeks","message":"https:\/\/ clicksend-api-downloads.s3.ap-southeast-2.amazonaws.com \/_private\/AF6A4AC9-5A78-41F7-89EC-990D00FFB98A.jpg?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD","sms":"[redacted]","custom_string":"[redacted]","to":"[redacted]","original_message_id":"[redacted]","originalmessageid":"[redacted]","customstring":"[redacted]","from":" [redacted]","originalmessage":"[redacted]","user_id":"[redacted]","subaccount_id":"[redacted]","original_body":"[redacted]","timestamp":[redacted]","message_id":"[redacted]"}

The client regularly sends multiple campaigns via the Dashboard. They need an easier way to review SMS delivery history per campaign. Currently, they have to download the full SMS history and manually filter the file to isolate a specific campaign, which is time-consuming and inefficient. Proposed improvement: Add a “Download” button beside each campaign in the Campaigns view. This would allow users to directly download the SMS history for a selected campaign without needing to export and filter all message data.

Why does your system not automatically split a long message into 2 or 3 messages? I do not believe this is something hard to do. Your system should automatically recognise the long message and split the message into multiple messages.