What happens if you create a Member Journey, it goes live / starts for a handful of new members, then you change it? Letβs say you set up 4 steps β 20 people start it β you remove 1 step & add a new step Will they be retroactively notified if they already completed the new step? When they look at the journey again, if they completed a certain step but then we remove it from the journey, I assume their list of steps (the green progress bar) will drop back down
Hey Shriya N. I know this topic can be a little complicated - please check out docs.tightknit.ai/gamification/journeys#β¦ and see if that answers your question. If any part is unclear please let us know! We want to make this one easy to understand!
Ah yes Stephen C. should have gone to docs first, apologies! π€¦ββοΈ
Ok I reviewed the docs thoroughly and set up our first journey! I started getting the updates about my own progress through the journey (Which I didn't expect, since I've done everything on the list!) and I realized that it's not detecting that I added a profile picture months ago, or that I already posted in the Intros channel. After I got these notifications, I updated the start time of the Journey from August 2026 to August 2023. Can Tightknit detect past behaviors like this? You've had access to the Intros channel from the very beginning, and we don't want to make long-time members re-introduce themselves just to complete this journey.
Good question, today we do not do retroactive checks when you create/edit your journey or milestones. We do retroactive checks the next time there is relevant activity performed by the user. For example, after you add the Intros channel post milestone, nothing will happen immediately. The next time you send a message, Tightknit will check if your message history fulfills any open milestone (within the journey window, if configured). It would see that you have posted in the intros channel and then award you the milestone.
Ah! Ok what about profile picture?
Just checked and I have sent a public message since then, but it didn't behave in the expected way you're describing (Intro is still unchecked)
Ah, so when I said "relevant activity" that means an activity that could typically complete the milestone. E.g. sending a message => could complete message-related milestones, updating your photo => completing the photo-related milestones. I understand the photo one is tough though because that activity is very narrow in scope. Maybe we can explore ways to make that one simpler for retroactive checks. Did you have any ideas on how you'd want that to work?
Do you get something from Slack that's a binary "Default profile image" / "Non-default profile image"? Is there any persistent "state" that you can look at? I would like it to just know if the profile picture is there, but idk what's possible.
And for "relevant activity", does that mean a top-level post in a different channel would cause Tightknit to check if they shared any top-level posts in "introductions"? Or that they have to post something else in "introductions"?
re:relevant activity I added a new column here to better explain it: docs.tightknit.ai/gamification/journeys#β¦
Yes, we can look up the users profile photo and determine if it is custom or not. However the lookup is individual per-user, so doing this pass over all members of the community would be a very large operation. We would also need to be respectful of Slack API limits. We may be able to do a "Check now" type of operation for the admin to kick off a job to do it. We'd have to plan some how we implement it on our side ;)
ahh
So for the intro post, since it's a top-level post, they'll have to share a top-level post in any other channel.
For the profile photo, that makes sense. So we would have to actively work with you to do kick off a review across all users' profile photos π«£ What would this look like? How hard would it be or how long would it take?
No, we'd definitely make it self-service! But we just need to be careful to rate limit, make sure only one job is happening at a given time, etc. Let me create a ticket to explore this one!

