7. An open door: the public wall *Help can begin before someone is ready to join.* The first visit is already an interaction A daughter finds a community program while looking for something her father might enjoy. She does not yet know whether the program fits, whether transport is available, or whether asking a question will lead to a sales call. She is looking for a useful beginning. A public wall can bring resources and invitations into an experience that does not begin with joining a private care community. Partners can present public content through supported website embeds or a dedicated landing experience. The opening should help someone understand what is available and what they can do next. This is a practical place for a partner’s knowledge to become visible. Local language, familiar questions, clear descriptions, and relevant examples can turn a generic resource into something a visitor recognizes. The first useful interaction may be reading a short answer, watching an introduction, or learning whom to contact. Image description: Conceptual partner website with a first-visit video and text alternative, practical service information, an optional AI information assistant, and a visible human contact route. Public content can be read without starting a chat. Figure 7. Offer a useful first step · Concept illustration Concept illustration, not a product screenshot. It shows how a partner could arrange public resources, an optional AI conversation, and a clear route to a person. 1. Begin with a specific audience and a question the service can help answer. 2. Keep essential information readable without chat and provide text alongside video. 3. Identify AI clearly, use reviewed resources, and offer a human contact route. A private need may require a different channel. Give each landing experience a purpose A landing page should make a manageable promise. It might help someone prepare for a first visit, understand a service, explore a topic, or begin a conversation. Trying to serve every audience and answer every question at once makes that promise harder to see. The public wall’s content and embed options support experiences that can sit within a partner’s existing website. The surrounding page still matters: the heading, context, accessibility, contact route, and explanation of what happens after a response. An embedded experience should feel like part of the relationship the organization is offering. For the community program, an initial arrangement might include a brief welcome, a video showing a typical activity, a practical transport explanation, and an invitation to ask about a first visit. Each item earns its place by helping the visitor decide. The team should be prepared for the questions that invitation creates. Conversation can help people find a way in The public wall includes chat experiences that can be embedded alongside content. When configured with approved resources and an appropriate remit, an assistant can help visitors explore information in their own words. Someone who does not know the name of a service may be able to describe what they are trying to do. The experience should explain that the person is interacting with AI and make a human contact route easy to find. It should also make the scope clear. A program information assistant can help someone find opening hours or understand an activity. That does not make it the right place to assess an urgent health concern or provide individualized clinical advice. Public conversation also calls for thoughtful prompts. Do not encourage visitors to disclose personal details that the experience does not need. Explain the relevant privacy arrangements and direct people to an appropriate channel when their question requires a private conversation. A warm invitation can still have clear boundaries. The carePhysics connection Awareness — Make Understanding Possible (https://genusconnect.org/carephysics/book/chapter-02) and Communications — Help People Feel Heard (https://genusconnect.org/carephysics/book/chapter-04) offer useful starting points. The first task is often to help a visitor recognize that the resource is relevant and understandable. Choice matters here. A person may want a short explanation, a video, or a conversation. Those options should lead toward the same useful understanding, with important information available in accessible text. A video should not be the only way to learn a practical requirement. Where AI helps Before release, AI can help editors identify unanswered questions, draft plain-language introductions, or propose variations for different audiences. During use, a configured assistant may help people navigate reviewed information. Afterward, appropriately handled feedback can help the team see which explanations need improvement. The partner supplies the current service knowledge and decides what the assistant may do. When the source information is incomplete or a request falls outside that scope, the useful response is a clear route to help. Fluency alone is not a reason to trust an answer. Bring your knowledge Choose one audience and one question they often bring to your organization. Build a small public experience around that question. Include a next step someone can actually take and identify the person or team responsible for it. Review the experience on a phone, with a keyboard, and with someone who has never heard your internal terminology. Ask them what they think will happen if they respond. Their expectation is part of the design. If it differs from the service you can provide, change the invitation before expanding its reach. Explore further — Public does not mean private care access A public resource, a question asked before signing in, a contact request, and a private community conversation are different interactions. Moving between them may require a clearer explanation, additional identity checks, or a different channel. Agree on those handoffs during configuration. Keep essential public information readable without requiring someone to start a chat, and provide a useful alternative when an embed or assistant is unavailable.