How to connect documents to an AI bot in Telegram

What you can add

A profile accepts:

• .pdf;
• .docx;
• .txt;
• a public web page;
• an open link to a document.

Before adding anything, make sure it is reachable, current and carries no private information.

Why spread documents across profiles

Load everything into one shared base and the assistant has a harder time keeping topics apart. A technical support instruction should not turn up in an answer to a partner, and a job description should not turn up in an answer to a client. More on splitting clients, support, partners and personal messages into separate profiles is in the article “Profiles in HeadHack”.

An example split

How to prepare a document

Keep one current version

Do not upload the old price list alongside the new one. With two versions of your terms in a profile, the assistant may quote the outdated one.

Give it a clear structure

A document needs headings, sections and unambiguous wording. Keep services, prices, limits and procedures apart.

Remove contradictions

If the FAQ says one thing and the document another, the answers become inconsistent. Compare every source before uploading.

Do not turn a document into a dumping ground

Several focused documents per profile beat one file holding every line of business, your personal notes, job openings and technical instructions.

Using a price list

A price list belongs to the profile that answers client questions. It needs current items and unambiguous terms.

If the price depends on the job, do not make the assistant pick a number at random. Add a line such as:

And a next step:

Using support instructions

For a “Support” profile these are useful:

• the user manual;
• a list of common errors;
• what information to collect;
• the order of checks;
• when to pass an enquiry to a specialist.

The system prompt should forbid inventing the cause of an error or promising a fix without confirmed facts.

Using decks for partners

The “Partners” profile can hold the company deck and a description of the partnership formats you offer.

The assistant can:

• clarify the format of a proposal;
• say what information to send;
• explain what happens next;
• pass the enquiry to the owner.

It must not decide on a partnership by itself unless the prompt gives it that authority.

Keeping documents current

Review the material whenever these change:

• prices;
• services;
• payment rules;
• your schedule;
• contact details;
• technical instructions;
• requirements for candidates;
• partnership terms.

Delete the old version rather than leaving it next to the new one. After an update, ask again the questions whose answers depend on what changed.

Data safety

Do not upload:

• passwords;
• secret keys;
• payment details;
• unnecessary personal data;
• medical data;
• confidential documents you do not need there.

Checking that it works

Ask questions whose answers sit in different materials:

• a price question from the price list;
• a service question from the description;
• an error question from the instructions;
• a partnership question from the deck;
• a question that is in no document at all.

Then check:

1. whether the assistant picked the right profile;
2. whether it found the right material;
3. whether it used something from another profile;
4. whether it quoted an outdated version;
5. whether it said the data was missing instead of guessing;
6. whether it offered a sensible next step.

Open @Head_Hack_bot, pick a profile and attach the first document — a price list or an instruction — then check the answer on a real question.

Related reading

In short

Documents add detail on top of the FAQ and the facts. Spread them across profiles, keep only current versions, remove contradictions, and leave confidential data out.