Crafting a better work experience

Note: Deferred end of support date"In response to the unprecedented situation we are in and knowing that priorities have changed for many of our customers we have decided to postpone retiring Basic Authentication in Exchange Online (MC204828) for those tenants still actively using it until the second half of 2021. We will provide a more precise date when we have a better understanding of the impact of the situation." - Microsoft

No worries, Missive still supports Office 365, Outlook and IMAP. 😅

On October 13th, 2020, Microsoft will stop supporting username & password authentication for the IMAP and POP3 protocols.

In layman terms, any email application out there that connects to Microsoft email servers using IMAP or POP3 (Basic Authentication) will stop working.

Basic Authentication is a term used to explain how an application passes the username and password of a user. It can, in many scenarios, be an insecure method to handle credentials. Especially when a third-party is involved and has to store the user credentials to authenticate itself in the name of the user (cloud email application).

As an alternative Microsoft developed Modern Authentication (a Microsoft term), which is based on an authentication method called OAuth 2.0. This method doesn’t share passwords but instead uses authorization tokens (think of them as temporary passwords) to prove the identity between users and service providers.

The apps that connect to your Microsoft account will never receive the real password. You also get the possibility to revoke access to those apps from your Microsoft account. That in itself is a good thing!

The temporary death of IMAP

The problem is Microsoft deprecating Basic Authentication is the kiss of death for a lot of email clients out there supporting only the IMAP/POP3 protocols. On October 13th, 2020, the only way for email clients to sync emails with Microsoft accounts will be to implement the proprietary Outlook REST API or the Exchange protocol.

Technically, the IMAP protocol supports OAuth 2.0 authentication via an extension; it’s how Gmail works. However, it is unlikely that Microsoft will support this on time. Incoming support has been recently announced, but no ETA was provided:

To make it easier to migrate your existing applications to use OAuth 2.0, we are making significant investments to our service that include OAuth 2.0 support for POP, IMAP, and background application support for Remote PowerShell MFA module. We will be sharing more information on these new features over the coming months.

For our users, this is not a problem; our syncing engine now supports Modern Authentication via Outlook REST API. As a cloud-based email client, not having to store and encrypt user passwords is a massive improvement. It’s just sad and unproductive Microsoft didn’t, out of the gate, offer IMAP connections with the OAuth 2.0 extension.

The changelog is one of the most visited pages on our website. It's visually appealing, informative, and recently a new way to distribute content to our users.

We are using it as a new marketing channel and you can too.

"Your changelog is one of the best I know because it's transparent, you can always see what's going on and see that the app keeps improving fast…"

Simon M.

What is a changelog?

For those who aren't familiar with the concept, a changelog is a tool used to announce changes to a project in a chronological order. Most websites out there with changelogs usually limit to technical updates for current users, but not us. We want ours to be a detailed timeline of our company's journey for new and existing users.

We're not reinventing the wheel here; we are only experimenting with this format of updating customers but with a twist, and we're sharing our experience with you.

Here are a few takeaways and a free goodie for you as well!

Be succinct

Try to keep it short, preferably with only one line of text. The tags (for example IMPROVEDBETANEW) immediately tell the user what the change is about, helping you to go straight to the point.

Sometimes notes are needed to complement the text. We opted for formatting them in smaller font size and different color.

If one line and note is not enough, add a read more link and bring the user to a separate in-depth article.

Add images, gifs, or videos.

Without graphics, it's just a long list of boring text. Try adding images or short videos to enhance the content.

But you don't want to cover the changelog with images. Otherwise, it will become hard to read, losing its appeal.

We usually add images to make the content clearer. For example, if you see this:

You have no idea what this is about; you have no context. But when adding a zoomed-in screenshot, you immediately understand it all.

Make it more than just the product.

Traditional changelogs usually contain modifications to the software like new features, bug fixes, and improved functionality. But this is where you can be creative.

We weren't getting many views on our blog posts and we knew people liked the changelog page, so we added a BLOGtag to the changelog, and people started reading our posts more!

Other tags have been added recently as well. We hired a new employee, so we added a HIREDtag, and one of our users took the time to write an email, welcoming the new teammate!

Email it too!

It's an excellent alternative to the classic overused email newsletter. At the end of 2019, we sent a newsletter formatted as the changelog. It turned out to be a success. The email open-rate was good, our blog post views went up, and we even received encouraging messages to keep this going!

Are you convinced?

Yes! But how can you implement it? Well, there are many changelog SAAS that offer precisely this. Here are three great options:

• Canny: A single service to that lets you implement a changelog, a roadmap, and a feature requests system.
• Beamer
• Changefeed

Or you can build your own like us! It's a simple YAML file in our Rails app. Maybe we can do another blog post about it. Reach out if you would like that.

We hope your users enjoy this as much as ours did!

This end-of-year retreat was different from past ones. We did the usual full week of intense work, but the weekend gave way to a relaxing, cheerful time with everyone's family under one roof.

It all started in mid-October, when Philippe, our CEO, decided it was time for a retreat. He booked a fantastic cabin, barely big enough for the five of us 😗, overlooking the Saint Lawrence River. It was suggested to us by one of our customers: MonsieurChalets.

After doing a quick Doodle to agree on a date, we decided to go during the last week of November. We also decided to hold the company's Christmas party on-site during the weekend. Great idea!

Before we knew it, we were packing suitcases, computer screens, and laptops in two small cars. Did I mention that we bought one week worth of food for five guys? That sort of looks like this:

‍

By 6 pm we were on full retreat mode, our defacto workstation was a big dining table situated on the eastern side of the cabin facing the grandness of the river.

Days passed by very quickly. A typical one went out like this:

6.30-8.30 am - At different times and in no particular order, people would start showing up at the work (dining) table. Some in a grumpy not-a-morning-person kind of way, others with a 5k already under their belt.

8.30-9 am - Self-serve breakfast, which included an array of fruits, eggs, bread, and all-you-can-drink coffee too.

9.30 am - 1 pm - First uninterrupted sprint of work.

1 pm - 1.30 pm - Lunchtime. Delicious and copious lunch prepared by our in-house master chef Philippe.

1:30 pm - 6 pm - Second sprint of work. With a few breaks here and there to refill your coffee mug, take a quick dip in the jacuzzi, go for a jog, or simply to admire the breathtaking view.

6 pm - 7 pm - Dinner time. Another large shared meal and time to open a couple of Coronas.

7 pm - As late as you wish - Third work sprint. For some, the most productive time of day, for others time to slow down and work by the fireplace. For all, a moment to have a ping pong match, a stroll near the cabin or another dip in the jacuzzi.

Tens of commits, five beautiful sunsets and many accidentally broken eggs later, here are a few of the most notable things that we accomplished during this retreat:

• Modern authentification for Office 365 accounts.
• Image resize in the composer.
• Multiple bug fixes.
• Feature fine-tuning.
• New FAQ content and landing pages.
• Missive Live Chat. Wait. What!? Yes, we will be releasing it soon, here's a quick preview:

By Friday evening, our families started to arrive, and our focus shifted to them. It was time to convert the work table back to a dining table.

Unlike the rest of the week, Saturday started as a sunny bright day; the cabin felt warmer and full of life with children playing and parents preparing breakfast. The day had a holiday feel to it, with people playing card games and kids sledding out in the snow.

By 6 pm, Christmas music started playing from the surround system in the living area, and everyone started chopping food in preparation for the Christmas dinner. We had raclette, some good wine, and a great conversation.

It's safe to say we all enjoyed the time working and the time off with our families. It's the first time we've done it this way and could very well be the last time.

We're at a point where we are small enough to do this, but this will undoubtedly change in a year from now — a good problem some might say. So yes, this was a special retreat.

From all the Missive team, we wish you a happy holiday season!

🎄

Companies nowadays have multiple points of contact (help@, info@, support@, Instagram DMs, Facebook messages, SMS…)

 Managing them can turn into a painful task, and unreplied requests give way to frustrated, bad-reviewing customers.

Let's talk about how people can deal with customer support.

Shared email accounts

It is the most simple yet most inefficient way to deal with customer support. The premise is quite simple, set up an email account, support@ for example, and share the password with your coworkers.

Everyone has access to all emails, which might seem like a good, easy option, but it entails problems.

• Sharing passwords is a terrible security practice.
• Emails can be answered twice by different people.
• There's no accountability.
• Impossible to scale.

Help desk

It is undoubtedly a step up from sharing email accounts; it turns emails into tickets, which can help you prioritize, and assign cases to the right people.

But just like sharing email accounts, it has downsides.

• They are complex to set up.
• They create a new silo of communications, meaning you will have both emails and tickets to monitor in some cases.
• It will be one more tool your team has to learn how to use.
• They use impersonal ticket numbers and auto-responses.

Help desks offen offer a myriad of add-ons that quickly add up to an expensive monthly burden.

Missive

It brings the best of both worlds.

Secure inbox sharing that allows you to monitor, assign, prioritize, and categorize support requests.

Missive doesn't add one more tool in your arsenal; it replaces one you already use: your email client. It doesn't create a new silo of isolated data. You can work on your personal/business emails, your shared inbox emails, and you will have all your team internal chat. It's magical.

Here are a few features that will help you manage customer support:

Team Inbox

It is a shared inbox made for collaboration and assignment between team members. It is useful for teams who want a "triage" step that will clean up messages for all coworkers at once.

Let's say you enable the Team Inbox flow for the account support@company.com and select the Support team. All team members (support employees) can now see incoming messages in the Support team inbox from the left sidebar. Observers (managers) don't get notified of new emails, but they can manage, monitor, and control the Team Inbox.

You can always add new accounts like info@ or hello@ with the click of a button.

With the Team Inbox flow, you can easily add new members as the organization grows. But what's interesting here is the fact that new support employees can access the old support requests; this helps accelerate the onboarding process of new employees.

They can consult past resolved cases to see how to handle new ones.

Rules

With Missive, you can create sets of rules that automize actions; these can save time and spare support employees from doing repetitive tasks.

For example, if you have a customer support employee that specializes in a topic, you can create a rule that whenever a message contains a specific word, it will always be assigned to that employee or team.

Or let's say you want to implement an SLA (Service Level Agreement) because it's always a good idea to set standards of excellent customer support; it also creates goals for employees to meet, so they stay productive.

A basic SLA implementation in Missive could be made with a rule. For example, to all emails containing the word "urgent" in the subject or message content and that are unreplied after 30 minutes, the system will show a message warning.

Workload balancing

Missive lets you automatically distribute your team's workload with four distinct balancing methods.

• Round-robin or in turn. The most used method to distribute incoming conversations across a team. It automatically assigns conversations to selected coworkers on a cyclical basis.
• Least busy first. The system looks for the teammate with the fewest assigned conversations and assigns the pending work.
• All at once. Any incoming conversation will be assigned to all selected teammates.
• Randomly.  It does not discriminate or take into account the workload of any teammate, it merely assigns a conversation randomly.

Canned responses

They will let you write and reply to emails faster with pre-written snippets. Responses are especially useful when you end up replying to the same questions over and over again.

By combining rules and canned responses, you can fully automate the reply of certain simple questions, bringing the response time down to seconds, leaving more time to your support employees to focus on more complex cases.

Internal Chat

This feature is essential for true team collaboration. It allows you to chat with coworkers inside emails. This is very helpful when an employee is unsure of how to answer a difficult question.

Instead of forwarding the email to a coworker or having to call a manager, they can just @mention someone and ask the question, all without leaving the email's screen. The other person will be able to access the email instantly to get the full context and guide the employee's reply through the chat.

Out of office

This status lets you set yourself or a coworker as unavailable for a determined period. Replies received in conversations assigned to you will automatically move the conversations to a Team Inbox so that other coworkers can handle these while you're away.

As a manager, you can also set this status for an employee calling in sick.

Social Media and SMS

With Missive, collaborative inboxes do not stop at email accounts; you can handle requests coming from:

• Facebook messages
• SMS with Twilio, Dialpad or SignalWire
• Instagram

Webchat

Missive Live Chat is the perfect way to interact with visitors and users from your website without creating additional silos of communication.

Whenever someone sends a message through the live chat on your website, it will instantly appear in your Missive app.

Integrations

The Missive API lets you enrich conversations with content from anywhere on the web. Customer profiles from Shopify, transactions from Stripe, Contact cards from FullContact, events from your servers! The possibilities are endless.

We currently offer and maintain the following integrations:

• Asana
• Pipedrive
• Todoist
• Trello
• Shopify
• FullContact Enrich
• PieSync
• Custom (learn more)

Stop sharing accounts and passwords; don't complicate your life with a help desk. Customer support is and will always be email first, and Missive is all about it.

According to this piece from Wired, a modern smartphone user receives around 73 notifications per day. It also states that people receive more than double the amount of pings they think they are getting.

But as much as we all try (or not) to limit the number of notifications that come through our phones and computers, we just can’t shut them all off. It’s an intrinsic part of modern work life.

What we can do is manage them better.

In this straight-to-the-point blog post, I’ll share three ways to take control of your notifications with Missive.

‍

Snooze with rules: Restore work/life balance.

Rules in Missive can help you automate many things, including getting some downtime.

Turning off notifications is an excellent way to reduce stress, rest better and be more present when in the company of loved ones or friends.

It may soon be a matter of legality like in France where employees can’t be emailed outside of business hours.

With Missive, you can create rules to snooze incoming emails to work on them later. You can get very creative and finely tune the rules to only let extremely important or personal messages go through.

Here’s a sample setup for snoozing all incoming emails arriving before and after business hours + weekends.

Unwatch: Call me when you’re done.

This is probably one of my favorites, it lets you see the level of granularity that Missive offers you to focus on your work.

Let’s suppose you’re in customer support and there’s a new email about an urgent feature request from an important customer.

Without the ability to unwatch you would have endured a steady stream of notifications for something that is not within your scope of work. This allowed you to keep responding to other customers without any noise in the background.

Read more about this feature.

Team Inbox: A manager’s dream.

This new feature is great for businesses receiving a lot of emails that have dedicated teams (e.g. sales, support, finance) tackling them.

Previously in Missive, incoming messages could be handled in two different ways:

• Unassigned flow. New messages appear in the Unassigned mailbox of everyone receiving the messages.
• Inbox flow. Everyone has their own unread and archived state. New messages will be added to everyone’s inbox.

With this third new flow, new messages appear in the Team Inbox. The team inbox is shared among its team members, meaning that whenever a message is assigned / archived / closed, it will be removed from the Team Inbox for everyone in that team.

So how does this reduce the amount of notifications?

When creating a team, you can define two types of users:

• Active members. They receive notifications for all new messages.
• Observers. They do not receive notifications. This is perfect for managers who want to monitor the team inbox instead of actively engaging with messages.

The examples above are rather broad and may not apply to your current workflow. But Missive is very flexible and a wide array of setups can be achieved with a little tweaking.

We went on a week-long work retreat in Italy.

Last month we decided to give ourselves a break from our co-working space and went on a week-long team retreat in the beautiful countryside of Charlevoix, Québec.

We set out to the Petite-Rivière-Saint-François village on a grey Sunday afternoon and arrived in a beautiful log cabin perched above the Saint Lawrence River. The view was stunning.

A change of pace

We knew from past retreat experiences that breaking the routine can be beneficial for productivity and new ideas. From way back into our client-work era, to building Conference Badge and Medali.st, we always got something big out of team retreats.

No specific goals were set for this one. We simply wanted to work more, with fewer distractions and more time to discuss. We firmly believe in work-life balance, but sometimes it’s just good to go all out for a few days. The key benefit was constant focus… with a view.

Working with a view 🌄 #missiveRetreat pic.twitter.com/iPUCwfnUpc

— Missive (@missiveapp) November 11, 2015

In between all the hard work we took the time for good food and relaxing spa sessions. Add a few refreshing runs rewarded with drinks and pool games and you get the dream retreat (let’s not forget Etienne’s classic late-night LoTR viewing).

Sharing the fun

Since the Airbnb “cottage” had enough space to house 12 people, we thought it’d be good to invite friends to come work with us for the week. It was a win-win situation: they got to spend a week in a nice spot and we got to have feedback on various aspects of Missive. Getting raw feedback from people you trust outside the bubble of your team is very important and surprisingly hard to get.

Late night dev is best dev 🤓#missiveRetreat pic.twitter.com/HRU1NsxxdV

— Missive (@missiveapp) November 11, 2015

All in all, going on a team retreat is like changing the tires on a racing car. You come back thirsty for new challenges with a refreshed view on your next steps and memories of good times spent together.

With Dropbox announcing they are sunsetting Mailbox, people are getting upset by the volatility hitting the email space.

The most upvoted comment on the HN thread crystallizes this frustration:

Ugh. Yet another intriguing email startup being acquired and killed off by a more-established tech company (see also: Sparrow). It’s 2015 and I still bounce around email clients every couple months because all of the major options have substantial flaws.schneidmaster

Email is rock solid. It didn’t change much over the past decade and stayed ubiquitous. However, the apps we use to consume it evolve at a frantic pace.

Is this a recent trend? Were email companies bought and sold in the past too?

We thought it might be interesting to visualize the history of all those email clients on a timeline: their start, acquisition, and discontinuation.

‍

It seems that each time a new platform is released, there is an influx of new email apps released to conquer the new market (web, iOS, Android). Then, big players start to acquire the winners to become the instant frontrunners in those new markets.

In 1998, Microsoft bought Hotmail and Yahoo bought RocketMail. More recently Google bought Sparrow, Microsoft acquired Accompli and Dropbox grabbed Mailbox.

The combined valuation of those last three acquisitions, $320 million, is probably another reason why so many apps are being developed since 2013.

What are your takeaways?

Notes

1. The timeline is undoubtedly incomplete; we probably have forgotten many apps, especially older ones. If so, go ahead and hit the comment section below to suggest missing ones, or open an issue on the Github repo.
2. We took inspiration from the team at sameroom.io and their Brief History of Chat Services.