{"id":"qawmicare-silver","name":"Qawmicare Silver (2 Screens)","free":false,"currency":"BDT",
"pricing":{"daily":18,"weekly":100,"monthly":300,"tri_monthly":850,"half_yearly":1600,"yearly":3000}}
Qawmicare Silver (2 Contacts / Dual Notify)
Staff sign in
Subscription dashboard
Subscriptions
Subscriptions
Settings
Newsletters
Compose
Loading…
Channels
Each service post sets whether its subscribers get Email, SMS, or Both — these switches are the master on/off for each channel site-wide.
bKash instant checkout
When on, paid services show a "Pay instantly with bKash" button that redirects to bKash, verifies payment automatically, and activates the subscription with no approval step — alongside the manual bKash/Nagad/Bank option, which still works either way.
Credentials (app key/secret, username/password) aren't set here for security — add them once in the Apps Script editor under Project Settings → Script Properties as BKASH_APP_KEY, BKASH_APP_SECRET, BKASH_USERNAME, BKASH_PASSWORD.
SMS gateway
Paste your gateway's send-SMS URL, keeping the {api_key}
{sender_id}
{number}
{message} placeholders — the script fills them in per message. Works with GET-style APIs (most BD gateways: BulkSMSBD, Alpha SMS, etc.).
Applies to every outgoing SMS — check-ins, newsletters, and manual sends — to control gateway cost. 70 is safe for Bengali/Unicode SMS (usually billed per 70-character segment); raise it toward 120–160 for English-only content.
Email branding
Every email now sends as a styled card with this name in the header and a colored accent bar per message type — you still just edit plain text below, no HTML needed.
Recurring check-in email
Sent repeatedly while a subscription is Active, on its own plan's cadence (see the daily/weekly/etc. schedule).
Transactional emails
Sent automatically the moment each event happens — separate from the recurring check-in above. Placeholders: {name}
{serviceName}
{plan}
{expiryDate}
{daysLeft}
SMS template
Used for the recurring check-in only, on subscribers whose service is set to SMS or Both.
New newsletter
Leave blank to send whenever the daily job next runs. Set a time (e.g. 05:00 for Fajr) to hold it until that clock time — but this needs your Apps Script trigger to run every 15–30 minutes rather than once a day; see section 7 of the setup guide.
Uses the free Aladhan API — no AI involved, so times are never paraphrased or guessed. Calculated times may differ slightly from your local mosque's announced times.
Each send continues from where the last one left off instead of starting fresh — the part number is added to the subject automatically.
Loading…
Search-based newsletters use Tavily to search and Groq to write. Prayer-times newsletters skip AI entirely and use the free Aladhan API directly.
Set TAVILY_API_KEY and GROQ_API_KEY once under Project Settings → Script Properties in the Apps Script editor (not needed at all for prayer-times-only newsletters).
A category is whatever you set in a post's category field (section 3) — use the same text across posts you want a newsletter to cover together.
Send a one-off message
Placeholders: {name}
{serviceName}
{plan}
{expiryDate}
{daysLeft} — filled in per recipient from their own subscription.
0 / 70 characters — longer messages are cut off automatically to control gateway cost. Same placeholders as email work here too.
Email and SMS are two independent fields on purpose — write each for its own format rather than reusing the same text. Nothing here is AI-generated; this is for a message you write yourself. If someone matches more than one active subscription (e.g. two services in the same category), they receive one personalized message per subscription rather than a single generic one.