AI & Tech · Church Communications

Plan Your Church's Christmas Communications with AI in One Afternoon (Prompts Included)

You read the week-by-week Christmas plan, you nodded, and then you looked at your calendar and thought: when exactly am I going to write six emails, a page, ten days of captions and a volunteer schedule? It’s the week of November 16. The invite cards go out in two weeks.

Here’s the afternoon version. AI drafts the things; you make the decisions. By dinner you will have a calendar, an invite line, the page copy, the captions, the emails and the follow-up, all in your church’s voice, all waiting for your edits. Let’s go.

Before you type a single prompt

Everything good that comes out of an AI tool this afternoon comes from what you put in first. Spend fifteen minutes on three things.

The facts document. If you did the first week of the plan, you have it: the services, dates and times, the address and parking, what each service is like, childcare and ages, how long, what to wear, and the one-sentence reason a guest should come. If you don’t have it yet, write it now, in plain text, one fact per line. This is the only source the tool is allowed to use for facts.

Three voice samples. Copy three things your church has already sent that sound like you: a good email, a good Facebook post, a paragraph from the website. Paste them under a heading that says “This is how we write.”

The no-go list. Write, in the same document, what never goes in: no congregant names, no prayer requests, no giving records, no counseling notes, no volunteers’ phone numbers. The facts about your services are public. The facts about your people are not. (If your church doesn’t have a written rule about this yet, the AI guide has a one-page one you can adopt this week.)

Paste all of it at the top of a new chat, or save it in your tool’s project or workspace feature so every chat this season starts with it. Use whichever tool your team already has, ChatGPT, Claude or Gemini; the facts and the samples matter far more than the brand. Then add this line before every prompt below: “Use only the facts in the document above. If you need a fact that isn’t there, ask me instead of guessing. Write in the voice of the samples.”

Prompt one: the calendar

Using the facts document and the seven-week plan I've described (decide the facts, build the page, hand out invites the first week of Advent, widen the circle the second week, push hard the last ten days, thank guests within 48 hours), make a week-by-week communications calendar from November 30 to January 3. For each week list: the goal, every email, every social post with its date and one-line idea, every print piece, and who needs to approve what by when. Put it in a table I can paste into a spreadsheet.

Read it with your real calendar open. Move anything that lands on a day you know is impossible. This is the decision the tool can’t make for you: what your week can actually hold.

Prompt two: ten invite lines

Write ten one-sentence invitations to our Christmas Eve service for a neighbor who hasn't been in a church in years. Each must include the day and time and feel like it came from a friend, not a brand. No exclamation points, no "join us," no "you won't want to miss." Vary the tone from warm to plain.

Pick one. Maybe two. Read them aloud. The one that sounds like something you’d text a friend is the one. That line now goes on the card, the page, the emails and the social posts, word for word, so a guest sees the same sentence everywhere.

Prompt three: the Christmas page and its FAQ

Write the text for our Christmas web page using only the facts document. Order it the way a first-time guest asks: what time, where, what it's like, kids, how long, what to wear, parking, how to ask a question. Short paragraphs, plain words, the invite line we chose at the top. Then write a four-question FAQ in the exact words a guest would type into a search engine, with one- or two-sentence answers.

That FAQ is for people and for the search engines and AI assistants that answer “Christmas Eve service near me.” Last Friday’s post covers where that page needs to go once it’s written.

Prompt four: ten days of captions

Write social media captions for the last ten days before Christmas Eve, December 15 to 24, one per day. Each day answers one guest question: which service should I come to, can I bring my kids, where do I park, what's it like, who will be there, and so on. Two to four sentences each, our invite line and the page link on at least four of them, no hashtags, no exclamation points. For each caption, suggest the photo or short video a volunteer could take this week to go with it.

The photo suggestions are the quiet gift here. Hand that list to someone with a phone this Sunday and the pictures exist before you need them.

Prompt five: the three emails

Write three emails to our whole church list: (1) the week of November 30, announcing the services and asking each person to invite three people, with the invite cards mentioned; (2) the week of December 14, a personal note from the pastor with the times and one line about who to bring; (3) December 22 or 23, a short reminder with the times and the link. Each under 150 words, subject lines under 50 characters, one link each, written in the voice of the samples. Mark the pastor's email as a draft for the pastor to make their own.

The pastor’s email is the one the tool should never finish. Send the draft to them with the facts and let them write the one line that matters.

Prompt six: the volunteer messages

Write the messages for our Christmas Eve volunteers: a confirmation two weeks out with the date, arrival time and role; a reminder the Wednesday before; and a thank-you for the morning after. Warm, short, specific, no guilt. Leave a placeholder where each person's name and role go. Do not invent any names.

You’ll do the mail merge from your own list, in your own system. The tool never sees who the volunteers are.

Prompt seven: the guest follow-up

Write one follow-up message for a first-time Christmas Eve guest who gave us an email address or phone number, to be sent within 48 hours by a real person. Under 100 words, one thank-you, one next step (the first Sunday in January and a short new-here gathering), and nothing else. Give me an email version and a text version.

Write this one now, in November, and it only needs sending on December 26. That is how the follow-up stops falling through the cracks.

Prompt eight: what did I forget

Read everything we've made this afternoon as a church communications director with twenty Christmases behind her. What's missing? What contradicts the facts document? Where does the voice slip into sounding like a brand? What would a first-time guest still be confused about? Give me a short list, most important first.

This is the review step, and it catches real things: a time that drifted between the page and a caption, a childcare age range that disappeared, a sentence that sounds like a department store. Fix what it finds, then fix what it missed.

What you still do yourself

An afternoon with these prompts gets you drafts. Here is the part no prompt does.

Decide. Which services, which invite line, which days you can actually post. Read every piece aloud; your ear will catch what the tool’s can’t. Check every fact in every draft against the facts document, because a wrong time on Christmas Eve is the one mistake you can’t take back. Cut anything that sounds like marketing. And tell people where AI helped, the same way you’d credit a volunteer: a line in the staff meeting is enough.

That’s the rule I ask every church to hold, and it’s the whole point of this series: AI makes the things, people make the decisions. If you want to get better at the asking part, the art of the prompt is where I’d go next; if you’re worried about losing your voice along the way, this one is for you.

Block the afternoon. Gather the facts. Run the eight prompts in order. Then spend December doing the part only you can do: being the person who welcomes someone in.

<details>
  <summary>Can AI write our church's Christmas communications?</summary>
  <p>It can draft them. Give it the facts (services, times, address, what each service is like) and a few samples of how your church already writes, and it will produce a calendar, captions, emails and page copy in an afternoon. You still decide what goes out, check every fact, and rewrite anything that doesn't sound like you.</p>
</details>
<details>
  <summary>What should never go into an AI tool when planning Christmas?</summary>
  <p>Anything about a person. No congregant names, prayer requests, giving records, counseling notes or volunteer contact details. The facts about your services are public; the facts about your people are not.</p>
</details>
<details>
  <summary>Which AI tool should a church use for this?</summary>
  <p>Whichever one your team already has an account for. ChatGPT, Claude and Gemini all handle these prompts; the facts document and your voice samples matter far more than the tool.</p>
</details>
<details>
  <summary>How long does this actually take?</summary>
  <p>About three hours the first time: fifteen minutes to gather the facts and voice samples, an hour and a half running the prompts and editing, and the rest reading everything aloud and fixing what sounds off. The second year is faster, because you keep the facts document.</p>
</details>