# Create default subscriber form templates

{% hint style="info" %}
You can show off your design skills and create opt-in subscriber form templates that are automatically added to new customer accounts, we give you a head start by shipping with around 20 of them that can be edited or deleted.
{% endhint %}

**Go to customers -> frontend settings from the backend top navigation**

<div align="left"><figure><img src="/files/1vE4KSBJWKaPkIq9TRRK" alt="" width="250"><figcaption></figcaption></figure></div>

{% hint style="info" %}
In the form templates tab click '**add template**' to create in our drag-and-drop composer, to learn more about designing forms [see our subscriber opt-in forms guide](/docs/subscriber-opt-in-forms/what-you-can-do-with-forms.md). Forms use the same drag-and-drop composer as email templates,[ learn more about the drag-and-drop composer](/docs/using-the-legacy-drag-and-drop-email-composer/the-basics.md).
{% endhint %}

<figure><img src="/files/1RIMzG3udwN5IwDeNrzG" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Edit or delete the templates that come included in the platform with the **action menu.**
{% endhint %}

<div align="left"><figure><img src="/files/nguHbYvHOPyAYdZv7ERA" alt="" width="334"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Use the properties tab to give your form a name**

Make sure you check '**show on frontend**', giving the template a display order number lets you place your favorites at the top of the list so they'll be seen first.
{% endhint %}

<figure><img src="/files/FR83w4U0rGRf6gphbW1a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.emaildelivery.com/docs/backend-administration/create-default-subscriber-form-templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.