Find the symptom you’re seeing and the fastest fix — wrong answers, stuck sources, a missing widget, exhausted credits, and access problems.
Find the symptom you’re hitting below and work through the fixes in order — they’re
ordered from most to least common cause. Each one links to the page that covers it in
depth. For shorter how-do-I questions, see the FAQ.
Most agent and answer issues trace back to one thing: a source that isn’t Completed.
That’s always worth checking first.
My agent says it doesn’t know, or gives the wrong answer
The agent answers from the sources in its knowledge base. When it can’t find a match —
or finds the wrong one — work through these in order.
1. Confirm the source is Completed
Open Expertise → Knowledge Base and check the source’s Status. Only
Completed sources are used in answers — content that’s still Unprocessed,
Processing, or Failed is invisible to the agent. See
Manage & reprocess sources.
2. Add a closer-matching Q&A pair
If a relevant source is Completed but the agent still misses, the question wording
probably doesn’t match your content. Add a Q&A pair phrased the
way a real customer asks — Q&A is the most precise way to control an answer. Add a few
variations if customers phrase it different ways.
3. Sharpen your instructions
If the answer is off-tone, off-topic, or guessing, refine your
instructions — set the persona, scope, and a clear fallback
(“if you can’t find the answer, say so — don’t guess”). Save each change as a new
version so you can compare or roll back.
4. Remove or update conflicting sources
A stale or contradicting source can outrank the right one. Update or
delete outdated sources — outdated
content is the most common cause of wrong answers.
5. Re-test before customers see it
Verify the fix in the Sandbox, and check the answer cites the right
source. To compare two full configurations, use the
Playground.
Adding a source runs background processing — read, chunk, and index. Large or
image-heavy files take longer.
It's been on Processing for a while
Large or image-heavy files take longer — give it a few minutes; processing runs in the
background even for big files. If it stays stuck or turns Failed,
reprocess the source from its
Actions menu (⋯).
A file source Failed
Reprocess it first. If it keeps failing, the file may not extract cleanly — scanned
PDFs (images of text) extract less reliably than digital PDFs. Try a text-based version,
or paste the key content as Text or a
Q&A pair. Supported file types are PDF, DOCX, and TXT — see
Upload files.
A website source returned little or no content
The page may render its content with JavaScript, or hide it behind a login or cookie
wall. Confirm the URL is public and reachable in a normal browser, then
reprocess. If it still comes up
empty, paste the key content as an
uploaded file or Q&A. See
Add a website.
A YouTube source failed or returned no transcript
The video likely has no captions, or it’s private/restricted. Use a public video with
captions, or add the content another way. See Add YouTube.
I changed the original content and the agent is out of date
Reprocess the source — it
re-reads, re-chunks, and re-indexes the latest version. For a website or YouTube
source it re-fetches the current content at the URL.
Both snippets from the Embed/Install screen need to be in place, and
your site’s cache cleared.
Check the snippet placement
Confirm both snippets are present: the widget script in your <head> and the config
(window.A2V2WidgetConfig = { chatbotId: "..." }) before </body>. Make sure
chatbotId is filled in and that your site doesn’t strip <script> tags. Copy the
snippet directly from the Embed/Install
screen rather than retyping it.
Check the browser console
Open your browser’s developer console on the page and look for errors. If your site
enforces a strict Content-Security-Policy, allow the widget’s font and script sources.
Clear the cache
Your site or CDN may be serving a cached copy of the page without the snippet.
Hard-refresh the page, and clear any site/CDN cache after embedding.
Fonts or styling look off
The widget loads its own font and isolates its styles in a Shadow DOM, so it won’t
clash with your site. If a strict Content-Security-Policy is blocking it, allow the
widget’s font/script sources. See Embed & install.
I just need a link with nothing to install
Use the Share Link instead — a hosted page you
can send anywhere, no code required.
My agent stopped answering / credits are exhausted
Credits are checked the moment an agent tries to act. At a zero balance, agents stop
generating new answers — but nothing is deleted, and answering resumes as soon as
credits are available.
Confirm the balance hit zero
Open Billing in your organization settings to check your balance. If it’s at zero,
visitors see a notice that there aren’t enough credits to respond, and voice messages
show “Insufficient credits to transcribe this recording.” See
Credits explained.
Top up now
Use Top Up Now to add credits immediately, or wait for your plan credits to refill
at the start of the next billing period. See Auto-recharge.
Prevent it from happening again
Turn on auto-recharge so A2V2.ai tops up automatically when
your balance gets low — set a Max recharges per month cap to bound your spend. For
agents customers rely on, this is the difference between staying online and turning
real visitors away.
Credits dropped faster than expected
A premium model costs more per message than a standard one, and high traffic
multiplies that. Check which model your agent uses on
Model & settings and compare costs in the Sandbox model
selector. Document processing and voice transcription also draw credits. Track spending
on the Usage page.
I topped up but the balance looks the same
Use Refresh Usage on the Billing page to pull the latest figures. Top-up credits
appear under Top-up Credits (“Remaining from recharges”), separate from your
monthly plan credits. Some card payments need an extra verification step from your
bank — the credits are added once that completes.
Auto-recharge stopped working
You may have reached your Max recharges per month cap, or a payment failed. If
several payments fail in a row, A2V2.ai disables auto-recharge. Update your card in the
billing portal, then re-enable it. See
Auto-recharge troubleshooting.
A public agent can be open, restricted to your CRM, or behind a paywall. The fix
depends on which mode it’s in.
Confirm the agent is Public
On Visibility & access, a Private agent is hidden to everyone
but you. Switch it to Public when it’s ready for real visitors.
Visitors are asked to identify before chatting
That’s expected with the Restrict mode — only users from your CRM can use the
agent, so visitors identify before the conversation starts and are captured as
contacts. Switch to Use for Free if you want no-friction access. See
Visibility & access.
A paying visitor can't get in after paying
On a Pay for Access agent, their access duration may have
expired or their message credits may be used up. Check their status in the
Subscriptions table. See
Paid agents troubleshooting.
I enabled Pay for Access but nothing seems set up
Pay for Access is finalized with the A2V2.ai team — after you enable it, they reach
out to set the price and duration. If you haven’t heard back, contact
support@a2v2.ai.
Large or image-heavy files take longer to process — this runs in the background, so you
don’t have to wait on the screen. Track status from the
source list. If it stalls or Fails, reprocess it.
Answers take a moment to appear
The agent streams its reply in real time — while it works, you may see it thinking
and using tools before the final answer appears. Heavier premium models can take a
little longer per answer than lighter ones; compare in the
Model reference.