Vivollo

Adding content

Fill your collection from your website, store, help center, files, or API — and keep it fresh automatically.

A collection needs content, and sources are where it comes from. You connect a source once, and Vivollo pulls in the content — then keeps it fresh on a schedule, so your agent never answers from last month's prices or a policy you've since updated.

You can add several sources to one collection, mixing and matching whatever fits.

The sources you can connect

Your website

Point Vivollo at your sitemap and it crawls your pages — reading each one (even pages that need JavaScript to render) and pulling out the meaningful text. Or add a single URL when you just want one page. This is the quickest way to teach the agent everything that's already written on your site.

Your help center

If your support content lives in Zendesk or WordPress, connect it directly. Vivollo imports your articles (and, for WordPress, their categories and tags) and keeps them in sync as you publish and edit.

Your store

Connect Shopify, WooCommerce, Ticimax, or Trendyol and your live catalog flows in — products, prices, stock, images, variants, and more. For Shopify and Trendyol, you can also import the store's Q&A / knowledge content as a separate source. This is the backbone of a Product collection; see Connecting your store for setup.

Written directly

Some knowledge isn't published anywhere — an internal guideline, a price list, a seasonal FAQ. You can add those to a Knowledge collection as documents you write or paste in directly, in plain text or markdown. Perfect for the answers that live in your head (or a spreadsheet) rather than on your website.

Your own systems (API)

For anything custom, you can push documents into a collection through the API. Useful when your knowledge lives in a system Vivollo doesn't connect to out of the box.

Staying fresh, automatically

Knowledge goes stale, so Vivollo re-checks your sources on a schedule you choose:

  • Once — a one-time import, no re-checking.
  • Daily, weekly, or monthly — re-crawl on a rhythm that matches how often your content changes.

A busy store catalog might refresh daily to keep prices and stock current; a stable policy page might only need a monthly look. When Vivollo re-checks, it notices what's new, changed, or gone and updates the collection accordingly — so the agent's knowledge keeps up with your business without you lifting a finger.

Managing your sources

Each source is yours to control:

  • Run it now — force an immediate refresh when you've just made a big change.
  • Pause and resume — stop re-crawling without deleting what's already there.
  • Check the logs — see when a source last ran, how many items it brought in, and whether anything went wrong.
  • Adjust the schedule — change how often it refreshes, anytime.

After a big content change — a price update, a new policy, a product drop — hit Run it now instead of waiting for the next scheduled refresh. Then ask your agent about it to confirm the new knowledge landed.

A note on freshness vs. instant

Source refreshes happen on a schedule, not the very instant something changes on the other end. For most businesses a daily refresh is more than enough — but if you've just changed something and want to be sure, trigger a manual run rather than waiting.

With content flowing in and staying fresh, the last piece is understanding how the agent actually finds the right answer.

How retrieval works