---
title: "Bajaj | ASD Termination Process"
description: "SOP – ASD Termination Note: Check whether request is for Vistaar Sales or Vistaar Service. ASD to be removed/Delete/Terminated Note: If any of these terms (Removed/Delete/Terminated) are used by ASM while raising the ticket, as a support you should ..."
url: "https://supportb.kinsta.cloud/docs/bajaj-asd-termination-process/"
updated: "2025-12-30"
category: Account Details_Master Folder
---

# Bajaj | ASD Termination Process

**SOP – ASD Termination**

Note: Check whether request is for Vistaar Sales or Vistaar Service.

1. ASD to be removed/Delete/Terminated 

Note: If any of these terms (Removed/Delete/Terminated) are used by ASM while raising the ticket, as a support you should not delete the ASD directly. Instead, first confirm the **Proposed Counter Type** with the ASM.

| Dealer Code | Dealer Name | SAP Code | ASD Name | Proposed Counter Type |
| --- | --- | --- | --- | --- |
|   |   |   |   |   |
|   |   |   |   |   |
|   |   |   |   |   |
|   |   |   |   |   |

These are the fields ASM needs to fill and provide. 
If Proposed Counter Type as ASD 
If the **Proposed Counter Type** is **ASD**, additional clarification is required via email to determine whether an **AGP** needs to be created for the same.
 
If an **AGP** is not to be created, the **ASD** must be made **Inactive** after receiving approval from **Bajaj HO**.
 
Approval from Bajaj HO (Vivek/Som)

Email ID’s:

1. Kumar Vivek = kvivek@bajajauto.co.in        
2. Som Debasis = sdebasis@bajajauto.co.in

The process = Manage ASD’s>Advance Stage>Filter through dealer code>Select the ASD’s>Actions button>Change Stage>Add a comment (Asked by ASM, Approved by HO)>Change the status. 

![](https://desk.zoho.in/galleryDocuments/edbsn5c5730cc33c262b78f2e54991af4505d29de6078da4efb94fd6a26e6b78308f1ec3efa398190c7292e048f26f12643c1b1437ba7da45f602f7a2795d6b4d0329)
![](https://desk.zoho.in/galleryDocuments/edbsn5c5730cc33c262b78f2e54991af4505dd3369eb83a5f3d7b9471840bed0fa570a224381c3d96801c3b7842d1da302127f11b1f7488a2bacc34eaaa37c87b1cfe)

*Note:*

Below is a reference table to refer **ASM Requests** to their respective **System Nomenclature**:

| Request | Counter Type in LSQ |
| --- | --- |
| ASD | ASD |
| Branch | BR |
| BR | BR |
| vacant | VCNT |
| Vcnt | VCNT |
| RSO | UNATH |
| FO | UNATH |
| Unauthorized | UNATH |
| Main Dealer | MD |
| MD | MD |

Once the required information is provided by the **ASM** and approval is received, the fields will be updated accordingly.

For **any counter type changes**, first obtain **approval from Bajaj HO** before proceeding.

Share the following details with **Bajaj HO** for approval. The **Suggestive Counter Name** field will be provided by the **HO team**.

| Dealer Code | Dealer Name | SAP Code | ASD Name | Proposed Counter Type | Suggestive Counter Name |
| --- | --- | --- | --- | --- | --- |
|   |   |   |   |   | To be asked from Bajaj HO |
|   |   |   |   |   |  |
|   |   |   |   |   |  |
|   |   |   |   |   |  |

Once approval is received from **Bajaj HO (Vivek/Som)**, the following fields need to be updated in the system:

| ASD Email Id | Stage | Counter Type | Counter Name | SAP Code |
| --- | --- | --- | --- | --- |
|   | Active |   |   |   |

**The process **= Manage ASD’s>Adva