Pixie — Travel questions. Useful next steps.

Support the uncertainty after booking.

The team explored the information travelers search for before and during a trip, from baggage rules to disruptions. Pixie proposes an assistant layer within the booking app, bringing guidance and possible next actions into the same conversation.

The design challenge

Who it is for

Travelers looking for practical help before and during a trip.

The central task

Ask a travel question and move from an answer to a useful next action.

The design tension

A conversational interface feels approachable, but travel advice also needs clear sources, freshness and limits.

Start a question. Keep the travel context.

The assistant is designed as a sheet within Ixigo, with booking categories still visible behind it.

1. Begin — Suggested prompts introduce what the companion can help with.
2. Ask — Messages and a persistent input let the conversation continue.
3. Act — Quick actions and advisory cards make possible next steps visible.
4. Revisit — History and place details give earlier conversations and suggestions their own views.

Conversation structure shown in the screen set.

Practical information came first.

The team’s questionnaire explored practical travel-information needs. Boarding times and disruption alerts were the strongest signals in the retained charts.

Original team questionnaire: 34 responses to each charted question. Information search allowed multiple selections. These are stated preferences, not usability results. Interview sample and recruitment details were not retained.

Redrawn from the original exports. Bars share a 0–100% scale. Published percentages retain their original rounding.

Design decisions

Make the conversation easier to begin.

Suggested prompts introduce the assistant’s scope before someone types. The companion opens as a sheet over the booking app, preserving context while keeping the input available as the conversation grows.

Separate suggestions from an advisory.

Destination cards make a recommendation scannable; a separate advisory panel gives a possible disruption its own hierarchy and actions. This scenario explores destination discovery; flight-specific questions would need verified airline information.

A friendly layer within the booking app.

Apricot, orange and the illustrated companion establish Pixie’s presence. Neutral message surfaces keep the conversation readable without replacing the parent app’s navigation.

A conversational hierarchy

A welcoming display line introduces the companion; compact body text carries messages, prompts and actions.

Colour roles: Apricot, Orange, Paper, Ink.

Components in context

The examples reproduce the original interface. Travel messages are illustrative prototype content.

An actionable answer still needs a trustworthy source.

Quick actions make the reply more useful, but the interface also raises questions about airline data and how current an answer is. The concept demonstrates the conversation design; reliable live guidance would require verified travel information.

A travel companion with a clear interface direction.

The team concept covers welcome, conversation, recommendations, advisories, history and place details. My primary contribution was translating the shared concept into the interface: a recognizable companion, suggested starting points and a conversation sheet that keeps the booking context in view.

Reflection & next questions

The most important next question is trust: what source, timing and uncertainty information does a traveler need before acting on a reply? That needs evaluation alongside the clarity of the suggested actions.