On a new episode of Avid Travel With Britton Frost, I am joined again by the Co-Founder and Executive Vice President of AmaWaterways, Kristin Karst. This week, we are discussing water levels.
Kristin puts the issue simply, stating that the issue is Mother Nature – and there is not much you can do about that. The only thing the river cruise companies can control is how they react. This reaction comes from a mix of quick thinking and teamwork. Communication is key in these situations, not only between cruise operator and guest, but within the cruise company itself.
Using her recent Danube cruise as an example, Kristin then speaks to how AmaWaterways has been handling the low water levels on the rivers – usually by rerouting itineraries. She even highlights a change in itinerary that led to an excursion hosted by a Count.
That and so much more on this week’s podcast. Listen below.
https://soundcloud.com/brittonfrost/avid-travel-with-britton-5
Denise Di Nicola says
We did that when we did the Po River cruise Venice. We were with Uniworld. Because we did not come on day of departure we had to find our own way to the riverboat. We phone the number given a few days before found a river taxi that would take us and set off only to find they again changed there dicking arrangements and not notified us. Of course. Venice is unique because often their “roads” are waterways. We phoned again and were told were they had moved the docking to and our friendly water taxi driver said no problem. However when we found the boat we could no transfer to it or be put off on the dock due to water levels. What a disaster. We had to be taken by our water taxi to a place nearest where we could get off the taxi which was a huge distance away and find other transport to deliver us by road to the riverboat. Very bad if Uniworld to not tell us they were now only accessible by road And guess what ? Not an apology when we’re finally arrived. The boat trip however in spite of water level problems on the trip was outstanding
Ralph Grizzle says
Thanks for sharing this. We’re sorry to hear it – and that you received no apology.