What is your workaround for the free version's 90-...
# 2-ask-for-advice
a
What is your workaround for the free version's 90-day messaging/history cap -- when building communities in Slack (that will continue to grow) Main issue I worry about is searching. If someone is looking for answers on something specific within Slack, it will only pull from recent 90-days. Such a bummer.
👍 2
j
Hi @Allie Mullen - You mean for a community on Slack?
a
Yes!
j
Dots + Notion (private) Notion database (public)
a
@Joel Primack like copy/pasting or screenshotting key convos and adding there?
j
Ish, Allie - it’s a process 😅
a
Following this - I also have this question
j
Allie M and I were thinking about chatting as it’ll be easier to explain via that then text. Maybe I should record a video + links to tools mentioned to explain the process that I’ve previously used for this. Would that be helpful?
a
Only if its not a ton of work! were in the really early stages of evaluating what is going to work for some new cohorts, but any advice is appreciated 🙂
a
I know VC Platform built out their own product integrated into slack where you can search archives across slack and their platform but know that must have taken forever and $$$$
a
omg I bet.. they worked on that for so long. Did you talk to anyone there about the process yet? Id be curious
a
I didn’t. My guess is they’d keep their cards close on that but could be wrong
👍 1
@Joel Primack yeah if you're able to record a video and share, that would be helpful!
j
@Allie Mullen & @Allie Kerr - Here’s my audio note loosely explaining the process. And, here’s the link to Dots to learn more about it: https://www.dots.community/ If you have any Qs, feel free to reach out - always happy to explain it further.
a
@Joel Primack thank you SO much for this -- I really appreciate it. Cool to see they have a free option and going to explore this a bit. May circle back with some questions, but again, thank you!
🙌 1
j
I’m here anytime, @Allie Mullen 😊
a
ALSO, to follow up on this thread, our team is now considering biting the bullet and potentially doing the Paid/Pro plan because, you only get billed for active users. Here are the summarized notes from Slack's site + me talking to their customer service -- • When you purchase a paid plan for your workspace, you’ll be billed for active members. Inactive = hasn’t used Slack in >14 days. ◦ Any changes to the number of active members in your workspace will be reflected in your billing statement.If someone you’ve already paid for becomes inactive, we’ll add a prorated credit* to your account for the unused time. Those credits will be applied toward future payments, such as new members being added to your workspace or your next renewal date. ▪︎ *Note: Credits have no currency or exchange value, are non-transferable and non-refundable, and will expire following the termination of your paid Slack plan ◦ What Slack considers a user active: ▪︎ If an active member goes 14 days without sending or reading messages, they're marked as inactive. ▪︎ They'll be marked active again if they send 10 or more messages in a 7-day period, or if they read channels in any 3 days of a 7-day period.
🤔 2
a
Thank you Joel!! Allie this is super interesting... that changes the way I was thinking about pricing significantly.
🙌 1
a
@Allie Kerr RIGHT?
🙌 1
d
New here and reading through some of the recent “asks.” This move by Slack is precisely why we decided to integrate/migrate our developer workspace into our Discord. There was no budget to pay for an open/public workspace and Discord is essentially free. We also had lots of examples from 100,000+ member developer-centric servers that the idea could work. We cut over on September 1 and haven’t looked back. I deleted the abandoned Slack workspace about two months ago and haven’t looked back. We had a few noisemakers and ultimately we’ve been able to win them over too.