Where do I download the EDUBase SMS app, and how do I open it and do the setup for my campuses?

The EDUBase SMS app runs on an Android phone with a school SIM: it collects the messages queued on the web and sends them from that SIM. Since v3.2 there is no Device ID any more — and the web screen SMS Gateway Settings is gone. The phone simply logs in, chooses its campuses, and starts.

Where to get the SMS app (APK)

This app is Android only and not on the Play Store, so its APK comes from inside your own portal: open General › EDUBase App Links, find the SMS App card and press Download APK. Copy link copies that same download link, so you can share it with whoever sets the phone up; it always installs the newest build, so share the link rather than an old APK file.

Set-up, first time

1. Install that APK and allow the install when the phone warns. If it says "app not installed", uninstall any older EDUBase SMS copy first; on Samsung, Auto Blocker (Settings → Security and privacy) can also block it. 📺 Watch: How Download & Install SMS App — https://youtu.be/SodSNbdQxhk
2. On EDUBase SMS App, log in with your institute code, web User Name and Password. The sign-in screen uses the same visual style as the native Android Owners App. Remember me is checked by default and prefills only your institute code and username after a successful login; the password field remains empty. Uncheck it to clear those saved form details. A current signed-in sending session stays active until logout, independently of Remember me.
3. Campuses are chosen automatically. If your institute has one campus, the app selects it and shows it under the top bar. If it has several, a Select campuses screen opens — tick every campus this phone should send for and press Start using. You can change the selection later with Change on the main screen (stop the service first).
4. Allow the SMS and Phone permissions. If you tapped Deny, the app shows "You denied the permissions Click Here to allow" and cannot start. 📺 Watch: SMS App Permission If Permission not allowed — https://youtu.be/KJ_zApS9T8Q
5. Press Send SMS — the screen changes to "Fetching and Sending messages…" with a Stop button. On a dual-SIM phone it asks which SIM to use.
6. Test from Exam & Att › Attendance Report › SMS Report → Send Testing SMS; the row should turn from Not Set to Sent within a minute or two.

Reading today’s messages (v3.3 and later)

Open Sent Today or Failed Today on the phone to see the newest messages first. Each list sorts by its saved message date and time, with the most recently saved row first when times match. Check Failed Today when the web report says Sent but the recipient did not receive the SMS.

How a message travels

An App SMS waits under the student's campus as Not Set until a phone that has selected that campus collects it — it checks about every 10 seconds while idle — sends it from the SIM and reports back. The SMS Report then reads Sent.

Why the running screen counts down from 20 (v3.4 and later)

On EDUBase SMS App → Send SMS, the running screen shows a 20-second countdown after a school message is successfully sent. The next school message waits until this countdown ends. For a long message split into parts, the countdown starts after all parts succeed. A successful resend follows the same rule.

A failed or skipped message does not start a new countdown; the app moves on without the extra 20-second pause. Fetching messages or reporting a result to the server can take longer, so 0 seconds does not promise an immediate send. Returning to the screen shows the remaining time, without restarting the wait.

Parent login OTP texts use a separate sending path and do not wait for this school-message countdown. They still depend on the phone, SIM and network being available. Branded SMS and WhatsApp do not use this timer.

Unable to send SMS through the SMS App — check in this order

Sab kuch set kar liya hai lekin message ja hi nahi raha — the app is installed and the campus is selected, but messages are still not sending. Work down this list; the first mismatch is usually the cause.

1. Campus selection — the main screen shows Campus: … or Campuses: … below the top bar. If it says not selected yet, tap Change (after stopping the service) and pick the campus again. The student's campus must be among the selected ones; Testing SMS and SMS Blaster are queued under your first campus, so keep that one selected.
2. App running — phone on, internet on, showing "Fetching and Sending messages…"; nobody pressed Stop or Logout. It restarts after a reboot if left running.
3. Permissions — SMS and Phone allowed (step 4).
4. SIM — balance, signal, right SIM. A toast "Failed to send SMS!" or "Error: 17" / "Error: 112" is the phone or network refusing, not the server; those sit in the app's Failed Messages.
5. Channel — sent as WhatsApp or Branded SMS? Then it never reaches this app. Choose App SMS.
6. Daily limit — it stops at about 500 per phone per day ("Sms sending limit reached!") and resumes next day. Operators also cap consumer SIMs.
7. Long messages — the Send Large Messages control has been removed. Existing saved handling is kept, so this update does not change how the phone sends or splits messages. If a long message fails, shorten the template or contact support; there is no YES/NO switch on the main screen now.
8. Number — a student with no mobile number, or a number the phone will not send to (wrong, unsupported, or empty), is skipped and the queue keeps going. That row stays failed / Not Set; later rows are still sent.

Which number do parents see?

An App SMS is sent from the SIM in the phone running the SMS App, so parents see that SIM's number — there is no setting to hide it. To have the school's name show instead of a number, the school buys Branded SMS (bulk SMS). It is paid per message and does not use your SIM package; EDUBase support integrates it with the software, after which you choose Branded instead of App when sending.

Just switched the SMS App on and old messages started going out

The SMS App sends everything still waiting as Not Set — including messages generated weeks ago that were never sent. To start fresh from today:

1. Open Exam & Att › Attendance Report › SMS Report
2. Select the old pending messages and press Delete Selected SMS
3. Now generate your new messages — only those go out

Make this a habit: messages generated but not sent stay in the queue until the app sends them.

One message per student about their fee — SMS or WhatsApp?

Both. When you send (fee, attendance, result…), the send options let you choose App SMS (through this app), WhatsApp (through your WhatsApp sender) or Branded SMS, and the message goes to each student's parent.

Videos

📺 How Download & Install SMS App — https://youtu.be/SodSNbdQxhk 📺 Different Ways To Send Text Messages (SMS) — https://youtu.be/PiFbuuQdTWQ

Common confusion

"SMS Report says Sent but the parent got nothing." Sent means the phone collected it and tried; a SIM-level failure shows only in the app's Failed Messages / Failed Today. Resend from the SMS Report once the SIM works.

"One wrong number stopped the whole queue." From EDUBase SMS v2.5 the app skips that contact, marks it failed, and continues with the next. Update the app from General › EDUBase App Links if an older build still stops.

"The app shows an update is required and stopped sending." Every SMS app release is force-updated for safety. Press Update now, install the new build over the old one, and the app resumes where it stopped — the login and campus selection are kept.