# Contact us!

### We are always here to help

###### We love feedback of any kind as this is a new project. We always appreciate code contributions and collaborations as our mission is to make it easy and useful for you.

![Contact Us](assets/images/contact-us.svg)

[Back to main page](../readme.md)

### ![Logo Slack](assets/images/logo-slack.svg) Slack

The fastest way to reach out to the Vivid team or get updated on the latest _on-goings_ is via the Slack channels.
We are interacting through, monitoring and frequently updating the following channels:
* [ask-vivid](https://vonage.slack.com/archives/C013F0YKH99) - public channel for any open conversation (well, Vivid related too :) )
* [vivid-engineering](https://vonage.slack.com/archives/GVC6M0QF2) - join-by-invitation channel for a more thorough technical discussions, please ask some of us to join you if needed

---

### ![Logo GitHub](assets/images/logo-github.svg) GitHub

Vivid uses Jira and GitHub Issues as the official bug trackers. While Jira is more for our own internal stuff management, GitHub Issues is probably the fastest channel to notify us on any issue. 

Please check the [existing issues](https://github.com/Vonage/vivid/issues) first.
It's possible someone has already reported the same problem.

If your problem or idea is not addressed yet, [open a new one](https://github.com/Vonage/vivid/issues/new).

---

### ![Logo Workplace](assets/images/logo-workplace.svg) Workplace

Join our [Workplace group](https://vonage.workplace.com/groups/532641777422792) to stay on top of new releases.

---

### Suggestions

Go through the [board](https://github.com/Vonage/vivid/projects/1) to search for existing feedback and share yours if not already addressed.