E-mail, SMS and notifications
SMTP and deliverability, mail templates, in-app notifications, web push, SMS gateways, WhatsApp ways, per-kind channel switches, phone verification and sign-in codes, SMS and WhatsApp templates and report, and the look of the mails.
Meetings depend on messages: invitations, reminders, receipts. This chapter shows how each channel is set up and what goes through it.
1. E-mail
Open Settings, General Settings, E-mail.
- Choose how mail is sent: SMTP (recommended) or the PHP
mail()function. - For SMTP type the host, port, encryption (TLS or SSL), user and password. Use the mailbox that belongs to your domain, for example
no-reply@your-domain. - Set the sender name and address. The address is the contact e-mail you gave in the installer unless you change it.
- Press the test button and send a message to yourself. Check the inbox and the spam folder.
Good deliverability needs three DNS records for your domain: SPF, DKIM and DMARC. Ask your host or mail provider for the values. Without them many mails land in spam, and a meeting invitation in spam is a lost meeting.
Mail sending goes through a queue. A page never waits for a mail server. The cron (every 5 minutes) works the queue and retries failures. If mail does not arrive, check Reports, E-mail Log and Automation Log first.
2. The mail templates
Open Settings, E-mail Templates. Each template has a subject and a body, with merge fields such as {$name}, {$title}, {$when}, {$code}, {$passcode}, {$link} and {$host_name}. These meeting templates exist.
| Template | Sent to | When |
|---|---|---|
| Meeting invitation | Invited people | The host sends invitations |
| Meeting reminder | The host and invitees | Before a scheduled meeting (default 10 minutes, see the Meetings setting) |
| Meeting summary (host) | The host | After a meeting ends |
| Recording ready | The host | A cloud recording finished |
| Registration received | A registrant | A webinar with manual approval |
| Registration approved | A registrant | The host approved, with a personal link |
The platform templates (welcome, e-mail verification, password reset, invoice, ticket replies and so on) are edited the same way. Edit the English and the Bengali text.
3. In-app notifications
Members see a bell with a count in the site header. Notification kinds include Meetings: invitations, reminders, registrations and Recordings ready, plus orders, tickets and account events. Each member chooses, in Notifications, whether each kind arrives in the app, by e-mail, or both. Staff get notifications too, for example a new ticket or a payment to confirm.
4. Push notifications
Browsers that allow it can receive web push messages, even when the site is closed. A member allows push from the bell panel. The service worker is push-sw.js. Push needs HTTPS. Phones that installed the app made with the App Builder receive push through the app.
5. SMS
SMS is optional. Open Settings, Push, SMS and WhatsApp and find the SMS card.
- Switch on Send text messages.
- Choose a Gateway. The list is grouped. Bangladesh: RT Communications, SSL Wireless, Alpha SMS, Greenweb, MiM SMS, ElitBuzz and Reve SMS. International: Vonage, Plivo, MessageBird, Infobip, Textlocal, ClickSend, Telnyx, Sinch, Africa's Talking and MSG91. Any HTTP gateway covers a provider that is not listed (GET, POST form or POST JSON). Test only writes to the log and sends nothing. Gateway plugins from earlier versions (Twilio SMS, BulkSMSBD) still show as plugins.
- Type the keys the chosen gateway asks for. Keys are stored encrypted and never shown again.
- Set the limits: texts per member per day, texts per number per hour, longest text, verified numbers only, one account per number, put the link in the text, and hide codes in the report.
- Save, then use Send a test SMS further down. Check balance shows when the gateway can report it.
160 letters make one SMS part (70 for Bengali). Mind the cost per message and the rules of each country about sender names.
6. WhatsApp
On the same page the WhatsApp card offers these ways to send.
| Way | What it does |
|---|---|
| Click-to-chat link | Free. The site sends nothing. Staff get a wa.me link in the report to open the chat by hand. |
| GREEN-API | An instance linked to a phone by a QR code. Needs the instance ID and the API token. Check the instance tells you if the phone is linked. |
| Twilio WhatsApp | Account SID, auth token and your WhatsApp sender number. Outside the 24-hour window WhatsApp delivers only approved templates. |
| Meta WhatsApp Cloud API | Phone number ID and a permanent access token, with an optional approved template name. |
| Any HTTP gateway | Your own address with {to}, {text} and {key} in it. |
Notifications and codes need one of the ways that really send. The click-to-chat way only makes a link. The WhatsApp limits (per member per day, per number per hour, longest message) work like the SMS ones, and a Send a test WhatsApp form sits below.
7. What may go by SMS and WhatsApp
The card What may go by SMS and WhatsApp is a table with one row per kind of notification and two switches, SMS and WhatsApp. Switch a kind on or off for each channel. Members then choose for themselves among the kinds you switched on. Meeting invitations, meeting reminders, registrations, recordings ready, payments and new-device sign-ins can all go by phone. Codes (phone verification and sign-in) always go when the channel is on.
8. Phone verification and sign-in codes
A member opens Account, Notifications and finds the card Text messages (SMS) and WhatsApp.
- The member types a mobile number in international form, for example
+8801XXXXXXXXX. - A 6-digit code arrives by SMS or WhatsApp. The member types it and the number shows Verified.
- The member ticks, per kind, whether to get SMS, WhatsApp, e-mail or an app message.
With Verified numbers only on, nothing goes to a number that was not verified. The same verified number serves SMS and WhatsApp.
The card Codes by phone turns on sign-in codes. A member with a verified number can ask for a code by SMS or WhatsApp when signing in on a new device. The code is good for 10 minutes by default. With Offer the code by e-mail when the phone fails on, nobody is locked out when the gateway is down. A member who uses an authenticator app is not asked for a phone code.
9. SMS and WhatsApp templates
Open Settings, SMS and WhatsApp Templates. Each message has its own words: meeting invitation, meeting reminder, new registration (host), registration approved, recording ready, order paid, sign-in from a new device, phone confirmation code, sign-in code and test message. Edit the text with the variables listed beside it. A preview shows sample values and the number of SMS parts. Send the sample to a phone tests the text with the gateway in use. A template shows Edited or Built-in, and Reset to the built-in words brings the original back. A kind that is switched off shows Kind off.
10. The SMS and WhatsApp report
Open Settings, SMS and WhatsApp Report. It lists every message with filters by channel, gateway, status and date. The top shows totals per day, per gateway and per status, and the latest failures. Statuses are Sent, Logged (test driver), Pending, Failed and Link only (click-to-chat). Resend tries a failed message again. CSV downloads the list. Codes are masked and never resent.
11. The look of the e-mails
Open Settings, Look of the Mails. The page has these parts.
- Header. A logo for light mode and one for dark mode (apps such as Apple Mail, Outlook and the Gmail apps switch to the dark one), the logo height, its position (left or centre) and the header colour for each mode.
- Footer: site info. Company name, address, phone, e-mail, website, social links and a custom line. Empty fields fall back to the General settings.
- Show in the footer. A switch for each part, so you can hide the phone or the address.
- Text and custom HTML. A signature for
{$signature}, and header or footer HTML for full control. - Preview. A live light and dark preview follows the fields as you type. Send a test e-mail sends the real thing to you.
12. What the host gets
- When a meeting is scheduled: nothing, except the meeting page.
- Before it starts: a reminder, if the setting is above 0.
- When it ends: a summary with length and number of participants, if "E-mail the host a summary after each meeting" is on.
- When a cloud recording is ready: "Recording ready" mail and a bell message.
13. What invitees get
An invitation e-mail with the topic, time, ID, passcode and a Join the meeting button. A reminder shortly before the start, if the host sent invitations by e-mail from the platform. Pasted invitations (copied text) do not trigger reminders, because the site does not know the address.
14. Checklist
- SMTP works and the test arrives.
- SPF, DKIM and DMARC are set.
- The cron runs every 5 minutes.
- The templates are rewritten in your tone.
- Push is tested on one phone.
- One SMS gateway is tested, if you use SMS, and one WhatsApp way if you use WhatsApp.
- The look of the mails is set and a test e-mail looks right in light and dark.