How it works: a corporate AI that thinks like your company

Today everyone uses AI their own way, with loose prompts and documents pasted over and over. With rekiam you configure once what the AI must know and follow, and each team works with a specialist in its field that respects the house rules.

Updated

From chaos to clarity

AI is already in your company, but everyone uses it their own way: their own instructions, the same things explained in every chat and nobody knows which data ends up where. You lose time, the answers don't sound like your company and confidentiality depends on each person being careful.

Without rekiam

  • Different prompts in every team
  • Documents pasted into every conversation
  • Policies that depend on each person
  • No control over who sees what

With rekiam

  • Context configured once for everyone
  • Knowledge organised by level
  • Inviolable rules and prohibitions
  • Permissions by role and department

What is a multi-level enterprise AI platform?

It's an AI platform organised like your company: company, departments, sections and people. Each level inherits from the one above and adds its own, so nobody has to explain again what has already been explained.
  1. Organisation

    Shared identity, culture, tone, policies and documentation. The foundation everything else inherits.
  2. Departments

    Marketing, Finance, HR, Legal, Sales… Each inherits from the company and adds its own knowledge and rules. That's how AI by department works.
  3. Sections

    Parts of a department, such as SEO or Google Ads within Marketing, with their own context and access only for the people you choose.
  4. People

    Each person adds their own private context and only accesses what their role allows.

How does the AI follow your company's policies and tone?

You explain them once in Contexts and the AI applies them every time. There you write and attach what the AI must take into account at each level. Each item has a type, so the AI knows whether it's information, a rule or a step to follow. It accepts PDF, Word, Excel, PowerPoint, CSV, TXT and Markdown documents.

Who manages each level is clear: the organisation, the administrators; each department and its sections, their leads; and personal context, only its owner. Not even administrators can see it.

Each level keeps its version history, shows what it inherits from above and has an instruction diagnostic that flags rules that contradict each other. You can also connect a Google Drive, OneDrive or SharePoint folder so its content stays up to date on its own, and upload document templates that the AI fills in while keeping the design.

  • Context
    What the AI needs to know: who you are, what you sell, how you work, your customers.
  • Rule
    What it must always do: tone, format, criteria, mandatory steps.
  • Prohibition
    What it must never do. No lower level can bypass it.
  • Procedure
    How a task is done step by step in your company, so the AI applies it.

The AI proposes, your team decides

When someone sets something in a chat that should apply to the whole company, a department or a section (a rule, a prohibition, a procedure), the AI detects it and leaves a card to add it to the context. If that person doesn't manage that level, the proposal goes as a request to their lead or to the administrators. Nothing enters the context without confirmation from someone with permission.
  • Card in the chat
    Proposed type, title, text and level, which can be edited before saving.
  • Requests
    Leads approve or reject them from Contexts › Requests.
  • Traceability
    Requesting, approving and rejecting are recorded in the activity log.

What happens if a department contradicts a company rule?

The company rule wins. A lower level can never override a rule or prohibition from above. Instructions combine from top to bottom, and the most specific level prevails only where nothing above prevents it. A specialist adds its knowledge, but doesn't change the house rules.
  1. Platform

    rekiam's global security policies, inviolable at every level.
  2. Organisation

    Your company's mandatory restrictions and general settings.
  3. Department

    Knowledge and rules of the area: Marketing, Finance, HR…
  4. Section

    Specialism within the department: SEO, Accounting, Recruiting…
  5. Project or chat space

    Each conversation only uses the context of its space and, if it has one, its project.
  6. Person

    Personal preferences and memory, always compatible with everything above.

Every chat, with just the right context

When you start a conversation you choose its space: General, one of your departments or one of your sections. The AI only uses that space's context, so an Accounting chat doesn't get mixed up with a Social media one. Chats and folders are personal: nobody else sees them unless you share them.
  • General
    Organisation + your personal context. For everyday work.
  • Department
    The above + the department's knowledge and rules.
  • Section
    The above + the section's specialism. Maximum precision.

Each topic, with its instructions and documents to hand

Tenders, contracts, payroll… A project brings together a topic's instructions (its role, what to always check, how to deliver) and its fixed documents (specifications, templates, regulations). Every chat you open with it takes them into account, on top of the company's context, without ever bypassing its rules.
  • Personal, for a section, a department or the whole company
  • Used by the people in that scope and managed by whoever manages that level
  • Can set the model their chats start with
  • Their documents are indexed and the AI searches and cites them

Your company already has its own standards. Make the AI follow them.

Tell us how your team works and we'll show you rekiam with examples from your day-to-day: your departments, your documents and your policies. The first call is free.

Already a customer? Log in to rekiam

La R de rekiam, tejida