Notification Status Lifecycles and Definitions

This document explains the different notification status, from initiation on the Client’s side till the delivery to the Client’s customers.

API Request Processing Status

The following statuses are received after API requests are received from the Client and fired by Fyno.

Status	Description	Email	WhatsApp	SMS	RCS	InApp	Push	WebPush	Voice	Slack/Discord/Teams
Error	Message was failed at Fyno’s end	✅	✅	✅	✅	✅	✅	✅	✅	✅
Failed	Message was failed at Provider’s end	✅	✅	✅	✅	✅	✅	✅	✅	✅
Timeout	Provider failed to respond within 5-10 seconds	✅	✅	✅	✅	✅	✅	✅	✅	✅
Dropped	Message was dropped (due to configuration in Fyno - supression/route/subscription)	✅	✅	✅	✅	✅	✅	✅	✅	✅
Success	Message was successfully submitted to the provider	✅	✅	✅	✅	✅	✅	✅	✅	✅

Submission Status

The following statuses are received after Fyno successfully submits the requests (or encounters a submission timeout).

Status	Description	Email	WhatsApp	SMS	RCS	InApp	Push	WebPush	Voice	Slack/Discord/Teams
Queued	Message was queued at the provider’s end	✅	✅	✅	❌	✅	❌	❌	❌	❌
Processed	Message request was processed and sent for delivery	✅	✅	✅	✅	❌	✅	❌	❌	❌

Undelivered Notification Status

The following statuses are received after the notification is sent from the service provider to the recipient but remains undelivered.

Status	Description	Email	WhatsApp	SMS	RCS	InApp	Push	WebPush	Voice	Slack/Discord/Teams
INVALID-SUB	Subscriber was invalid	❌	❌	✅	❌	❌	❌	❌	❌	❌
REJECTED	Message was rejected by the provider (DLT/Template/Complaint issue)	✅	✅	✅	❌	❌	❌	❌	❌	❌
BOUNCE	Email was bounced	✅	❌	❌	❌	❌	❌	❌	❌	❌
DENIED	Notification was denied (Push disabled / Call denied)	❌	❌	❌	❌	❌	✅	❌	✅	❌
FAILED	Message has failed at the provider’s end (due to congestion/error/template issue)	❌	✅	✅	❌	❌	❌	❌	✅	❌
NOANSWER	Call was not answered (or user was busy)	❌	❌	❌	❌	❌	❌	❌	✅	❌
UNDELIVERED	Message could not be delivered by the provider	✅	✅	✅	✅	❌	✅	❌	❌

Successful Delivery Status

The following statuses are received after the notification is successfully sent from the service provider to the recipient and delivered.

Status	Description	Email	WhatsApp	SMS	RCS	InApp	Push	WebPush	Voice	Slack/Discord/Teams
DELIVERED	Message was delivered successfully	✅	✅	✅	✅	✅	✅	✅	❌	❌
UPDATED	Message content was updated successfully	❌	❌	❌	❌	✅	❌	❌	❌	❌
CLICKED	URL/Link in the message or the entire notification was clicked by the user	✅	✅	✅	✅	✅	✅	✅	❌	✅
OPEN	Message was opened by the user	✅	❌	❌	❌	❌	❌	❌	❌	❌
READ	Message was read by the user (or marked as read)	❌	✅	❌	✅	✅	❌	❌	❌	❌
ANSWERED	Call was answered	❌	❌	❌	❌	❌	❌	❌	✅	❌
DELETED	Message was deleted/dismissed by the user	❌	❌	❌	❌	✅	✅	✅	❌	❌
KEYPRESS	Call was answered and a key was pressed by the user during the call	❌	❌	❌	❌	❌	❌	❌	✅	❌
REPLIED	Message was replied to by the user	❌	✅	❌	❌	❌	❌	❌	❌	❌
UNSUBSCRIBED	The user unsubscribed for notifications from this particular message	✅	✅	✅	✅	✅	✅	✅	✅	✅
SPAMREPORT	This status is received when a recipient marks an email as SPAM.	✅	❌	❌	❌	❌	❌	❌	❌	❌
UNKNOWN	The status received is UNKNOWN. Please report to Fyno in such cases	✅	✅	✅	✅	✅	✅	✅	✅	✅

Converted & Verified Notification Status

The following statuses are received after the notification is sent from the service provider to the recipient and if its marked as Converted (Conversion Tracking enabled) or Verified (OTP/Link verified via Fyno Verify).

Status	Description	Email	WhatsApp	SMS	RCS	InApp	Push	WebPush	Voice	Slack/Discord/Teams
CONVERTED	Notification status will be marked as Converted, if the Conversion tracking is enabled for a notification event and API is triggered to mart it as converted	✅	✅	✅	✅	✅	✅	✅	✅	✅
VERIFIED	Notification status will be marked as Verified if a user successfully verifies OTP/Link generated through Fyno Verify	✅	✅	✅	✅	✅	✅	✅	✅	✅