So you've decided that messaging is the future and is looking for a solution for your organization. Now you're wondering how Briteback compares to Slack. Let's get down to business and check out the pros and cons.
Where Briteback is better
Briteback is built for large and growing organizations. Of course there are teams and channels, but unlike Slack, all teams belong to an organization. Together with role-based administration this makes it work even for really large organizations. And the organization structure in Briteback is not something you need to add as after thought once you have grown out of the singe-team concept. It's there from the start, even on the free version of Briteback. This way, Briteback grows seamlessly with your organization.
Here's a film that illustrates how large organizations can be setup in Briteback.
Slack is betting on email dying, and wants to replace all use of email with messaging. To understand this position it may be good to know that Slack is a tool mainly catering to software developers (at least that's where Slack comes from). A software developer can replace email with messaging in a heartbeat because he or she really only interacts with other people in the development team. Ask a seller, a manager, or a business developer to drop email and they will think you just arrived from the cuckoo planet. When you frequently interact with people outside your organization, email is still, and will remain, the de facto standard for external communication.
This is why Briteback provides a great email Power Up, where you can connect any number of email accounts. It's perfectly fine to switch to messaging for internal communication, and have your external communication in Briteback as well. Got an important email that needs to be discussed internally? Just Share it to a messaging channel and have the discussion there. Anyone in the channel can pick up the shared email and reply to it, without the nasty message build-up that results from endless forward/reply-all-chains. Of course, Briteback supports email accounts on MS Exchange, Office 365 and Gmail/Google Apps.
Check out this video that illustrates how simple it is to Share an email in Briteback.
Communication and calendars belong together. This is why Briteback provides a built-in top-of-the-line calendar as a Power Up. Want to book a meeting with your team? It's literally just one click to add all members of your team to the meeting. We support calendars from MS Exchange, Office 365, and Gmail/Google Apps.
Want to book a meeting with your team in Slack? You'll have to open another app, and then manually add all team members to the meeting, one after the other. And after that? Your team members must leave Slack and manually open their email app and respond to the invitation there.
Here's a video illustrating the Briteback calendar.
Briteback is built for flexibility in terms of media. Messaging is great for some things so we put it in. Email is great for external communication, so we put it in.
Similarly, online calls with voice/video and screen sharing is great for show and tell, and where the written word is simply not rich or quick enough, so we put it in. It's just one click to start an online call with all members of a messaging channel.
The full range of online call functionality is available even on the free version of Briteback. Also, a call can be minimized or placed in the background allowing you to work on other things in Briteback at the same time. And of course, it's possible to invite people outside your organization to an online call. Just enter an email address, and an invite email is sent. The invitee can join the call without having to register for Briteback, it simply works in the browser.
And screen sharing? You can even have several people sharing their screens at the same time.
Slack also has built-in support for online calls. At the moment though, it's limited to voice only. No video. No screen sharing. And the free version of Slack only supports one-on-one calls.
Briteback provides a powerful and flexible integration interface. Better still, it works in the same way, no matter what integration you want to interact with. It's just clicking and selecting from a sequence of options, combined with text input where needed. You can share tasks etc directly into a messaging channel from integrated system, and also subscribe to streams of messages to get notified when something changes in the integrated system.
As an example, this is what Briteback's Trello integration looks like:
In comparison, Slack relies on a command-line interface, where you manually have to type each part of the integration command sequence in one go (and if you type something wrong, you have to retry from scratch; remember the infamous Syntax error message).
And why not compare Briteback's Giphy integration with Slack's? With Briteback you get live previews to choose from. And when posting an animated GIF on Briteback, it really is animated, even on mobiles...
Customization and Self Hosting
Do you have a special use case and is looking for a solution that can be adapted to fit your needs? Briteback is very modular and custom-built to be set up in different ways. As an example, we recently completed a custom module for data collection (online surveys) for a customer that has been used in large research studies, e.g. in association with the Rio Paralympics.
We also provide self hosting as an option for customers with extra sensitive data. Just contact us.
Admittedly, Briteback currently has a smaller install base than Slack. We're a smaller company and a second mover in the field of messaging. This has made us humble and it's why partners are important to us. We welcome win-win partnerships and are there for you. We are reachable, we listen, and we can adapt. It's part of our strategy.
So, looking to partner with us? Just contact us, and we promise to get back to you, quickly.
Where Slack is better
Let's face it, Slack is good and we like them. We even used an early version of Slack before we decided to build something that suited large and growing organizations better. In all fairness, we believe you would do the right thing to go for Slack if any of the following issues were of great importance to your organization.
Slack supports many platforms. While Briteback currently is focused on the most common platforms (Web, Android and iOS), Slack also supports Apple Watch and Windows Phone. If those platforms are crucial for you, then we recommend Slack.
When it comes to integrations, Slack has lots of them, many more than Briteback. Looking for notifications from events on minor developer tools? Slack may very well have an integration for it. Looking for messaging bots that automatically post cute cat pictures in your messaging channels on a daily basis? Slack's got you covered.
Slack has a good API for developers that want to create their own integrations. There is also a Briteback API on the way, but not yet released. So, if an open API is crucial, you should go with Slack. On the other hand, Briteback works closely with customers to provide customized solutions, way beyond what can be done with the Slack API.
So, what's the verdict? Should I go for Briteback or Slack? Well, dear reader, it depends. If you want a solution for a single team, not likely to grow, and with a faiblesse for developer tools and APIs, I would recommend you to go with Slack.
On the other hand, if you want something you can grow with, and get in on a good structure from the start when you try out the free version, I would recommend Briteback. And with Briteback, you can also get customizations and self hosting, as well as partnership possibilities.
comments powered by Disqus