Existing booking ticket require the right information for all the fields. Agent retrieve information from chat history, hence, sometimes it will hallucinate information if it is not recorded in the chat history.
Existing booking workflow:
user request to book flight -> present confirmation page (sometimes with hallucinated information) -> book ticket (will fail if information inaccurate) -> ticket booked confirmation or failure
New booking workflow:
user request to book flight -> validate ticket (using airline, flight number, departure airport, departure time) -> retrieve other information from flight (such as arrival airport, arrival time etc.) -> present confirmation page to user (with accurate information) -> book ticket -> ticket booked confirmation
Existing booking ticket require the right information for all the fields. Agent retrieve information from chat history, hence, sometimes it will hallucinate information if it is not recorded in the chat history.
Existing booking workflow: user request to book flight -> present confirmation page (sometimes with hallucinated information) -> book ticket (will fail if information inaccurate) -> ticket booked confirmation or failure
New booking workflow: user request to book flight -> validate ticket (using airline, flight number, departure airport, departure time) -> retrieve other information from flight (such as arrival airport, arrival time etc.) -> present confirmation page to user (with accurate information) -> book ticket -> ticket booked confirmation