Guided beta for church communications teams
Church communications, without the chaos.
Church Comms Dashboard gives your team one calm place to collect requests, plan the week, prepare drafts, review changes, and verify what happened next. The hosted workspace is the source of truth; WordPress and Squarespace connect when your website needs to participate.
Request-only access is open while we finish guided beta. Submitting the form does not create a workspace, subscription, or charge.
Where CCD is right now
We are building the communications loop before opening the doors wider.
CCD is in guided beta. The hosted app, WordPress connector, request forms, review paths, Phoebe-assisted drafting, pricing structure, and support/onboarding pages are in place. Public self-serve signup remains closed until the end-to-end workflow, tenant isolation, support, billing lifecycle, and approval/readback gates are proved enough to trust.
Now: guided beta and request intake
Churches can request access. Approved testers get guided setup, safe testing boundaries, and a simple first-workflow path.
Next: one complete communications proof
We are proving that one real request can become a plan, draft/output package, approval trail, and readback receipt without losing source facts or skipping human decisions.
Later: careful channel and calendar integrations
Email, SMS, social, Planning Center, liturgical calendar, Worship Guide, and Squarespace work should connect only when the approval, data, and verification model is ready.
The bigger vision
A communications source of truth for churches, not another place to lose tasks.
The long-term goal is a calm operating layer for church communications: requests, people, follow-up, calendar context, Worship Guide planning, brand memory, source assets, channel packages, approvals, and verified outputs. CCD is Episcopal-first in its first maturity path, with language that can adapt for other mainline and liturgical churches over time.
1. Catch the ask
- Staff portal and site-native intake
- Requester, ministry, channel, date, and context together
- Missing-info checks before work drifts
2. Plan the next move
- Open requests, source assets, dates, and owners stay visible
- Calendar and Worship Guide context can shape the package
- Phoebe can summarize, rewrite, and draft with human review
3. Verify the closeout
- Approvals stay connected to the request
- Channel packages show what is ready and what is not
- Readback receipts keep people from wondering what happened
What teams use most
The daily tools are big. The risky actions stay gated.
The Command Center keeps the highest-value work front and center: Requests, This Week, Review Mode, Phoebe, source assets, and follow-up. Sending emails, publishing pages, changing billing, writing to Planning Center, or touching provider accounts should stay approval-gated until the church can see exactly what will happen and what happened afterward.
Turn announcements, page edits, stories, events, design needs, and “can you post this?” moments into one queue.
See what needs a target date before it drifts, then move requests toward the channels where they belong.
Unite reviewers around specific page notes, content feedback, photo decisions, and approval trails.
Use draft help for summaries, missing-info checks, rewrites, and first-pass copy while staff keeps final approval.
Keep voice guidance, logos, colors, photo rules, SOPs, deadlines, and approved files where people can find them.
Give the team a verified closeout instead of another thread asking whether anything happened.
Connected, not reckless
The SaaS app is the product. Website connectors help when the site needs to participate.
CCD should connect to the tools churches already use, but connection does not mean automatic action. WordPress is active in private beta for intake, review, and handoff work. Squarespace starts with embedded intake, review links, staff access, and copy packages instead of pretending it has a WordPress-style plugin.
Hosted command center
Requests, planning, drafts, people, Phoebe, roles, approvals, and receipts belong in the SaaS workspace.
WordPress connector
The free plugin remains maintained for WordPress-native intake, Review Mode, Gravity Forms routing, and content handoff.
Squarespace pilot path
Squarespace support is in pilot shape for intake and copy-package workflows, not a finished installable connector.
Provider integrations later
Email, SMS, social, Planning Center, Drive, Canva, ads, and reporting should connect only when approvals and readback are trustworthy.
Want to test it on a real church workflow?
We are inviting a small group of churches, nonprofits, denominational teams, and trusted agencies to test CCD with ordinary ministry communication work: requests, reviews, calendar planning, source assets, first drafts, approvals, and follow-up.