I have posted my BLOG about my AIR BALTIC EXPERIENCE at about 17h10 PM German time.
My blog connects automatically to my facebook and to my TWITTER ACCOUNT and was published on facebook and twitter.
At June 22, 2010 5:23:30 PM GMT+02:00 (about 15 minutes after I published my BLOG) I have received the first feedback from AirBaltic!!!
Here it is:
I linked to the AIR BALTIC message and went to their TWITTER PAGE and was positively surprised to discover that they have sent me 2 messages.
Here it is:
- @Avi_Konigsberg Can we ask you to send in DM your booking reference so we can investigate?about 1 hour ago via web
- @Avi_Konigsberg Dear Avi, we are listening and regret to hear about poor service of Helsinki airport ground staff.about 1 hour ago via web in reply to Avi_Konigsberg
So, so far so good...
I say that AIR BALTIC should check it the whole way because there were two additional problems that did happen during this flight (IN RIGA and IN DUSSELDORF) and that I plan to publish as NO CUSTOMERS/PASSENGER should accept this code of customer service and customers should be fairly treated!!!!
This POST should make it clear in how strong social media is!
How social media gives consumers a new way to communicate with suppliers
How social media also allows suppliers to react and improve their customer service
Every business should have TWITTER as their communication tool and communication channel where customers can share their experiences with suppliers and where suppliers can share their transparent procedures of solving customers problems.
Thank you TWITTER for giving consumers a voice to protect themselves and force suppliers to act within consumers codes of ethics.
Thank you also to Air Baltic for acting as fast as they did and i hope that they will take this issue and check it rom where it starts (Helsinki) via Riga to where it ended in Dusseldorf.
Let’s wait and see how this issue with Air Baltic is resolved and I will be happy to give Air Baltic the credits and publish my thanks once that they will really solve this issue!!!



















