For schools & coaching centres

Reach every guardian, not just the ones who call.

Fees reminders, results notices and admissions follow-up — sent to guardians in Bangla or English over the channel they actually read, and answered in one shared inbox.

SMS under your school's own nameWhatsApp, SMS and emailReplies in one shared inbox
The shared inbox: WhatsApp, Email and SMS conversations in a single list, with one WhatsApp thread open beside it.

It sends the messages. It does not keep the records.

QuickGrow is a messaging system, not a school management system. Attendance registers, exam marks and fee ledgers stay in whatever you use now — a school ERP, an accounts package, or a spreadsheet in the office. QuickGrow holds a guardian contact list and sends from it. You bring the names, the numbers and the dates; it does the reaching out and collects the replies.

One record per guardian

Guardians, not students

The contact is the guardian and the mobile number they answer. Tag each one by class, section, campus or shift, so a Class 6 notice goes to Class 6 guardians and to nobody else.

Bring your own list

Import the sheet you already keep

Upload a CSV and QuickGrow reads your column headings and suggests the mapping. Columns it does not recognise — fees due date, roll number, section — are kept on the contact and can be used inside a message. Guardians already on the list are skipped or updated, whichever you pick.

Consent on record

Opt-outs handled for you

Consent is recorded per channel at import. A guardian who replies STOP reaches your inbox with the word recognised; once you withdraw their consent, every later send skips them without anyone keeping a list by hand.

The channel a guardian will actually read.

Nearly every guardian opens an SMS. Many will also reply on WhatsApp. Email carries the long things — a prospectus, a results sheet, a term calendar. QuickGrow sends all three from the same guardian list, so you choose the channel per message rather than keeping three separate lists.

Masking and non-masking SMS each have their own volume slider, metered separately.
Masking SMSNon-masking SMSWhatsAppEmail
What the guardian seesYour school nameA number, not a nameYour business WhatsAppYour school address
Works on a basic handsetYesYesNoNo
Bangla textYesYesYesYes
Best forFees and urgent noticesBulk notices in volumeConversations and admissionsProspectus, results, long notices
How it is boughtIts own volume sliderIts own volume sliderVolume per message categoryYour own mail server, or ours

A message from the school, with the school's name on it.

A fees reminder from an unknown eleven-digit number gets ignored, or it gets a phone call to the office asking whether it is real. A masking sender puts your short school name where the number would be, so a guardian knows in one glance who is asking. It is the single thing that changes how seriously a school notice is taken.

Step one

Apply for the name once

Choose the short name guardians will see, then fill in what the operators ask for: the institution details and registration numbers, the address, the contact person and their national ID, sample messages, and the confirmation that your traffic stays inside Bangladesh.

Step two

Verify, then wait for approval

The contact mobile is confirmed by a one-time code before the application can even be submitted. It then goes for approval, and the name stays unusable until that comes back. This is the part that takes days, so start it before admission season, not during it.

Step three

Pick it per campaign

Once approved, choose the sender on any SMS campaign. If a campaign ever points at a name that is not approved, QuickGrow quietly falls back to the default sender instead of failing the send — the notice still goes out.

Scheduled before the due date. Stopped once it is paid.

A fees reminder in QuickGrow is a date-based automation. It works off a date held on the guardian record — not off a payment gateway and not off your ledger — which is why it can run for a school that keeps its accounts anywhere. Here is the whole mechanism, start to finish.

  1. Put the due date on the contact

    When you import the guardian list, map your due-date column onto the contact. It is just a date sitting on a record: QuickGrow never reads your fee ledger and never needs to.

  2. Write the message once

    One template, with placeholders for the guardian name, the student name and the amount. Bangla is fine — but a Bangla SMS fits about 70 characters per message where English fits 160, and QuickGrow counts messages the same way your bill does.

  3. Set how many days before

    A date-based automation checks every day and picks up guardians whose due date is a set number of days away: three days before, on the day, two days after. Each guardian enters at most once a day, so nobody is reminded twice by accident.

  4. Stop it once the fee is paid

    Put a check step before the send. It reads a field on the contact and, if that field says paid, skips past the message to the end of the journey — nothing is sent. Update the field by hand, by re-importing the sheet, or from your own system through the API. Or pause the whole reminder for the term in one click.

A saved segment showing its matching contact count above the condition rows that produce it.
Audiences

Know who it goes to before you send.

Build the audience from rules rather than by copying rows between spreadsheets — a tag for the class, when the guardian was added, how engaged they have been — and the matching count updates as you edit the rules. Save it once and every notice for that class reuses it.

  • Rules on tags, status, source, sign-up date and engagement
  • A live count of matching contacts before you commit to a send
  • On an SMS campaign, exclude a group as well as include one — the guardians who have already paid, for instance

An enquiry that gets answered, then followed up.

Admission season is two weeks of phone calls and a long tail of families who never hear back — not because anyone decided against them, but because the note was on a different desk. Put the enquiry form where parents already are, and let the follow-up run on its own.

The form builder: the field list beside a live preview of the sign-up form it produces.
Enquiry forms

A form on your website, in about a minute.

Build the enquiry form — guardian name, mobile, class applying for — and drop a single line of script onto your school website to embed it. Every submission is stored, and the form keeps its own view and conversion counts so you can tell whether the page is doing its job or just sitting there.

  • Embed on any site with one script tag, or use a hosted landing page instead
  • Pause, duplicate or replace a form without touching the website again
  • A hidden field quietly swallows bot submissions before they reach your list

A reply in minutes, not days

Build the follow-up once on the automation canvas: a first reply, a wait, a WhatsApp message with the prospectus, another wait, a last SMS before the deadline. Enquiries added to your list start the journey, and you can start one for a single family by hand.

Replies land in one place

When a guardian answers on WhatsApp, SMS or email, the reply arrives in the shared team inbox with the rest of that family history beside it. Whoever is on the desk picks it up — no forwarding, no personal phone.

Nothing goes out at ten at night

SMS campaigns will not deliver during Bangladesh quiet hours, 9pm to 8am Dhaka time, and per-channel frequency caps stop one family being messaged five times in a single day.

What actually reached the family.

Guessing is expensive when you are buying volume. Every campaign reports what it did, and the channel comparison puts email, WhatsApp and SMS beside each other so next term you spend on the one guardians answer.

Every term, on repeat

  • Reusable templates for results, holidays, exam schedules and fees
  • Duplicate last term campaign and change the dates
  • Saved audiences per class, section and campus

For the office team

  • One shared inbox across WhatsApp, SMS and email
  • The full message history on each guardian record
  • Separate logins for the staff who need them, with their own permissions

Reporting you can show the board

  • Delivered, opened and clicked, per campaign
  • Email, WhatsApp and SMS compared side by side
  • Best send times from an engagement heatmap

Pay for the platform, or pay for volume — rarely both.

Pricing is in taka. There is a platform fee for the tooling, and there is the volume you buy on each channel. The two work against each other on purpose: buying managed volume waives part of the platform fee, and buying across email, SMS and WhatsApp at a high enough tier waives it entirely. Longer billing terms discount the fee and the volume separately.

Before you sign anything.

Does this replace our school management software?

No, and it does not try to. QuickGrow keeps no attendance register, no exam marks and no fee ledger — those stay in whatever system or spreadsheet the office uses now. QuickGrow holds the guardian contact list and sends the messages. You supply the dates and figures a message should mention, either by importing a sheet or by pushing them in through the API.

Will guardians see our school name on an SMS?

With a masking sender, yes. You apply once with your institution details, registration and tax numbers, the contact person and national ID, sample messages, and a declaration that traffic stays inside Bangladesh. The contact mobile is verified by a one-time code, and the name goes live once approved. Non-masking SMS is the cheaper alternative and sends from a number instead of a name.

Can we write to guardians in Bangla?

Yes, on all three channels. One thing to plan for on SMS: Bangla characters take more room, so a Bangla message fits about 70 characters before it counts as two messages, where English fits 160. Short reminders normally still fit in one — it is worth writing them tight.

Talk to every family, every time.

Import the guardian list, write one reminder, and let the term run itself.