TALIA × KISTU · IMPLEMENTED INTEGRATION
KISTU is already integrated into AI Builder and Catalog Assistant.
KISTU integration with TALIA is already implemented in AI Builder and Catalog Assistant. From a brief to an itinerary draft, and from sources to catalog candidates, outputs remain subject to operator review. Availability in your environment is checked through the guided access process.
TALIA · INTEGRATION STATUS
Implementation, enablement and commercial availability are three separate states.
AI Builder and Catalog Assistant already include KISTU. The authenticated check on 23 September reopened a saved Catalog Assistant result with 10 candidates and sources. For AI Builder it confirmed KISTU configuration and scaffold construction; the final draft still requires technical validation and is not presented as a successful E2E. Access remains checked per workspace.
TALIA Assistant, Content Assistant and Business Intelligence remain on the roadmap. The additional supplier PDF extension remains in staging and does not change the status of the base Catalog Assistant integration.
Explore the TALIA platform →AI BUILDER
Build itinerary drafts grounded in your real catalog.
The KISTU-assisted workflow across brief, catalog and draft is implemented. The current demo confirms configuration and processing, but is not presented as a newly successful generation E2E.
TALIA Assistant
Work with Travel context, catalog data and tasks from one place.
Catalog Assistant
Turn Travel sources and documents into dossiers ready to review.
Content Assistant
Create Travel content connected to real catalog items.
Travel Business Intelligence
Turn Travel operations into metrics that support decisions.
KISTU products connected to Travel
Prepare rate documents and migrations before the destination software.
Questions about status and access
Integration does not mean universal enablement or public self-service.
Is KISTU already integrated into TALIA?
Yes, in AI Builder and Catalog Assistant. The implementation exists, but access and enabled features are checked for each workspace and do not amount to a public self-service offering.
What is the difference between implementation, enablement and commercial availability?
Implementation means the KISTU–TALIA workflow has been built. Enablement means the feature is configured in a specific environment. Commercial availability defines who can access it and under which terms; access remains guided today.
Are drafts and candidates published or imported automatically?
No. Outputs remain under operator review. Editing, approval and catalog insertion are explicit steps.
Do all Travel and Supplier modules have the same status?
No. This clarification applies to AI Builder and Catalog Assistant. TALIA Assistant, Content Assistant and Business Intelligence remain on the roadmap; additional supplier PDF intelligence remains in staging.