Ask for enough information to help
Put the connection-card link where visitors can find it: on a welcome slide, a QR code at the desk or a page on the church website. Keep the first form focused. A name, a way to respond and the question or next step they want may be enough.
Explain what happens after submission and how the church will use the information. Do not ask for sensitive pastoral details just because the form can hold them. Offer a personal conversation for information that should not go into a general-purpose form.
Assign a person, not just a stage
Someone should own each next action. Choose the staff member or ministry team responsible for a welcome message, answering a question or helping a guest find a group. A task with a due date is easier to review than a note that nobody knows they should act on.
Use guest stages to describe progress, such as needing a first response or having spoken to a leader. Keep membership decisions separate. A connection-card submission is a request for contact, not automatic consent to become a member or receive every campaign.
Automate the handoff thoughtfully
Automation can create a task, attach a useful tag or queue a message after a form submission. It should support a defined process rather than sending a long sequence simply because it is possible.
In ChurchFoundry, identified form submissions and guest-stage changes can trigger workflows. Imported people do not trigger the person-added workflow. That helps staff bring over a directory without mistakenly treating every old record as a new visitor.
Make the first conversation specific
Respond to what the person actually asked. A family looking for children’s ministry needs a different answer from someone asking about a small group. Check contact preferences before choosing email or another channel.
Record the outcome and the next action so another staff member can continue the conversation. If no response is needed, finish the task. A completed task should not linger as an unresolved commitment.
Review the process together
Each week, review guests needing a response, overdue tasks and the stages that tend to stall. Attendance and guest reports measure different things; a Sunday headcount cannot tell you whether a particular visitor received a helpful answer.
Use fictional submissions to test the connection card, task creation and permissions before publishing the QR code. ChurchFoundry supports a branded web card, guest tracking, follow-up tasks, workflows and custom guest reports as connected parts of that process.
By ChurchFoundry · Reviewed