Messages

One place to reach the workforce. Write sends as Email (an email to each person, with the recipient picker and personalisation), as a Notice (in the app and on their phone, free, with an optional WhatsApp Channel step) or Both; a Site filter narrows either to the people on a site. Sent notices lists every notice you may see with its reach, who has read it, who acknowledged it and whether it was posted to WhatsApp. The office (emails.batch_send) may do all of it; a site manager with notices.post may post a notice to their own sites.

You enter

Send as — Email, Notice or Both — and the site or the whole company it goes to; anyone on the site to leave out of a notice.
A notice's kind (General, Safety, Site closed, Deadline), its title and text, an optional link to a page in the worker portal, and whether it needs acknowledging.
For an email: the recipients, subject and text, as on the email form. After a notice: whether you pasted it into the site's WhatsApp Channel.

Saral fills in

Who is on a site: everyone who worked there in the last so-many days by the register, started there recently, or runs its register — the window is a setting — and how many of them have the app.
Warnings before a notice goes to everyone: a name or something that reads like personal data in the text, a link that is not a page inside Saral; a notice from a site manager that needs the office's approval waits as such.
On Sent: reach, in-app count, reads and acknowledgements — each a record the worker's own tap wrote, never a tick in the office — and the WhatsApp record.

It produces

An email to each recipient; a notice in each worker's app with a push to their phone; a ready-to-paste WhatsApp text; and a per-notice list of who has read and acknowledged it.

What this page is for

A site closes tomorrow, a gate moves, a deadline lands — the people who need to know are on site, on their phones, and many of them never read email. A notice reaches them in the app and as a push, free, and a site manager may post one to their own site without going through the office. Email stays for what email is for: a message to chosen people, personalised, with attachments. This page puts the two side by side with one Site filter, so the office never has to work out the audience by hand.

Who is on a site

Saral resolves the audience from the register: everyone marked or confirmed on the site in the last so-many days, anyone who started there recently, and the people who run its register. The line under the Site picker says how many that is, how many have no app (they see a notice only on WhatsApp or by email) and lets you see who and leave anyone out of a notice. A site is yours to post to once you have marked or confirmed its register within the window; a crew-scoped seat reaches its crew only.

Notices, warnings and WhatsApp

A notice has a kind — General, Safety, Site closed, Deadline — a title and short text, an optional link to a page in the worker portal, and may require an acknowledgement. Before it goes, Saral warns if the text names someone or reads like personal data and asks you to send anyway, and refuses a link that is not a page inside Saral. A company-wide notice may need HR's approval first when the account says so; it waits on Sent until someone else approves it. WhatsApp lets no software post to a Channel, so the WhatsApp step copies the text and opens the Channel for you to paste, then records whether you did.

What Sent shows

Reads and acknowledgements are evidence, not a tick in the office: each is a row the worker's own tap wrote, and the detail lists every worker with when they read it and, where it was required, when they acknowledged it — Missing stands out. Office and register staff without a worker record are told in the app but not listed. The list keeps every notice you may see; a worker's own list in the portal keeps 90 days.

Where the settings live

HR → Settings → Messages owns the attendance and starter windows that decide who is on a site, each site's and each company's WhatsApp Channel link, and whether a company-wide notice needs HR's approval (off unless your account changed it). Who may email is the emails.batch_send key and who may post a notice is notices.post, set on roles in Settings → User Permissions. Notices themselves arrive with a database update; until it is applied the page says so and email works as before.

Next screen: /hr/leaves

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.