Actions on AI answers

Copy, share, try again, report: which belong?

Under every answer, AI apps now offer a row of icons: copy, share, save, read aloud, try again, make it simpler, branch, double-check, thumbs up and down, report a legal issue. Each one makes a promise about where the answer goes, who sees the feedback and what the model did. In a Bible app, a shared answer can also be mistaken for Scripture. Each action is a chance to send people back to the text, or away from it.

At a glance

Four action bars, side by side

  1. 1Every action in a rowBorrowed Everything one tap away Fourteen unlabelled iconsTry it →
  2. 2Three, then MoreBorrowed The common three, clearly Rating is one tap furtherTry it →
  3. 3Actions on the passagesObserved Scripture is what travels Harder to keep the answerTry it →
  4. 4No action barLeave it out A quiet, reflective screen No way to report problemsTry it →

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

Try it

Try four ways to act on an answer

One answer about rest, four ways of offering actions on it. Try copying, sharing, rating and asking what the assistant did, and watch what each action says it will do.

Prototype controls

Option

Borrowed

1. Every action in a row

Borrowed from general AI apps: Gemini (good/bad, share and export, double-check, modify, report legal issue), ChatGPT (copy, read aloud, branch in new chat, try again) and Claude (copy, try again, thumbs with an issue type).

Try this

Without tapping, guess what each icon does. Then try Make it simpler, Read aloud and Report.

Makes easier

Everything is one tap away for people who use it often.

Costs

Fourteen unlabelled icons scroll off the side of a phone, and the ones that matter most look the same as the rest.

Ask your teamWhich three of these would your readers miss?

The same answer appears in every option. Actions are simulated: nothing is copied, shared, sent or stored, and read-aloud playback is shown rather than spoken, but each action shows the screen or message it would give. Switching options restarts the example from the same starting point.

What we noticed

Takeaways

  1. Two or three actions, the rest behind More

    Ten unlabelled icons are a puzzle on a phone. Most people need two or three actions; the rest are easier to understand as labelled rows behind “More”.

  2. What travels matters most

    A copy or share should carry the label and the references, so whoever receives it can tell generated interpretation from Scripture or a pastor’s words. Making the passage, not the answer, the thing people save and share is stronger still.

  3. Changing the answer needs care

    Try again can become shopping for the doctrinal answer someone hoped for, so keep every version visible and the original first. Simpler and shorter versions help readers at different levels. Checking quotations against the edition catches misquoted verses but cannot judge the interpretation.

  4. Feedback and “thinking” need honesty

    Thumbs should say who reads them and whether they train models. A list of steps should describe what the service actually did, such as searching and checking quotations, not present the model’s reasoning as proof. A report button needs a named owner and a response time.

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 Every action in a row2 Three, then More3 Actions on the passages4 No action bar
Reading an answer onceNothing in the way of the textPoor fitPossiblePossibleGood fit
Sending it to a friend or groupThe label and references travel with itPossibleGood fitGood fitPoor fit
Keeping it for later studySaved apart from their own notesPossibleGood fitGood fitPoor fit
The answer looks wrongA way to check or report, with a named ownerGood fitGood fitPossiblePossible
Wanting it simpler or shorterA new version that keeps the originalGood fitPossiblePoor fitPoor fit
Screen readers or large textFew, labelled actionsPoor fitGood fitPossibleGood fit

Editorial judgments drawing on the research below, not test results.

The research behind it

Theology, practice and science

Scripture and tradition

Holding answers lightly

  • Test, then keep what is good

    “Test all things. Hold fast to what is good” (1 Thessalonians 5:21). Checking a quotation, comparing versions and reporting a problem are ways of testing; saving and sharing are ways of holding fast, and should carry what was tested.

Research and guidance

What each action promises

  • Icons need words

    Few icons are recognised by everyone, and labels revealed on hover do not work on touch screens. Label the actions people need, and put the rest in a labelled menu.

    Aurora Harley

  • Say what feedback does

    Human–AI interaction guidelines ask products to make clear what the system can do, how well, and what happens when people correct it. Thumbs that train a model and thumbs read by a pastor are different promises.

    Microsoft HAX ToolkitGoogle

  • Regenerating can become shopping

    Assistants sometimes favour agreeing over accuracy; trying again until the answer agrees compounds it. Keep the original first and every version visible.

    Anthropic researchersITdaily

  • Checking changes trust

    People trust cited answers more, even with random citations, and less once they check. A check action that opens the verses builds the right kind of trust.

    Yifan Ding et al.

  • Overreliance is a known risk

    NIST lists overreliance among the risks of human–AI configuration. Actions that make an answer easier to keep and spread than to question add to it.

    NIST

Every source, with what it can and cannot show, is listed under Go further → Sources and their limits.

Where to start

Which fits your product?

These are editorial judgments from design review, not results of user testing.

In real apps

Examples in use

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

Explore the growing app-example collection

Theological reflection

What is this practice for?

What doing is for

“Be doers of the word, and not hearers only” (James 1:22). Reading Scripture leads outward: to prayer, to obedience, to other people. The disciples on the road to Emmaus, their hearts burning, went straight back to Jerusalem to tell the others (Luke 24:32–33).

Where Christians differ

Christians share Scripture in many ways: verse cards, tracts, social media, a text to a friend. Some traditions encourage personal sharing; others prefer that teaching come through the church. All would distinguish the word of God from commentary on it.

What follows for design

“Let him who has My word speak it truthfully. For what is straw compared to grain?” (Jeremiah 23:28). Let the passage, not the generated text, be what people save and share, and label everything else. The best actions lead out of the app: read the whole passage, pray, talk to someone.

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?

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

Which actions does this product need, and what does each one carry with it?

Exercise

Ask three people to name every icon before tapping it. Then copy and share an answer and look at what arrives on the other end, and ask each person who they think reads their thumbs down.

Make the text easier to keep and share than the answer about it.

Record the decision with the worksheet →

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

Details

Go further

Edge cases to design for

Decide which actions this product needs. Keep two or three visible and put the rest behind “More”. Copy and share carry the AI label and references; saving to notes keeps AI answers apart from the reader’s own words; feedback says who sees it and whether it trains models; try again and simpler versions keep the original and let people compare, because regenerating until a preferred doctrinal answer appears is a real risk; checking quotations compares every quotation with the edition; “what the assistant did” lists real operations rather than private reasoning; reporting routes to a person with a stated response time. Consider putting actions on the Scripture objects instead, so the passage, not the generated text, is what travels.

What tends to go wrong

Icon-only rows without accessible names; a copy that drops the AI label; thumbs that silently feed training; “thinking” presented as proof of correctness; a report button with no stated owner; sharing generated interpretation as if it were Scripture.

How to test it

Ask people to say what each icon does before tapping it. Copy and share an answer and check what the recipient sees. Rate an answer and ask who they think will read the rating. Compare a full row with three actions plus “More” for findability and errors.

Sources and their limits

Editorial design proposal. Editorial review, not user validation.

Faith and interpretation

What travels beyond the conversation matters. A shared answer may be read as Scripture, as the church’s teaching or as a friend’s counsel. Letting the passage, rather than the generated text, be the thing people save and share keeps the Bible and its interpretation distinct.