Engagement & Bot

[apentori]

Description

The Status App team need a Engagement Bot to interact with user and help for support.

Requirements

Engagement

• Send a welcome message to the newly onboarded user, prompting them to invite a friend, check Status App's wallet, communities etc. The messages will have deep links.
• Send 3 to 4 follow up messages to new users on a particular schedule (1, 3, 7 and 15 days) to re-invite the user to use the app.

Support

• Users that have the bot in contact, can send us a message directly with feedback, feature proposal or an issue faced when using Status.
• Must be able to read and reply to user feedback if needed / appropriate.

Workflow

Engagement

sequenceDiagram
    NewUser->>+Bot: Add Bot as a Contact
    Bot-->>NewUser: Acces Contact request
    Bot->>+NewUser: Send First Message
    Note over Bot,NewUser: Wait for 1,3, 7 and 15 days
    Bot->>+NewUser: Send new message

Loading

• The Bot will have to store the Contact in the Database and everyday check if it reach the date to send another message.
• The messages will be store in the config file.

Support

sequenceDiagram
    User->>+Bot: Send a message to the bot
    Bot->>Bot: Verify if the message contain the support keyword
    alt is asking for support
        Bot->>+Group: send message to group
        Group->>-Bot: Send Reply to the message
        Bot->>User: Transfert reply to the User
    else not correct message
        Bot->>-User: Reply with automatic message
    end

Loading

• The support group will be create with the Bot at start up if it don't exist. The accounts in the group will be configurable in config.yaml
• The group will have to reply to the message, any message send without repying to the message will not be transfert to the user
• The Bot will save each request in the database to store the chatId for each message.
• The Bot will check if the user message have a keyword to avoid spam. Example of keyword for the support: Help, help, support, Support

[nickninov]

Support

To make the bot a bit more interactive:

• Messages that are within the rate limit and will be forwarded to the group chat will have a ✅ on them
• Messages that exceed the rate limit will have a ❌ on them and an automatic reply. Reply should tell the user that the message exceeds the allowed rate limit and when the limit will be reset. For example Message exceeds current limit. Please try again in 1hr and 3m.

[sunleos]

1 Issue: the word feedback is only acceptable when it is lower case "feedback".
Expected:
Make it case-insensitive: "FEEDback", "Feedback", "FEEDBACK", "feedbacK", "feedback" - all these options should be acceptable and recognized as the indicator that the user wants to send this message to the Status team.

[sunleos]

2. Issue: screenshots attached to a user message are stripped down from the message
   Expected: the attached screenshots are included in the users message posted in the Feedback group