FR

Knowledge

Sources prepared for answering.

Bring together useful web pages, documents and articles. Your team chooses what Sol and the copilot can consult, then checks replies before deployment.

See how it works
  • Private beta by invitation. Participation terms are agreed individually with each tester.
Compiled doue interface showing knowledge sources and their status with synthetic data.
doue interface showing source type selection in a demo account.

Prepare sources

Add the content that serves as a reference.

Sources display their processing status. Added content must be ready and authorized before it can support a reply.

  • Add a public URL or a supported document.
  • Check errors and readiness status.
  • Respect website, page and document limits.

In your workspace

Publish your own help centre.

In the application, the help centre publishes your company’s articles. The doue website guides explain how to use the platform.

  • Organize categories, languages and articles.
  • Review content before publishing.
  • Check your plan’s help centre and article limits.
Read the guide

Maintain and test

Your policies change. So do your sources.

Check content freshness and the replies it produces. A policy change calls for an update and another test.

  • Refresh sources within available settings and limits.
  • Prepare the French and English content you need.
  • Test replies and human handoff situations.
doue interface showing assistant languages and coverage of sources and tests in a synthetic account.

Features and access

What your team can do.

Availability follows enabled features, permissions and account limits.

Available today

Web pages

Crawl authorized public content within account limits.

Documents

Add supported documents and check their processing.

Product help centre

Organize your public articles and use them as knowledge.

Reply tests

Check the knowledge used before expanding Sol’s use.

Limits and control

A clear framework for the team.

An available feature does not replace checking the context.

  • A source does not authorize an action or commercial exception.
  • Status, permissions and account limits determine which content can be consulted.
  • Bilingual content requires review by your team; automatic synchronization is not promised.

Explore this workflow in doue.

Check pricing for allowances, or tell us about your team.

Contact us
  • Access by invitation
  • Terms agreed individually
  • Private beta by invitation. Participation terms are agreed individually with each tester.