Ask Pad
Pad is PraisePad's AI assistant. Ask in plain words about Sunday, the songs, a sermon, or how to do something.
Open Pad with the button (or press ? on a keyboard), or from the line at the top of Home. Type your question the way you'd ask a friend. Pad answers from your church's pages and from PraisePad's help, with the steps, where the answer came from, and a button that opens the right page.
Asking
- Open Pad from the button, from the line on Home, or from your account menu.
- Type your question, like "Who's on Sunday?", "Who leads Cornerstone, and in what key?", "Which song has the words 'my anchor holds'?", or "How do I set a capo just for me?"
- Press Enter, or the arrow button.
Ask about any day: "last Sunday", a date, "Easter", "Pentecost", "Thanksgiving", "this month" or "last year". The answer says which day it read, so you can tell it read you right. A count like "most sung" or "led the most" counts a day once, even when a song was sung at two services that day.
The "Try asking" chips are good first questions for your role. On Songs, "Which song has the words…" puts the start of the question in the box, ready for the words you remember. On the schedule, Staff get "Who's away on Sunday?" and "Who could cover…", which waits for the spot and the day. On Services, Staff get "Build me a set about…", which waits for the theme; on People, "Who hasn't accepted their invitation?"; in Present, "How many pictures can we still make this month?". You can ask a follow-up; choose for something new. On a lesson in Learn your part, the box says "Ask Pad about this lesson…", and the answer starts from that lesson.
If the answer mentions something only Staff or admins can do, it says so, and what you can do instead.
Past conversations
Pad keeps your conversations for you for 90 days, so you can go back to one and carry it on. See Go back to a conversation with Pad.
What Pad reads
In the app, Pad reads the pages you can already open, as you:
- Your schedule and open spots; how many times you've served and where, and when you last played (counted as the serving report counts: services you said yes to, once each); your own time away, and whether you're free on a day. Who's on a service, past or coming. Set lists once they're published (Staff see drafts too), past ones too, where your teams see service plans: for a Speakers team, each song by its title only.
- For the band and the tech team (and Staff and up), the songs' keys, tempos and CCLI numbers; who has led each song and how often; what your church sang over any time, and which songs were new. They can ask who led the most songs, who leads a song most, or what someone has led. A guest who led a song is named as a guest. Someone whose teams don't see the songs, like a greeter, hears who they're for, and that their Sundays are on their schedule; Home's line for them reads "Ask Pad about Sunday or your schedule…".
- Who's away on a day: Staff see everyone, a team's Team Leaders the people on their teams, and everyone else their own and their household's. Pad says whose it read, and only the dates: never why.
- Who could cover a spot: your own on a day ("Who could cover my spot on Sunday?"), or for whoever schedules it, any spot or an open one ("Who could play bass on the 15th?"). Each person is free, away, already on, or can't be asked, never why. Pad points you to the screen to ask them; it never asks anyone itself.
- For whoever records it, whose requirement, like a background check, ran out or runs out in the next 60 days: names and dates only. For Staff and Team Leaders, the serving report: who served most, and who hasn't served lately.
- Attendance as counts, with the same Sunday or weeks a year before, for Staff, admins and anyone with People access.
- A song from a line of its words: Pad names the song and the part it's in, and the line from your chart shows under the answer. Pad never reads a chart's words or writes them out.
- Published sermons and their words, people as the People page shows them, and Learn.
- Once a version is approved, What we believe, as your team's page shows it, for everyone who can open that page (below).
- The church's coming events; for Events Directors and an event's organizer, how many signed up, never who.
- On the Kids and Giving teams, counts and totals only, and a time against the year before ("Is giving up from last year?"). Owners and admins can ask about billing.
- For Staff and admins, who's been invited and hasn't joined yet: when it was sent, and whether it ran out or the email bounced. Pad never shows their email address. Each one opens the person's page, where or is; Pad never sends an invitation.
- For whoever can make pictures (owners, admins, Staff, and the people who run Present's slides), how many pictures and moving backgrounds Present can still make this month with AI, and when they start again: the same count Make a picture shows.
- For owners and admins, how many times your church's website was opened this month and by about how many people, its pages, and the gifts started there: counts only, as Settings › Website shows them, with two-step sign-in. Pad sees this month so far.
A set started for you
Ask "Build me a set about grace" (or "…for Easter Sunday"), and Pad picks songs from your library tagged with that theme, songs the team knows and hasn't sung for a while first (a song you've never sung only when there aren't enough), never one already on the plan, up to 12, set in the service's flow by each song's feel, like Fast to slow, each with why: "Tagged grace · last sung Aug 16". The picks go by your tags and by when you last sang each song, and use none of your AI allowance.
For Staff, when the service's plan isn't published yet, opens the plan with Suggest songs showing Pad's picks, all ticked. Untick any you don't want, then "Add 3 songs to the plan": they go where the worship goes (under your Worship heading, or before the message), in that order. Nothing goes on the plan until you press Add; close it, or reload the page, and nothing changes. opens Suggest songs' own form instead. Team Members see the songs without the button. If nothing in your library has that tag, Pad says so: Suggest songs picks by meaning instead.
It never reads private notes, a child's details or a giver's gift, why someone is away or said no, or a requirement's note or document, and it never sends or changes anything. When nothing covers the question, it says so, and names who in your church, or which page, can help. Owners and admins can turn Pad's reading off under , in ; then Pad answers from the help only, as it does on the help site and our website.
What your church believes
Once a version of What we believe is approved, ask "What do we believe about baptism?" and Pad answers with your church's own sentences, word for word, in quote marks: "Here's what Grace Church says about baptism:", the quote, Open what we believe, which opens that topic, and a line like "Approved by Grace Church, version 3". PraisePad puts the sentences in itself, so Pad can't change a word, and it never says a belief in its own words, argues, compares churches or works out what your church might believe. A topic your church marked to ask a person gets "That's one to ask Pastor Matt about." One it hasn't written about gets "Grace Church hasn't written about that in what it believes. Ask a pastor.", and the people who look after it also see Add it to what you believe. Pad never reads the draft.
Pad's answers also take your church's tone and its own words from How we sound, like "guests" instead of "visitors", and still keep to Pad's rules: short, plain, and the steps first. Pad in PraisePad's help centre and on PraisePad's website keeps PraisePad's own voice.
Pad is an AI, not a person. Apart from your own past conversations, of what it reads for you PraisePad keeps only that it looked and at which pages; questions answered from the help are kept for 180 days. See Your privacy.
When Pad can't answer
For a question about your church that Pad can't answer, it names who in your church can help, since the PraisePad team can't see your church's plans. Under that answer, and after a thumbs down on any answer about your church, one line offers . It opens a small sheet with your question (and the one before it, for a follow-up) to read over and change: leave out names and anything personal. Only your question goes, with the pages Pad tried; Pad's answer stays here. Send turns into "Sent ✓", and stays that way in the saved conversation.
When Pad can answer it, you hear back in Pad: "Pad can answer this now", with your question and , which puts it in the box. If it isn't something PraisePad will add, a line from us says so. The note shows once; puts it away. PraisePad keeps a sent question for a year, or 90 days after we reply. During a support visit, nothing can be sent. See Your privacy.
When you need a person
For a problem with PraisePad itself, choose at the bottom of Pad's panel. Your questions to the help go along, so you don't have to explain again. Our reply comes to Pad's panel while you're there, and by email if you're away. On the help site and our website, it's under the answer, and we reply by email. See Report a problem.
Answers from the help ask "Did this help?". Your thumbs up or down help us write better help.
Want something PraisePad doesn't do yet? Under that line at the bottom of the panel, opens Requests, where you can ask for it and vote for what other churches asked. See Ask for what PraisePad doesn't do.
Open in PraisePad to try it