Xeno Conversation Flows

As a SaaS entrepreneur, I’ve quickly learned that there’s no one-size-fits-all solution for everything.🤷‍♂️ So here in Xeno, our entire team has thought of a way to be able to accommodate as many different customer communication needs as possible. What better way to do that than to let organizations create their own customized communication workflow?🤓 With Xeno Conversation Flows, organizations can now design unique Conversation Flows that match their own needs.💪 Whether you have a support team that’s available 24/7 or just 2 team members, whether you want to communicate over social networks or your website only, whether you have a multilingual target market or a single country market, we made Xeno Conversation Flows just for you! Your imagination is the only limit! 🙌 Try Xeno Conversation Flows now and let us know your thoughts so we can make it an amazing solution for all your customer communication needs!🚀 Cheers, Alex

Hello there! I’m the developer and the maker of Xeno Conversation Flows. This is the biggest project I’ve ever worked on so far so it has been a real challenge for me. To the developers out there, you must know what I mean! From its conception to its development, I’ve been responsible for it since the beginning and brought it to where it is now. I always ask myself questions: Did I build it the right way? Will it meet people’s needs? I must say that all of this started with a few customer needs - that is: * Being able to chat to customers in different languages. * Being able to see your contacts chatting with your bot in real-time. * Being able to take back control of an automated conversation if needed. * Standardizing conversation behaviors between bot and human teams. * Being able to customize all bot responses. * Uniforming code across multiple channels (Chatbox, FB Messenger, Twitter, SMS…). After much thought and after discussing with the entire Xeno team, we figured that these needs could be addressed by a single solution: Conversation Flows! The development was tough but I persevered to make it work. I had to analyze Xeno’s existing behavior and find a way to abstract the messages into reusable components, migrate the legacy data model into a new one, take into consideration beta-testers’ feedback, apply changes in a timely manner as needed, and the list goes on... Also, building the visual flow editor to have a WYSIWYG display has been tough but very fulfilling at the same time. I once tried to build an arrow and I got a match instead (see image: https://pbs.twimg.com/media/EKSd...)! 🤔 Oh! And working on that “auto arrange” / “anti-collision” feature?! It went all haywire at some point, so don't even let me start talking about it! 🤯 The experience has been a rollercoaster ride - there were ups and downs but it was a really fun ride! I continue to work hard in improving the Conversation Flows day-by-day so let me know what you think in the comments section! I look forward to seeing more and more people use Xeno Conversation Flows in the future so, together, let’s make this product the best it can possibly be! Rémy

We were already happy with Xeno, this push it to another level, especially for large teams.