You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quick chat today with @timgl, and we were thinking that a cool way to incentivize meetups is creating a Slackbot that works like the Donut bot and creates a conversation between the matched teammates to start the conversation. We could even suggest some cool places for the most common cities.
If we do build the Slackbot, we could use it to detect location changes and suggest adding trips too. Thoughts?
Spent some time thinking about this today. Some ideas.
MVP Scope
Connecting Slack to your WITW account.
When a Match is created, we open a conversation between the two matched users and the bot (same as the Donut bot, so we don't pollute the user's DMs).
We probably want to add a delay of maybe ~1 hour in case there are immediate changes to the trip (we would need to add a worker to the app if so).
The conversation includes details on who's traveling, matched city and overlap dates.
Users can click on button to open the match in WITW (we need a match page for this). From there, users can mark that they're meeting or dismiss the suggestion.
We store the conversation ID in the Match record. If the Match is deleted (e.g. the underlying trip is removed), we send another message saying the trip has been cancelled.
If you're matched to multiple users for the same trip, we create a single conversation with all matched users.
Quick chat today with @timgl, and we were thinking that a cool way to incentivize meetups is creating a Slackbot that works like the Donut bot and creates a conversation between the matched teammates to start the conversation. We could even suggest some cool places for the most common cities.
If we do build the Slackbot, we could use it to detect location changes and suggest adding trips too. Thoughts?
@timgl maybe you're interested in building this ?
The text was updated successfully, but these errors were encountered: