tywalch / recluse Goto Github PK

Details stored re: contact.
Critical:

• Name
• Omni-contact field (Phone, email, social media, address)
• Contact frequency (Twice per month, Once per month, once a quarter, twice a year, once a year)
• Future clue (Free text written by user to be displayed on next notification)
• Date last contacted
• Upcoming contact date
• Date added

Nice to have:

• How you met
• Birthday
• Tags
• User defined dates

• Users to receive text message notifications when recluse has schedule them to reach out to their contact. This is based on a user defined frequency
• Notifications are sent with some degree of variance in date range. The range of variance in notification date increases with less frequent frequencies. For example: With a chosen frequency of once a year, users may receive notifications as much as a month and a half before 365 days has passed while frequencies of once a month may only be off by one week. The goal is to invoke a level of serendipity with user messages.
• Contained in the notification is the contact's name, specified contact method, and a "Clue" created by the user either during the contact's initial creator or a previous outreach.
• After a few days have passed since the original notification, recluse is to reach out to the user with a message similar to "Did you end up reaching out to JOHN DOE? If so reply back with a Clue to be sent to you next time you connect with JOHN.