diff --git a/_config.yml b/_config.yml
index 1e6e61f0ac..bf182e268f 100644
--- a/_config.yml
+++ b/_config.yml
@@ -448,6 +448,7 @@ intro_columns:
title: "Layout"
items:
"Window": "components/window/overview"
+ "Predefined Dialogs": "dialog-predefined"
"Animation Container": "components/animationcontainer/overview"
"Tooltip": "tooltip-overview"
"Drawer": "drawer-overview"
diff --git a/components/dialog/images/alert-first-look.gif b/components/dialog/images/alert-first-look.gif
new file mode 100644
index 0000000000..c28ed4750f
Binary files /dev/null and b/components/dialog/images/alert-first-look.gif differ
diff --git a/components/dialog/images/confirm-first-look.gif b/components/dialog/images/confirm-first-look.gif
new file mode 100644
index 0000000000..2a20983637
Binary files /dev/null and b/components/dialog/images/confirm-first-look.gif differ
diff --git a/components/dialog/images/prompt-first-look.gif b/components/dialog/images/prompt-first-look.gif
new file mode 100644
index 0000000000..42b40c5af7
Binary files /dev/null and b/components/dialog/images/prompt-first-look.gif differ
diff --git a/components/dialog/predefined.md b/components/dialog/predefined.md
new file mode 100644
index 0000000000..d4e7fe722d
--- /dev/null
+++ b/components/dialog/predefined.md
@@ -0,0 +1,149 @@
+---
+title: Predefined Dialogs
+page_title: Predefined Dialogs - Alert, Confirm, Prompt
+description: Predefined Dialogs (alert, confirm, prompt) for Blazor.
+slug: dialog-predefined
+tags: telerik,blazor,dialog,predefined,alert,confirm,prompt
+published: true
+position: 10
+---
+
+# Predefined Dialogs - Alert, Confirm, Prompt
+
+Telerik UI for Blazor provides styled substitutes to the standard confirm, alert and prompt dialogs. They match the Theme of the components to make it obvious to the user that the modal dialog is coming from your application.
+
+To use these dialogs, receive a cascading parameter of type `Telerik.Blazor.DialogFactory`. It exposes the methods you can use in your method calls.
+
+````CSHTML
+[CascadingParameter]
+public DialogFactory Dialogs { get; set; }
+````
+
+There are three available ready-made dialogs:
+
+* [Alert](#alert)
+* [Confirm](#confirm)
+* [Prompt](#prompt)
+
+## Alert
+
+The alert dialog usually shows the user that something went wrong, such as a major error that requires their attention and blocks the UI, as opposed to a [notification]({%slug notification-overview%}) that is not modal and is small.
+
+>caption Use an Alert dialog
+
+````CSHTML
+@* Use Alert dialogs, monitor the console for when the code continues *@
+
+Show Alert
+Show Alert with Custom Title
+
+@code {
+ [CascadingParameter]
+ public DialogFactory Dialogs { get; set; }
+
+ public async Task ShowAlert()
+ {
+ await Dialogs.AlertAsync("Something went wrong!");
+
+ Console.WriteLine("The user dismissed the alert box.");
+ }
+
+ async Task ShowAlertWithTitle()
+ {
+ await Dialogs.AlertAsync("Something went wrong!", "Read this!");
+
+ Console.WriteLine("The user dismissed the alert box with the custom title.");
+ }
+}
+````
+
+
+
+## Confirm
+
+The confirm dialog returns a `bool` value that indicates which button the user clicked - `true` for the `OK` button and `false` for the `Cancel` button. This lets you `await` its execution, and then continue the application logic based on that decision. The method that calls it must be `async Task` and *not* `async void` in order to await the execution.
+
+>caption Use a Confirm dialog
+
+````CSHTML
+@* Use Confirm dialogs, monitor the console for when and how the code continues *@
+
+Show Confirm
+Show Confirm with Custom Title
+
+@code {
+ [CascadingParameter]
+ public DialogFactory Dialogs { get; set; }
+
+ public async Task ShowConfirm()
+ {
+ bool isConfirmed = await Dialogs.ConfirmAsync("Are you sure?");
+
+ if (isConfirmed)
+ {
+ Console.WriteLine("The user is sure, continue.");
+ }
+ else
+ {
+ Console.WriteLine("The user changed their mind");
+ }
+ }
+
+ async Task ShowConfirmWithTitle()
+ {
+ bool isConfirmed = await Dialogs.ConfirmAsync("Are you sure?", "Confirmation!");
+
+ Console.WriteLine($"The user is sure: {isConfirmed}.");
+ }
+}
+````
+
+
+
+
+## Prompt
+
+The prompt dialog returns a `string` that the user enters when they press `OK`, and `null` when they press `Cancel`. This lets you `await` its execution, and then continue the application logic based on that decision. The method that calls it must be `async Task` and *not* `async void` in order to await the execution.
+
+>caption Use a Prompt dialog
+
+````CSHTML
+@* Use Prompt dialogs, monitor the console for when and how the code continues *@
+
+Show Prompt
+Show Prompt with Custom Title
+
+@code {
+ [CascadingParameter]
+ public DialogFactory Dialogs { get; set; }
+
+ public async Task ShowPrompt()
+ {
+ string userInput = await Dialogs.PromptAsync("Enter your answer.");
+
+ if (userInput == null)
+ {
+ Console.WriteLine("The user will not answer.");
+ }
+ else
+ {
+ Console.WriteLine($"The user said: {userInput}");
+ }
+ }
+
+ async Task ShowPromptWithTitle()
+ {
+ string userInput = await Dialogs.PromptAsync("Enter answer:", "Input needed");
+
+ Console.WriteLine($"The user answer: {userInput}");
+ }
+}
+````
+
+
+
+
+## See Also
+
+* [Live Demo: Predefined Dialogs](https://demos.telerik.com/blazor-ui/dialog/predefined-dialogs)
+