Assets

Let your chatbot share rich content — documents, images, videos, and booking links — directly inside conversations.

What assets are

Assets let your chatbot share rich content — documents, images, videos, and calendar booking links — directly in conversations. When a visitor asks for your brochure, menu, or a booking link, the AI can surface the right asset in the chat. You manage them under the Assets tab of your chatbot.

Note:
Assets are not used for training. They are content the chatbot shares, not knowledge it learns from. To feed documents to the AI for answering questions, add them as Sources (see the Behaviour tab and the Sources section) instead.

Supported asset types

Documents

PDFs, brochures, menus, forms — shared for visitors to view or download.

Images

Product photos, diagrams, screenshots shown inline in the chat.

Videos

YouTube tutorials and product demos.

Calendar Links

Calendly or Cal.com booking links the AI shares to schedule.

Note: Calendar links are shared as Calendly / Cal.com booking links — this is link sharing, not a direct calendar integration.

Turn assets on

Assets are off by default. Until you enable them, the AI will not reference these items in chat responses.

1

Open the Assets tab

In your chatbot, select the Assets tab.
2

Add an asset

Choose a type (Documents, Images, Videos, Calendar) and select Add asset. Add a clear description so the AI knows when to use it.
3

Enable assets in Advanced Settings

Open Advanced Settings → General and turn on Enable Assets so the chatbot can attach and share them.
4

Publish

Save and publish. The chatbot can now share relevant assets in conversations.

How it works

  • You upload assets with a description that helps the AI understand when to use them.
  • The AI automatically includes relevant assets in responses when appropriate.
  • Visitors can view, download, or interact with assets directly in the chat.
Tip:
Write descriptive overviews for each asset (e.g. "Spring menu PDF — vegetarian and vegan options") so the AI picks the right one to reply with. Vague descriptions lead to the wrong asset being shared.