Maintain · Knowledge
Knowledge: what your workers know about you
Heliyos reads your website, decks, pricing and docs and extracts what a new colleague would need to know about your company: what you sell, to whom, at what price, in which words. Add custom data fields and organisation files, and every worker writes and decides from the same brief.
Knowledge is the organisation-level memory in Heliyos: everything a worker needs to know about your company, as opposed to the customer memory it keeps per account. When you set up a workspace, Heliyos extracts your positioning, products, pricing, ideal customer, tone and objections from your website and the files you add, and keeps that brief as structured knowledge. You can add custom data fields (for example "security certifications" or "implementation time") and organisation files from Google Drive, OneDrive or upload. Taylor, Parker and custom workers read this knowledge before every run, so a proposal uses your real pricing and a reply uses your real words.
Use cases
Use cases
A new workspace, nothing typed in
Point Heliyos at your website and a deck. It extracts what you sell, who it is for, how you price it and how you talk about it, and shows you the brief to correct.
Pricing changed last week
Replace the pricing sheet in the connected Drive folder. The next proposal Taylor writes uses the new numbers; the old ones are gone from every worker at once.
"Do you have SOC 2?" in every security review
Add a custom field for certifications and the answer. Workers answer it the same way every time, from the field, not from memory.
Objections the team has learned to handle
Keep the five objections and the answers that work as knowledge. Taylor’s drafts and Parker’s summaries use them.
A new rep, or a new worker, on day one
Both read the same brief: positioning, products, pricing, tone, ideal customer. Nobody has to re-explain the company.
Internal only stays internal
Mark files as internal and workers read them for context but never attach or quote them in anything that goes outside.
How it works
How it works
- 01
Connect sources
Your website, Google Drive or OneDrive folders, uploads.
- 02
Heliyos extracts the brief
Positioning, products, pricing, ideal customer, tone and objections, as structured knowledge you can edit.
- 03
Add what only you know
Custom fields and files for the facts a website never says.
- 04
Workers read it every run
Alongside the account memory, so every draft and decision reflects your company as it is today.
Workers
Who works here
Workers show up where the team already is, with a clear marker for who did what. Your own custom workers join them.
Taylor
ParkerFAQ
Questions people ask
- How do AI workers know about my company?
- From Knowledge: Heliyos extracts a brief from your website and files, you correct and extend it with custom fields and organisation files, and every worker reads it before it acts.
- What is the difference between Knowledge and customer memory?
- Knowledge is about you: products, pricing, tone, policies. Customer memory is about each account: people, conversations, deals. Workers read both.
- Can I add fields that are specific to my business?
- Yes. Custom data fields hold the facts your workers should answer consistently, from certifications to implementation times.
- Which file sources are supported?
- Google Drive, OneDrive and direct upload. Files stay where they are; Heliyos indexes them for the workers.
Deploy your first AI worker, today.
Closed beta, usage-based pricing, no seats. Join the waitlist and we review your request.