An announced boundary
The Seventh-day Adventist General Conference announced AKAI and Adventist+ at its October 13 Annual Council session. Its news service, ANN, describes AKAI as a church-information tool drawing on the Bible, the Encyclopedia of Seventh-day Adventists and the denomination’s 28 Fundamental Beliefs. It reports a demonstration in which answers linked to encyclopedia articles.
The consequential boundary concerns prayer. Organizers say AKAI is not the church’s official voice or a spiritual authority: requests for prayer should connect users to a person. Adventist+ is intended to combine Bible reading, media and conversation.
Availability needs careful wording. The ANN page inspected for this brief says both apps will launch in 2027, while also reporting a promise to integrate AKAI into the encyclopedia the following week, initially in English. Those are distinct announced milestones, not independently confirmed completion dates. Source: adventist.news
What would make a referral useful?
The practical distinction is between answering a question and accepting responsibility for a person. A citation can help someone examine a factual answer. A referral needs someone available to receive it.
Earlier reporting by Amanda Blake in the May–June 2026 Visitor described AKAI as a project in development. Richard Stephenson said it would be terminated if it proved unreliable or could not consistently provide representative, factual answers. The same report included Adventist educator Adam Fenner’s warning against replacing an existing human ministry relationship with AI. These are attributed commitments and judgments, not evaluation results. Source: columbiaunion.org
For a church considering a similar service, we propose a simple, hypothetical check: ask a volunteer to follow a referral using a fictional, non-sensitive request. Can the volunteer tell when a human takes over, what information is shared and what happens if nobody is available? The point is to inspect the transition before inviting people to entrust it with personal concerns. This is our suggested exercise; we have not tested either announced app.
The announcement does not provide staffing coverage, response-time evidence or a retention policy for these conversations. A ministry should explain those arrangements and offer a direct route to a person before presenting automated referral as dependable care. That is a question for implementation, not evidence that the announced service has failed.
A Christian perspective
Galatians 6:1–5 places mutual burden-bearing alongside gentleness, self-examination and personal responsibility. Paul is addressing how members of a community treat one another, not specifying a technology policy. Applied here, the passage asks what happens after a request reaches someone: who listens, who responds and who remains responsible? Galatians 6:1-5 (NIV)
The announced refusal to automate prayer is a meaningful design intention. Its value for a person seeking help will depend on the human relationship the service actually makes possible. A church should be able to explain that relationship without asking users to infer care from the presence of a chat window.