sanketc

It's to understand more about your members. You can use that to drive what sort of events you want to run, and what times, as an example.

Some customers prefer asking in a community because that can lead to responses from other customers (at times it can even be faster response than a company rep getting to respond). A good example is dev infra related companies, where a customer can get a lot of value by hearing from how other customers think about a specific problem. You don't get that through a typical customer support software which is one to one.

It comes down to preference. The trend is that companies have to meet where customers are already hanging. Some customers will prefer only email (and for them you still need a ticketing software), some will prefer social (depending on industry), and some will prefer chat/forum communities. If you want to stand out as a company (esp when you are starting out), you have to serve them where ever they prefer. Sure, if you have an amazing product with a strong moat, you have more leverage on how you want customers to interact with you. But that comes much later in a company lifecycle.

Absolutely! It’s helpful for us to keep the long tail of usecases in mind tho as we prioritize, so we can capture aspects of those. We’ll ofcourse never be able to replace a full custom bot. However, bots coded for specific uses come with its own set of challenges (eg. managing a backend server, logging, relying on someone else to update basic things etc.) which we hope to mitigate.

Wow, thanks for the detailed use cases here!

- Discord as a notifications service - we do support aspect of it where folks can click a button to get a specific role (e.g. I want notification for xyz). We have a recurring trigger that can check an endpoint, and post an update from that endpoint. We don't yet support conditions on that (e.g. only notify if price hits x)

- Wiki - pvme.github.io looks pretty cool. I have seen couple other products that help convert community content into indexable pages. I like the idea of like a web interface where folks can edit, but the content also some how gets updated in discord (e.g. forums in discord could be a good use case for this?)

- Intra guild look tracking - this is definitely a little bit more complex than what we plan to support given it involves storing specific data for access at a later date. Is this pretty common for a lot of gaming communities?

- Crappy rest client - yes we can support this! Definitely get in touch if you find yourself wanting to do something like this in the future.

Ahh agreed, need to set up the mic correctly! Appreciate the feedback.

What usecases resonated with you the most?

Appreciate the candid feedback! We started with use cases that are relevant for most communities, and plan to build out the functionality to make it more comprehensive. We recently added ability to query external APIs, and triggers through webhooks (you can check out NBA's discord which has live game threads powered by our bot builder). But agreed with you that there is more work for us to do here.

What sort of organizational things have you built bots for? Curious to hear about, so we can build towards that :)

Looking forward to your feedback. If are open to sharing what sort of bots have you thought about building for your community, I can see if we can support those specific use cases.

We have been happy customers of Arctype for a few months. What started as a nice to have tool has now turned into a must have for our team in terms of sharing queries, and browsing data.

Love this! If you can pull in info from Slack/Discord convos that would be a big unlock. Do you plan to make this available to private repos shortly? Would love to try it out on an internal one, as we always find ourselves repeating information when onboarding new team members.