Spur caught Wander's AI concierge going silent mid-conversation
What this run
has verified.
Spur's AI Feature Testing agent opened Wander's concierge chat, sent a detailed message, and waited for a response. After 10 seconds with no reply and no sign of activity, it flagged the chat as non-responsive.
Response reliability
The concierge chat returning a response naturally.
AI availability
The chatbot staying functional across varying conversation lengths.
Guest support
A working channel for guests to get help during booking.
Session stability
Chat interactions completing without silent failures or timeouts.
Compare
The customer's live site,
captured by
Spur
during the run.
Wait 10 seconds for a response, scroll through the chat
What this
one catch saved.
8hrs
Dev time saved
Shipped, a silent chatbot is the kind of thing that surfaces first through guest complaints, then takes time to reproduce reliably, since it only breaks under certain conversation lengths.
Rescued
User experience
A guest mid-booking who opens the concierge for help and gets no reply doesn't wait around. They leave, or worse, they book somewhere else.
4hrs
Manual QA time
Reproducing this manually means having enough back-and-forth conversations in the chat to trigger the failure, then confirming it's consistent, the kind of edge case that doesn't show up in a quick smoke test.
The actual test
in
No response
A 7-step AI feature test of Wander's concierge chat on staging. Spur opened the chat, sent a complex request, and verified the response before following up with a second question to check quality. It never got past step 3, the concierge didn't respond at all.
Click on the chat icon
Simulate a long and Simple intelligent request in the chat
Wait 10 seconds for a response, scroll through the chat
No response
Verify that the response matches what was asked
Ask a follow up Question
Scroll through the chat
Verify that the question asked is answered well
.avif)
Checkout
.avif)
UI/UX
.avif)
Pricing
Interactions
Checkout
UI/UX
AI Feature Error