As it is possible to create a customize APK for server, I can easily provide way to create custom APK with signing keys of the user so it shouldn’t be issue if it comes to pass.

You can find changelog from the following link.

No, RCS is not yet supported. Google still not released RCS in Android SDK for third party devs.

Please follow the below guide to resolve this issue.

If you already purchased the app, then please open a support ticket on the following portal if you need further help regarding this.

Comment section is reserved for presale questions only.

Dear Sir,

I have not purchased your script yet; I am currently testing the demo version. However, I have noticed a serious issue. Messages are sent only when the mobile app remains active on the front screen. As soon as the app goes into the background, the messages start showing as pending. When the app is opened again, all pending messages are sent.

This behavior is not professionally feasible. It is not practical to keep the app open all the time or repeatedly reopen it just to ensure messages are delivered. In its current state, this makes the script unsuitable for real-world use.

Kindly let me know if there is a proper solution for this issue. If it can be resolved, I would consider purchasing the script.

I look forward to your response.

Please open a support ticket on the following portal using the email you used for demo account.

I’m planning to integrate your SMS Gateway with Google Calendar for my office appointment reminder system. I need to send 3 different SMS messages per appointment: 1 Confirmation SMS – sent immediately when appointment is created 2 Reminder SMS – sent 24 hours before the appointment 3 Follow-up SMS – sent 2 hours after the appointment My questions: Q1: Scheduled Messages – Multiple schedules per recipient Can I schedule 3 different messages to the same phone number at different times? For example, if I have an appointment on February 10th at 10:00 AM, can I: • Send message 1 immediately (confirmation) • Schedule message 2 for February 9th at 10:00 AM (reminder) • Schedule message 3 for February 10th at 12:00 PM (follow-up) Do I need to make 3 separate API calls to /api/v1/messages/send with different schedule parameters? Q2: Best approach – Campaigns vs Individual Messages What’s the recommended approach for my use case? Option A: Use Campaigns with recurring feature Option B: Use individual /messages/send API calls with schedule parameter (3 calls per appointment) Option C: Another approach you’d recommend? Q3: Workflow confirmation Is this the correct workflow for my integration? 1 My script reads Google Calendar API every 15 minutes 2 Finds new appointments with: Name, Phone, Date, Time 3 Makes 3 API calls to SMS Gateway for each appointment: ◦ Call 1: Send confirmation (no schedule, sent immediately) ◦ Call 2: Send reminder (with schedule = 24h before appointment) ◦ Call 3: Send follow-up (with schedule = 2h after appointment) Is this efficient, or is there a better way? Thank you

Your workflow is correct. I think separate API calls for each reminder is better suited for your use case. This way you can also send different message for each reminder and follow up.

Please use following support portal instead of posting long comment like this. As comment section don’t allow formatting it is very hard to read.

Thank you. Will do from now on

1. If you want to use your Android device SIM to send messages, then it is not possible to use brand name. Your mobile number will be visible to the receiver. To use brand name you can integrate third party SMS Gateway service as Sending Server.

2. Can you tell me what error you encountered? You can try to register from the following link.

3. There is no limit on this from the app.

4. It uses your mobile SIM to send messages so any usual charges associated with sending messages using your mobile will apply.

That update was issued to fix installation issue happening due to bug in Apache. There are no changes made to the app though.

You can have one license running only on single instance (Domain, Subdomain or PC). Three custom APKs are given so you can change something if you don’t like it after creating it. Also, APK builder allows removing certain features from APK, so it will also help you create multiple APKs with different features.

Thanks. And landing page demo url please send me. Or where I find ?

You can check it out from the following link.

Please open a support ticket on the following portal with instruction on how to reproduce this issue.

replied to your email! thanks. standing by.

There was no screenshot in attachment. Just replied. Standing by. Thank you.

Replied to your ticket.

It doesn’t provide OTP generation API itself, but you can use the API to send the OTP generated by your app. You can also use the API in demo if you want to try it out before purchasing.

It uses your Android device SIM to send messages, so any cost associated with sending message normally from your phone will apply.

Currently, there is no offer for Christmas or New Year.

Please use the official build server to create custom APK by following the below guide. Creating an app using a third party site won’t work.

But this box didnt showup. I tried in chrome and edge, the same issue.

It does show up for me on Firefox, Chrome and Edge. Maybe some extension is blocking it? It usually shows up after some seconds after page load.

Thanks. now it’s working.

You can register for demo from the following link.

It uses your Android phone SIM to send messages to SMS, cost depends on your SIM operator. Each user can add their own sending server or android device and create an API if they want.

Replied to your ticket.

yes thank you

Yes, you should be able to use this app to provide a messaging platform for your customers. There are 2 ways to do this. You can use your own devices and share them with your customer and charge for that, or you can create a plan where they can add their own Android devices and user their own SIMs to send messages. You can use the API to integrate it into your application. You can also do that in demo before your purchase.

Sorry, I can’t provide an ETA, but it should be ready sometime in 2026. New beta versions will be released meanwhile with any bug fixes and new features. You can use stable version v9.x.x in production for now if you don’t want to update to a new beta version.

Replied to your tickets.