TALIA × KISTU · IMPLEMENTED INTEGRATION

KISTU is already integrated into AI Builder and Catalog Assistant.

Catalog Assistant supports research and prepares source-backed candidates; after operator review, AI Builder uses the request and approved catalog to prepare an itinerary draft. The draft still requires review and does not automatically become a proposal or booking. Availability is checked per workspace through guided access.

REQUESTSCATALOGS
TALIA + KISTUDRAFTS + CANDIDATESSources · coverage · gaps · review
2 already integrated modulesAI Builder · Catalog Assistant
Workspace-specific enablementGuided access, not public self-service
Operator reviewNo automatic proposal, publishing or import

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 →

Agency operating workflow

From request to proposal, with human control at every stage.

1

Request

The operator structures the client needs, constraints and brief before work begins.

2

Research · Catalog Assistant

Catalog Assistant compares the available catalog and sources, then prepares candidates with evidence and unresolved fields.

3

Review

A person checks sources and relevance, corrects the data and approves any catalog insertion.

4

Proposal draft · AI Builder

AI Builder combines the request and approved catalog into a draft with coverage and gaps. The operator edits it and decides whether to use it in the proposal; no proposal or booking is sent automatically.

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.