Feasibility: Automated Onboarding Slack Messages

### Overview

As a developer, we occasionally need to do feasibility testing to discover new technology that may improve our team. For this issue we will explore the viability of sending automated slack messages through a bot.

### Action Items

- [ ] Discover whether a bot on slack can perform these things:
- [x] Add a custom bot created by HackForLA. (already done by VRMS team).
- [ ] Send out automatic messages via an API.
- [ ] Send out automatic messages to individual members.
- [ ] Check out the slack bots we currently have. Can a custom-made bot integrate all the tasks that the current slack bots do.
- [ ] As part of testing for feasibility, make sure to create a spreadsheet of every bot we currently use and list out: name, task it is doing, and whether we can re-engineer the tasks this bot does. This spreadsheet should be in our google drive, inside an appropriate directory, and under an appropriate name. Be sure to put a visible note (maybe on the top cells) to delete the file if it has gone stale (so future developers can clean up this file).
- [ ] Once testing is done, invite the VRMS to join us during a meeting to discuss a possible collaboration to start porting our existing bots into the VRMS bot.

### Resources/Instructions

The intent of this issue is to find a way to streamline the onboarding process. The onboarding experience tends to be a lot of information at once, which can make it difficult to know exactly how to start. Our organization as well, has installed a lot of processes which needs to be disseminated in a standardized way. This issue is intended to consolidate information into one place when orienting new members to the team (of this project and other projects).

You might be wondering, why would we want to integrate all of our bots into one? The reason is that we have reached our slack bot limit, but we want to add more! There is a need to combine one, two, even three into one. The goal of this issue is to see if we can combine everything into, ideally, one bot (or, if impossible, as few as possible).

For now, the VRMS team has a bot implemented already. This is the bot we plan to leverage at the end of this research.

- [Create a bot for your workspace](https://slack.com/help/articles/115005265703-Create-a-bot-for-your-workspace)
- [Enabling interactions with bots](https://api.slack.com/bot-users)
- [slack api](https://api.slack.com/)
- [VRMS repo](https://github.com/hackforla/VRMS)
- [VRMS project page](https://www.hackforla.org/projects/vrms)

Also, feel free to contact them at the #vrms sack

### Resources and Instructions
- [List of existing Slack app and its functionality](https://docs.google.com/spreadsheets/d/1VsXISNeregvOrMPK1yV-39OR3Fyi1fsU1IajTlqYyCo/edit#gid=0)