Pattern 27

Support human connections

Keep quiet, exit and appropriate human support available.

Research-informed design proposal

Concrete takeaway

Let people stop or remain quiet without being pursued.

Choose an approach

These are editorial decision conditions to validate. Some alternatives are successive states or can be combined; they are not always exclusive choices.

AlternativeUse whenTradeoff or requirement
A · Quiet or exitThe person wants quiet or to endDo not pursue them with another disclosure request
B · Choose a personA real person could provide useful supportThe user decides which person is safe
C · Honest support routeA service is offered as a destinationA contact card is not a staffed transfer

The problem

A conversational product can encourage exclusive attachment or imply a human handoff that it cannot deliver.

The pattern

Let people stop or remain quiet without being pursued. Offer relevant, maintained human-support options and state whether contact is user-initiated, asynchronous or an actual staffed transfer. Avoid exclusivity or dependency cues.

Compare the alternatives

Keep quiet, exit and appropriate human support available.

A · Quiet or exit

Assistant · Example interface
You can pause or stop here.
Stay quiet
End the conversation

Ending does not require another disclosure.

B · Choose a person

Assistant · Example interface
Someone you trust
Contact is your choice.
Qualified support
Verified options for your location.
Explore support options

Real connections remain part of the picture.

C · Honest support route

Assistant · Example interface
Support service
Audience, hours, language and contact method.
You contact this service yourself.
Open the contact information

A contact card states what will actually happen.

Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations

Download this wireframe as SVG

Failure modes

“Only I understand you”; false live monitoring; implying a contacted service has received the conversation when it has not.

Bible and faith considerations

Faith community, pastoral care and clinical care are different forms of support. Choose options appropriate to the person and context.

What to validate

Check every support destination, eligibility and availability. Can users understand who will receive data, whether anyone is responding and how to leave?

Evidence status

Research-informed design proposal. These visual alternatives have not been tested with users in this atlas. Source findings, documented behaviour and this proposed adaptation are different kinds of evidence.

Sources and adaptation

This card is an original design synthesis. The following sources inform its content distinctions, interaction approach or review requirements; they do not validate the whole pattern.

Common scenarios and flows

Design principles in this decision

Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.

Compare alternatives using the task and evidence above. Record competing needs instead of treating a principle as an automatic verdict.

Regional applicability

Design review questions · 5 October 2026. These prompts identify possible triggers; they do not classify this pattern or every faith app as a regulated service.

Could functionality, marketing or reasonable expectations make this a companion or mental-health service? Define the human role, health claims, escalation capability and locally verified support route before selecting dialogue UI.

Start with EU and Germany, then review the relevant market:

Use the jurisdiction decision guide to record the trigger, source version and resulting product requirement.