This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

How a Chatbot Can Help You Build a Strong and Productive Team

  • 13757 views
  • 12 min
  • Nov 28, 2017
Kirill S.

Kirill S.

Ruby/JS Developer

Gleb B.

Gleb B.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Tags:

Share

The digital age has changed how we work.

Today, people from different parts of the world can work on the same project without ever meeting each other. Still, insufficient communication can harm team efforts and make collaboration inefficient.

Poor communication causes teams to become less motivated and productive. Solving the problem of communication is extremely important for all businesses, from relatively small companies to large multi-billion-dollar corporations.

The founder of betwixt.us approached RubyGarage with a fantastic solution to this problem – zanie, a chatbot to help companies build strong and productive teams.

Idea

Delivering a viable product that fully realized zanie’s goals was a challenge for our team. To develop a successful digital product, you need to ensure that software is not only useful for businesses but convenient for users.

We put ourselves in the shoes of businesses to define the right functionality and put ourselves in the shoes of users to make zanie intuitive.

In-depth research, a lot of brainstorming, and hours of discussions with our client gave us a complete understanding of what functionality this Slack chatbot should have and how we should build it.

That’s how zanie passed from a concept to a blueprint for further development.

What is Zanie?

Zanie is a virtual host or, in other words, a chatbot whose task is to build bridges between people by promoting communication and helping teams be more efficient.

Zanie was conceived as a chatbot that would integrate with one of popular communication tools used by businesses, so that team members could engage in informal conversations right in the messaging platform they already use.

Zanie is based on a solid scientific background, as the team behind zanie developed a unique 4-D framework based on principles from psychology, sociology, human behavior, and philosophy (which we’ll talk about later).

Zanie’s Business Value

Zanie is a powerful tool for businesses that helps them boost productivity and effectiveness. It’s a cloud-based team building solution that encourages interesting and meaningful conversations that build trust and ultimately make teams more productive.

Here’s a chart showing how zanie brings real-life results by asking questions and sparking conversations:

Zanie Flow

As you can see, zanie offers a concrete benefit – higher productivity.

Zanie is a helpful tool not only for distributed teams but for co-located teams as well; this chatbot helps build stronger teams within any company. Moreover, zanie is a powerful tool for HR departments, letting them receive feedback from employees.

How Does Zanie Work for Businesses?

Using a chatbot for team building sounds great, but you’re likely wondering how it works. Before explaining how our team developed zanie, you need to have a clear understanding of how exactly businesses use this chatbot.

Imagine you’re a business owner who wants to boost your team’s performance with the help of zanie. There are several steps to this process:

Step #1 Add zanie to your Slack team and set it up

First, you need to add zanie to your existing Slack team. Next, zanie will let you create groups, assign administrators, and manage team members. Of course, you can create groups based on your company’s own preferences (for example, by department, by location, or randomly).

Zanie Configuration

Step #2 Zanie conducts polls

Once you’re done setting up your Slack team, zanie can start interacting with it. First, zanie gets acquainted with your team by polling all team members. Zanie uses two polling rounds that contain different types of questions:

  • Onboarding round. The questions in this first round are useful for HR departments as they help them learn more about each team. The onboarding round helps companies find out how people interact within their teams. These questions can be tailored to the needs of your company.
Onboarding Round
  • Lightning round. When the onboarding round is over, zanie moves to the lightning round that includes simple and entertaining questions. The purpose of this round is to get users interested in conversations with the Zanie bot.
Lightning Round

Step #3 Zanie asks questions

When the two polling rounds are over, zanie starts asking questions to trigger discussion. The chatbot creates a new Slack discussion channel and adds people who have answered zanie's questions. Team members can see each other’s responses and thus have something to discuss.

All of zanie’s conversation starters are designed according to the 4-D framework developed in collaboration with the Institute of Cognitive and Brain Sciences at UC Berkeley. This framework is designed to bring people together despite their location, culture, and so on.

The framework is based largely on Social Penetration Theory, which states that interpersonal communication gradually progresses from shallow to more intimate levels.

Zanie Question

The 4-D framework involves incremental and frequent interactions, so zanie asks a new question at a specified interval (daily, weekly, etc.). When the chatbot asks a new question, it archives the previous discussion channel and creates a new one.

Step #4 Receive advanced real-time analytics

Businesses must be sure that zanie works well, which means they need to monitor the performance of their teams. Zanie has an intuitive dashboard that displays important analytical information about the chatbot (number of groups, activity in each group, etc.).

Zanie’s analytics are based on machine learning algorithms that collect, process, and analyze all information generated by zanie. Thanks to machine learning, zanie is really smart. For example, the chatbot keeps track of the skip rate and doesn't ask questions about topics that most users don't answer. Moreover, zanie matches user responses and clusters people according to interests.

Zanie Dashboard

Challenges

To deliver an effective application, our team had to address a few big challenges:

  • Integrate zanie with the most popular collaboration platforms used by businesses
  • Design a scalable architecture capable of being upgraded without downtime
  • Create an effective mechanism for interactions between the chatbot and users
  • Suggest and implement a monetization strategy
  • Develop an easy-to-use dashboard for clients to track zanie’s performance and manage their Slack team accounts
  • Implement data collection functionality and machine learning algorithms for data analysis

This project was really exciting for RubyGarage, as it required non-standard approaches and out-of-the-box thinking. As soon as we defined the main challenges, we got down to turning the idea into a fully functional digital product.

Solutions

Zanie isn’t a typical web or mobile application like our team usually develops, but rather a chatbot integrated into a messaging platform. Building a fully functional chatbot was a real challenge, so our team carried out a lot of research to find solutions.

Slack as the Launch Platform for Zanie

Efficient communication is one of the pillars of productivity. No wonder there are many messaging tools designed specifically for businesses, including:

  • Slack. Launched in 2014, Slack quickly became the fastest-growing app in history. As of November 2017, Slack was used by over 50,000 paying companies and boasted 9 million weekly active users. Slack provides direct and group messaging, video and voice calls, smart notifications, lots of integrations with third-party solutions, and more.
  • Microsoft Teams. Microsoft’s hub for teamwork supports chats, calls, meetings, integrated Office 365 apps, and other functionalities for team collaboration.
  • Stride. In September 2017, Atlassian’s previous team collaboration platform, HipChat, was replaced with a new tool called Stride. Stride’s functionality includes direct messaging, group chats, video and voice conferencing, meetings, and more. When our team started working on zanie, Stride hadn’t been released.

Our team selected Slack as the first platform to build zanie on with the goal of creating a similar bot for other platforms later on. We chose Slack because, first of all, it’s used by businesses of all sizes – from small companies to large corporations. Second, the Slack API allows developers to easily integrate apps with Slack.

We faced the challenge of integrating zanie with the Slack API. To be able to function as a real user, zanie needed to connect to several Slack APIs:

Using these three Slack APIs allowed our team to build a fully functional chatbot.

Microservice Architecture

To ensure the scalability and updatability of zanie, we decided to go for a microservice architecture. This means that the Slack bot comprises separate microservices that work together. In the microservice architecture, each microservice is in charge of just one functionality and has its own database.

The microservice architecture provides a number of benefits, the most important being:

  • Independent deployment. Each component of a microservices-based application can be deployed independently. This makes updating components fast and easy.
  • Scaled development. The microservice architecture speeds up development, as team members are responsible for rolling out just one particular service.
  • Flexible technology stack. Each service can be developed with different technologies. This allows developers to use the most appropriate technologies for each service.
  • Improved uptime. Faults usually affect only one component, while other services keep functioning.

Now that you know what the microservice architecture is and what benefits it provides, let’s talk about what components (i.e. services) zanie consists of.

  • Chatbot application. This application contains the code responsible for the chatbot’s behavior. It connects to the Slack Real Time Messaging API and Events API to receive events such as channel creation or archiving. Zanie communicates with people using responses from the Slack Real Time Messaging API and zanie’s own API.
  • Zanie RESTful API. This is the main interface for storing and processing data for the chatbot and dashboard.
  • Client dashboard. The dashboard is a single-page application that allows users to manage their accounts and view real-time analytics.
  • Betwixt analytics. To reduce load on the zanie RESTful API, our team built this application specifically to listen to all events in the chatbot and send them to Segment (which is used for pushing data to powerful marketing tools providing deep analytics, such as Mixpanel).
  • Administration platform. This application allows the founder to manage zanie as well as to monitor its performance (through the administrator dashboard). The platform contains a database of questions, stores all user responses, shows statistics (such as a total number of teams and groups), and more. Our team used Active Admin to build this app.

Selecting the right technology stack is crucial for the success of any application. We used the following technologies to build the Slack bot:

Slackbot Technology Stack

Scalability

Our team had to develop a chatbot application that would work perfectly with an increasing number of users. Therefore, scalability was our priority, and we used a service-oriented architecture to achieve it.

We used Amazon EC2 for secure, reliable, and highly scalable cloud-based hosting. To maximize the efficiency of our Amazon Web Services configuration, our team included Elastic Load Balancing and Auto Scaling, which automatically scale capacity up or down depending on conditions.

The Zanie chatbot app is intended to help businesses globally, which means the chatbot requires fast and reliable storage. Our team picked Amazon S3 for object storage, Amazon RDS for a relational database, and ElastiCache as an in-memory data store.

Adding Monetization Functionality

Our team needed to suggest a viable monetization strategy for zanie. According to zanie’s business logic, the chatbot had to be available in two versions – a free trial and a paid version.

Based on this business logic, our team suggested subscription functionality to differentiate free and paid users. This made a payment system necessary to allow users to pay for subscriptions.

We selected Stripe, as this payment platform can be used to manage both subscriptions and payments.

A free trial gives businesses a one-year subscription and allows them to create one group with up to 7 users. If businesses want to keep using zanie after the free one-year subscription expires or if they want to create more than one group, they need to switch to one of the paid versions.

Subscriptions and payments are managed in a client dashboard.

Zanie Subscription

Building the Conversational User Interface

In a conventional web or mobile application, designers create a human-centered graphical interface that helps users interact with the app. In other words, they use the power of a graphical user interface.

Chatbots are different. Being integrated into a messaging tool, a chatbot inherits its graphical interface, so the only way it can interact with users is through conversations. Therefore, a chatbot requires a conversational interface that encourages communication and user involvement.

To help zanie trigger discussions, our team created an engaging conversation interface. First, the chatbot asks questions in a friendly manner so that people feel comfortable interacting with it.

Second, we implemented a button flow for interactions with the chatbot. Initially, we used slash commands to communicate with Zanie, which is the usual method for communicating with bots in Slack. This method, however, turned out to be inefficient, as users were reluctant to answer zanie’s questions by typing slash commands. That’s why our team opted for a button flow that lets team members reply to zanie’s questions by clicking buttons.

Thanks to the button flow, users can answer questions in a matter of seconds and without any special knowledge (not everyone is familiar with Slack commands).

Data Analysis

We’ve already drawn your attention to the strong scientific background behind zanie. To be able to improve and upgrade the chatbot, its owners needed to collect and analyze data related to performance and answers to questions.

So our team implemented data collection functionality – zanie stores information such as message history, likes, stars, and polling results. All this information allows betwixt.us to monitor zanie’s performance and find out which questions are efficient at triggering conversations among team members and which don’t work.

We’ve already mentioned that Zanie uses advanced machine learning algorithms for data analysis. Our team was in charge of preparing data (anonymizing and encrypting it) and implementing algorithms. The algorithms themselves were developed at UC Berkeley.

Wrapping Up

Our team did a great deal of work to deliver a top-notch digital product that connects people across distributed and co-located teams. Zanie helps people get to know each other, establish trust, and work well together.

If you want to develop a chatbot for your business, don’t hesitate to drop us a line. Our team will help you get your project up and running.

CONTENTS

Tags:

Authors:

Kirill S.

Kirill S.

Ruby/JS Developer

Gleb B.

Gleb B.

Copywriter

Vlad V.

Vlad V.

Chief Executive Officer

Rate this article!

Nay
So-so
Not bad
Good
Wow
2 rating, average 4.5 out of 5

Share article with

Comments (0)

There are no comments yet

Leave a comment

Subscribe via email and know it all first!