Itinerary draft
Prepared from the agreed request, catalog or sources in the enabled workspace.
Already integrated in TALIA · Guided access
AI Travel Builder · TALIA × KISTU
Build itinerary drafts grounded in your real catalog.
KISTU integration is already implemented in TALIA AI Builder: it combines the brief and catalog into a draft with coverage and gaps for review and approval. Access and enabled features are checked for each workspace.
INPUTBrief + catalog
→
OUTPUT reviewable travel proposal
Implemented capabilityEnablement checked per workspace
Source-bound outputsSources, coverage, gaps and unresolved fields
Human approvalNo automatic publishing or import
What you review in the demo
An existing capability to verify in your environment and Travel workflow.
Catalog evidence
Evidence, coverage and gaps remain visible during review.
Review and approval
The operator edits, approves and decides whether to use it in the catalog or proposal.
How it works
From sources to an output ready for approval, with the KISTU workflow already implemented.
Captures context
Starts from the request, catalog, documents and available sources.
Preserves evidence
Structures the result and keeps coverage, gaps, warnings and unresolved fields visible.
Hands off to the operator
A person reviews, edits and decides whether to insert or use the output.
Verified evidence · 23 September 2026
Integration confirmed; the final draft still requires validation.
The check confirmed the handoff from TALIA to KISTU and scaffold construction. The final draft did not pass the expected validation and was not applied or sent. The landing therefore keeps guided access and does not present the test as a successful E2E.
Implemented
The workflow and contract between TALIA and KISTU exist.
Enabled per environment
Configuration and features are checked in each workspace.
Guided commercial access
A demo or enablement does not amount to universal self-service access.
Questions about integration and access
What already exists and what still needs to be checked.
Is AI Builder already implemented or still a future project?
The workflow and KISTU connection are implemented. The latest check confirmed configuration and scaffold construction; the final draft still requires technical validation and is not presented as a successful E2E.
Do Travel Builder and AI Builder mean the same thing?
Travel Builder also includes manual composition and review. AI Builder identifies the KISTU-assisted capability within that TALIA workflow.
Is AI Builder automatically active in every workspace?
No. Access, configuration and enabled features are checked for each environment through the demo or guided enablement process.
Does the draft automatically become a ready proposal?
No. Coverage, gaps and sources must be checked; the operator edits and approves the draft before any operational use.
Control before automation
Data and evidence must remain verifiable.
The result remains a draft or decision aid until the operator approves it.