A workspace assistant is most useful when it understands the difference between asking for product help and asking it to change the workspace. A user who writes “How do I share this Doc?” needs an explanation. A user who writes “Create a task from this Doc” wants an action.

Aamu.app now has a dedicated AI product-help path for the first case. In the Launch AI dialog, start a question with aamu: to ask how Aamu works. The answer is generated from Aamu's public documentation and includes the source pages used to prepare it.

Using aamu: in Launch AI

Open Launch AI from the Aamu header and write a question such as:

aamu: How do I share an Aamu Doc with a public link?

You can ask in your own language:

aamu: Miten teen tietokanta-automaation, joka käynnistyy kun uusi rivi lisätään?

The aamu: prefix routes the question to Aamu's product-help assistant before the normal workspace action router. This keeps the request separate from commands that create tasks, edit Docs, update meetings, draft replies, or change database rows.

The current Aamu page path is included as lightweight context. A question such as aamu: How do I automate this? can therefore be easier to interpret when the user is already looking at a database or project settings page. Team content from the current workspace is not sent into the public documentation search.

A separate knowledge base for Aamu itself

Every Aamu team can have its own Team Brain. A team's Team Brain contains knowledge relevant to that organization: internal Docs, policies, support material, selected web pages, FAQs, and other maintained sources.

Product help needs a different knowledge base. Questions about Aamu should be answered from Aamu's own public material, not from the customer's Team Brain. The product-help assistant therefore uses a dedicated Aamu support workspace whose Team Brain indexes the Aamu landing page and the public Aamu blog sitemap.

This separation has two benefits:

  • Aamu product instructions do not become mixed with the customer's company knowledge.

  • The product-help service can be available even when the customer's own team AI is not enabled or does not have a connected model account.

What the assistant can answer

The quality and coverage follow the public documentation. Current material can help with questions about areas such as:

  • Team Brain knowledge sources, indexing, and retrieval;

  • AI-assisted Helpdesk and email reply drafts;

  • public sharing and snapshots in Aamu Docs;

  • tasks, Forms, meetings, files, and project workflows;

  • database tables, rows, GraphQL, and database automations;

  • the Aamu API, API keys, scopes, and supported operations;

  • AI commands and the distinction between drafting, acting, and sending.

If the indexed public material does not support a reliable answer, the assistant should say so instead of inventing a product capability. For example, an undocumented interface setting should not be presented as available merely because a general AI model considers it plausible.

Answers include public sources

Before writing an answer, the service searches the dedicated support Team Brain for relevant entries and document chunks. Only results connected to public Aamu URLs are allowed into the answer context.

The response includes a list of source pages. These links make the answer easier to inspect and give the user a path to the longer product explanation. A sitemap may contain many blog posts, but an individual answer shows only a limited set of URLs selected from the relevant retrieval results.

The source list is supporting context, not a claim that every linked page contributed equally to every sentence. As the documentation and retrieval metadata improve, source attribution can become more precise.

The public Support API

The same product-help service is available as a small public HTTP API:

POST https://support.aamu.app/api/ask
Content-Type: application/json

{
  "question": "How do I add a sitemap to Team Brain?",
  "language": "en",
  "context": {
    "path": "/project/edit/PROJECT_ID/helpdesk"
  }
}

A response contains the answer, public sources, a retrieval confidence value, and an indication of whether supporting material was found:

{
  "answer": "Add the sitemap as a Team Brain knowledge source...",
  "sources": [
    {
      "title": "Team Brain is Aamu's shared knowledge layer",
      "url": "https://aamu.app/blog/posts/..."
    }
  ],
  "found": true,
  "confidence": 0.61
}

The API does not require an API key. The hostname fixes the service to the Aamu support knowledge base, and callers cannot select another team, project, or Team Brain through request parameters.

Why the API is public but constrained

The indexed knowledge consists of public Aamu pages, so requiring every caller to create an API key would add friction without protecting private workspace content. The endpoint is therefore intentionally public.

Public does not mean unlimited. The service applies request-size limits, question and context length limits, an IP-based rate limit, output limits, and a short response cache. It is read-only: it cannot create a support ticket, contact a person, send a message, or modify an Aamu workspace.

The endpoint also rejects requests made through another Aamu team hostname. POST /api/ask is specifically a service of support.aamu.app, not a generic unauthenticated path into customer Team Brains.

Product help is not a human support channel

This feature is AI product help. It does not escalate a conversation to a person, promise a human reply, or open a ticket. That boundary is deliberate: the Launch AI dialog is a workspace assistant, not a hidden Helpdesk queue.

The assistant is best for questions that can be answered from maintained product documentation. Account-specific problems, billing decisions, security reports, and situations requiring investigation still need an appropriate human contact path.

Examples

Here are some questions that fit the product-help path:

aamu: How do I add a Doc as a Team Brain source?

aamu: How does an AI Helpdesk reply draft reach the reply editor?

aamu: How do I share a Doc as a read-only snapshot?

aamu: How do I create a row_inserted database automation?

aamu: Which permissions does an API key need to retrieve Team Brain knowledge?

A question can also expose a documentation gap. If the assistant can describe an API operation but cannot explain the equivalent UI workflow, that is useful feedback: the public product documentation needs a clearer step-by-step guide.

A documentation loop

The product-help assistant turns Aamu's public documentation into an interactive interface. It also makes documentation quality easier to evaluate.

  1. A user asks a real product question.

  2. The support Team Brain retrieves the most relevant public material.

  3. The assistant answers from that material and returns links.

  4. A weak or incomplete answer reveals missing, vague, or poorly structured documentation.

  5. The documentation is improved and the support Team Brain is indexed again.

This is the same principle that makes Team Brain useful for customer support: better maintained knowledge produces better grounded answers. In this case, Aamu itself is the product being supported.

The bottom line

Use aamu: in Launch AI when the question is about using Aamu.app. The request goes to a dedicated read-only product-help assistant, searches Aamu's public documentation, and returns an answer with supporting links.

For integrations, the same capability is available without an API key at POST https://support.aamu.app/api/ask. It is a small, focused API: one support knowledge base, public sources, no workspace actions, and no pretend human handoff.