Setup

Install AnswerTide on your site

Seven steps, all inside the dashboard. Most teams finish the first five in one sitting; the last two wait on your website deploy.

  1. Create an account

    Create an account from signup, then choose a plan. The assistant starts answering after your first import of approved content.

    Create an account
  2. Add approved content

    Paste your public website URL, upload a PDF, TXT, or DOCX file, or write an approved Q&A. The assistant answers only from what you add here; an empty or failed import is not ready.

  3. Try the assistant

    Ask a question a real customer would ask. A good answer cites your page. If the content does not cover the question, the assistant says so and offers a person — that is the intended behavior, not an error.

  4. Appearance and handoff

    Set the color, greeting, and suggested questions, add the websites allowed to load the widget, and set a team email for handoff. Email handoff with the full transcript is on every plan, including the trial. Slack handoff is included on Growth and Scale. Scale also includes webhook actions. Add a Slack incoming webhook on Growth and Scale when you want transcript handoffs in Slack.

  5. Voice and teammates

    Browser voice (Talk in the widget) answers from the same approved docs as chat, with source links and human handoff when the docs do not cover it. Paid plans include monthly voice minutes. Turn voice on under Usage & billing when you are ready — visitors see Talk only when voice is enabled for your workspace. Team members are unlimited on every plan. Owners and admins invite teammates from Settings › Team. The invite must be accepted with the same email it was sent to.

  6. Paste the snippet

    Copy the one-line script tag from Install and add it before the closing body tag on your site. Docs platforms that take custom code a different way have their own steps in the install guides. Visitors can ask questions and reach your team without signing in to anything.

    Install guides by platform
  7. Verify readiness

    Install shows what the server actually saw: the widget loading from an allowed website, a test question that got a sourced answer, and a test handoff the email provider accepted. Copying the snippet is not proof of install; a saved email is not proof of delivery.

Ready when your content is

Pricing · Status