📖
ZeroAuthority Docs
  • Welcome to the Zero Authority Docs!
  • The Dao
    • Vision and Values
    • Meet the core team
    • How to contribute to the DAO
    • How to reward contributions
    • Zero Authority Solutions
      • Bounty Onchain
        • Create a bounty on v2 beta
        • How to create a bounty
        • How do I select a winner
        • Selecting Winner the Bounty
        • Bounty Ideas for Community-Centered Engagement
      • Gigs Onchain
        • Gigs on v2 beta
        • How To Offer or Accept Gig Onchain
      • Milestone Gigs Onchain
      • Overview of Email Notification
      • Reputation Onchain
      • Nova
        • 🔹 Bot Commands
        • 🔹 Token Distribution Index
        • 🔹 Try Telegram Bot
        • 🔹 Try Discord Bot
        • 🔹 Setup the Tracker Bot
        • 🔹 Setup the Stacks Tokens Bot
        • 🔹 Setup the Runes Bot
        • 🔹 Setup the NFT Bot
        • 🔸 Premium Benefits
        • 🔸 Setup Premium telegram or discord
        • 🔸 Setup Premium Notifications
    • Tokenomics
    • Product Roadmap
      • Road Map Overview
        • Roadmap Detailed
      • The Gig Marketplace
      • Bounty
      • Expertia Release
      • SmartTrail
    • Updates
      • Zero Authority V2 on Testnet
      • Zero Authority V2
      • MFA for All Access Points
      • v.1.0.0 Bounty Onchain
      • v.1.5.2 Gig Mkpl update
      • v.1.5.1 Gig Mkpl update
      • v.1.5.0 Gig Mkpl update
      • v.1.4.0 Gig Mkpl update
      • v.1.3.1 Gig Mkpl Bug Fix
      • v.1.3.0 Gig Mkpl
      • v.1.2.0 Gig Mkpl update
      • v.1.1.0 Gig Mkpl update
      • v.1.0.2 Gig Mkpl Bug Fix
      • v.1.0.1 Gig Mkpl update
      • v.1.0.0 Gig Mkpl on mainnet 🎉
      • Testnet 1.4 update
      • Testnet 1.3 update
      • Testnet 1.2 update
      • Testnet 1.1 update
      • Testnet 1.0 update
      • Target Launch Date
    • Standard Reputation Framework
      • 15 Common Categories
      • Clarity & JSON Implementation
      • Clarity Contract
      • JSON Metadata
    • Access to the Platform
    • Investors & Stakeholders
      • December 2024
Powered by GitBook
On this page
  1. The Dao
  2. Zero Authority Solutions

Overview of Email Notification

Overview procedure regarding email notifications for gig activities

PreviousMilestone Gigs OnchainNextReputation Onchain

Last updated 10 months ago

Introduction

On July 2, 2024, we launched a new feature that allows users to receive email notifications for key activities related to gigs. This feature is designed to enhance user engagement and communication by keeping both creators and clients informed about their gig activities.

How to Enable Email Notifications

To start receiving email notifications, users must connect their wallet and update their profile with an active email address. This ensures that notifications are sent to the correct address associated with their account.

Why Email Notifications Help Users

Email notifications provide users with timely updates and reminders about important gig-related activities. They help improve the overall user experience by:

  • Keeping users informed about the status of their gigs.

  • Reducing response times by notifying users promptly about actions taken on their gigs.

  • Increasing transparency and trust by maintaining clear communication between creators and clients.

  • Enabling users to manage their gigs more efficiently by staying up to date.

How Email Notifications Work

Once a user has connected their wallet and added an active email address to their profile, they will start receiving notifications for specific actions related to gigs. These notifications are triggered automatically based on the activity flow of the gigs.

Notification Process

The email notification process is outlined as follows:

  1. Email to the Creator When Gig Request:

    • The creator receives an email when a new gig request is submitted by a client.

    • This email includes details about the gig request, allowing the creator to review and respond promptly.

  2. Email to Client When Gig Accepted:

    • The client receives an email when their gig request is accepted by the creator.

    • The email contains information about the acceptance and any additional details provided by the creator.

  3. Email to Client When Gig Declined:

    • The client receives an email when their gig request is declined by the creator.

    • The email provides the client with a reason for the decline and any feedback from the creator.

  4. Email to Creator When Satisfaction Vote as Client:

    • The creator receives an email notification when a satisfaction vote is submitted by the client.

    • This email includes the client's feedback and rating, helping the creator understand their performance.

  5. Email to Client When Satisfaction Accepted from the Artist/Creator:

    • The client receives an email when the creator accepts the satisfaction vote.

    • This email confirms that the creator acknowledges the client's feedback, promoting a positive feedback loop.

This procedure ensures that all parties involved in gig activities are well-informed and can act accordingly based on the notifications received.

fixed gigs notifications