Help
What to check, in the order that usually fixes it.
Three things: your church details and timezone, a few facts for the assistant to answer from (service times, where to park, what happens with children), and your first guest.
Then send yourself a test. On the last setup step there is a button that sends a real text and a real email from your church's own number and sender name. If both arrive, everything a guest will receive works.
That is normal for the first few minutes after signing up, and it is ours to finish, not yours. We retry it automatically, including if a step fails.
If it is still saying that after a day, that is not expected — get in touch and we will look at the provisioning directly.
From your church profile first, then optionally from your own website if you connect it. If neither answers a question, it says so and offers to connect the person with your team — it will not guess.
So the fastest way to improve its answers is to add the question to your church profile. That takes priority over anything on your website.
Check their record first. If the channel shows as declined, no text can be sent — they either did not tick texts on your guest form, or they replied STOP. Neither is something to override.
If consent is fine, check the message itself on their timeline: it records whether it was sent, delivered, or failed, and why.
Not from your side, and deliberately so. They can start again themselves by replying START. Adding them back by hand would be exactly the thing the law and the rest of this product exist to prevent.
The fixed ones, yes — the Sunday thank-you and the following-Sunday welcome-back are your wording. The Monday check-in and Friday invitation are written for the individual guest, so you set the objective rather than the sentence.
Each of those steps has its own on/off switch in settings. If a step is off, nothing is sent and the sequence simply moves on.
If both are on, check the guest consented to email — the same rule as texts.
Set a reply-to address in settings and replies go straight there. Leave it blank and they come back through SundayLoop, where the assistant keeps answering them.
Worth knowing early rather than late, which is why the setup test sends you a real one. The usual cause is a brand-new sending reputation, which improves as real mail is delivered and opened.
AI Calls is a paid add-on. Without it, that Wednesday step sends a short devotional email instead — that is working as intended, not a failure.
With it on, a call still will not be placed outside your calling hours, or to a guest who did not consent to automated calls. Both are shown on the guest's record.
Yes. Everything else in the week runs unchanged, and Wednesday falls back to the devotional email.
Settings, then invite them with a role. Church admins get everything; staff get guests, conversations, tasks and the church profile; volunteers see guests and tasks and work their own follow-ups.
We show you what adding someone changes about your bill before it happens.
Deactivate them rather than deleting them. Their history stays intact and they immediately lose access.
Follow-up for the guests you already have keeps running and your team keeps full access. New guests stop being added until the next period or a plan change.
You will see it in the app, and follow-up keeps running for a grace period while you fix it. Update the card from your billing settings — it opens your own portal, where you can also change plan or cancel.
Delete them from their own record. That removes the person and their messages rather than hiding them.
Export every guest as a CSV from your account, any time, without asking us.
Still stuck?
Write to sundayloop.church@gmail.com. Tell us the guest’s first name and roughly when it happened — that is enough for us to find the exact message and what it did.