Help: Calendar
How calendar writeback works for your church team
Calendar writeback puts an approved follow-up reminder on a calendar your team already watches, so a visit or a call does not slip through the week. FlockConnect writes to Google and Microsoft calendars only, and it writes generic event text with a secure link back to FlockConnect. The sensitive details stay inside FlockConnect, never in the calendar event.
What is calendar writeback?
When a pastor approves a follow-up reminder in FlockConnect, calendar writeback can place that reminder as an event on a calendar your team already checks. The point is simple: the person who needs to make a call or a visit sees it where they already look, instead of inside one more tool.
Nothing is written until a person approves it. FlockConnect drafts the reminder, you review it, and only an approved reminder becomes a calendar event. It never writes to a calendar on its own.
- Writes to Google and Microsoft calendars only, no other providers.
- Supports personal, shared church, and shared team calendar destinations.
- Event titles and descriptions are generic and localized, with a secure link back to FlockConnect.
- Sensitive pastoral details, names, notes, and assessment answers never appear in the calendar event.
- Nothing is written until a person reviews and approves the reminder.
- Confirms write access to a destination before using it, and surfaces problems in Integration Health.
Which calendars can it write to?
FlockConnect writes to Google and Microsoft calendars. No other calendar providers are supported for writeback. Within those two, a reminder can land on a personal calendar, a shared church calendar, or a shared team calendar, depending on the destination your church connects.
Before FlockConnect uses a destination, it confirms it can actually write there. If write access is not available, the destination is not used and an owner or admin can see the problem in Integration Health.
What does the calendar event actually say?
The event uses generic, localized text. A title reads something like "FlockConnect follow-up" or "Care team reminder," and the description is a short line pointing to a secure link back into FlockConnect, where the real context lives.
Sensitive pastoral details never go into the external calendar copy. No names of who is being cared for, no notes, no prayer details, no assessment answers, and no health information appear in the event. Anyone who can see the calendar sees only that a follow-up is scheduled, not why.
How does approval state work?
Calendar writeback is tied to an approval. FlockConnect can surface who looks like they need a follow-up and draft a reminder, but a person reviews and approves it before anything is written. The approval is the gate.
If an approved follow-up is later completed or the reason for it goes away, FlockConnect can clear the matching calendar event so a stale reminder is not left sitting on your team's week. The source of truth stays inside FlockConnect.
Personal, shared church, and shared team calendars
A personal destination writes to one staff member's own Google or Microsoft calendar. A shared church or shared team destination writes to a calendar the whole team watches, so care does not rest on one person's memory.
Because the event text is generic for every destination type, sharing a calendar widely does not expose who is being cared for. The secure link is what carries someone into the details, and only signed-in FlockConnect users see them.
Still have a question?
FlockConnect is built and supported by a real person. Email support, or see how FlockConnect is priced.
