Discord Introduction Bot Questions/Actionable Items

When someone enters a new online community, a typical practice is to have an Introductions Bot. I would like to know what our community wants to ask and offer new SourceCred community members. My take on Introduction Bots is that they should:

  1. Welcome the newcomer
    Letting newcomers know we want them there is a way to encourage community-building and future contributions. A humorous tone can help build rapport just by showing we’re a personable and kind community.

  2. Provide information
    We want a bot that is useful, not spam. "Visit the Start Here channel to learn how to a) meet community members b) have questions answered c) make contributions and d) earn Cred’"offers key information and is short n sweet (aka is not a block of text that they will disregard because it’s a bot). We can also offer info on how to check one’s Cred when the Cred bot has been made.

  3. Provide actionable steps
    The main difference between actionable steps and information, to me at least, is that we suggest or ask the newcomers to do something, rather than just tell them it’s an opportunity that exists. This is where we can ask them to complete the steps in the Start Here channel, tag themselves on Discord, fill out the Contributor Profile Google Forum or look at the Initiatives Spreadsheet to see where they’d like to get started and who to contact.

The specific questions I’m trying to answer are:

  1. What information is relatively short and easy for newcomers to provide and is useful for us to know?
  2. What next steps would we want newcomers to take after joining Discord? (many are already listed in the Start Here Channel, so maybe the Intro Bot can highlight resources listed there to gain the newcomer’s attention).

All that being said, here’s my proposal first draft at an Intro Bot message. Let me know your thoughts and I’ll try to get this up and running (with some technical help) asap!

Bex’s Introduction Bot message draft:
Welcome to the SourceCred Discord! I know bots aren’t advanced enough to have feelings (yet), but I’m still really glad you’re here. I’d love to give you some next steps to connect you with the community and to get you earning Cred!

  1. The Start Here channel is your home base. You’ll find our starter resources, how to introduce yourself to the community (we don’t bite) and how to get started on working with us if you’re looking to! Complete what’s listed there, and you’ll be in tip-top shape.
  2. We’d love to know more about who you are and what your skills are. Type ‘something technical’ here to have my friend, the Tags Bot, give you tags for whichever skills you have. Don’t know how exactly to tag yourself? Check out our Discord Tags Document!
  3. Give yourself a pat on the back, you done good.
1 Like

What’s nice about a bot is when you have quick interactions with the commands displayed. Some rough layouts of how we could build this

// Introduction display //

Your one welcome sentence introduction. Where is your start?

  • ! Quick task
  • ! read
  • ! listen
  • ! watch
  • ! contribute


and for every command you make, you could have the following information displayed :

// ! Quick task //

  • task 1 : introduce yourself to the community in #introductions
  • task 2 : fill-in your profile&skilll in the XXXX
  • task 3 : attend one of our community call every tuesday at 10am PT

Once you’re done make sure to drop us a ! Quick task done with the links and date for the tasks to get your 1st :sourcecred:

// ! read //

What type of reading are you looking for?

  1. Some overview
  2. Some technical rabbit hole
  3. Some insights from the community

// ! listen //

We’ve got you covered on :

  • some podcasts that make a good introduction

  • the last community call

// ! watch //

We’re have something for you on :

  • an overview of SourceCred …

// ! contribute //

you can check-in in different places :

  • if you want to share ideas : *Discourse link *
  • if you want to code : github link to the open issues
  • Look in the #didathing, someone is maybe asking for you (!)
1 Like

I think the “Getting Involved” docs I’m writing will be useful for the intro bot content. Rough drafts will be done by Monday. :slight_smile:

Quick update. We’ve designed with @Bex an information Bot. It will help new comers to get information in a different way & enable other tasks too (linking your adress&nickname in the ledger etc).

  1. the Bot is here. Although it will be off (no interaction), I’ve displayed all the information that it can provide.

  2. the idea is to plug the content of our bot into the metagame (prev. aracred) bot and to set it up in a dedicated SourceCred channel as the InfoBot. My suggestion would be to use the #bot-command channel. Maybe we’ll need to move the channel up in the list as well

  3. the exhaustive list of links will be filled late August

1 Like

Following up the cultivation jam, here is the action plan :

  1. make the cred command working > When asked, the bot will give the weekly & total cred

  2. integrate a few links to the “read / listen / watch” section of the bot. We thought also about including some discourse posts. >> Please drop your top 3 << @LB @Bex

These posts provide an additional understanding of SourceCred through the ideas, issues or development brought up. It’s also a good way to get to know its contributors. And it can be an excellent gateway to get some fresh thinking too.

  1. show the beta version of this bot in a contributor call to get feedbacks & validation

If validated :

  1. run the bot with Heroku to make it available at any time

  2. deploy the bot in the #bot-commands of the SourcreCred discord


The infobot is ready to be plugged in the SC server to get feedback & be used by the community.

What has been done :

  • hosting the bot on Heroku to make it 24/7 available
  • making the command line easier : “!read” for eg.

The last steps:

  1. we may create an #infobot in the “initiative coordination” for the feedbacks

  2. we need also a channel in which we can interact with the bot : create a new one? or use an existing one (#bot-commands)?

  3. regarding the repository : do we fork my repository in the SourceCred repository?

  4. we need to invite the bot in the discord channel (someone with admin rights)

  5. quick task here for creddies : to curate media & links so as to have an on-spot-bot:boom:. The bot will help anyone to explore SourceCred & to know better its community

1 Like

Ben, this all sounds great. I no longer have admin rights, I’m guessing @KuraFire does though. Let me know if there’s anything I can do to help.

Hi Ben! I’m excited by all this progress! :slight_smile:

Some questions before next steps:

  1. What do you mean by “create an #infobot”? A channel in the Discord? A Tag here on Discourse? An initiative plugin-related project?

  2. Does the bot not interact server-wide, or are you suggesting we only limit its interactions to one specific channel? (If the latter, I would love to discuss this with more people in the Discord about what is actually most desirable)

  3. That’s a question for @topocount and/or @decentralion.

  4. I can do that, ping me on Discord in private and I’ll bring it in.

  5. When people request information from the bot and it leads to these links being output, does that output go in the channel where they’re asking, or does the bot open a private message with the user and provide output there?

1 Like

to your questions, my answers :grinning:

  1. I meant to create a channel in Discord called #infobot
  2. the bot interact server wide, but it’s better in my mind to limit its interactions to one specific channel. It prevents from spamming other channels of links or cred score of other players
  3. I’ve dropped the question in the discord channel : #operation
  4. I’ll do that, but maybe we need to fix where the bot will be available
  5. yes the output are provided in the channel where they asked.

For 1 & 2: I don’t think it is necessary to create a dedicated channel; it just puts interactions out of context all the time. We already have a default-muted #bot-commands channel for interacting with bots without clogging conversations; we can make it a best practice for people to go there if they want to use the bot a lot.

For 3, 4 & 5: :slight_smile: :+1:t3: