---
# System prepended metadata

title: User Stories for wiki bot
tags: [user stories]

---

---
tags: user stories
title: User Stories for wiki bot
description: User Stories for wiki bot
---

# Goal :maple_leaf: 

Discord users commonly ask questions that might have already been answered in the #faqs channel or FAQ section of the wiki.

We have a carl bot setup using which active users can trigger pre-defined response. We have validated the usefulness of this bot, based on it's usage.

**Mission of this new undertaking** is to:

- allow contributors to fetch _any_ article from wiki (not just FAQs)
- remove overhead for contributors to remember tagname corresponding to each article
- remove overhead for maintainers to add/update tag for every article

---

### [TODO] User Stories :libra: 

If the Carl bot is to be manually invoked, based on user's query, we need there be some simple triggers

|Trigger words |Typical comment| Expected response
|-----|--------|-----|
| `.bestmf` | _Which is the best mutual fund?_, _What MF should I invest in?_ | Hello `@user`, no one can predict how a mutual fund would perform in the long run. Data also shows consistently chasing best mutual funds result in behaviour gap. Pick one that you can stay with for long term. Learn more [here](https://indiainvestments.gitbook.io/content/faqs/whats-the-best-mutual-fund-i-can-invest-in) |
| `.sipdate` | _Which day of the month gives best returns for SIP?_ | Unfortunately, there's no such thing, `@user`. It's rare for markets to move up / down so much in a single month, that a single SIP installment being on a different date would make a sizeable difference in your long term. Read [more here](https://indiainvestments.gitbook.io/content/faqs/which-date-s-is-are-best-for-sip-in-a-month) |


---

### [TODO] How can you ask wiki bot to ping a pre-defined message?

Each FAQ has a tagname mapped to it (first column in above table). Just send this message in any of the supported channel — `.<tagname> @user`

This would command bot to send pre-defined message and also mention `user` in the description.

