Lifted Prayers FAQ — WordPress Prayer Wall Plugin Questions

One license covers one production church website: the full plugin, a year of updates and support, and license management from inside your own WordPress admin. The plugin keeps working even if you don't renew — what lapses without a renewal is the safety net: security patches, compatibility updates, bug fixes and support. There's a 14-day money-back guarantee, no explanation required. Testing on a local environment or staging copy of your site doesn't count against the one-site license — set up and try it before pointing real traffic at it.

No. Installing it is a standard WordPress plugin install — upload, activate, and it adds its own settings pages to your admin menu. Setup is a short walk through real decisions rather than code: pick a Prayer Atmosphere palette, set your notification email, adjust category labels if needed. Placing it on a page is a shortcode or block, and it inherits your site's fonts and reading width automatically. Developer help earns its keep only at the edges — a heavily customized theme, a multisite network, or wiring submissions into some other system you already run.

Yes — through thirteen curated Prayer Atmosphere palettes (Appearance settings), each already checked for readability and internal harmony, rather than an open color picker that could accidentally produce a jarring result. Switching palettes is purely visual: it never touches an existing request or the moderation queue, so it's safe to try one, sit with it, and change your mind. If none of the thirteen quite fits a very specific brand color, get in touch — it's not a free-form setting, but we're not precious about it either.

Not as an automatic bulk import, and that's usually the right call rather than a limitation — an old request carries a kind of consent tied to a specific moment and informal norms that a mass import can't safely carry forward. What works better is a clean cutover: pick a date, direct new requests to Lifted Prayers from then on, and re-enter by hand the handful of genuinely still-active needs your team is still walking with. If you have a large, genuinely active volume that needs to move over, contact us — we won't leave you to sort it out alone.

Nobody, at first — it sits in a moderation queue visible only to your assigned care team, not the wider congregation. The person submitting chooses the sharing level themselves (team-only, anonymous, or named), and that choice defaults to the most private option unless they actively choose otherwise. A member of your care team reviews it before anything can reach the congregation, and can keep something team-only even if it was marked shareable. Only after that review does anything reach the public prayer wall, and only at the visibility level the requester chose.

The request lands in a moderation queue inside WordPress — not on any public page. Someone on your care team reviews it: deciding whether it's ready to share at the level requested, whether it needs a private conversation first, or whether it should stay quietly team-only. How quickly that happens depends on how often your team checks the queue, not on any fixed schedule the plugin imposes. Once approved, a shareable request appears on the prayer wall exactly as the person chose — anonymously or by name — and prayers for it are logged quietly, not displayed as a counter.

Both. If someone opts into follow-up when submitting, your care team gets a way to return to them later — a private note, a check-in — that stays visible rather than disappearing the moment the request is approved. It's deliberately not automated: no timer-based email sequence, because the moment follow-up feels automated, it stops feeling like care. The tool creates the opportunity and the reminder; a person still decides what to say and when. Someone who didn't opt into follow-up gets none — their original terms hold.