Registration closes in 4 d 10 h 45 minAfter that, subscriptions and Stars can't be bought — only renewed by those already inside. 30% off all plans right now.Join now

Practical guide · August 4, 2026

Profiles in HeadHack: splitting clients, support and personal messages

Profiles in HeadHack: splitting clients, support and personal messages

A profile in HeadHack lets you use different rules and different knowledge for different kinds of conversation. Clients can be answered on a sales script, people reporting bugs on a support script, partners in a businesslike tone, and relatives by personal rules.

Short answer. A profile is a separate set of style, system prompt, FAQ, facts, topics and documents for one kind of conversation. Create “Clients” and “Support” profiles, plus “Partners” or a personal one if you need them — and HeadHack picks the right profile from the sense of the incoming message.

This is part of the guide “A free Telegram auto-reply: how to connect it without Premium”. This page is only about profiles.

What a profile is

A profile is a separate set of settings and knowledge that the AI assistant uses for one kind of conversation.

A profile answers several questions:

  1. How should the assistant address people?
  2. What job does it do?
  3. Which knowledge and facts may it use?
  4. Which topics belong to this profile?
  5. Which documents should it take into account?
  6. May it offer a booking through the calendar?

Inside a profile you can set the reply style, the system prompt, the FAQ, facts, topics and roles, documents and Google Calendar.

How a profile differs from an account and a separate bot

A profile is not a new Telegram account and not a separate bot. One assistant can use several profiles depending on the topic of a message and the conversation so far.

You might create profiles for:

  • clients;
  • support;
  • partners;
  • hiring;
  • your mother;
  • your father;
  • a single service;
  • a specific project;
  • a particular professional topic.

That way sales, technical support, business proposals and personal conversations never have to share one prompt.

Why you want different profiles

One general prompt rarely suits every message.

A client needs to hear about services and booking. Someone with a bug needs step-by-step help. A partner needs a businesslike reply. A relative needs an ordinary personal message with no marketing tone.

MessageThe profile that fits
“How much is a consultation?”Clients
“My account will not open after the update”Support
“We would like to propose a joint project”Partners
“Where do I send my CV?”Hiring
“When will you be home today?”Personal profile
“I need help with an LLM integration”Technical profile

Each case needs different knowledge, different limits and a different style.

How the system picks a profile

When a message arrives, the system reads the text and the conversation before it. Then it picks the profile whose topics and roles fit that conversation best.

Incoming message
Reading the text and the conversation so far
Matching against topics and roles
Choosing a profile
Applying the system prompt
Searching the FAQ, facts and documents
Answering in the chosen style

“And how much does that cost?” is incomplete on its own. If a consultation was being discussed just before, the system may use the “Clients” profile. If the person had been reporting a bug, the conversation may stay in “Support”.

With little to go on, the assistant can ask one clarifying question — provided that rule is set in the style or the system prompt.

How many profiles you can have

As many as your work needs.

One possible structure:

  • clients;
  • prospective clients;
  • regular clients;
  • technical support;
  • partners;
  • suppliers;
  • staff;
  • candidates;
  • your manager;
  • your mother;
  • your father;
  • friends;
  • a single service;
  • a specific project;
  • one particularly important client;
  • AI engineering;
  • LLM integrations.

A large number of profiles is only worth it when they genuinely differ in knowledge, behaviour or the kind of message they handle. If two profiles share the same rules and material, do not duplicate them.

Filling in topics and roles

Topics and roles are the signals the system uses to decide that a message belongs to a profile.

You can list:

  • lines of work;
  • services;
  • kinds of request;
  • job titles;
  • professional roles;
  • topics the assistant should answer on.
ProfileExample topics and roles
ClientsServices, price questions, booking a consultation, payment, client support
SupportApp errors, login problems, order number, screenshot, user instructions
Personal profileFamily matters, personal messages, questions about free time

The wording has to be specific. Topics as broad as “conversation” or “questions” do nothing to separate one profile from another.

Example profiles

Four worked examples below: for clients, for support and for two personal contacts. Each shows how the style, the system prompt and the topics move together with the profile's job.

A profile for clients

Reply style:

Answer briefly, clearly and politely. After answering, offer one next step.

System prompt:

You are the company's assistant. Answer questions about services, prices and booking. Use only what is in the knowledge base and never promise anything that is not in the terms.

Topics and roles: services, price questions, booking a consultation, payment.

Material: service descriptions, the current price list, booking terms, payment rules — more on which documents are worth uploading to a profile.

A profile for support

Reply style:

Answer briefly and step by step. Clarify the problem first. Ask for the order number and a screenshot if you need them.

System prompt:

Help the person find a solution from the knowledge base and documents. Never invent the cause of an error. If there is no exact solution, pass the case to a specialist.

Topics and roles: errors, account will not open, problems after an update, instructions, technical support.

Material: the user manual, a list of errors, instructions for fixing common problems.

A profile for your mother

Reply style:

Answer warmly, calmly and in plain words. No businesslike tone and no complicated phrasing.

System prompt:

You are a personal assistant. Answer kindly. If a question needs the owner's personal answer, say that they will reply themselves.

Topics and roles: family matters, personal messages, questions about free time.

A profile for your father

Reply style:

Answer briefly and specifically. No emoji and no long explanations.

System prompt:

Give a direct answer when the knowledge base has what is needed. If it does not, say the owner will answer later.

Topics and roles: personal messages, family matters, important requests.

Mistakes when setting profiles up

A topic that is too broad

If both “Clients” and “Support” carry the topic “user questions”, the system has a harder time choosing. Use sharper wording.

The same knowledge in every profile

Do not load every document into one shared base. The price list and booking terms belong to the client profile; a technical instruction belongs to support.

Contradicting instructions

If the style asks for short answers and the system prompt asks for the fullest possible explanation, the replies become erratic. The rules inside a profile have to work together.

No rule for missing data

Say what the assistant should do: ask one clarifying question, state that information is missing, or hand the conversation to the owner.

Too many similar profiles

Split profiles only where the knowledge, the style or the goal of the conversation genuinely changes.

Testing the routing

Try each profile on several kinds of message.

For “Clients”:

  • How much is a consultation?
  • What services do you offer?
  • How do I book?

For “Support”:

  • My account will not open.
  • An error appeared after the update.
  • Where do I send a screenshot?

For “Partners”:

  • We would like to propose working together.
  • Who should I send the deck to?

For the personal profile:

  • When will you be free?
  • Tell them I called.

Then check:

  1. which profile was chosen;
  2. whether the style matches the kind of conversation;
  3. whether only the right facts and documents are used;
  4. whether material from other profiles leaks in;
  5. whether a clarifying question is asked when context is thin.

It is easiest to prepare the example questions and facts for the knowledge base in advance — how to do that is in the article on the FAQ and the knowledge base.

In short

Profiles let one AI assistant handle different kinds of message without mixing rules and knowledge. Start with two or three genuinely different scenarios, fill in topics and roles precisely, spread the documents out, and test the routing on real wording.

Open @Head_Hack_bot and create your first profile.