Contact FridayLocalAI

General inquiries

Email info@hubbardgenesis.com or call 888-442-1725. Include your goal and relevant deployment context. Response times depend on the request and availability.

Product assistance

Describe the visible error and reproducible steps. Do not send passwords, API keys, session data, or private document contents.

Access and availability

Application access and store accounts serve different purposes. Contact us about the appropriate access path; a store account does not imply workspace access.

What to include

FridayLocalAI is available through early-access inquiries. Contact the project to discuss access. There is no public installer, and the FridayLocalAI Store is not accepting purchases. For access inquiries, describe your goal and environment. For product help, include the feature, time, expected and actual result, and a small example. Use the contact details above; do not send private source documents unless a suitable channel has been agreed.

Ask Friday to guide you

In an authorized FridayLocalAI conversation, try:

Help me draft an early-access inquiry for FridayLocalAI. Ask about my intended use, environment, and essential capabilities. Keep it concise and leave out credentials and private data. I will review and send it myself.

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.

Choose the purpose of your inquiry

Tell us whether you are asking about early access, application help, deployment suitability, a documentation correction, or a possible collaboration. A clear subject and a short description of the desired outcome make it easier to understand the request. If more than one topic is involved, identify the most important question first. For example, an early-access inquiry might describe a document-review workflow and ask whether the current deployment path could support it. A help request might identify a particular control and explain what happened when it was used. A partnership inquiry might describe the proposed role and audience. You do not need to provide a complete technical dossier to begin an ordinary conversation about the project.

Prepare an early-access request

Describe the work you want to do, the environment in which you expect to use the application, and the capabilities that matter most. Include relevant hardware details if known and explain whether local-only operation or optional connected services are part of the requirement. Mark uncertain details as unknown rather than inventing specifications. FridayLocalAI does not currently offer a public installer or accept purchases through the store. An inquiry is the starting point for discussing access, not a guarantee of an invitation or a release date. Application accounts are distinct from website or store accounts. Use the access route supplied by the project or operator if participation is arranged; browsing the website or purchasing a third-party book does not create workspace access.

Prepare a product-help request

State the feature, the steps that led to the issue, the result you expected, and what you observed. Include a relevant time and visible error text. Agent and model attribution can help with a response issue, while a source’s type and processing status can help with an attachment question. Explain whether a small non-sensitive example reproduces the symptom. Keep the report factual. “The response stopped after the second paragraph” is more actionable than an unsupported claim about the underlying service. Mention what still works and which checks you already tried. If the issue involves an unexpected change, inspect the current state before retrying so the report does not become complicated by duplicate actions or additional modifications made during experimentation.

Share only the information needed

Do not include passwords, API keys, session cookies, private keys, or unrelated personal records in an ordinary inquiry. A screenshot or log can contain more than the visible problem, so review what you are sharing. If a private source is necessary to investigate the issue, agree on an appropriate way to provide it rather than attaching the entire original collection by default. You can usually begin with a sanitized description or a harmless reproduction. State that the original material is sensitive when that affects the support process. The project can then discuss what evidence is needed. Keeping the first message narrow makes it easier to review and reduces unnecessary disclosure while preserving the important distinction between a public contact channel and the application’s governed workspace.

Ask Friday to help draft the message

If conversation is working, Friday can help turn your observations into a concise draft. Tell it the intended recipient and purpose, provide only the details you want included, and ask it to identify unanswered questions. Review the resulting message for accuracy before using it. The assistant should not fill missing values with plausible-sounding technical details. Make clear that you want a draft, not an assumed external action. A generated message has not been sent simply because it is complete. Use the contact details on this page through your normal communication method unless a separate authorized workflow has been arranged. If chat itself is unavailable, use the written troubleshooting guide to organize the same information without depending on the failing service.

Know what happens after an inquiry

The next useful step may be clarification, an early-access discussion, a request for a small reproduction, or direction to deployment-specific guidance. The website does not promise a fixed response time, support entitlement, or delivery schedule. Explain any practical deadline so it can be understood, but do not assume a response commitment that has not been agreed. Keep a copy of the relevant exchange and update it when the situation changes. If a problem is resolved, describe the verification that passed rather than only saying it appears better. If a question is no longer relevant, clarify that as well. Clear communication helps connect the project’s guidance with the actual task, environment, and evidence needed to decide what should happen next.