Find answers and resolve common issues.

Use Forgot password on the login screen. Enter your account email and follow the reset link from your inbox. For security, Amevia will not expose account existence details beyond the standard recovery flow.

Open the verification message sent to your account email and confirm the address. If you did not receive it, check spam folders and request a new verification email from the account flow.

Open the login page and sign in with your account email and password. If you are already signed in on another device, you may need to complete email verification first.

Sign in and open account settings to update profile details and notification preferences for your workspace.

For security, sessions can expire after inactivity. Sign in again from the login page to continue. Unsaved public-page actions are not affected; unfinished workspace edits should be reviewed after you return.

Use Log out from your account menu when you finish on a shared computer. This ends the current workspace session on that browser.

An AI conversation is a visitor session that includes one or more messages with the Amevia agent. A session can contain several visitor messages and agent replies during the same activity window.

Each plan defines how many websites, monthly AI conversations and indexed pages your account can use. See Pricing for the current Free, Starter and Growth limits.

Pages from your website that Amevia may use when answering visitor questions. Only pages that are successfully imported and retained as approved knowledge count toward the plan limit.

You can start on Free and move to Starter or Growth when you need higher limits or paid capabilities. Choose a plan from Pricing, then continue from signup with that plan selected.

Plan limits define the intended usage for each tier. Before public billing launches, Amevia will clearly document how warnings, pauses and upgrades work when a limit is reached.

For teams that need higher limits, deeper website intelligence or tailored workflows, Amevia can be scoped around your requirements. Custom projects may include advanced visitor analytics, conversion funnels, heatmaps, reporting and specialized integrations.

Add the website domain in your workspace, then complete ownership verification before scanning and public installation. Detailed setup steps are in Documentation.

Verification confirms you control the website. Complete the verification step shown in your workspace before running a full content scan.

After verification, run a scan to import website pages as approved knowledge. Re-run a scan after major content updates so the agent stays current.

Missing pages are often blocked by robots rules, unpublished URLs, redirects or crawl limits. Confirm the page is publicly reachable, then recheck or run another scan.

Use another scan from your workspace when pages change. Plan entitlements control whether rescans are manual or automatic.

Remove the website from your workspace when you no longer need the agent on that domain. Related knowledge and conversation retention follow your plan and account settings.

Confirm the script is present on the live page, verify you are testing the connected domain, hard-refresh or clear CDN cache, then recheck installation in Amevia. Review CSP rules if the script is blocked.

After publishing the snippet, use installation recheck in your workspace. Recheck validates that the script can be detected on the connected website.

Copy the installation snippet from Documentation, place it before the closing body tag, publish the page and recheck installation from your workspace.

Install the widget script once per page. Duplicate copies can cause unexpected behavior. Remove extras, publish, then recheck installation.

If you just added the script, purge CDN cache and hard-refresh the browser. Cached HTML without the snippet is a common reason the widget still looks missing.

If your site uses Content-Security-Policy headers, allow the Amevia widget script source. After updating CSP, publish and recheck installation.

Confirm you are viewing the exact domain connected in Amevia. Staging subdomains or alternate hosts will not show the agent until they are connected and installed separately.

Some themes or plugins inject footer scripts automatically. Keep a single install path, remove duplicates, then recheck.

Sign in and open Conversations for the connected website where your plan includes conversation tools. Retention length depends on your plan.

When lead capture is enabled, submitted contacts appear with conversation context in your workspace leads area. Availability depends on your plan capabilities.

Conversation status reflects whether a visitor session is still active or has ended. Use conversation history to review outcomes and follow-up needs.

Confirm lead capture is enabled for the agent and that the conversation reached a capture step. Preview the agent in your workspace before publishing changes.

Configure notification preferences in account or website settings. Common events include new leads and important workspace alerts where enabled.

View page source on the live URL and search for the Amevia widget script. If it is missing, republish the install and clear caches.

Confirm the site is publicly reachable, verification is complete and robots rules allow crawling. Then run another scan and review missing pages.

Purge CDN and browser caches after installing or updating the widget script, then hard-refresh the live page and recheck installation.

Review Content-Security-Policy headers and browser extensions that block third-party scripts. Allow the Amevia script source, then recheck.