One composer for a designed email or a text from your church's own number, to everyone or to one group. Audiences resolve out of your people data as you send. The count of who will be reached, who will be skipped, and why, is on the screen before anything leaves.
Often replaces a separate email platform, a texting product, and the audience spreadsheet beside them.
No credit card to start · 30-day trial of every module in the suite except Stewara Assistant. · See pricing
Email is unmetered. Texting is real per-message money, so it comes with an included monthly allowance and a hard cap, never a surprise bill. See the texting economics
Comms is one composer for a designed email or a two-way text, sent to everyone, a saved segment, a group's roster, or a hand-picked list resolved out of your people data as you send. Every merge field, template, reply and delivery status lands beside the member record it belongs to. Email is unmetered and goes out under your church's own name; texting is real per-message money, so it carries an included allowance and a hard cap.
{{firstName}} and {{churchName}} fill themselves in per person.
Nobody is skipped for consent on email: a church may write to its own people so long as every message can be unsubscribed from, and the footer below does that in one click.
Hi Taylor,
We are back in Colossians this Sunday, and the youth are serving coffee before both services. Come early if you can.
The nursery is open at 8:45. If you have not been in a while, there is no catching up to do. Just come.
An automation can never write its own words. It sends a template a person wrote. Nothing goes out before 9am or after 8pm local, no automation sends more than 200 times a month, and nobody receives the same one twice. Two triggers may never message anybody at all: a lapse in giving, and an overdue staff task.
Grace Harbor is our demo church, never a testimonial, and the roster numbers are invented. The machinery is not: the segment count, the price per segment, the monthly allowance, the text starters and the automation watchers on this page are the shipped ones, imported and run here.
Send it from the same record.
Start your 30-day trialEveryone, a saved list, a group's roster, or a handful of people you name. Every audience is resolved out of Flock the moment you press send — status, lifecycle stage, group or tag — so it is never a spreadsheet somebody exported in March.
A drag-and-drop email builder with 33 starting points across eleven kinds of message and three looks, tinted from your own brand color — or a plain text from a pack of ten. Both merge each person's name in as they go out.
Email leaves under your church's own name over a verified sending domain: no DNS to configure and nothing to misconfigure into a spam folder. Text leaves from a toll-free number that belongs to your church alone, not a shortcode another church can get blocked.
STOP, START, JOIN and HELP are answered the moment they arrive, and a suppression always wins over anything else. The count of who will be skipped, and why, is shown before you press the button rather than explained afterwards.
Not until they've said yes. A text needs a confirmed opt-in on file — the TCPA, not our rule — and today that means the person texting JOIN to your church's number. Email is different: you may write to your own people as long as every message can be unsubscribed from, which is why the email count is nearly your whole roster and the text count is not.
No. Email goes out with your church's name on the From line over one verified Stewara sending domain, so there are no DNS records to add and nothing that can silently break your authentication. Members see your church; you see nothing to configure.
Every plan with Comms includes 2,500 message segments a month, roughly an all-church text plus everyday back-and-forth. A 160-character text is one segment; a single curly quote or emoji cuts that to 70 and costs two. The composer counts it with the same function the sender charges with, and when the month's segments are gone sending stops rather than quietly billing you.
Yes, replies land in a two-way inbox beside the person's record, not on somebody's personal phone. Replying to a thread a member started never needs a consent record; starting a new one does.
A first-time guest, a new group member, an upcoming birthday, somebody who hasn't been seen in a month — each can send a template a person wrote. Never before 9am or after 8pm, never more than 200 times a month, never the same message twice. Two triggers may never message a member at all: a lapse in giving, because it may be a job loss or a diagnosis, and an overdue staff task, because that is the staff's problem and not the member's.
No, and it is not part of any plan. Life-safety alerts are free to every church on Stewara, whatever you pay: a staff member or teacher holds a button for three seconds, and enrolled phones with audible notifications and fresh on-campus presence are eligible to alarm. The mobile app shows each phone's readiness so your church can check it and practice the response process before an emergency.
One audience, email or text, and consent that actually holds. Start your 30-day trial today: every module in the suite except Stewara Assistant, no card required.
Stewara