Our main use case for Slack Business - Enterprise is internal communication within the team, especially test communications, which primarily happens through Slack channels.

We typically use Slack channels for test communications for any kind of internal discussions. When issues arise, we start a Slack thread and continue the conversation on that particular thread. We have been mainly using Slack threads for putting all conversation related to one topic in a single place.

Slack Business - Enterprise is definitely a communication channel across multiple teams that we have. However, what we are heavily using is the integrations. Since we are a tech company, there are many operations going on at the backend. If something breaks, production issues happen, or tickets are raised by the client, we have set up a bunch of notifications and automations on Slack Business - Enterprise, and that is the primary use case that our organization is sticking with Slack Business - Enterprise. We haven't switched to any other communication tool because copying all those automations and interactivity that we have built does not make sense to migrate to any other tools.

Our organization uses multiple vendors across AWS as a cloud provider and Slack Business - Enterprise as the communication channel, among multiple others. We are using the premium version, which is a paid version. AWS provides a multiple suite of their services starting from database service, storage service, compute, and many other services.

I am still with HubSpot and work on the basic HubSpot platform, not Marketing Hub or Service Hub.

I have recently moved jobs, so apart from HubSpot and Pipedrive, the tech stack is pretty basic. We use Slack Business - Enterprise and Granola, which is interesting.

We use Slack Business - Enterprise for internal company communication.

The call functionality when making direct calls to peers could be improved. Notifications need to be set up properly initially, but once configured, they work effectively.

My experience with Slack is that for the past two years in my present company, we use it as a communication channel for each and every team discussion, manager discussion, or any alerts through various channels.

We primarily use the application on our system, connecting it with our official email address, and we have been doing this for almost a year. However, they plan to change to improve cost efficiency.

We use Slack for collaboration between engineering teams, cloud teams, and technical support. One particular use case is releasing updates to our software. This process involves a risk management process, code review by different stakeholders, and testing by QAs. It is a multi-disciplinary task, and Slack helps to manage these releases via channels.

I am an end user of Webflow, building and designing our website while integrating third-party tools with Webflow, which I have been using for the last four years.

I have been using Slack for over four years, specifically for communication with my colleagues and clients.

I am working only with Web Application Scanning.

We use Slack Business - Enterprise to communicate. We have a few use cases. We don't use it for the whole company. The R&D team uses it just for themselves. In addition, we use Slack Business - Enterprise to communicate when we do deployments. We have a small group of people who are involved with the deployment of our website, so we send out information on that in the Slack Business - Enterprise channel.

We also have a channel with our external DevOps team and we find it provides very good communication to be able to have the relevant people at PeerSpot and the relevant people at our outsourced DevOps team all in a single Slack Business - Enterprise channel. In case any urgent issues come up, we can talk to them and chat with them in real time.

They use the deployments through Slack Business - Enterprise. Every deployment goes through Slack Business - Enterprise. It's really our source of record for all of our deployments. Everything out there is accessible, and in that way, everyone gets to see it. It's something that is important for all the people that need to know what's being deployed and when. If there's a problem with deployment, they're able to flag it in the Slack Business - Enterprise channel, and then we may need to roll back the deployment or fix it immediately.

I worked with ThreatMetrix before, but I do not currently use it. A year ago, I transitioned to a different field and do not work with technical tools anymore; I do only analysis now, primarily using Excel and collaboration tools like Slack Business - Enterprise.

The major purposes for using Slack Business - Enterprise are company communication and intra-team communication.

In terms of client relationships, we did use Slack Business - Enterprise occasionally; we talk with other companies, so we utilized it for external communications.

We use the tool for project collaboration within our team. It helps us manage our daily activities. We've also integrated Slack with other tools to schedule our meetings. I'm unsure if we're currently using a professional or standard license, as there may be some limitations. Overall, we're utilizing it mainly for collaboration purposes.

I categorize Slack as a modern workstream collaboration and automation tool. The simple use cases are peer-to-peer or group chats and collaborating in channels. I might create a channel based on certain needs, like a project or a particular subject, but it's not just chat, there are also features like the sharing of information and knowledge. I also use Slack for document collaboration.

Then you get into more advanced features for tools with things like automation, such as being able to integrate with ServiceNow. This ITSM platform opens up tickets and automatically creates a channel where service teams can easily communicate about that event or that outage if it's a high-priority ticket.

We use the solution to collaborate with other teams. As a product manager, I need to engage with the engineering team, marketing department, and account executives.

The solution suits collaboration, where multiple people work on the same issue. We use it for integration with Google Drive and Zoom. It syncs up with the official Google account. So, I get notified through Slack whenever I have a meeting or if somebody shares a particular document on Google Drive. It also tells if somebody leaves a comment on a document on Google Drive. I also use it to connect with my internal IT team.

We use the solution for internal communication within the company. We also use Slack for one-to-one messages and audio and video meetings.

Slack is primarily used for communication, file sharing, and sometimes for Huddle, which is similar to a Zoom call within Slack. You can start a call with the person directly. 

Our clients use Slack because it is highly customizable, allowing us to create applications and plugins to easily connect with various applications and receive updates.

I used it for managing competition-related matters, as well as for handling announcements regarding new products or services. It was also a go-to platform for tracking logs related to ticketing and service issues that required urgent attention, as well as for internal tasks like software deployment and operationalizing services promptly.

We primarily use it for internal communication and coordination. Mostly, we were using it to share information and then, you know, use it more as a repository for exchange and communication among users. 

So we were using it more like an alternative to email, at least for all internal conversations and coordination. That's one. And mostly to share info and share docs, etcetera.

We use the solution to manage communication within our organization.

I work alongside other departments, and we use Slack mainly as a source of communication.

I use the solution to communicate with the developer community. If I have any issues, I reach out to them for troubleshooting. I also use the product to know about upcoming tool upgrades. We use the solution as a community to reach out.

My organization uses it for collaboration and updates. We use it for meetings. Slack can be integrated with Confluence, Google Meet, and Zoom. We use it for important events. We constantly check Slack for updates from our bosses, CTO, and CEO.

I use the product to chat and huddle with company members.

The tool helped us with collaboration. Another use case for us was ticketing, where people who needed to take action could be informed immediately on Slack rather than over the conventional mechanism of emails. You need to look over hundreds of emails and then realize that there is a ticket. You can also collaborate to get document reviews done and avail feedback immediately rather than exchanging and putting it in our systems. 

My main use case for Slack Business - Enterprise is connecting between different teams and facilitating communication for teams.

A quick, specific example of how my teams use Slack Business - Enterprise for communication is to see how different things are proceeding and growing.

My teams rely on it day-to-day for their communications.

We use it with our clients for sharing files and for communication.

I use the solution mainly for chat. I go on spontaneous calls with colleagues. We also have channels for specific topics or customers and share workspaces with partners. Some of our partners also use Slack. So, we use shared workspaces and channels, which is a very good way to stay in contact with them.

We primarily use it for sharing official documents and compositions instead of using platforms like WhatsApp. Although we haven't utilized it for meetings, the main purpose behind creating and using it is to streamline the sharing of official information within our team.

I use the solution for communicating with all the teams. We can communicate with people from other countries.

We use the product in the office for communication. It's our main channel for any communication.

I use the tool to communicate with my team because we work remotely since COVID. 

We're using Slack to communicate with other partners outside of our company. In most of the cases, it's for external communication.

We use it for internal communication, and we also use it for external communication or customer relations.

We use Slack for general communication, conference calls, and sharing screens because we have people working from different countries.

There are 53 people using Slack in our organization.

The solution is deployed on-premises.

We use Slack for communication and announcements.

The solution is deployed on-premises. We have around 65 people using this solution in our company.

We are using Slack for web conferencing. It is primarily for external communication with one of our suppliers.

I use Slack for team collaboration.

We use the solution for basic communication such as chatting. 

We use Slack for communication, file sharing, meetings, text messages, etc. Slack has been so helpful for us.

We use the tool to communicate with the design team, and exchange links, and code needs. I use it for collaborating with outside spaces. 

We use the solution for communication within our internal teams and with external organizations.

We use Slack for Team communication and also for channel alignment functionality. We also use the solution for monitoring. Meaning that we integrate it with other workloads that we have in the cloud, so that we can monitor. 

Slack is our main source of collaboration and we use it for all internal messages.

Our internal team primarily used Slack for communication with each other. If two or three people were working on the same modules then they were able to share code and work together.

I use Slack primarily for communications. This includes communicating with individuals as well as grouping people into cells to work on specific parts of a project. We don't use the features beyond just the basic communicative side of it.

We used Slack for all of our internal communications during the COVID pandemic.

We are using Slack to collaborate between employees, as many of them are working from home. While I personally started using it a couple of years ago, it has been about a month since all of our employees began using it.

We use Slack for having meetings with one of our vendors.

I use Slack to communicate mainly for content related tasks with clients as they find it easy and quick to keep track of all of the on-going projects. Most importantly, it helped me to communicate with other content writers whenever I have to work in a team for a particular content project.

It's our organization's chatroom where workflows and information are passed. We use Slack for communication within teams.

I mainly use Slack as a collaborative chat, video and audio tool. I am able to set up a Slack room for different purposes and have all major stakeholders collaborate in real time. I enjoy the functionality on Slack that enables my team members to edit and collaborate on documents simultaneously.

We are using Slack for all office internal communications — to create polls, reminders, notifications for builds, etc.

I use it every time. For professional and personal use. Their integration is a game changer, and the UX is really great.

The idea of using Slack was to keep non-business related talks from business talks. In Slack, you have different channels where you can set topics, therefore people will not divagate on a specific subject.

We used the solution to communicate within the team and with other people outside the company. We only used the solution for chatting.

I use it if I want to search for information from Kubernetes communities, and then I chat with someone who already has knowledge or knows about Kubernetes. I use it to talk to people using other software like Kubernetes.

We mainly use Slack as a communication channel. Additionally, we use it for remote working and voice meetings through Slack Connect.

I use Slack for communication with my colleagues. 

We use Slack for internal communication between cross-functional teams.