# Delete Softphone Layout

The **SoftPhoneLayoutDel** template enables the deletion of a specific SoftPhone Layout in Salesforce through AutoRABIT's Environment Provisioning module.

## Steps to Create the SoftPhoneLayoutDel Template

1. Log in to your AutoRABIT account.
2. Navigate to the **Env. Pro.** module.
3. Click **Create New Template**.
4. Go to the **Create** [**Unsupported Metadata Template**](/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates.md) tab.
5. Enter a **name** and a **short description** for the template.
6. Select the **SoftPhoneLayoutDel** checkbox under [**Softphone Layout**](/product-guides/arm/arm-features/environment-provisioning/unsupported-metadata-templates/softphone-layouts.md).
7. Click **Add**.
8. On the next screen:
   * A **Test Case Name** is auto-generated by default.
   * In the **Softphone Layout To Delete** field, enter the name of the layout to be deleted.
   * Click **Add** to input custom test data, if needed.
   * Click **Save** to save this test case.
9. Click **Save** again to save the template.
10. After successful creation, you’ll be redirected to the **Environment Provisioning History** screen.
11. Click **Run** to execute the template on your destination org.
12. Select your **destination org** from the dropdown and enter the **email address(es)** to receive a notification upon execution.
13. In the **Post Deployment Steps**, select the test cases you recently created.
14. For a detailed summary report, refer to the **View History** page.


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/environment-provisioning/unsupported-metadata-templates/softphone-layouts/softphone-layout-delete.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.