bachonk

I set up the self-hosting option, but doesn't look like you can OAuth into any of your accounts, and all balances/transactions have to be managed manually, is that right?

Thank you for sharing this, I added a few of them to a personal project[0] this morning! Will add a note to the about page to link to your repo

[0]letris.app

Yeah I agree with this. Dedicate 1 to 2 hours of focused work, fill it out, and move on.

This assumes that you're far enough along in the sales process that there's a high likelihood of close (you've already negotiated price and timeline), and the deal value should generally be five figures or above. This means it's worth your time.

Slightly risky hack: you can buy yourself some additional time by answering some questions with "Documentation will provided separately", and often times clients don't follow up to ask for it.

I tried Aman's videos but found Daniel Naroditsky to be far more helpful in terms of explaining advanced theory and tactics in a way that's easy to understand and practical at any ELO.

Here are some of his playlists: https://www.youtube.com/@DanielNaroditskyGM/playlists

It's a tough problem but the system is smart enough to group messages that come in through the top level. We use a time-based system where messages that come in within a certain period of time get grouped into the same ticket

Yeah totally true. And a lot of times, team members put a lot of time into answering questions but there's no way to track their effort that's equivalent to PRs in GitHub for example.

Would love to! I feel like a luddite who doesn't know Discord super well yet, but will definitely explore

Curious to hear – what would make Slack search work better for you?

Yeah that totally makes sense. I used to work at a big tech co where we had a Slack channel for internal users of our product, and it was hard to keep up.

Kind of an interesting idea to use different SLAs depending on the role of the user who posts. Or maybe exclude people who you know won't add anything to the conversation.

Abbot's pretty great, but uses a chatbot with customers. We stay behind the scenes and empower the reps to respond themselves. We also support email <> Slack which they do not

This is our #1 priority right now and are actively building it. We still have an Intercom widget on our dashboard just in case, and can't wait to replace it. If you sign up, I can let you know when this is closer to being live (and you can share some feedback on an early prototype)

That makes a ton of sense. We currently have a freemium with 1 free channel, but could be good to increase that limit so you can get it into your workflow early on

Solid batch of questions!

1. No they do not

2. We require quite a few permissions, but they're all deliberate and we only use what's absolutely necessary. We laid out some detail here: https://unthread-help.notion.site/Connecting-to-Slack-36a42b...

3. Because this derived from a previous enterprise SaaS app, our infosec policies are nicely buttoned up. Going through the fun of SOC2 now :)

4. It's coming! The first thing we're building is a relay so you can use Slack to talk to customers in Teams. Down the road, we'll consider building the same inbox functionality native to Teams, but we're waiting to see demand first.

5. Yes this works! You can even treat your team members as customers for internal ticketing systems (like IT or HR requests).

High ACV B2B is right on. The most common customer use-cases that we've been seeing:

– Devtool SaaS (engineers want to debug over Slack)

– High-touch SaaS (software with a strong services component, like tax software)

– Agencies (sales & marketing agencies use Slack as primary ticketings/comms platform)

Woot!

– Yes there is. This is available for any tier

– We currently have auto-responses for Slack messages. Auto-responses for emails is on the way!

Platform risk is always there, but we see this as a highly targeted use-case outside of their core competency.

The Salesforce acquisition spices things up a bit, but Slack's been great at supporting developers in the same way Apple did with the App Store

Our goal is to make it scalable! With the Slack Inbox and the auto-assignments, you could literally mute all of your customer channels and still stay on top of everything. Our largest customer right now has >700 Slack Connect channels

We have a Zapier integration that handles syncing with external systems. But yeah we want to keep the conversation in Slack rather than splintering it to some external ticketing platform

If you're hosting free events and need signups/newsletters/distribution lists in one place, interested to hear your feedback how how well everyspacehq.com would work. We're early and mostly enterprise-focused, but shoot me an email at tom@ if you're looking for a single tool to manage this.

This looks pretty great, will definitely take a deeper dive. I manage most of this today through a series of shared google docs attached to calendar invites, but this should be less clugey.

Regarding shared meeting notes, I think the killer feature that would make gdocs obsolete is auto-suggesting canceling a 1on1 or other meeting if there are no items to discuss. This removes the awkward "Hey do you still want to chat?" conversations and makes it a blameless way to get time back.

+1 for commonkey and their client-side encryption/decryption