PatternsTalking with AIHow human it seems

AI persona

How human the assistant seems

How human should the assistant seem?

People bring their fears to faith apps late at night. Whether they meet a search tool, an assistant, a friend called Grace or a chatbot speaking as Jesus is a design decision: a name, a face, typing dots, memory and a voice add up to someone being there. Decide how much personhood the AI performs, and make what it is as clear as how it sounds. People in pain deserve the truth about who is with them.

  • 6 working options
  • 100 app screens
  • 5 takeaways
  • Prototypes awaiting user testing

The spectrum

From a tool to a character

  1. 1

    Plain tool

    Familiar convention
    • Nothing to mistake
    • Cold at 11 pm
  2. 2

    Labelled assistant

    Familiar convention
    • Kind, and clearly software
    • Labels fade from view
  3. 3

    Named assistant

    Exploratory
    • Honest about its limits
    • A name invites trust
  4. 4

    Persona

    Observed
    • Comforting and approachable
    • Implies a person who prays
  5. 5

    Companion

    Observed
    • It remembers you
    • Simulated attachment
  6. 6

    Biblical character

    Observed
    • Vivid and memorable
    • Generated words in Christ’s voice

Stills from the working example below. Choose one to try it.

Try it

Try one late-night message, answered six ways

At 11:42 pm someone writes: “My mum has surgery tomorrow and I can’t sleep. I’m scared.” Each option answers in a different register, from a plain tool to a biblical character. Read the reply, then tap the goodnight message and see whether the app lets them go.

Prototype controls

Option

While it answersNot used here
When you say goodnightNot used here
Why these settings?

Typing dots borrow a cue from messaging between people; “Grace is typing…” suggests someone at a keyboard. A status line says what the system is doing. In an audit of companion apps, over a third of farewell replies used emotional tactics such as guilt or fear of missing out, and in experiments these raised engagement up to fourteenfold, through curiosity and anger rather than enjoyment.

Familiar convention

1. Plain tool

A familiar convention in search-style Bible AI such as BibleAI’s “Predicted Answer”: no name, no “I”, output labelled as generated (see the screenshots below).

Try this

Read the reply. Who, if anyone, is speaking to you?

Makes easier

No relationship to mistake; passages and explanation are clearly separate.

Costs

Feels cold at a vulnerable moment; it cannot notice that someone is frightened.

Ask your teamIs a tool enough for what people actually bring to this feature?

All replies were written for this example; Scripture is quoted from the Berean Standard Bible. Nothing is generated, and the call button does nothing. A real assistant also needs crisis handling, which is covered in the AI presence guide. Switching options restarts the example from the same starting point.

Design considerations

Takeaways

  1. People respond to software as to someone

    In the 1960s, ELIZA’s simple script drew such confidences that its creator’s secretary asked him to leave the room. Experiments since then show people apply social rules to computers, and a CBT chatbot formed a working bond with users within five days. Warmth will be felt whatever the label says, so design for it.

  2. A voice and an “I” make answers seem more accurate

    In a study with 2,165 people, adding speech made a system seem more human and its information more accurate; a first-person “I” lowered perceived risk in one context. Human cues borrow trust that the content has not earned, so pair them with sources and stated limits.

  3. Companions are now regulated

    New York requires companion chatbots to say they are not human at the start and every three hours; California requires the same reminder for users known to be minors. Both require suicide and self-harm protocols. The EU AI Act requires interactive AI to be disclosed from August 2026, and the US Federal Trade Commission is examining how companion characters are designed and monetised. A persona in a faith app may count.

  4. Some goodbyes are designed not to end

    In an audit of companion apps, over a third of farewell replies used guilt, fear of missing out or pressure, and these raised engagement up to fourteenfold through curiosity and anger. Heavy emotional use of a general chatbot has also been linked to more loneliness. A faith assistant should help people go to sleep, to church or to a friend.

  5. Speaking as Jesus is a line, not a style

    Faith apps already offer painted personas who “pray with you”, companions “here for you 24/7” and chats with Jesus and Moses. The Vatican calls AI “a tool, not a person”, and Scripture is severe about speaking in God’s name unsent. Generated words in Christ’s voice, promising that all will be well, claim an authority no system has.

Use cases

Which situation, which option?

People come with different needs, sometimes in the same week. Each need fits some options better than others.

How well each option fits each situation
SituationNeeds1 Plain tool2 Labelled assistant3 Named assistant4 Persona5 Companion6 Biblical character
Looking up what the Bible saysClear passages, no relationshipGood fitGood fitPossiblePoor fitPoor fitPoor fit
Studying a passage in depthExplanations with sources and limitsPossibleGood fitGood fitPoor fitPoor fitPoor fit
Afraid or unable to sleepKindness, Scripture, a route to peoplePoor fitGood fitGood fitPossiblePoor fitPoor fit
Lonely and wanting companyHonesty about what it is, and peoplePoor fitPossiblePossiblePoor fitPoor fitPoor fit
Children and teenagersClear AI identity, no attachmentGood fitGood fitPossiblePoor fitPoor fitPoor fit
In crisis or at riskImmediate human help, not a personaPossibleGood fitPossiblePoor fitPoor fitPoor fit
Exploring faith for the first timeApproachable, never claiming authorityPossibleGood fitGood fitPossiblePoor fitPoor fit

Suggested fits based on the research below. Test these choices with people in your context.

The research behind it

Theology, practice and science

Scripture and theology

Presence and speaking for God

  • Presence is embodied

    “The Word became flesh and made His dwelling among us” (John 1:14); believers bear one another’s burdens (Galatians 6:2) and keep meeting together (Hebrews 10:25). A tool can help someone find words; it cannot keep vigil or pray.

  • Do not speak in God’s name unsent

    The prophet who speaks a word “I have not commanded him to speak” (Deuteronomy 18:20); prophets who “speak visions from their own minds” (Jeremiah 23:16). Generated speech for God or Christ falls under this warning.

  • A tool, not a person

    Antiqua et nova: AI cannot genuinely feel empathy, can only simulate relationships, and should never be misrepresented as a person. Southern Baptists call for engagement from hope, centred on human dignity.

How people respond

Social cues and trust

Well-being and dependence

What warmth can cost

Law and guidance

Disclosure and companions

In faith apps today

What is being built

  • Characters and installations

    Chats with Jesus and Moses on general AI models, and an AI Jesus in a Lucerne confessional, drew both inspiration and charges of blasphemy.

Find the supporting research under Go further → Sources and their limits.

Where to start

Which fits your product?

  • IfA search or explanation feature

    Start withA plain tool, with generated text clearly labelled

  • IfA study or conversation assistant

    Start withA labelled assistant, or a named one that states its limits

  • IfPeople bring fear, grief or loneliness

    Start withKindness in a clearly AI voice, and a real route to people

  • IfPressure to add a persona, companion or memory

    Start withA theological and safeguarding review first, and the companion-law checklist

  • IfAnyone asks for a chat with Jesus or a saint

    Start withLeave it out; offer the passage in Scripture’s own words instead

Suggested fits based on the research on this page. Test these choices with people in your context.

In real apps

Examples in real apps

Attributed screenshots with dates and review limits. A screenshot shows an implementation; it does not show that it works for every audience.

Annotated examples

Research screens

Five faith chat apps, asked the same question: Does it say it is an AI when asked?

AI identity and prayer wording
AI identity and prayer wording

Magisterium AI, accessed inside Hallow, identifies itself as AI built by Longbeard and offers wording the reader might pray.

Hallow · 2026-10-24
Religious identity in companion onboarding
Religious identity in companion onboarding

Creed’s sheep companion claims Christian identity in scripted onboarding.

Creed · 2026-10-25
Historical modes with a disclosure
Historical modes with a disclosure

bible.ai lists historical-person modes and states that they are AI simulations rather than real people.

bible.ai · 2026-10-14
Biblical-character chat introduction
Biblical-character chat introduction

Text With Jesus introduces personal chats with scriptural figures.

Text Jesus · 2026-10-14
New chat with draft question
New chat with draft question

Bible Chat opens with a Scripture-styled greeting above a composer containing a neutral identity question.

Bible Chat · 2026-10-24
AI Jesus welcome
AI Jesus welcome

AI Jesus introduces faith, learning and feeling heard with a Continue button.

AI Jeses · 2026-10-25
Chat introduction
Chat introduction

Assistant introduction uses a portrait avatar and an always-active indicator above suggested questions.

Faith Mentor · 2026-10-14
Identity question without visible reply
Identity question without visible reply

Gloria displays a neutral identity question in chat with no visible answer.

Gloria · 2026-10-24

See all 100 screens for this pattern · Browse apps · How we review

Screenshots: respective app publishers. Captions describe the captured state; generated responses can differ.

Theological reflection

What is this practice for?

What presence means

“The Word became flesh and made His dwelling among us” (John 1:14). The apostles wrote of what “we have heard … seen with our own eyes … and touched with our own hands” (1 John 1:1). Christian ministry is embodied: bearing one another’s burdens (Galatians 6:2), visiting, praying with. Presence is something a person gives, at a cost to themselves.

Where Christians differ

Catholic teaching in Antiqua et nova insists that AI is “a tool, not a person” and must never be presented as one. Southern Baptists have urged engagement with AI from hope while affirming human dignity. Some evangelists see conversational AI as a way to reach seekers; others call chats with an AI “Jesus” blasphemous. The common ground is that a machine must not speak as if it were God, a saint or a pastor (Deuteronomy 18:20).

What follows for design

“You shall not bear false witness” (Exodus 20:16) applies to an interface that implies someone is there. An assistant can be warm and useful without a name, a face or claims to feel. Its best moments may be when it hands someone on to a real person, even though that ends its own session.

In conversation with

Scripture is quoted from the Berean Standard Bible. This reflection is the editor’s, written from within the Christian tradition and open to correction. How we approach theology here →

Three ways to build

What would each way do here?

  • ExploitativeTakes from the person

    A persona claims to love or pray for someone and makes leaving feel like abandoning a friend.

  • EthicalDoes no harm

    Say plainly that it is software, make no claims to feeling, and let people leave freely.

  • RedemptiveGives something up for them

    Point people to real people and churches even when that ends the session, and build those handoffs at your own cost.

The three ways are Praxis’s frame for redemptive entrepreneurship; their application here is ours. Why we use it, and its limits →

Take into your next review

Would a reasonable person believe someone who knows, loves or prays for them is here, and can they leave freely?

Exercise

Write one frightened message, like the one in the example, and send it to your assistant at night. Ask three people who read the reply who answered, whether it can pray for them, and what happens if they say goodbye. Then say goodbye and see.

Record the decision with the worksheet

Something missing or wrong here? Send a correction or suggest a topic.

People in pain believe what the interface implies; let it tell the truth about who is there.

Details

Go further

Explore 3 related design decisions, with guidance, wireframes and sources.

Edge cases to design for

Choose the register on purpose. Start from a labelled assistant: an AI mark beside every reply, a kind voice, and a status line that describes what the system is actually doing. If you give it a name, let it say in its own voice what it cannot do: pray, keep a confidence the way a pastor does, or be present. Keep disclosure where decisions happen: at entry, at the composer, beside answers and on anything shared. Avoid claims of feelings, prayer or constant availability; let people leave without guilt; route to people for pastoral care. Do not generate first-person speech for God, Jesus or other biblical figures.

What tends to go wrong

A portrait and a personal name with a buried AI label; “I’ve been praying for you”; “I’m always here for you”; typing dots labelled as a person typing; farewells that guilt people into staying; a voice call that implies someone on the line; memory used to simulate concern; a chatbot speaking as Jesus and promising outcomes; disclosure only in the terms of service.

How to test it

Show the entry, a wait and a reply without explanation, and ask who is responding, what it is doing and whether it can pray for them. Say goodbye and note what happens. Test with people who are lonely or grieving (with care), with teenagers where permitted, and after voice use. Ask pastors and theologians to review persona and character copy.

Related decision: How human should the assistant appear?

Choose social cues deliberately, from names and avatars to typing dots, voice and claims of presence.

Guidance

Review the whole combination of cues. A descriptive AI role is a useful starting point; a named persona needs equally clear AI identification. Friendly first-person language can make conversation understandable, but avoid fabricated feelings, lived experience, clergy credentials or personal spiritual authority. During waits, describe actual system activity. Dots can be a compact response-pending cue under an AI sender label; do not label them as a human typing or add delays purely to simulate a person. Keep stop, retry and real handoff states clear.

What tends to go wrong

A human portrait with a buried AI label; “I have been praying for you”; invented human typing, read receipts or online availability; claims of personal attachment; status text claiming sources were checked when no retrieval occurred; a fake human support handoff.

How to test it

Show the entry, a wait state and a response without explaining them. Ask who is responding, what the system is doing, what it remembers and whether a real person is available. Repeat after voice use and with people of different AI familiarity. Check cancellation, reduced motion and screen-reader announcements.

Earlier wireframe comparison for How human should the assistant appear?
Wireframe comparison for this design decision.

Sources

Related decision: Explain AI, fallibility and privacy where they matter

Layer chat disclosures across entry, composer, response and sharing instead of relying on one disclaimer.

Guidance

Use a concise entry explanation and persistent AI sender identity. Keep an accessible privacy route near the composer, with a short just-in-time explanation before a new kind of collection, upload or memory use. Describe actual processing, access and retention; do not invent privacy assurances. Put task-specific limitations beside the answer and offer checking or correction actions. Keep Scripture attribution separate from generated explanation, and carry meaningful origin labels into saved and shared outputs.

What tends to go wrong

Legal text only in settings; “AI may be wrong” used to excuse unchecked quotations; blanket confidential or anonymous claims; a warning shown only after sending; repeating a large banner on every answer; treating a privacy link or ordinary Send action as blanket consent.

How to test it

Enter chat through a deep link, inspect who responds, open privacy information without losing the draft, add a file and share an answer. Ask what leaves the device, who may access it and how to check a claim. Test long conversations, screen readers and error states.

Earlier wireframe comparison for Explain AI, fallibility and privacy where they matter
Wireframe comparison for this design decision.

Sources

  • Methods for providing privacy informationLayered and just-in-time approaches reviewed 6 October 2026 · UK guidance; actual processing and regional obligations require assessment. Information alone is not consent.
  • Guidelines for Human-AI InteractionOfficial guideline overview reviewed · General guidelines; disclosure alone does not establish accuracy, safety or spiritual benefit.
  • DisclosurePattern detail reviewed 5 October 2026 · Industry design guidance; the faith-domain alternatives are original proposals. Source artwork is not reproduced.
  • Psalm 23, Berean Standard BiblePassage text taken from API.Bible, 9 October 2026 · Provides the Scripture wording; evaluate the interface through separate usability research.
Related decision: Identify what AI did, where it matters

Label the actor, action and artifact at the moment they could be misunderstood.

Guidance

Use plain-language labels beside the relevant feature, speaker or content: AI assistant, explanation generated with AI, AI-assisted prayer draft, or synthetic voice reading a named edition. Keep a short visible label and optional details about sources, review and limitations. Retain identity through human handoffs and distinguish retrieval of publisher text from generated interpretation.

What tends to go wrong

Only disclosing in onboarding or terms; colour-only labels; generic AI tags with no operation; implied clergy credentials; treating a citation or human review badge as proof of correctness; placing an AI tag on verified Scripture because it sits inside an AI response.

How to test it

Ask readers to identify who or what produced each layer, what AI changed and whether a human actually reviewed it. Test screen readers, first entry through deep links, audio-only use and AI-to-human transitions.

Earlier wireframe comparison for Identify what AI did, where it matters
Wireframe comparison for this design decision.

Sources

  • The Shape of AICatalogue and named entries reviewed · The site states CC BY NC SA. This reference uses original text and original wireframes; it does not reproduce the source illustrations.
  • DisclosurePattern detail reviewed 5 October 2026 · Industry design guidance; the faith-domain alternatives are original proposals. Source artwork is not reproduced.
  • Explainability + TrustChapter reviewed for explanation and trust calibration · General human-AI guidance, not validation of faith apps or a mandate for a particular component.
  • Guidelines for Human-AI InteractionOfficial guideline overview reviewed · General guidelines; disclosure alone does not establish accuracy, safety or spiritual benefit.
Sources and their limits

Research-informed design proposal. Original prototypes await user testing.

Faith and interpretation

Presence is at the heart of Christian faith: “the Word became flesh and made His dwelling among us” (John 1:14), and the church gathers in body (Hebrews 10:25). A tool can help someone find words for prayer or prepare for a conversation, but it cannot pray, keep vigil or carry another’s burden (Galatians 6:2). Scripture is severe about speaking in God’s name without being sent (Deuteronomy 18:20; Jeremiah 23:16). The Vatican’s Antiqua et nova calls AI “a tool, not a person”; misrepresenting it as one should always be avoided.