Skip to main content
Supply the agent with knowledge about your product through the Knowledge tab in the Navattic Agent editor. The more context the agent has, the better it can answer questions and demonstrate relevant features.

Product context

Product context is general information about your product, key features, and value propositions. This helps the agent understand what to demonstrate and when. Click Upload context to have Copilot extract context automatically from a website URL or an uploaded document (PDF, Word, or text file). Copilot shows you a preview of the extracted content before applying it.

Knowledge resources

Add documentation, support articles, or other materials that the agent can reference. When you add a URL, Navattic crawls the site and formats the content for the agent to reference during demos. Full-website crawls appear as a single entry for the hostname. Click the entry to open a page browser where you can browse and search all crawled pages, organized by folder. To manage a source, hover over it and click the menu. Available actions depend on the source type: Flag a source as outdated to mark it for review without removing it from the agent’s context immediately.

FAQs

Common questions and their answers help the agent respond accurately to frequently asked questions.

Pronunciations

Control how your agent pronounces specific words during voice synthesis. Use this for product names, technical terms, or brand names that the voice model might mispronounce by default. Each entry has two fields:
  • Term: The word or phrase as it appears in your product content (for example, “Navattic”)
  • Pronunciation: A phonetic respelling using hyphens to separate syllables (for example, “nuh-VAT-ick”). Capitalize syllables to indicate stress for your own reference; the agent normalizes the spelling before sending it to the voice model.
Pronunciations are applied automatically to everything the agent says. You do not need to add them to scripts or instructions separately.

Sharing resources during demos

Resources are links and files you pre-configure in the Knowledge tab that the agent can drop into the chat panel as rich-preview cards at the right moment in a conversation. When the agent determines that a resource is relevant, based on what the prospect is asking about and the When to share guidance you provide, it automatically sends the card into the chat. The prospect sees the title, a short description, and for links, a thumbnail preview. They can open the link in a new tab or download the file without leaving the demo. A badge on the chat toggle shows how many new resources have been shared while the panel is closed, so prospects don’t miss them.
1

Open the Resources section

In the Navattic Agent builder, open the Knowledge tab. Scroll to the Resources section and click Add link.
2

Enter the URL

Paste the link URL. Navattic automatically fetches the page title, description, and preview image. You can edit any of these fields.
3

Fill in the details

  • Title: The headline shown on the chat card (required). - Description: A short summary shown beneath the title on the card (optional but recommended). - When to share: Instructions for the agent describing when to surface this resource, e.g. “When the prospect asks about pricing tiers or wants enterprise pricing.”
4

Save

Click Save. The resource appears in the Resources list and is immediately available to the agent.

Adding a file resource

1

Open the Resources section

In the Knowledge tab, click Add file.
2

Upload the file

Drag a file into the upload area or click to browse. Supported formats are the same as knowledge base documents (PDF, Word, plain text).
3

Fill in the details

  • Title: The name shown on the chat card (required). - Description: A short summary visible to the prospect (optional). - When to share: Instructions for the agent, e.g. “When the prospect asks for the security overview or SOC 2 report.”
4

Save

Click Save. The file is uploaded and the resource is available to the agent immediately.
The When to share field is the most important part of each resource. Be specific about the conversation signals that should trigger sharing. Vague guidance leads to the agent sharing too broadly or not at all.
Each resource is only shared once per session. If the agent determines the same resource is relevant a second time, it will not resend it.