oceanprotocol-archive / oceandao

🐡 OceanDAO wiki
28 stars 9 forks source link

Establish a system to manage all community inbound requests timely and efficiently #622

Closed andreaarmanni closed 2 years ago

andreaarmanni commented 2 years ago

As Ocean grows so will be its community and the inbound requests we’ll be receiving.

We’ve been having challenges with managing all of them, particularly:

With the above in mind, I wanted to create a better process for managing all inbound requests to allow every team to be notified in real time when a request comes in and take the lead.

This is the new proposed process:

  1. The Community Managers will funnel all non-technical enquires from Discord and Telegram via this form. All technical enquiries will still be processed via Discord.

  2. All answers will automatically be collected in this spreadsheet

  3. A new bot will filter requests by team/type. Currently we have 3 teams in the GForm: OceanDAO, Marketing & Communication, Partnerships & Integrations. If any of you would like to edit the content of the form, please propose suggestions here

  4. The bot will fetch data from GForm, connect to the Ocean Protocol Slack via Zapier and send a notification within each team's Slack channel. This is a test example

With this new process we should be able to have each team processing their own inbound requests, as well as achieve better leads, resources and time management for everyone.

CC: @idiom-bytes @AnaLoznianu @sheriff4 @MonicaBotez @brucepon @trentmc