Document Ingestion
How Ghloria turns supplier files, emails, and pasted text into structured proposal content.
Document Ingestion
Ghloria uses document ingestion to reduce manual data entry when an agency receives supplier confirmations, booking emails, PDFs, spreadsheets, presentations, or other trip material. The workflow reads operational content, converts it into structured proposal data, and keeps the agent in control before the content becomes part of the proposal.
AI supports the parsing step, but the product behavior is operational: Ghloria helps the team move from fragmented supplier material to a reviewed proposal structure.
What You Can Import
The proposal import dialog supports two main inputs:
- Files:
.xlsx,.xls,.doc,.docx,.ppt,.pptx,.pdf,.html,.eml, and.msg. - Pasted text or email content: useful when the source is an email thread, a supplier note, or copied booking details.
Workspace owners can choose the parsing style for itinerary content, while standard imports use the narrative mode. The import also lets the user choose the proposal output language before processing.
How Processing Works
Start From A Proposal
Open a proposal and choose the import action. Add one or more supported files, or expand the text section and paste the source content.
Ghloria Submits The Job
The app sends the content to the ingestion service and waits for a background task to finish. Large documents can take time, so the import screen shows a processing state while the task is running.
Parsed Content Is Normalized
The returned content is converted into Ghloria's proposal document model. Imported flights, accommodations, options, pricing snapshots, notes, and document groups are marked as imported so they can be handled consistently inside the editor and budget workflow.
Review Before Confirming
Ghloria opens an ingestion review screen with the fields it found. The review step lets the agent mark values as correct or problematic before confirming the import.
Review And Feedback
The review screen is a quality-control layer. It shows structured sections such as trip details, flights, accommodation, itinerary, notes, and budget items when those fields are present in the parsed document.
Users can mark individual fields with thumbs up or thumbs down, use bulk feedback for a section, add an overall rating, and leave a comment. This feedback is submitted in the background and does not block the proposal import.
Feedback does not block import
Thumbs down records that a field needs attention. It does not remove that field from the import. Review the proposal after import and correct any value that should not be used.
Parsed Documents In Proposals
Imported data is preserved as part of the proposal tree, including document_group content for supplier-derived pricing and grouped document details. This allows Ghloria to keep parsed operational data connected to the proposal while still letting agents edit, merge, and price the final client-facing version.
Flight airport codes from imported content are resolved against the airport lookup service when possible. This helps imported flight legs use richer airport records instead of plain text codes.
When To Use It
Use document ingestion when you need to move supplier material into Ghloria quickly:
- Turning booking confirmations into proposal content.
- Importing flights, accommodations, itinerary notes, and supplier pricing.
- Consolidating multiple source documents into a reviewed proposal structure.
- Capturing feedback when the parser identifies a field incorrectly.
For final accuracy, always review imported content in the proposal editor before sharing the proposal with a client.