For the use-cases when the demand side creates a listing on the marketplace and supply sends a request for demand listings. The use-case is mostly seen in "services marketplaces" in which the user types would be as following:
Demand - Client (buyer): The user, who is in need of, look for something, and therefore posts a listing on the platform.
Supply - Provider (seller): The user, who provides something (service), and send a request to a demand listing.
No: |
Email Slug |
Email Title |
Receiver |
When is the email received? |
1 |
Welcome |
Welcome email |
Both |
when both demand and supply register |
2 |
password-reset |
Password reset |
Both |
when both demand and supply reset their password |
3 |
new-task |
New Task |
Supply |
Supply receives the email when there is a new task based on his preference |
4 |
new-request-sent |
New request sent |
Supply |
Supply receives the email when he sends a request for a listing |
5 |
new-request-received |
New Request received |
Demand |
Demand receives the email when there is a request for the listing he posted. |
6 |
request-declined |
Your request has been declined |
Supply |
1- Supply receives the email when demand books someone else. 2- Supply receives the email when demand cancels the listing that provider sent a request. 3- Supply receives the email when demand books nobody. 4- Supply receives the email when the listing he sent request is marked as spam. |
7 |
listing-cancelled |
Listing has been canceled |
Demand |
Demand receives the email when he cancels the listing he created. |
8 |
request-cancelled |
Your request has been canceled |
Supply |
Supply receives the email after he cancels/revokes his request |
9 |
task-request-cancelled |
Request for your task has been canceled |
Demand |
Demand receives the email when supply revokes/cancels his application from the listing that he has sent a request |
10 |
request-accepted |
Request has been accepted |
Supply |
Supply receives the email when he is booked by demand. |
11 |
new-order |
Order confirmed |
Demand |
Demand receives the email when he completes booking the provider (after filling billing details) |
12 |
request-marked-as-done |
You marked the task as done |
Supply |
Supply receives the email when he marks the listing as done |
13 |
order-marked-as-done |
Order has been marked as done |
Demand |
Demand receives the email when supply marks the listing as done |
14 |
order-completed |
Order has been completed |
Demand |
Demand receives the email when he marks the listing as done (from this email it is directed to leave review page) |
15 |
request-completed |
Assignment has been completed |
Supply |
Supply receives the email when demand marks the job as done (from this email it is directed to leave review page) |
16 |
review-left |
New review |
Both |
Both demand and supply receive the email when there is a review done |
17 |
request-closed |
Your task has been closed |
Supply |
Supply receives the email when demand closes the listing due to unsuccessful result. |
18 |
order-closed |
You closed the booking |
Demand |
Demand receives the email when he closes the listing due to unsuccessful result. |
19 |
message-received |
New message |
Both |
Both demand and supply receive the email when a private message is sent. |
20 |
task-marked-spam |
Your task has been marked as spam |
Demand |
Demand receives the email when his listing is marked as spam by admin. |
21 |
user-blocked |
You have been blocked |
Both |
Both demand and supply receive the email when he is blocked by admin. |
1- Apart from the action URL parameter, every email related to "request" has also the following parameter: <%-LISTING_TITLE %>
Admin can paste the parameter into the request related emails in order to specify the related listing for the provider. E.g. If admin pastes the parameter in the "request declined" email, the parameter will be shown as the name of the listing that the provider has been declined.
2- The two following parameters can be included in "new message" email:
<%-SENDER_FIRST_NAME %> and <%-SENDER_LAST_NAME %>
The parameters enable the receiver to see in the email the person who sent him/her a message.
3- The parameter <%-EMAIL_SETTINGS_URL %> will direct the user to the email settings.
PS: If you add any parameter which is not supported, the email will not be sent to the related user.