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?
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.
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.
My number one pain in the butt with Slack search is the fact that "advanced" operators or "advanced search" suck.
And I am not talking about the ui: there are multiple interfaces to filter/refine your search instead of being in a single localized page; additionally it would be better to be able to modify your search and view the results side by side, so that you immediately figure out if your new search params are better than the previous ones without having to go through a couple of clicks..
I am so surprised that no one has came up with better search in Slack in so many years, I could literally come up with a better search spec in less than a month - given search is something that is used AT LEAST once a day by people in our org
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
Abbot CEO here! Appreciate the kind words, we hope you enjoyed your trial before starting Unthread :)
It's true that we use a bot user in channels - we do this to help synchronize conversations that happen in Slack with other systems. We figure that conversations happen in Slack but often get shared elsewhere. Abbot only responds if customers set it up to do that.
