dawn-crm

byHemen Ashodia

build a general purpose crm which allows all my in bound whatsapp and telegram lead on my number follow some nature style

LandingLeads
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 6

System Requirements Document for dawn-crm

1. Introduction

The dawn-crm project aims to develop a general-purpose Customer Relationship Management (CRM) system that captures all inbound leads from WhatsApp and Telegram messages received on the user's number. The system will feature a nature-inspired design style, providing a visually appealing and intuitive user experience. The primary audience includes CRM owners/administrators and sales agents who manage and track inbound leads.

2. System Overview

The dawn-crm system will facilitate the capture and management of inbound leads from WhatsApp and Telegram. It will provide a unified interface for CRM owners and sales agents to track, manage, and follow up on leads. The system will feature a nature-inspired aesthetic to enhance user experience. Key functionalities include lead capture, lead management, and user authentication.

2a. Product Interpretation and Delivery Boundary

The CRM will be delivered as a web application with custom UI components. It will require backend integration to capture leads from WhatsApp and Telegram. The system will support self-service enrollment for CRM owners and require returning verification for accessing protected lead records. The CRM will be accessible via a web interface, with identity management handled by the application.

Page 2 of 6

2b. Source Content Inventory

Not applicable as no content source directive was provided.

2c. Page Content and Component Coverage

Landing

  • Information/State: Introduction to the CRM, its purpose, and features.
  • Primary Actions: Navigate to Sign Up or Login.
  • Design: Nature-inspired style with imagery and color palette.
  • States: Loading, success, error.

Login

  • Information/State: User authentication for returning users.
  • Primary Actions: Enter credentials, submit login.
  • States: Loading, success, error, password recovery.

Sign Up

  • Information/State: User registration for new CRM owners.
  • Primary Actions: Enter user details, submit registration.
  • States: Loading, success, error.

Leads

  • Information/State: List of inbound leads with status and next action.
  • Primary Actions: View lead details, update status, assign next action.
  • States: Loading, empty, success, error.
Page 3 of 6

Lead Details

  • Information/State: Detailed view of a lead, including conversation history and follow-up notes.
  • Primary Actions: Update lead status, add notes, view conversation history.
  • States: Loading, success, error.

3. Functional Requirements

  • As a CRM Owner/Administrator, I should be able to enroll in the CRM and connect my WhatsApp and Telegram number to capture inbound leads. (Provenance: required_inference)
  • As a Sales Agent, I should be able to log in to the CRM to access and manage lead records. (Provenance: required_inference)
  • As a CRM Owner/Administrator, I should be able to view a unified list of all inbound leads with their status and next actions. (Provenance: required_inference)
  • As a Sales Agent, I should be able to update the status and add notes to each lead's record. (Provenance: required_inference)

4. User Personas

Sales Agent

  • Context: Manages inbound leads from WhatsApp and Telegram.
  • Primary Goal: Ensure every inbound lead has a clear status and next action.
  • Responsibilities: Review new leads, track through the pipeline, record follow-up activity.
  • Interactions: Collaborates with CRM Owner/Administrator to maintain lead accuracy.

CRM Owner / Administrator

  • Context: Owns the CRM and connected messaging numbers.
  • Primary Goal: Ensure the CRM reflects all inbound leads and their progress.
  • Responsibilities: Oversee lead inbox, maintain lead records, review lead activity.
  • Interactions: Works with Sales Agents to ensure lead management efficiency.
Page 4 of 6

5. Core User Flows

5.1 CRM Owner/Administrator Enrollment

  1. Start: Access the Landing page.
  2. Action: Navigate to the Sign Up page.
  3. Action: Enter registration details and submit.
  4. Result: Successful enrollment and connection of WhatsApp and Telegram numbers.
  5. Next Step: Access the Leads page.

5.2 Sales Agent Login and Lead Management

  1. Start: Access the Landing page.
  2. Action: Navigate to the Login page.
  3. Action: Enter credentials and submit.
  4. Result: Access to the Leads page.
  5. Action: Select a lead to view details.
  6. Action: Update lead status and add notes.
  7. Result: Lead record updated successfully.
Page 5 of 6

6. Visuals Colors and Theme

  • Muse: Nature-inspired
  • Headline: Organic and calming
  • Color Palette:
    • Primary: #4CAF50 (Green)
    • Secondary: #8BC34A (Light Green)
    • Accent: #FFEB3B (Yellow)
  • Font Families:
    • Headings: 'Roboto', sans-serif
    • Body: 'Open Sans', sans-serif
  • Type Scale: Responsive, with a base size of 16px
  • Radius/Shape Language: Rounded corners
  • Spacing Rhythm: Consistent with natural flow
  • Imagery Style: Nature-themed photography and illustrations

7. Signature Design Concept

The Landing page will feature a hero section with a nature-themed background image, showcasing the CRM's purpose and features. The design will incorporate organic shapes and a calming color palette to create a welcoming first impression.

8. Interaction Model & Motion Direction

  • Interaction Model: Static (direction)
  • Motion Tempo: Restrained
  • Hero Dimensionality: Layered_2d
  • Landing Hero Motion Brief: The hero section will feature a static nature-themed background with layered elements to create depth. The design will focus on a calming and organic aesthetic, with minimal motion to maintain a serene user experience.
Page 6 of 6

9. Non-Functional Requirements

  • The system must support secure authentication for user login and registration. (Provenance: required_inference)
  • The system must reliably capture and display inbound leads from WhatsApp and Telegram. (Provenance: explicit)

10. Tech Stack

  • Frontend: React
  • Backend: Python/FastAPI
  • Storage: PostgreSQL
  • Deployment: Docker/docker-compose

11. Assumptions and Constraints

  • Lead capture is limited to inbound WhatsApp and Telegram messages arriving on the user's own number.
  • The visual style must adhere to a nature-inspired aesthetic.

12. Glossary

  • CRM: Customer Relationship Management
  • Lead: A potential customer or client captured through inbound messaging platforms.
  • Pipeline: The stages through which a lead progresses in the CRM system.
Preview dataChanges stay in this preview.
Landing design preview
Landing: Explore CRM features
Sign Up: Enter registration details
Sign Up: Submit registration
Leads: View all inbound leads
Leads: 1. Review lead status and next actions
Lead Details: 2. Review lead activity
Lead Details: 3. Update lead record
Leads: 4. Confirm records reflect all leads
Preview dataChanges stay in this preview.
Landing design preview
Landing: Explore CRM features
Sign Up: Enter registration details
Sign Up: Submit registration
Leads: View all inbound leads
Leads: 1. Review lead status and next actions
Lead Details: 2. Review lead activity
Lead Details: 3. Update lead record
Leads: 4. Confirm records reflect all leads