Give each message an appropriate place
Use announcements for church-wide information, email campaigns for a selected audience and group conversations for ongoing discussion. Keeping those tools connected to the directory helps staff reach the people involved without building another contact list for every message.
Announcements can be pinned, scheduled and set to expire. In current mobile builds, the Home screen highlights unread announcements and hides the empty section. A member can still open the announcements list to revisit content they have already read.
Keep staff alerts useful
A request to join should reach the staff responsible for approvals without overwhelming every leader’s phone. Each eligible staff member can choose immediate, hourly, daily or disabled join-request alerts for a church.
Approval notifications are separate from staff request alerts. The approval process queues a notification and email for the applicant. App delivery depends on push registration and the church’s Firebase setup, while retries help recover from temporary provider failures.
Write emails that look like your church
Church administrators can edit church-owned automated email templates in the web settings. Default templates use the church’s name, branding and language. Account-wide security messages remain ChurchFoundry-owned rather than inheriting an arbitrary church’s branding.
Before sending a campaign, check the audience, contact preferences and unsubscribe behavior. Choose a channel because it fits the message, not because it can send the most notifications.
By ChurchFoundry · Reviewed
