All work / Case study 01

About 6 minutes to read

YANTRA Task management for Quote Assist

Designing how Sales and Contracting work together on a travel quote.

Status

A proposed feature for a later phase. It has not been built yet, so this case study shows design reasoning, not measured results.

Role
Sole UI/UX designer: workflow, information architecture, interaction design, high-fidelity UI
Project
YANTRA, Thomas Cook India’s internal platform for travel proposals
Period
2026
Status
Proposed, not built
Tools
Figma
The Quote Assist board as Sales sees it: a New Task button, a search box, filters for date range, team, destination and due date, and four columns: My Tasks, Awaiting Response, Response Received and Completed. Each task card has an Air or Land tag, an orange or green top border, a due date and an assignee. Completed is empty.
Fig. 01The Quote Assist board as Sales sees it. One place to request, track and close quotes from both contracting teams. Scroll sideways to see the whole screen.
01

Overview

YANTRA is Thomas Cook India’s internal platform for building travel proposals. Sales, Contracting Air, Contracting Land, Visa and Operations all work in it. I was the only UI/UX designer on the product, and I designed its Task Management feature, called Quote Assist, on my own.

02

The context

To put together a proposal, Sales needs information from the contracting teams. Contracting Air checks airline availability and fares. Contracting Land covers hotels, transport, sightseeing and ground services. A single trip often needs both.

This was a new workflow, not a redesign. There was no task feature in YANTRA to improve, so I started from the process itself: who asks whom for what, and what happens next. The requirements came from my manager, from stakeholders and from my own analysis of the workflow.

03

The design challenge

How might we give Sales one place to request airline and land information, track each request, and keep the conversation and documents for it together?

Three things made this harder than a simple to-do list:

  1. One request can go to two teams, and each team needs different details.
  2. Each team sees the same request from a different side. Sales is waiting for answers. Contracting is working through requests.
  3. The answer is not a yes or no. It is flight options, hotel worksheets and costing, often revised several times.
04

Mapping the workflow

In my design, a request moves between the three teams like this.

  1. 1 · SalesOpens a lead and presses Quote Assist
  2. 2 · SalesPicks Air, Land or both
  3. 3 · SalesFills one form per team
  4. 4 · AirTask appears in New Requests
  5. 4 · LandTask appears in New Requests
  6. 5 · AirWorks on it, replies in Updates, shares files
  7. 5 · LandWorks on it, replies in Updates, shares files
  8. 6 · SalesSees Response Received, reviews, asks follow-ups
  9. 7 · SalesTask completed
Fig. 02Three lanes, one request. Sales starts and closes it. Air and Land work in parallel and answer inside the task.
05 · Decision 1

One request, one or two teams

Sales starts from the lead they are already working on. A Quote Assist button on the Update Lead screen opens a small window that asks one question: which contracting team should handle this request?

  • Both teams are checkboxes, not a single choice, because one trip often needs both flights and hotels.
  • Each option has a one-line description, so a new Sales user can pick the right team without knowing internal team names.
  • With both picked, Create Task becomes a two-step form, one step per team. The button names the next step, so Sales always knows where they are.
  • A confirmation closes the flow, so Sales knows the request has gone out.
Fig. 03Update Lead, top section. The blue Quote Assist button sits on the lead Sales is already editing.
Send to Quote Assist window: two ticked checkboxes, Air Contracting (flight quotations and airline coordination) and Land Contracting (hotels, transport, sightseeing and ground services), with Cancel and Assign buttons.
Fig. 04First window: Sales can pick one team or both. Each option says what the team handles.
Confirmation window: Quote Request Assigned. The quote request has been assigned to Air Contracting and Land Contracting. Buttons: Cancel and Go to Quote Assist.
Fig. 05Last window: the confirmation names both teams and leads straight to the Quote Assist board.
Create Task form, step 1 of 2. A stepper shows Contracting Air active and Contracting Land next. Details and Files tabs, General Details fields for title, due date and assignee, Trip Details for travel place, travel date, preferred airlines and price, and a button labelled Next: Contracting Land.
Fig. 06In between: with both teams picked, Create Task has two steps, Contracting Air then Contracting Land. The button names the next one. Scroll sideways to see the whole screen.
Why a window and not a separate page

It keeps Sales on the lead they were working on, and it keeps the number of steps down. After assigning a task, Sales goes straight to the Quote Assist board, so a full page just for choosing a team would have added a step for no reason.

06 · Decision 2

One board, seen from each team’s side

Every team gets a board with four columns, but the column names follow each team’s point of view. Sales tracks what it is waiting for. Contracting tracks what it is working on. Completed is the same for everyone.

Column names on each team’s board
Sales seesContracting Air and Land see
My TasksNew Requests
Awaiting ResponseIn Progress
Response ReceivedAssigned Task
CompletedCompleted
  • Questions can go both ways. A contracting team can ask Sales something like “Is the client open to 3-star properties if 4-star is sold out?” It appears in Sales’ My Tasks and in the team’s Assigned Task column.
  • On the Sales board, colour and a tag show the team. Air tasks have an orange border and an Air tag. Land tasks have a green border and a Land tag.
  • Filters match how Sales looks for work: opportunity ID, date range, team, destination and due date.
The Quote Assist board for Contracting Air, with columns New Requests, In Progress, Assigned Task and Completed. The cards are airline requests for Dubai, Bali, Hanoi, Vietnam and Singapore. One card in Assigned Task carries a grey Sales tag.
Fig. 07Contracting Air’s board. Every request here is an Air task, so there is no team filter. Assigned Task holds a card tagged Sales. Scroll sideways to see the whole screen.
The Quote Assist board for Contracting Land, with the same four columns and hotel and land requests for Dubai, Phuket, Osaka, Vietnam and Da Nang. In Assigned Task, a card tagged Sales asks: Is the client open to 3-star properties if 4-star is sold out?
Fig. 08Contracting Land’s board uses the same structure and the same names as Air. Its question to Sales sits in Assigned Task. Scroll sideways to see the whole screen.
Team filter menu: All Teams (selected), Contracting Air, Contracting Land. Destination filter menu with a search box: All Destinations (selected), Vietnam, Dubai, Singapore.
Fig. 09Team and destination filters. The destination list has its own search for long lists.
Why separate column names

Sales and Contracting work on the same tasks, but their responsibilities and expectations differ. Sales needs to see which responses they are waiting for and which have arrived. Contracting needs to see which requests are theirs and what needs their attention. Role-specific names make each status meaningful to the person reading it, so nobody has to translate a generic label into their own situation.

07 · Decision 3

Keep details, conversation and files together

Opening a task shows a summary strip that stays in place across three tabs: the task’s stage, opportunity ID, assignee, status and task ID.

  • Details holds what was asked: title, due date, assignee, destination, travel date, trip length and number of guests.
  • Updates is the conversation. People mention a colleague with @ and attach files, and each file appears inside the message it belongs to.
  • Files collects every document in one list, split into Files Sent and Files Received, with search.

The same document can appear in Updates and in Files on purpose. Updates answers “what happened and why?” Files answers “where is the latest worksheet?”

Fig. 10Details, top section. The summary strip (opportunity ID, assignee, status and task ID) stays in place above the tabs on all three tabs. Full screen. Sample data.
A Land task in Response Received, Updates tab. The summary strip shows opportunity ID, assignee, status and task ID. Below, a box to write an update with Mention and Attach Files buttons, then a thread of messages, two of them with an attached hotel worksheet and an Open Worksheet button.
Fig. 11Updates: the conversation for one task, with each worksheet attached to the message it answers. Sample data. Scroll sideways to see the whole screen.
The same task on the Files tab: Add File and a file search, then a Files Sent list with one PDF and a Files Received list with two hotel worksheets.
Fig. 12Files: every document from the conversation, split into sent and received, with search. Full screen. Sample data. Scroll sideways to see the whole screen.
Why one place instead of email and chat

The work is a continuous back-and-forth of requests, clarifications, responses and documents, all about the same task. Keeping them inside the task keeps the information connected to its context, so nobody has to piece a task’s history together from email, chat and a shared folder. It also makes handoffs easier: when a task moves between teams, the details, the discussion and the documents move with it.

08

From wireframe to final design

Three screens, each as a wireframe and as the final design. The wireframe settles the structure. The final screen adds the content, colour and controls on top of it.

  • Sales board: a header with one main button, a search with four filters, and four columns of cards. None of that moves between wireframe and final.
  • Land response: Contracting Land answers in a workbook. Tour information sits at the top, then one table per day with itinerary, cost, currency and remarks. The team can add a day or upload an Excel file.
  • Air availability: the team pastes availability or uploads an Excel file, then creates options to share with Sales. Each option is one complete itinerary Sales can compare.

Wireframe

Wireframe of the Sales board in grey blocks: a header with one button, a wide search field with four filters beside it, and four columns holding three, four, two and no cards.

Final

Final Sales board: Quote Assist header with a New Task button, search and four filters, and the columns My Tasks, Awaiting Response, Response Received and Completed with Air and Land task cards.
Fig. 13Sales board. The header, filters and four columns stay where the wireframe put them. The cards gain a team tag, a due date and an assignee. Select either screen to open it full size.Scroll the final screen sideways, or tap it to open it full size.

Wireframe

Wireframe of the Land response: a two-column tour information block, a full-width row, two day tables with five columns each, a six-column pricing table, and three tabs along the bottom.

Final

Final Land response workbook for a three-day Sydney tour: a summary strip, Back to Updates and Upload Excel buttons, tour information, an Add Day link, and tables for Day 1, Day 2 and Day 3 with itinerary, cost, currency and remarks. Along the bottom: Hotel 1, Hotel 2, Hotel 3 and Add Hotel tabs, then Cancel and Submit.
Fig. 14Land response workbook. Tour information, then a table for each day. The wireframe shows two days and a pricing table. The final screen shows three days, with hotel tabs, Cancel and Submit along the bottom. Select either screen to open it full size.Scroll the final screen sideways, or tap it to open it full size.

Wireframe

Wireframe of Air availability: a tall panel on the left with two tabs and a large input area, and four option cards on the right, each with two small buttons.

Final

Final Air availability screen: a summary strip, an Add Availability panel with Paste Availability and Upload Excel tabs, a text area and a Create button, and four option cards. Each card shows a route, the flight lines, and edit and delete icons. Cancel and Submit sit at the bottom right.
Fig. 15Air availability. Paste or upload on the left, options on the right. Each option card shows its route and flights, with edit and delete. Four options in this example. Select either screen to open it full size.Scroll the final screen sideways, or tap it to open it full size.
09

Reflection

What I learned

How important it is to understand the different perspectives of people working within the same workflow. Sales and Contracting collaborate on the same tasks, but their priorities, responsibilities and expectations are different. I also learned that designing task management isn’t just about organising tasks into columns. It means thinking through ownership, handoffs, communication, and how information stays accessible for the whole life of a task.

What I would test before it is built

  • Whether Sales understands the difference between Air and Land from the window alone.
  • Whether the different column names help each team, or confuse people who move between boards.
  • How long it takes a contracting team to answer a request, measured before and after launch.
Status

Task Management is planned for a later phase of YANTRA. I will update this case study if it is built.