When the robot writes the reminder: AI and the image of God

A tool can draft the reminder and surface the name. It cannot show up. Presence belongs to the person who bears God's image, and software never will.

Key takeaways

• The image of God is the line. Genesis 1:27 says people are made in God's image. That gives every person a dignity, and a capacity for relationship, that no tool shares. Software can prepare; only an image-bearer can be present.
• Drafting is not caring. A tool can write a reminder, surface who looks isolated, and clear the busywork. The phone call, the visit, the meal, the prayer: those stay irreducibly human.
• FlockConnect's assistant, Collie, is advisory by design. It surfaces and drafts. It never sends a message, writes to a record, or changes anyone's care on its own. A person reviews and approves every action.
• The point of clearing the busywork is presence. Time a pastor does not spend hunting through systems is time freed for the one thing only a person can do: show up for another person.
• This is an old conviction, not a new worry. The church has always said people are sacred because they bear God's image. A reminder tool does not change that. It just hands the pastor back the hours to act on it.

A robot can write the reminder

Picture the small, ordinary task. A family has not been seen in three weeks. Someone should reach out. Before that can happen, a pastor has to notice the gap, remember the names, find the phone number, and recall what was going on the last time they talked. On a busy week, all four of those steps fail quietly, and the family slips further out of view.

A tool is good at the first four steps. It can hold the attendance pattern, flag the three-week absence, pull up the history, and draft a warm first line. None of that is the hard part of ministry. It is the part that keeps eating the hours that should go to the hard part.

So let the tool write the reminder. The interesting question is the one underneath it: why is everything after the reminder still a human job, and why should it stay that way? The answer is not nostalgia about technology. It is a claim about what a person is.

What Genesis 1:27 establishes

The Bible opens with a sentence that decides the whole matter. "So God created man in his own image, in the image of God he created him; male and female he created them" (Genesis 1:27). Theologians call this the imago Dei, the image of God.

Read it slowly and two things stand out. First, the dignity is universal. The image is not given to the impressive, the connected, or the useful. It is given to humanity as such, which means the quiet member at the back of the room carries exactly the same weight as the elder on the platform. Second, the image is relational. The God who creates is, in the Christian confession, a God of relationship within the Trinity, and the creature made in that image is built for relationship too. Right after this verse, God says it is not good for the person to be alone.

This is the foundation a tool cannot touch. Software can hold information and propose a next step. It does not bear the image of God, it is not owed the dignity that comes with the image, and it cannot stand in the relationship the image was made for. When a person reaches out to another person, image meets image. That meeting is the actual substance of care. Everything a tool does is preparation for it.

Presence is the thing that cannot be delegated

C.S. Lewis, in a sermon collected in The Weight of Glory, presses how heavy an ordinary person really is. He writes that there are no ordinary people, that "you have never talked to a mere mortal," and that the dullest, least interesting person you can meet is a being of staggering and eternal significance. His point is moral: the way to treat someone who carries that kind of weight is with real attention, real presence, the whole of yourself turned toward the whole of them.

That is precisely what no tool can give. A drafted message can carry information. It cannot carry attention, because there is no one inside it doing the attending. When a pastor sits in a hospital room, the value is not the words. It is the fact that a person who bears God's image chose to be there, with this other person who bears it too. Take the human out and you have not made the care more efficient. You have removed the care and kept the envelope.

This is why the right line to draw is not "use the tool less." It is "use the tool for exactly the work that is not presence, so the presence has room to happen." Let the tool carry every part of the preparation. The showing up never moves off the pastor's desk.

How this shapes FlockConnect's assistant

FlockConnect is a Church Relationship Manager, a ChRM, built to help a pastor see who is connected and who is drifting. It works alongside the systems a church already runs. The assistant inside it is named Collie, and the imago-Dei conviction is the reason Collie is built the way it is.

Collie is advisory. It surfaces who looks isolated, and it can draft a note or a suggested next step. Then it stops and waits. It does not send the message. It does not write to a record. It does not change anyone's care on its own. A person reads what Collie surfaced, decides whether it is right, edits the draft to sound like themselves, and chooses whether to act at all. The tool prepares; the human is present.

That boundary is not a limitation that better engineering will someday remove. It is the point. The moment a tool sends a "thinking of you" message by itself, the message becomes a fiction, because no one was actually thinking of anyone. People can feel the difference between a note someone meant and a note that arrived because a threshold tripped. The first is care. The second is the appearance of care, and the appearance is worse than silence, because it teaches a person that the relationship is automated.

So Collie's job is narrow on purpose: get the right person in front of a pastor at the right moment, with enough context that the pastor can act quickly. The pastor does the rest, because the rest is the part that requires an image-bearer. For the working definition of the relationship Collie is trying to protect, the companion piece on what a church connection is is the place to start.

The temptation worth naming

Every tool that handles the busywork creates a quiet temptation: if it can draft the message, why not let it send the message? If it can surface the isolated person, why not let it reach out? The logic of efficiency runs straight toward automating the care itself, and it is worth saying plainly why a church should refuse that road.

Automating the reminder saves time. Automating the relationship destroys the relationship, because a relationship is the thing two persons do, and a tool is not a person. The category that protects against the slide is the one Genesis 1:27 names. People are image-bearers. They are not data points to be processed, and care is not a workflow to be optimized to zero human steps. A church that forgets this will eventually treat its people the way its software treats its records, and the people will feel it long before anyone can name it.

This is the distinction worth keeping. AI in ministry is not mainly a question of how much to use. It is a question of where the line falls, and the line is simple: the tool's work ends at the draft, and the relationship begins where the tool stops. A fuller version of why community cannot be outsourced to technology is the subject of a companion post on the AI question churches are getting wrong.

What this looks like on a Tuesday

The doctrine cashes out in something very practical. A pastor opens the week and sees that a tool has already done the noticing. Three families have gone quiet. One new member is at week six with no group yet. A longtime member's last contact was a hospital visit that no one has followed up. Each of those would have taken an hour to dig out by hand, and most weeks the hour was not there, so the digging did not happen and the people stayed invisible.

Now the surfacing is done in seconds, and the drafts are sitting ready. The pastor reads them, deletes the two that do not fit, rewrites one to mention the thing the family is actually walking through, and picks up the phone. The tool gave back the hour. The pastor spent it on a person. That is the whole design, and it is the imago Dei working itself out in a calendar: the busywork goes to the machine so the presence can go to the people who bear God's image.

About the author

Michael Tribett is the founder of FlockConnect, a Church Relationship Manager built to help pastors see who is connected and who is drifting. He holds a Master of Divinity in Christian Ministry from Southeastern Baptist Theological Seminary, where he focused on missions and discipleship, and he serves as a small group leader at his church in the Raleigh, North Carolina area. FlockConnect is an official Planning Center partner.

Frequently asked questions

Can AI replace pastoral care? No. A tool can draft a reminder, surface who looks isolated, and clear administrative work, but it cannot be present. Genesis 1:27 grounds why: people bear the image of God and are made for relationship, and care happens when one image-bearer turns real attention toward another. A tool has no one inside it to do the attending.

What does the image of God have to do with technology in church? It draws the line. Because people bear God's image, they carry a dignity and a capacity for relationship that software does not share. That makes presence, discernment, and showing up irreducibly human, while preparing the ground for them can safely go to a tool.

Does Collie send messages or contact members on its own? No. Collie is advisory. It surfaces who looks isolated and can draft a note or a next step, but it never sends a message, writes to a record, or changes anyone's care by itself. A person reviews, edits, and approves every action.

Is it wrong for a church to use AI tools at all? Not at all. The question is where the line falls. Using a tool to handle the preparation frees a pastor's time for the work only a person can do. The problem is not using the tool; it is letting the tool stand in for presence.

Why not let the software send a caring message automatically? Because a message sent without anyone meaning it is the appearance of care, not care. People can tell the difference, and a relationship that is quietly automated stops being a relationship. The draft saves time; the sending should stay with a person who actually chose to reach out.

What is the difference between a ChMS and a ChRM here? A Church Management System keeps records and runs operations. A Church Relationship Manager like FlockConnect works alongside it on the relational layer, surfacing who is connected and who is drifting so a person can act. Neither replaces the pastor; both serve the human work.

How does FlockConnect handle pricing? FlockConnect is priced by church size, not by staff or volunteer seats, with a free trial. The people who serve a church are never the line item.