|Eyes colour:||Huge gray-green eyes|
|Body features:||I'm slim|
|Hobbies:||Driving a car|
In an effort to be practical, my husband and I decided to marry on our 10th anniversary and keep our anniversary date the same.
For us this meant fulfilling family expectations but spending as little resources and time as possible. Being highly committed to my work made planning a wedding a bit of a challenge; I had to schedule one or two hours weekly on my calendar, and also had a Trello kanban and Airtable lists of providers and guests.
Right after sending the e-vites and publishing the website, my inbox kept getting flooded with questions from our guests. I had little time to reply and often left some messages unanswered for weeks. This soon proved to be very time-consuming for me and my idea of keeping it practical.
By that time, coincidentally, I started working on a chatbot project for the bank I work for, and while benchmarking chatbot platforms, I came to the realization that it was the perfect solution for the flood of wedding messages.
I've created this just for you!
The very next weekend I started detailing the conversational architecture mainly including the frequent questions asked like the date of the wedding, the time of the ceremony or reception, the location, accommodation, the dress code, and also somewhat controversial topics like the registry or the food. The first stage of creating our wedding chatbot was to identify common questions and lay out a carrousel with suggested topics as a conversational starter.
For example, as the wedding day was getting closer, people would rather ask how much time remained until the big day, instead of the date of the wedding. I talked a bit more with a couple of guests to get a sense of what else will they need to know in the future, and planned some follow up questions using the Quick Reply feature on some of the topics that seemed to require more in-depth answers.
Using technology to ease a personal affair
After feeling satisfied with the range of possible questions to answer I sent an inviting our guests to use our chatbot on messenger, and every time I got a new question on my inbox I would just copy-paste a link to the bot. I realized it was important to as some personality traits and an explanation of who they were talking to. This was a very insightful exercise that allowed me to put into practice on a personal level something that I was researching and deing at work for a completely different industry.
A lot of knowledge between both projects were cross-pollinated and helped me anticipate situations for both chatbots.
Salinas matrimony tips & advice
So realizing situations like this and adding some instructions to the chat was very helpful for guests. And the most amazing thing for me is to hear from acquaintances that some of the features that we deed for our wedding have become a reference for several wedding requests for deers and developers locally. This may be the start of a new wedding trend.
If you have any questions or had a similar experience I would love to hear it on the comments or twitter gabrielasalinas. in.
Our Wedding Chatbot. Using technology to ease a personal affair. Gabriela Salinas Follow. Launch time!
But who am I talking to? Takeaways This was a very insightful exercise that allowed me to put into practice on a personal level something that I was researching and deing at work for a completely different industry. Chatbots Magazine Follow. Written by Gabriela Salinas Follow. More From Medium.
Thinking of outsourcing UX deers? Supul Amarakoon in UX Collective. Why Confidence is Key and 10 other useful tips for User-Testing. John Rimmer in UX Planet. How a good UI becomes a good UX. Dizparada in The Startup.
Browse salinas brides
A swift guide to better typography for iOS. Pranav Ambwani in UX Collective. Joshua Smith in Nightingale. DeInTech John Maeda.
Case Study: Garden Space Rebrand. Danyelle Brady.