GetCommunityMail

Volunteers do not need to learn a dashboard simply to send an announcement. They write in Gmail, Outlook or any other email client and send the message to their group's address. GetCommunityMail verifies the sender, scans any attachments and returns a delivery preview. The sender approves it with one click or by replying APPROVE. The message is then delivered in personalised batches, while replies return to the person who wrote it.

Email remains the simplest way to reach the whole community. The resident app gives members somewhere to return to: announcements are organised by group, community documents remain available in one place and votes can be completed without leaving the app. The inbox is the front door; the app becomes the community's continuing record. The screens shown use a demonstration community.

A board or committee defines the question, available choices and closing date. Members can respond from the email or inside the resident app. For recorded decisions, votes can be exported by name for inclusion in meeting minutes. For anonymous ballots, the record of who participated is kept structurally separate from the ballots themselves. A ballot can include supporting documents, group several questions into one request and account for requirements such as quorum or household weighting.

Community communication fails if messages do not arrive—or if members lose control over how their address is used. Every send therefore includes authenticated email delivery, auditable confirmed consent and immediate one-click unsubscribe at list, organisation or platform level. Hard bounces and complaints are automatically suppressed, and attachments remain unavailable until malware scanning clears them. These are not administrative additions around the product. They are part of making the product dependable.