Integrations

Sturdy announces Slack integration

By
Joel Passen
May 11, 2021
5 min read

Slack has become the de facto tool for internal communications for many teams. By shifting internal communications out of inboxes and into channels, teams can work more collaboratively while reacting to critical issues in real-time. This is why we are excited to announce that SturdyAI is now integrated with Slack. Now teams that rely on Slack to collaborate can create custom channels to receive important signals from SturdyAI.

For those less familiar with SturdyAI, we’ve built a product that analyzes business language(support tickets, emails, customer chat sessions, video and phone call transcriptions, etc.) for important signals that impact the bottom line. For example, when a user asks, “Can I have a copy of our contract?” in a support ticket, our product instantly recognizes this as a potential cancellation signal, flags it, and alerts the team in charge of triaging accounts. Today, our AI today recognizes 7 distinct signals, with dozens more currently in development. And the cherry on top is that SturdyAI gets smarter with every message.

Here’s how it works. 

Step 1 

First, a customer communicates with their vendor via email, support ticket, chat or recorded call. Below is an example of a ticket submitted through a ticketing system. 

Customer Support Ticket
Customer Support Ticket

Step 2

Next, SturdyAI ingests and analyzes the ticket in real-time looking for important signals. In this ticket, there is a critical issue. The customer, Brightlight, is asking for a copy of their contract. This is a clear signal that this customer may be at risk. Furthermore, the customer is indicating that they have purchased a product that may have similar features reinforcing the urgency of this message. Below is the original ticket that SturdyAI analyzed and applied the Strong Churn signal.

SturdyAI analyzes customer support tickets for signals that can indicate customer churn.


Step 3

Now that SturdyAI is integrated with Slack, critical signals are  “chirped” into Slack channels.  SturdyAI’s customers create their own Slack channels to receive critical signals. Integrating SturdyAI takes minutes. When SturdyAI is integrated with Slack, critical signals are  “chirped” into Slack channels.  SturdyAI’s customers create their own Slack channels to receive critical signals. We've seen some great use cases already. Here are a few of our favorites.

#competitor-mentions

#customer-references

#executive-change

#feature-request

In this example, we’ve created a “Churn Alerts” channel. These customized channels provide teams and leaders with real time visibility into critical customer issues so the right people can take action before it’s too late. Below is a screenshot of our churn-alerts channel and the alert that was triggered by the original message that this customer sent about requesting a copy of their contract.

SturdyAI chirps signals into custom Slack channels.

Why now?

Integrating with Slack was moved to the top of our feature roadmap as the pandemic has created new challenges for our customers related to remote operations. Less in person attendance by customer-facing teams means widening internal communication gaps at each stage of the customer lifecycle. Plus, integrating with Slack just isn't that hard. In the coming weeks, we will continue to refine the integration and, ultimately, the user experience making it easier for users of Slack to get mission-critical signals from customers in the apps that they use most.

Similar articles

View all
Customer Churn

The Four Horsemen of Customer Churn

Joel Passen
December 4, 2024
5 min read

Our data scientists have combed through mountains of unstructured customer usage data to crack the code on proactively identifying accounts that are a churn risk. After analyzing thousands of signal combinations, we found that four key indicators—Budget Issues, Unhappiness, Value Issues, and Urgency—are the ultimate predictors of revenue risk.

Nearly every B2B tech and services company sees the same pattern: when these signals align, it’s time for action.

Hold on, what is unstructured usage data? It’s the raw, untamed data that tells you what customers are *really* doing and saying—not just what they’re willing to admit in a survey or conveyed by numbers of daily average logins (also critical but lacking context). Here are the harbingers of risk; when combined, they are what the team needs to act on right now. 🧯

1️⃣ Budget Issue: This signals a customer struggling to justify the cost, possibly due to tighter budgets or a perceived lack of value.

2️⃣ Unhappy: Customer dissatisfaction can stem from unmet expectations, unresolved issues, or lack of engagement.

3️⃣ Value Issue: If a customer doesn’t see the ROI, they’ll start questioning the worth of your service.

4️⃣ Urgent: An urgent flag indicates an immediate problem that requires rapid action. They are expressing a need to engage with a teammate now.

Customer Retention

Improving Revenue Retention in 2025

Joel Passen
November 15, 2024
5 min read

If improving revenue retention is a key priority in FY25, here is some food for thought. If you believe data is the essential foundation for improving retention, imagine the possibilities with 50-100x more data about your customers. Here’s the thing: Every business has this customer data, but 99% of businesses are sleeping on a data set that could change their business. It’s the unstructured data that’s sitting in ticketing systems, CRMs, chat systems, surveys, and the biggest silo by volume - corporate email systems. Most of us still rely on structured data like usage, click rates, and engagement logs to gauge our customers' health. However, structured data provides only a partial view of customer behavior and revenue drivers. Unstructured data—like customer emails, chats, tickets, and calls —holds the most valuable insights that, when leveraged, will significantly improve revenue outcomes.

Why Unstructured Data is Essential for Revenue GrowthImproving Customer Retention: Unstructured data helps businesses identify early warning signs of dissatisfaction, allowing them to create proactive interventions before customers churn. Repeated mentions of poor experiences, response lags, product-related frustration, and more in call transcripts, cases, and emails indicate potential churn risks. By identifying these trends while they are trending, businesses will improve retention.

Fueling Product Innovation: Let’s face it: Our customers bought a product or service. Post-sales teams don’t develop products and are limited in what they can directly impact. Product teams need more unbiased, unfiltered contextual customer data, and they need it consistently. Unstructured data provides real-time feedback on how customers use products and services. Businesses can analyze customer feedback from multiple channels to identify recurring requests and pain points. This data fuels product innovation and informs customer-led roadmaps that lead to higher engagement rates and more profound value. Developing products that directly respond to customer feedback leads to faster adoption, better advocacy, and a competitive advantage.

Identifying Expansion Opportunities: Unstructured data reveals customer needs and preferences that structured data often overlooks. Businesses can uncover untapped expansion opportunities by analyzing email, chats, and case feedback. These insights help identify additional products or services that interest customers, leading to new upsell or cross-sell possibilities. To drive immediate improvements in revenue retention, the key isn't pouring resources into complex churn algorithms, chatbots, or traditional customer success platforms—it's being more creative with the data you're already collecting. Start listening more closely to your customers, identify the patterns in their pain points, and share this knowledge with your peers who can improve your offerings. This is the year to start thinking outside of the box.

Customer Retention

Burton's Broken Zippers

Steve Hazelton
November 15, 2024
5 min read

Last year, I bought a pair of ski pants and the zipper fell out on the first chair lift. I called Burton, and they offered an exchange. New pants, first chair, same problem. Support informed me that I was required to return the pants for repair. The repairs would be completed after ski season. For the inconvenience, Burton offered me a 20% discount on my next purchase of skiwear. The next time I am in the market for skiwear that I can't wear during ski season, I will use that coupon.

I started my first business over 25 years ago. Since that day, I have lived in an almost constant state of fear that somehow, somewhere, things would get so broken that we'd treat a customer like this.

Let's be clear, no one who runs a business wants stuff like this to happen. Yet, it happens all the time.

If you run a software company, your engineering team will have usage tools and server logs to tell you when your product is "down" or running slowly. They can report which features are being used and which ones aren't. You'll learn that certain features in your product cost more to run than others, maybe because of a bad query, code, or something else. And you'll know what needs to be upgraded.

However, every time a customer contacts a business, they are "using" (or "testing") your product. If you sell ski pants, your product is ski pants, and your customer service team. If you sell software, your product is your tech and your customer service.

Yet, your customer-facing teams have very poor usage data, if any at all. Which feature of our service gets used the most (billing, success, support)? What are the common themes? Is one group working more effectively than the others? Does a team need an upgrade? 

(BTW, what costs more, your AWS bill or your payroll?)

The reason your customer-facing teams don't have usage data is because this data is "unstructured," and it is everywhere. Imagine if your engineering team needed to check 50 email inboxes, 1,000 phone recordings, a CRM, and a ticket system to get your product usage statistics. 

That's where your customer-facing teams are today. Until you can get answers from these systems as easily as an engineer can, you’ll continue to churn, annoy customers, and try to hire your way out of a retention problem. It won’t work.

How many customers will you have to lose before you try Sturdy?

Schedule Demo
A blue and gray logo with a black background
A number of different types of labels on a white backgroundA white background with a red line and a white background with a red line andA sign that says executive change and contact request
A white background with a red line and a blue lineA number of different types of logos on a white backgroundA pie chart with the percentage of customer confusion and unhappy
A number of graphs on a white background