You can ask application questions directly in a conversation. Relevant active Help topics may be supplied to the response when available to your role. You can also use the information icons beside Organizer, Projects, Conversations, and other sections. A reply is guidance: compare it with the controls and results in your installation.

Ask Friday to guide you

In an authorized FridayLocalAI conversation, try:

I am new to FridayLocalAI. Guide me through a small practice task one step at a time. Ask what I want to do, use the relevant built-in Help where available, explain each control before I use it, and wait for me to confirm the result.

Tell Friday what you can see and which step you have reached. If the instructions do not match your screen, say so; ask for the relevant Help topic or contact your operator. Friday cannot be assumed to see your screen or know your current settings.

Colleagues helping each other at a desktop computer. Illustrative stock imagery; not a FridayLocalAI screenshot. Credit: pressmaster - stock.adobe.com. Image use notice.

Keep a guide handy

The consumer document catalog provides downloadable Quick Start and User Guide PDFs. You can also continue with the web guides linked above.

Choose the kind of help you need

Start by deciding whether you need an explanation, a guided action, or help with an error. An explanation answers a question such as “What is a conversation scope?” A guided action walks you through something you can do in the interface. Troubleshooting investigates why the expected result did not occur. Naming the kind of help you want makes it easier for Friday to respond at the right level. Describe your goal in ordinary language and mention the section you are using. You do not need to know an internal component name. “I am in Organizer and cannot find yesterday’s conversation” is a more useful starting point than “the system is broken.” Include what you already tried, but keep private content and account secrets out of the description.

Use the information beside the interface

The application includes information icons associated with workspace sections and controls. These can provide explanations relevant to the area you are viewing. An icon beside a conversation description may explain that item’s context, while a section-level Help control can explain the section itself. Read the label and the resulting explanation rather than assuming every icon has the same purpose. If the guidance does not answer your question, bring the specific wording into a conversation with Friday. State which part remains unclear and what you are trying to accomplish. Relevant active Help topics may be supplied to the response when available to your role. A missing or unhelpful explanation is useful feedback; it is not a reason to invent a control or make an administrative change.

Ask for one step at a time

A guided exchange is easiest to follow when Friday gives one action and an expected result, then waits for you. After completing the action, describe what changed. If nothing changed, say that explicitly. If your screen differs from the instructions, provide the visible labels rather than guessing which button might be equivalent. For example, ask how to start a practice conversation. Friday can explain where to look in Organizer and what creation controls may be available. You perform the permitted action and confirm the result. This keeps the distinction between guidance and execution clear. It also prevents a long chain of instructions from carrying you past an early mismatch that should have been resolved first.

Colleagues discussing work around a laptop. Illustrative stock imagery; not a FridayLocalAI screenshot. Credit: bernardbodo - stock.adobe.com. Image use notice.

Provide enough context without oversharing

Useful context includes the feature, your intended task, the visible error if any, and the point at which you became uncertain. A short description of the Agent and model selection may matter for a response issue. A source’s type and approximate size may matter for an attachment question. The contents of unrelated documents, credentials, and private account details usually do not help. Use a small fictional example when possible. If a document question can be reproduced with three harmless sentences, begin there. If the problem only occurs with a particular source, describe that distinction to your operator and agree on a suitable way to review it. The public contact route is not an invitation to send your entire workspace or raw diagnostic material.

Decide whether the guidance worked

Before following a step, understand what success should look like. Opening a panel should reveal the intended controls. Sending a message should produce the expected conversation entry. Saving a note should make the note visible in the correct scope. Completing a source review should produce an answer that can be checked against the source. If Friday reports a successful change but you cannot find the result, ask for clarification and inspect the relevant screen. Do not accept a conversational assurance as a substitute for evidence. For factual answers, compare the important details with the original material. For a workflow you will repeat, record the short sequence that worked so you can return to it without rediscovering every step.

Get help when conversation is unavailable

If sign-in or chat is failing, the application cannot be your only support channel. Use the first-run and troubleshooting pages on this website, or keep the downloadable consumer guide available. Contact your operator with a concise description of the failure, the time, what you expected, and what still works. Avoid repeated retries that could duplicate an external action or overwrite useful evidence. Access questions go through the project’s early-access contact path. There is no public installer to download and no store purchase that automatically creates a workspace account. Once access is established, return to a harmless practice task before important work. The purpose of these guides is to help you understand the application well enough to use it deliberately and recognize when further assistance is needed.