Fractera Admin

Communication channels

Telegram, email and the other channels the project speaks through.

Telegramno token yet
Channel active
Bot token from @BotFather
Schedule

How often the product is asked whether a reminder has come due. Reminders have to fire while nobody is looking at the site, so something has to knock — this is it. Off means the project has no reminders and pays for none.

Once linked, the bot answers from the knowledge base built in Agentic RAG. It never invents an answer: with the base empty or the service off, it says so.

What the assistant tells people

This is what the bot answers on /start and on «what can you do». It is not a setting: it describes what the product really does today, so it changes with the product, not from this page.

It can:

  • listen by voice or text — a voice note is transcribed and treated exactly like typing
  • remember WHEN it happened, not only when it was told: «yesterday I bought…» is stored under yesterday
  • understand what it was told — a purchase, a task, a place, a promise — and keep the useful fields, such as an amount and a vendor
  • mark anything involving money, so «what did I spend» is answered from a column instead of re-reading a year
  • keep the location when one is sent
  • search by MEANING, not by words: «where did I buy electronics» finds the shop even when that word appears nowhere
  • build a knowledge graph out of everything, so connections between separate days can be found later
  • set reminders and events, one-off or repeating, warning in advance when asked — and it always reads the time back before setting it

Phrasings it is taught:

  • «запомни …» — remember as a promise, not as a passing note
  • «напомни … в …» — a reminder at a time; it names the time and asks first
  • «напоминай каждый рабочий день в 9 …» — repeating: daily, weekdays, weekly, monthly
  • «запланируй встречу … в 10, напомни за час» — an event with advance warning
  • «найди …», «когда я …», «сколько я …» — search their own history
  • «что ты умеешь» — this list

What it does NOT promise: Storing files. A photo, a video or a PDF arrives with its caption saved, but the file itself is not yet kept in the media library. Until it is, the assistant deliberately does not offer it — a promise nobody keeps is discovered at the worst moment, when someone relied on it.

What a channel is, and what it is not

What this gives you. A door into your project from a messenger instead of a browser. A person writes to your bot and gets an answer built from your own knowledge base — no separate app, no login screen.

Why your own bot and not ours. The token belongs to a bot you created, so the conversation runs between your visitors and your server. Nothing passes through us, and if you ever move the server the bot moves with the token.

Why linking needs a one-time code. The link is opened inside a messenger, where it is visible to anyone who sees the screen. A code that worked twice would let someone else attach their account to your project, so it works once and expires.

Turning the channel off. The switch stops the bot answering without deleting the token or the link — useful while you are changing the knowledge base and would rather nobody got half-built answers.

GitHub connection required
en

North America

🇺🇸Englishen

Eastern Europe & CIS

🇷🇺Русскийru

Sub-Saharan Africa

🇺🇸Englishen

Asia Pacific

🇺🇸Englishen