1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption. 2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue 3. Missing context for occasional needs: There was no separate space for occasional or one-off requests 4. Lack of tracking & transparency: Users couldn’t see their request's progress
Timeline
12 Days
Live On
Mobile and Desktop
🤣
Guests Had Special Needs
Many travellers wanted to ask for late check-ins, extra beds, or even small surprises like birthday arrangements.
😍
Hidden Request Flow
The option to add special requests was buried deep in the booking journey, so very few people even discovered it.
🔥
No Confirmation from Hotels
Even when requests were made, guests didn’t receive any acknowledgment. This left them uncertain whether the hotel had received or acted on their request.
🥹
bleh
Magicpin's POV
Enable seamless in-app requests, no calls needed Quick acknowledgment builds guest trust Personal touch drives loyalty Smooth flow boosts booking conversions
Hotel's POV
Manage requests via MMT CMS Option to enable/disable requests All chats centralized in Myra Better visibility improves efficiency
1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption.
2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue
3. Missing context for occasional needs: There was no separate space for occasional or one-off requests
4. Lack of tracking & transparency: Users couldn’t see their request's progress
From data, I understood: Awareness Gap – Only 16% of guests (30% premium) accessed Special Requests, showing poor discoverability despite being free. High Drop-offs – 84% dropped off mid-flow due to confusion, effort, or lack of clarity on request placement, leading to more hotel calls. Lost Potential – With 80% using just one request, opportunities for personalization, upsell, and higher engagement were missed. No Communication – Only 16% of users received updates from hotels regarding the status of their requests, while hotels faced significant challenges in managing and responding to them.
This will hide itself!
1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption. 2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue 3. Missing context for occasional needs: There was no separate space for occasional or one-off requests 4. Lack of tracking & transparency: Users couldn’t see their request's progress
Timeline
12 Days
Live On
Mobile and Desktop
🤣
Guests Had Special Needs
Many travellers wanted to ask for late check-ins, extra beds, or even small surprises like birthday arrangements.
😍
Hidden Request Flow
The option to add special requests was buried deep in the booking journey, so very few people even discovered it.
🔥
No Confirmation from Hotels
Even when requests were made, guests didn’t receive any acknowledgment. This left them uncertain whether the hotel had received or acted on their request.
🥹
bleh
Magicpin's POV
Enable seamless in-app requests, no calls needed Quick acknowledgment builds guest trust Personal touch drives loyalty Smooth flow boosts booking conversions
Hotel's POV
Manage requests via MMT CMS Option to enable/disable requests All chats centralized in Myra Better visibility improves efficiency
1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption.
2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue
3. Missing context for occasional needs: There was no separate space for occasional or one-off requests
4. Lack of tracking & transparency: Users couldn’t see their request's progress
From data, I understood: Awareness Gap – Only 16% of guests (30% premium) accessed Special Requests, showing poor discoverability despite being free. High Drop-offs – 84% dropped off mid-flow due to confusion, effort, or lack of clarity on request placement, leading to more hotel calls. Lost Potential – With 80% using just one request, opportunities for personalization, upsell, and higher engagement were missed. No Communication – Only 16% of users received updates from hotels regarding the status of their requests, while hotels faced significant challenges in managing and responding to them.
This will hide itself!
1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption. 2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue 3. Missing context for occasional needs: There was no separate space for occasional or one-off requests 4. Lack of tracking & transparency: Users couldn’t see their request's progress
Timeline
12 Days
Live On
Mobile and Desktop
🤣
Guests Had Special Needs
Many travellers wanted to ask for late check-ins, extra beds, or even small surprises like birthday arrangements.
😍
Hidden Request Flow
The option to add special requests was buried deep in the booking journey, so very few people even discovered it.
🔥
No Confirmation from Hotels
Even when requests were made, guests didn’t receive any acknowledgment. This left them uncertain whether the hotel had received or acted on their request.
🥹
bleh
Magicpin's POV
Enable seamless in-app requests, no calls needed Quick acknowledgment builds guest trust Personal touch drives loyalty Smooth flow boosts booking conversions
Hotel's POV
Manage requests via MMT CMS Option to enable/disable requests All chats centralized in Myra Better visibility improves efficiency
1. No clear entry point: There was no dedicated CTA which reduced visibility and led to low adoption.
2. Choice overload: Once inside the flow, all requests were shown together, creating decision fatigue
3. Missing context for occasional needs: There was no separate space for occasional or one-off requests
4. Lack of tracking & transparency: Users couldn’t see their request's progress
From data, I understood: Awareness Gap – Only 16% of guests (30% premium) accessed Special Requests, showing poor discoverability despite being free. High Drop-offs – 84% dropped off mid-flow due to confusion, effort, or lack of clarity on request placement, leading to more hotel calls. Lost Potential – With 80% using just one request, opportunities for personalization, upsell, and higher engagement were missed. No Communication – Only 16% of users received updates from hotels regarding the status of their requests, while hotels faced significant challenges in managing and responding to them.
This will hide itself!