<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>AOVA AI Assistant Blog</title>
        <link>https://docs.aova.app/blog</link>
        <description>AOVA AI Assistant Blog</description>
        <lastBuildDate>Tue, 29 Sep 2026 12:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[How to create an AI Telegram bot that answers from your documents — no code]]></title>
            <link>https://docs.aova.app/blog/ai-telegram-bot-from-your-documents</link>
            <guid>https://docs.aova.app/blog/ai-telegram-bot-from-your-documents</guid>
            <pubDate>Tue, 29 Sep 2026 12:00:00 GMT</pubDate>
            <description><![CDATA[Step-by-step guide to building an AI Telegram bot that answers questions from your own PDFs, docs and recordings. BotFather, knowledge base, agent, channel — about 10 minutes, no programming.]]></description>
            <content:encoded><![CDATA[<p>Most "AI Telegram bots" are a thin wrapper around a general chatbot: ask them about <em>your</em>
prices, <em>your</em> course or <em>your</em> return policy and they make something up. This guide shows how
to build a bot that answers <strong>only from your own documents</strong> — and how to do it in about ten
minutes without writing code.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="what-youll-end-up-with">What you'll end up with<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#what-youll-end-up-with" class="hash-link" aria-label="Direct link to What you'll end up with" title="Direct link to What you'll end up with" translate="no">​</a></h2>
<ul>
<li class="">A Telegram bot with your own name and username (for example <code>@acme_help_bot</code>).</li>
<li class="">It answers questions using the files you uploaded — PDFs, Word documents, FAQs, even audio
and video recordings, which are transcribed automatically.</li>
<li class="">You choose the AI model behind it (Claude, GPT, Gemini or Amazon Nova) and can switch any time.</li>
<li class="">The same assistant can later answer on your website and in WhatsApp too.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="what-you-need">What you need<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#what-you-need" class="hash-link" aria-label="Direct link to What you need" title="Direct link to What you need" translate="no">​</a></h2>
<ul>
<li class="">A Telegram account.</li>
<li class="">The documents your bot should know: a price list, FAQ, course materials, policies, manuals.
Start with one or two good files — you can add more later.</li>
<li class="">A free <a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=telegram-bot-guide" target="_blank" rel="noopener noreferrer" class="">AOVA account</a>.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="step-1-create-the-bot-in-telegram-with-botfather">Step 1. Create the bot in Telegram with @BotFather<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#step-1-create-the-bot-in-telegram-with-botfather" class="hash-link" aria-label="Direct link to Step 1. Create the bot in Telegram with @BotFather" title="Direct link to Step 1. Create the bot in Telegram with @BotFather" translate="no">​</a></h2>
<p>Every Telegram bot is registered through Telegram's official <a href="https://t.me/botfather" target="_blank" rel="noopener noreferrer" class="">@BotFather</a>.</p>
<ol>
<li class="">Open <a href="https://t.me/botfather" target="_blank" rel="noopener noreferrer" class="">@BotFather</a> in Telegram and press <strong>Start</strong>.</li>
<li class="">Send <code>/newbot</code>.</li>
<li class="">Send the bot's <strong>display name</strong> — what people see in the chat header, e.g. <code>Acme Help</code>.</li>
<li class="">Send its <strong>username</strong> — it must be unique and end in <code>bot</code>, e.g. <code>acme_help_bot</code>.</li>
<li class="">BotFather replies with a <strong>token</strong> that looks like <code>123456789:AAH...</code>. Copy it.</li>
</ol>
<p>:::caution Keep the token private
Anyone with the token can control your bot. Paste it only into AOVA, and if it ever leaks,
send <code>/revoke</code> to @BotFather to issue a new one.
:::</p>
<p>Optional, but it makes the bot look trustworthy: <code>/setdescription</code> (the text shown before
someone presses Start), <code>/setabouttext</code> and <code>/setuserpic</code>.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="step-2-create-a-project-and-a-knowledge-base">Step 2. Create a project and a knowledge base<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#step-2-create-a-project-and-a-knowledge-base" class="hash-link" aria-label="Direct link to Step 2. Create a project and a knowledge base" title="Direct link to Step 2. Create a project and a knowledge base" translate="no">​</a></h2>
<p>Sign in to <a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=telegram-bot-guide" target="_blank" rel="noopener noreferrer" class="">AOVA</a>
and create a <strong>project</strong> — the folder that will hold your bot's knowledge, agent and channels.</p>
<p><img decoding="async" loading="lazy" alt="Create a new project form" src="https://docs.aova.app/assets/images/create-project-filled-62c5bfa46716b7c85dcadcbf35767c52.jpg" width="1518" height="784" class="img_HB6S"></p>
<p>Inside the project, create a <strong>knowledge base</strong> and click <strong>Upload</strong> to add your files.</p>
<p><img decoding="async" loading="lazy" alt="The upload dialog with a file staged, ready to upload" src="https://docs.aova.app/assets/images/upload-dialog-staged-f400d642a29cf6b3b29025bb5a36c0f6.jpg" width="1568" height="764" class="img_HB6S"></p>
<p>Files are indexed in the background; wait until the status shows a green check before testing.
A few tips that make the biggest difference to answer quality:</p>
<ul>
<li class=""><strong>One topic per section.</strong> Clear headings ("Delivery", "Refunds", "Prices") help the bot find
the right passage.</li>
<li class=""><strong>Write facts down.</strong> If a price or rule only lives in your head, the bot can't know it.</li>
<li class=""><strong>Recordings count.</strong> Webinars, lectures and voice notes are transcribed to text — see
<a class="" href="https://docs.aova.app/docs/how-to/add-audio-and-video">Add audio and video</a>.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="step-3-create-an-agent">Step 3. Create an agent<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#step-3-create-an-agent" class="hash-link" aria-label="Direct link to Step 3. Create an agent" title="Direct link to Step 3. Create an agent" translate="no">​</a></h2>
<p>The <strong>agent</strong> is the assistant itself: an AI model connected to your knowledge base, plus
instructions about tone and boundaries.</p>
<ol>
<li class="">Open the <strong>Agents</strong> tab and click <strong>New agent</strong>.</li>
<li class="">Pick the knowledge base you just filled and choose a model. Claude Haiku or Amazon Nova are
fast and inexpensive defaults; move to a larger model if answers need more reasoning.</li>
<li class="">Optionally, describe how it should talk: "Answer briefly and politely. If the answer isn't in
the documents, say so and suggest contacting <a href="mailto:support@acme.com" target="_blank" rel="noopener noreferrer" class="">support@acme.com</a>."</li>
</ol>
<p><img decoding="async" loading="lazy" alt="Create agent form with a knowledge base and model selected" src="https://docs.aova.app/assets/images/create-agent-filled-8f0447d35ad198b9a59dadfc7811f004.jpg" width="1568" height="764" class="img_HB6S"></p>
<p>Click <strong>Test</strong> to chat with the agent right in the dashboard before connecting Telegram.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="step-4-connect-the-telegram-channel">Step 4. Connect the Telegram channel<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#step-4-connect-the-telegram-channel" class="hash-link" aria-label="Direct link to Step 4. Connect the Telegram channel" title="Direct link to Step 4. Connect the Telegram channel" translate="no">​</a></h2>
<ol>
<li class="">On the agent's page, open the <strong>Channels</strong> panel and click <strong>Add channel</strong>.</li>
<li class="">Choose <strong>Telegram</strong>, give the channel a name and paste the token from Step 1.</li>
<li class="">Click <strong>Create</strong>.</li>
</ol>
<p><img decoding="async" loading="lazy" alt="New channel dialog set to Telegram, with a Bot token field" src="https://docs.aova.app/assets/images/new-channel-telegram-416f8190d28b304f678c4199484799b9.jpg" width="1568" height="764" class="img_HB6S"></p>
<p>That's it. Open your bot in Telegram, press <strong>Start</strong> and ask it something from your documents.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="keep-it-improving">Keep it improving<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#keep-it-improving" class="hash-link" aria-label="Direct link to Keep it improving" title="Direct link to Keep it improving" translate="no">​</a></h2>
<ul>
<li class=""><strong>Check the conversations.</strong> Every chat appears in <strong>Contacts</strong>, so you can see what people
actually ask — and which questions your documents don't answer yet.</li>
<li class=""><strong>Fill the gaps.</strong> When the bot says it doesn't know something it should, add a short document
that covers it. That fixes the answer faster than rewording the instructions.</li>
<li class=""><strong>Add more channels.</strong> The same agent can answer on your website with a
<a class="" href="https://docs.aova.app/docs/how-to/embed-the-chat-widget">chat widget</a> — no extra setup of the knowledge.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="faq">FAQ<a href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents#faq" class="hash-link" aria-label="Direct link to FAQ" title="Direct link to FAQ" translate="no">​</a></h2>
<p><strong>Do I need to know how to program?</strong> No. Everything above happens in Telegram and the AOVA
dashboard.</p>
<p><strong>Will the bot make things up?</strong> It answers from the passages it finds in your knowledge base
(this approach is called retrieval-augmented generation). If the information isn't there, it
follows your instructions — for example, saying it doesn't know. More in
<a class="" href="https://docs.aova.app/docs/explanation/how-your-assistant-answers">How your assistant answers</a>.</p>
<p><strong>What does it cost?</strong> There's a free plan to try it with your own documents. After that you pay
in credits for the answers the bot actually gives — see <a href="https://aova.app/#pricing" target="_blank" rel="noopener noreferrer" class="">pricing</a>.</p>
<p><strong>Can I use it in a Telegram group?</strong> AOVA connects to the bot you create; how the bot behaves in
groups follows Telegram's own bot settings (such as privacy mode in @BotFather).</p>
<hr>
<p><strong>Ready to try?</strong> <a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=telegram-bot-guide" target="_blank" rel="noopener noreferrer" class="">Create your Telegram bot for free →</a></p>]]></content:encoded>
            <category>Telegram</category>
            <category>Tutorial</category>
        </item>
        <item>
            <title><![CDATA[Turn your expertise or course into a 24/7 AI assistant in Telegram]]></title>
            <link>https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant</link>
            <guid>https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant</guid>
            <pubDate>Tue, 29 Sep 2026 11:00:00 GMT</pubDate>
            <description><![CDATA[For coaches, consultants and course creators — how to turn your materials, webinars and methodology into a Telegram assistant that answers students and clients in your voice, around the clock.]]></description>
            <content:encoded><![CDATA[<p>If you teach, consult or coach, you answer the same questions again and again: <em>where's the
recording of lesson 3, how do I apply step 2 to my case, what did you say about pricing
objections?</em> The answers already exist — in your slides, workbooks, webinar recordings and
old chat replies. An AI assistant built on <strong>your</strong> materials can give them instantly, at 2 a.m.,
in the Telegram chat your audience already uses.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="why-telegram-first">Why Telegram first<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#why-telegram-first" class="hash-link" aria-label="Direct link to Why Telegram first" title="Direct link to Why Telegram first" translate="no">​</a></h2>
<p>Your students and clients are already in Telegram: course chats, your channel, private messages.
A bot there needs no new app, no login and no link to remember — they just write to it. It's
also the fastest channel to set up: one token from @BotFather and you're live.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="what-to-put-in-the-knowledge-base">What to put in the knowledge base<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#what-to-put-in-the-knowledge-base" class="hash-link" aria-label="Direct link to What to put in the knowledge base" title="Direct link to What to put in the knowledge base" translate="no">​</a></h2>
<p>Think of it as everything you'd hand a brilliant new assistant on their first day:</p>
<table><thead><tr><th>Material</th><th>Why it helps</th></tr></thead><tbody><tr><td>Course modules, workbooks, slide decks (PDF, DOCX)</td><td>The core of your methodology</td></tr><tr><td>Webinar, lecture and Q&amp;A recordings (MP3, MP4, M4A…)</td><td>Transcribed automatically — often your best explanations are spoken, not written</td></tr><tr><td>FAQ and your best replies from chats</td><td>The exact questions people really ask</td></tr><tr><td>Program terms: schedule, prices, access rules</td><td>So logistics questions stop reaching you</td></tr></tbody></table>
<p>Recordings are billed at 5 credits per minute and shown as an estimate before you upload —
see <a class="" href="https://docs.aova.app/docs/how-to/add-audio-and-video">Add audio and video</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="make-it-sound-like-you">Make it sound like you<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#make-it-sound-like-you" class="hash-link" aria-label="Direct link to Make it sound like you" title="Direct link to Make it sound like you" translate="no">​</a></h2>
<p>In the agent's instructions, describe your style and boundaries. For example:</p>
<blockquote>
<p>You are the assistant of the "Confident Negotiation" course. Answer like the author: warm,
direct, with a practical example. Answer only from the course materials. If a question needs
personal coaching, suggest booking a session at example.com/call.</p>
</blockquote>
<p>Instructions shape <strong>tone and limits</strong>; the <strong>facts</strong> still come from your materials. If an answer
is wrong or missing, the fix is almost always adding or clarifying a document.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="ideas-that-work-well">Ideas that work well<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#ideas-that-work-well" class="hash-link" aria-label="Direct link to Ideas that work well" title="Direct link to Ideas that work well" translate="no">​</a></h2>
<ul>
<li class=""><strong>Course companion.</strong> Students ask "how does the framework from module 4 apply to…" and get
an answer grounded in the lesson itself.</li>
<li class=""><strong>Pre-sales assistant.</strong> Prospective clients learn about your program, format and prices
before they ever book a call.</li>
<li class=""><strong>Your back catalogue, searchable.</strong> Years of webinars become something people can actually
ask questions to, instead of hours of video nobody rewatches.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="keep-control">Keep control<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#keep-control" class="hash-link" aria-label="Direct link to Keep control" title="Direct link to Keep control" translate="no">​</a></h2>
<p>Every conversation is saved under <strong>Contacts</strong>, so you can read what people ask, spot gaps in your
materials — and discover questions worth turning into your next post or lesson. You can switch the
AI model at any time without rebuilding the knowledge base.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="get-started">Get started<a href="https://docs.aova.app/blog/turn-your-expertise-into-a-telegram-assistant#get-started" class="hash-link" aria-label="Direct link to Get started" title="Direct link to Get started" translate="no">​</a></h2>
<p>The step-by-step setup (BotFather → knowledge base → agent → channel) is in
<a class="" href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents">How to create an AI Telegram bot that answers from your documents</a>.
It takes about ten minutes, and there's a free plan to try it with your own materials.</p>
<p><strong><a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=expert-assistant" target="_blank" rel="noopener noreferrer" class="">Create your assistant for free →</a></strong></p>]]></content:encoded>
            <category>Telegram</category>
            <category>Use cases</category>
        </item>
        <item>
            <title><![CDATA[A Telegram support bot for your small business — FAQ answered from your own files]]></title>
            <link>https://docs.aova.app/blog/telegram-support-bot-for-small-business</link>
            <guid>https://docs.aova.app/blog/telegram-support-bot-for-small-business</guid>
            <pubDate>Tue, 29 Sep 2026 10:00:00 GMT</pubDate>
            <description><![CDATA[How a small business can set up a Telegram customer-support bot that answers questions about prices, delivery, bookings and policies from its own documents — and hands off what it can't answer.]]></description>
            <content:encoded><![CDATA[<p>For a small business, every unanswered message in Telegram is a customer who might go elsewhere.
But most of those messages are the same dozen questions: <em>what are your hours, how much is
delivery, can I return this, do you have a slot on Saturday?</em> A support bot that answers them from
your own price list and policies takes that load off — without giving customers made-up answers.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="start-from-the-questions-not-the-bot">Start from the questions, not the bot<a href="https://docs.aova.app/blog/telegram-support-bot-for-small-business#start-from-the-questions-not-the-bot" class="hash-link" aria-label="Direct link to Start from the questions, not the bot" title="Direct link to Start from the questions, not the bot" translate="no">​</a></h2>
<p>Before building anything, scroll through your last month of messages and write down the
questions that come up most. Then check that each one is answered somewhere in writing. Typical
starter set:</p>
<ul>
<li class=""><strong>Price list</strong> or menu (PDF or spreadsheet exported to PDF).</li>
<li class=""><strong>Delivery, returns and payment</strong> terms.</li>
<li class=""><strong>Opening hours, address, how to book.</strong></li>
<li class=""><strong>An FAQ</strong> — even a rough one written in 20 minutes beats nothing.</li>
</ul>
<p>Upload these into a knowledge base. The bot answers from the passages it finds there, so the
quality of these files matters more than anything else.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="set-boundaries-in-the-agents-instructions">Set boundaries in the agent's instructions<a href="https://docs.aova.app/blog/telegram-support-bot-for-small-business#set-boundaries-in-the-agents-instructions" class="hash-link" aria-label="Direct link to Set boundaries in the agent's instructions" title="Direct link to Set boundaries in the agent's instructions" translate="no">​</a></h2>
<p>A good support bot knows what it <em>shouldn't</em> do. For example:</p>
<blockquote>
<p>You are the assistant of Acme Flowers. Answer briefly and politely, only from the documents.
Never promise discounts or delivery times that are not in the documents. If the customer wants
to place an order or has a complaint, give them our phone +44 20 0000 0000 and working hours.</p>
</blockquote>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="connect-telegram">Connect Telegram<a href="https://docs.aova.app/blog/telegram-support-bot-for-small-business#connect-telegram" class="hash-link" aria-label="Direct link to Connect Telegram" title="Direct link to Connect Telegram" translate="no">​</a></h2>
<p>Create a bot with @BotFather, paste its token into a Telegram channel on your agent — the full
walkthrough with screenshots is in
<a class="" href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents">How to create an AI Telegram bot that answers from your documents</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="run-it-like-a-support-team-would">Run it like a support team would<a href="https://docs.aova.app/blog/telegram-support-bot-for-small-business#run-it-like-a-support-team-would" class="hash-link" aria-label="Direct link to Run it like a support team would" title="Direct link to Run it like a support team would" translate="no">​</a></h2>
<ul>
<li class=""><strong>Read the conversations weekly.</strong> They're all under <strong>Contacts</strong>. The questions the bot
couldn't answer are your to-do list: add a line to the FAQ and it knows next time.</li>
<li class=""><strong>Update, don't rebuild.</strong> Prices changed? Re-upload the price list — the bot picks up the new
version once it's processed.</li>
<li class=""><strong>Add the website next.</strong> The same agent can answer in a <a class="" href="https://docs.aova.app/docs/how-to/embed-the-chat-widget">chat widget on your
site</a>, so customers get the same answers everywhere.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="what-it-costs">What it costs<a href="https://docs.aova.app/blog/telegram-support-bot-for-small-business#what-it-costs" class="hash-link" aria-label="Direct link to What it costs" title="Direct link to What it costs" translate="no">​</a></h2>
<p>There's a free plan to try it with your own documents. After that you pay in credits for answers
the bot actually gives — a typical answer on a fast model costs about 1–2 credits. Details on the
<a href="https://aova.app/#pricing" target="_blank" rel="noopener noreferrer" class="">pricing page</a>.</p>
<p><strong><a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=support-bot" target="_blank" rel="noopener noreferrer" class="">Set up your support bot for free →</a></strong></p>]]></content:encoded>
            <category>Telegram</category>
            <category>Use cases</category>
        </item>
        <item>
            <title><![CDATA[Turn voice and video recordings into your bot's knowledge]]></title>
            <link>https://docs.aova.app/blog/turn-recordings-into-bot-knowledge</link>
            <guid>https://docs.aova.app/blog/turn-recordings-into-bot-knowledge</guid>
            <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
            <description><![CDATA[Webinars, lectures, sales calls and voice notes can become the knowledge base of an AI Telegram bot. How automatic transcription works in AOVA, which formats are supported, and what it costs.]]></description>
            <content:encoded><![CDATA[<p>A lot of what you know was never written down. It's in webinars, lectures, client calls and voice
notes — hours of recordings nobody will ever rewatch. AOVA can turn that speech into text and put it
in your bot's knowledge base, so people can simply <strong>ask</strong> your recordings a question.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="how-it-works">How it works<a href="https://docs.aova.app/blog/turn-recordings-into-bot-knowledge#how-it-works" class="hash-link" aria-label="Direct link to How it works" title="Direct link to How it works" translate="no">​</a></h2>
<ol>
<li class="">You drop a recording into a knowledge base next to your documents.</li>
<li class="">AOVA transcribes the speech to text, with a timestamp at the start of each paragraph.</li>
<li class="">The transcript is indexed like any other document. Your agent — in Telegram, on your website,
anywhere — can now answer from it.</li>
</ol>
<p>The original audio or video isn't kept after transcription; only the text stays in your knowledge base.</p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="supported-files">Supported files<a href="https://docs.aova.app/blog/turn-recordings-into-bot-knowledge#supported-files" class="hash-link" aria-label="Direct link to Supported files" title="Direct link to Supported files" translate="no">​</a></h2>
<table><thead><tr><th>What</th><th>Details</th></tr></thead><tbody><tr><td><strong>Audio</strong></td><td>MP3, WAV, M4A, FLAC, OGG, AMR, WEBM</td></tr><tr><td><strong>Video</strong></td><td>MP4 (only the soundtrack is used)</td></tr><tr><td><strong>Size and length</strong></td><td>Up to 1 GB and 4 hours per file</td></tr><tr><td><strong>Languages</strong></td><td>Detected automatically: English, Russian, Ukrainian, German, French, Spanish, Italian, Portuguese, Polish, Turkish</td></tr><tr><td><strong>Cost</strong></td><td>5 credits per minute of recording, rounded up per file</td></tr></tbody></table>
<p>Before you upload, the dialog shows each recording's length, the estimated credits and your
balance — so there are no surprises.</p>
<p><img decoding="async" loading="lazy" alt="The upload dialog with a recording staged, showing its length and credit estimate" src="https://docs.aova.app/assets/images/audio-upload-estimate-03525ecb3cc66b248d482ff1915337ca.jpg" width="1568" height="1080" class="img_HB6S"></p>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="good-candidates">Good candidates<a href="https://docs.aova.app/blog/turn-recordings-into-bot-knowledge#good-candidates" class="hash-link" aria-label="Direct link to Good candidates" title="Direct link to Good candidates" translate="no">​</a></h2>
<ul>
<li class=""><strong>Webinars and lectures</strong> — become a Q&amp;A assistant for your course or community.</li>
<li class=""><strong>Recorded consultations or demos</strong> — the explanations you've given a hundred times.</li>
<li class=""><strong>Internal voice notes and meetings</strong> — decisions and know-how your team can search by asking.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_bZjq" id="tips-for-better-answers">Tips for better answers<a href="https://docs.aova.app/blog/turn-recordings-into-bot-knowledge#tips-for-better-answers" class="hash-link" aria-label="Direct link to Tips for better answers" title="Direct link to Tips for better answers" translate="no">​</a></h2>
<ul>
<li class=""><strong>Pair recordings with a short glossary.</strong> Speech recognition can mishear names and brand words;
a one-page document that spells them correctly fixes that.</li>
<li class=""><strong>Set the language for short or mixed recordings.</strong> Auto-detection works best on longer clips.</li>
<li class=""><strong>Recordings are answered from words only.</strong> The agent sees what was said — not slides, tone or
what's on screen. If the slides matter, upload them as a PDF too.</li>
</ul>
<p>Full details: <a class="" href="https://docs.aova.app/docs/how-to/add-audio-and-video">Add audio and video</a>. To put it all behind a
Telegram bot, follow <a class="" href="https://docs.aova.app/blog/ai-telegram-bot-from-your-documents">the step-by-step guide</a>.</p>
<p><strong><a href="https://console.aova.app/?utm_source=docs&amp;utm_medium=blog&amp;utm_campaign=recordings" target="_blank" rel="noopener noreferrer" class="">Upload your first recording →</a></strong></p>]]></content:encoded>
            <category>Telegram</category>
            <category>Knowledge base</category>
        </item>
    </channel>
</rss>