Church automations: from first contact to follow-up
When someone fills in the form, has a birthday or stops coming, Brado opens a task or alerts the team. The team chooses the rules and decides what to do for each person.
Follow-up no longer depends on who remembered
Brado doesn’t decide for people. It just makes sure the next step stays in view.
- The form reply sits in an email inbox.
- Someone remembers the birthday the day before, if they remember.
- The list of people who have gone missing is put together by hand, now and then.
- Every task depends on who wrote it down.
- The reply creates the record, a task and an alert to the team.
- On the birthday, the team gets the alert or the task to phone.
- Anyone with no contact for the number of days you set shows up in an alert.
- The history shows what ran and what failed.
When this happens, do that, once you’ve seen the effect
You choose the trigger and the action, and Brado explains in plain language what will happen. Before saving, you can simulate: you see who would be affected now, with nothing created or sent.
- Nothing exists until you save, and inactive rules don’t run.
- Active rules run every day after 06:00, church time.
- You can run a rule by hand, with confirmation.
The moments the church already follows up
Each trigger pairs with one of these actions: alert the team, create a pastoral task, send a message, apply a label.
New visitor
When a visitor is registered in the last 48 hours, for example through the “I’m new here” form.
Birthday
On each person’s birthday, and on wedding anniversaries too.
Long absence
When a member or regular attender has had no recorded contact for the number of days you set.
First donation
A task to say thank you, or an alert to the team.
Joined a group
When someone joins a group within the last number of days you set.
Event registration
Right after a registration, to confirm or follow up.
Review first, act afterwards
Automations prepare the work. They don’t make decisions about people.
The team acts
The most-used templates create a task or alert the team. Whoever phones, visits or writes is a person.
You simulate first
The simulation shows who would be picked up and who has already been dealt with. Nothing is created or sent.
It respects the person
If the person has switched off the channel, it’s outside quiet hours or they’ve reached the weekly limit, the message isn’t sent and the reason is logged.
History of what ran
Every run is logged, with the person, the source (scheduled or manual) and the result.
Frequently asked questions
Do automations send messages without me seeing?
Only the ones you set up. Each rule is created and switched on by the church, after you simulate it, and the history shows what went out. If you prefer, use rules that only create tasks or alert the team.
What happens when someone fills in the “I’m new here” form?
The form can create the record or link it to an existing one, open a task and alert the team. Then a new-visitor rule can send a welcome message, if you set it up.
Do the rules decide what to do with each person?
No. The rule does what you asked when the trigger fires, such as creating a task. What happens next with the person is the team’s decision.
When do the rules run?
Active rules run every day after 06:00, church time. You can also run a rule by hand.
Can I use ready-made templates?
Yes. There is a gallery of ready-made rules, such as a visitor welcome or a birthday alert. The template only fills in the form, and the rule exists only once you save it.
Which plan includes automations?
Automations are available on every plan.
See a rule simulated before it is switched on
We show the form, the task and the team alert with sample data. If you go ahead, we set it up with you.