Email Studio + QR Codes.
The communications toolkit, in your $379.
A visual email builder with branded templates. Broadcast scheduling and segmented sends. A workflow engine that ties form submissions to follow-up emails and pastoral tasks. And trackable QR codes for every bulletin, postcard, and visitor sign — measuring reach the way digital communication measures it.
How a church actually reaches its people
The weekly email. The follow-up after a welcome card.
The QR code on the back of the bulletin.
Church communications happens across more channels than most platforms acknowledge. The weekly newsletter goes out to a list of a thousand people. The personalized follow-up email to the family that filled out a welcome card on Sunday goes to one. The QR code on the back of the bulletin — scanned by a visitor in the pew — needs to lead them to a specific page and tell the staff who scanned it. The reminder text the day of an event. The pastoral check-in that needs to land on a specific person's task list before Friday.
Most churches piece this together with three or four tools. An email service for broadcasts. An automation service for follow-ups. A QR generator for printed materials. A task tool for pastoral follow-up. Each one is a subscription. None of them talk to the CRM. None of them know that the visitor who scanned the QR on Sunday is the same person who clicked the welcome email on Wednesday and ended up on a pastoral follow-up list on Thursday.
Email Studio + QR Codes is the communications toolkit, built as one workspace. The email builder, the workflow engine, and the QR generator all run off the same CRM. A QR scan is an identified action. A workflow can fire from a form submission, a member milestone, a giving event, or a QR scan — and route a follow-up email and a pastoral task in the same motion. Communications stops being a stack of subscriptions and becomes a coherent practice.
Brand once. Send for years. Every email feels like the church.
The email builder uses a visual editor that any communications director can drive — no HTML, no CSS, no “why does this look broken in Outlook” debugging session. Brand the templates once with your logo, your colors, your typography, your standard footer. Every broadcast pulls from that brand. The Sunday recap looks like the church. The midweek devotional looks like the church. The event announcement looks like the church.
Templates are scoped per ministry or per series, so the worship team's newsletter can have a slightly different palette than the kids ministry's parent updates — without breaking the overall brand. Sends preview across desktop and mobile before they go.
- Drag-and-drop visual builder, no HTML required
- Branded templates per ministry, per series, or per cadence
- Desktop + mobile preview before send
- Segmented sends — by ministry, by tag, by lifecycle stage, by attendance pattern
A trigger. A condition. An action. Real automation, written like sentences.
When a visitor fills out the welcome card, three things should happen automatically: a welcome email goes out, a task lands on a pastor's to-do list, and the person's lifecycle stage moves from “first-time visitor” to “new contact.” In most churches, two of those three happen — the third gets dropped because nobody's system enforces it.
The workflow engine makes the third one happen. Workflows are visual rules: when [trigger], if [condition], do [action] — and actions chain. A single workflow can send the welcome email, create the pastoral task, update the CRM tag, schedule a follow-up email seven days later, and add the contact to the next new-members cohort. The communications director writes the rule once, and the rule runs forever.
- Triggers: form submission, giving event, milestone, QR scan, lifecycle change, event attendance
- Conditional branches — different follow-ups for different audiences
- Chained actions: email + task + CRM update + scheduled future step
- Visual builder; no scripting required
Every QR is a measurable scan, tied to a real person.
The QR code on the back of the bulletin isn't a static image generated from a free website. It's a trackable redirect — every scan is logged, attributed to a member if they're signed in, and surfaceable as the trigger for a workflow. Generate a QR for an event registration, a giving page, a welcome form, a sermon, a visitor card, a guest survey — anything you'd normally print a URL for.
QR codes carry styling — your logo in the center, your brand color, your preferred error-correction level. They can rotate destination over time (the Sunday-morning bulletin QR points at a different page each week without reprinting). And they show up in analytics next to your email opens and your event registrations — measuring the printed half of your communications the same way you measure the digital half.
- Trackable redirect per QR — every scan logged with attribution
- Styled QRs with logo, color, and error-correction control
- Rotating destinations — change where the same printed QR points to over time
- Workflow trigger on scan — the QR is part of the automation
The communications stack, in one workspace
Everything the communications director was paying for separately.
Broadcast scheduling
Schedule a broadcast for a specific date and time, or send immediately. Recurring sends — weekly newsletter on Friday morning, monthly giving recap on the first — set once and run on their own schedule.
Smart segments
Segments aren't static lists; they're live queries. “Members who haven't attended in 60 days” updates automatically. “Parents of kids in 3rd-5th grade” pulls from the CRM live. Send to the segment, get who's in it today.
Deliverability hygiene
Authenticated sending, bounce handling, and unsubscribe flow are built in. List health metrics are tracked so the communications director knows when to clean a list before deliverability tanks.
Open + click tracking
Open rates, click maps, link-by-link performance — the same analytics standalone email tools offer, integrated with the rest of your church data. The members who clicked the giving link in the newsletter show up tagged accordingly.
A/B test sends
Run a subject-line test on a slice of the list, send the winner to the rest. Same flow for preview text, hero image, or CTA copy. Test what matters; measure what works.
Form-to-workflow pipeline
Every form on the platform can be a workflow trigger. Welcome card → welcome email + pastoral task. Volunteer interest → onboarding sequence. Prayer request → prayer team routing. The whole communications loop, automated.
One visitor, one welcome card, one connected follow-up.
Sunday morning, a first-time visitor scans the QR code on the back of the bulletin to fill out a welcome card. The scan is logged. The form submission triggers a workflow. Within five minutes, she receives a personalized welcome email signed by the lead pastor — with a link to her next suggested step (a women's ministry group, picked based on the demographic info she shared). At the same time, a task lands on the pastoral team's to-do list to follow up by phone or text on Wednesday.
Wednesday morning, the pastor sees the task. He sees the visitor's name, her email, her QR scan history (she's scanned three different bulletin QRs over the last month), and the suggested follow-up script. He calls. Marks the task complete. The workflow advances to the next step: an invitation to the women's ministry the following Sunday.
The visitor ends up at the women's ministry meeting. Joins a small group. Three months later, she's teaching kids ministry. Every single step was tracked, every email tied to a real person, every action attributed back to that first QR scan on the back of a bulletin.
That's communications doing what communications is supposed to do.