Chat portal
உரையாடல்
A coordinator sees the groups beneath them in the organisation — their centre, their region, or everything, depending on their role — and can read and reply. This is the one place the application listens rather than speaks.
This screen is not drawn yet
What has been decidedமுடிவானவை
Who sees which conversations
The groups beneath you in the organisation tree, and no others. A centre coordinator sees their centre; a regional role sees the region; an org-wide administrator sees everything. The same scoping the rest of the platform already enforces, rather than a second rule that drifts.
Replies go out from the Isha number
Not from the coordinator's own phone. The operator number is what the group knows, and it is the number that is an admin there.
The person's name goes in the text
So a reply from a shared number is still a reply from somebody. Whoever is reading it can see who answered them, and the record can too.
Messages are kept about thirty to sixty days
And then discarded. This is a window onto a live conversation, not an archive of what everybody said — which is also what stops it becoming a second, unwanted record of people's lives.
What has notமுடிவாகாதவை
- Whether a coordinator can reply to one person privately, or only into the group.
- What happens to a conversation when the group it belongs to is dissolved — a mandala cohort ends every forty-eight days.
- Whether an unread count belongs on the navigation, and what it would count across several hundred groups.
- Exactly where in thirty to sixty days the line falls, and whether it is a setting like the others.
- Whether anything in a conversation can be attached to the person it came from, given that the record deliberately holds a stage and a group history and not much else about anybody.
It is not a moderation screen, and both are missing
Nothing on this page is real, and there is nothing behind it at all. About this wireframe.