> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# NexG Platforms
# Introduction
NexG provides a communication platform for a quick, seamless, and secure flow of conversational interactions and transactions between businesses and consumers through multiple channels.
**Prerequisites**
Ensure you have access to your NexG Platforms dashboard and have the API key for your NexG Reach account.
# Configure NexG as a Custom SMS Connector (Service Provider)
This article will help you set NexG as a custom connector on the MoEngage dashboard. Perform the following steps to configure NexG as a custom SMS connector:
1. Log in to the MoEngage Dashboard.
2. Navigate to **Settings** > **Channel** > **SMS** > **Sender Configuration**.
3. Click **+ Add Service Provider** at the top right corner.
4. Add the following details in the **Sender Details** screen.
| Field | Description |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Mark as default** | Turn on this toggle to mark the sender as the default sender for the service provider being configured. If marked as default, this sender would be used for sending all SMS campaigns from MoEngage unless you select a different sender while creating the campaign. |
| **Service provider name** | This field identifies the service provider you are configuring on the MoEngage Dashboard and has to be unique. Type the name of the service provider here. |
| **Sender name** | This field identifies the readable sender name that can be used while creating a campaign or alert. |
| **Sender type** | The Sender type can either be **Promotional** or **Transactional**. - Choose the **Sender type** as **Promotional** when you would be using the Sender for sending information about your brand, promoting deals, or engaging with users.
- Choose the **Sender type** as **Transactional** when you would be using the Sender for sending alerts about transactions, OTPs, security information, or any information that can be classified as transactional in nature.
|
5. Configure the Webhook by adding the following details:
| Field | Description |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **API URL** | This field contains information about the URL that should be used to send an API request to the Sender. You can get this information from the API Documentation of the Sender. Type the API Endpoint of the sender here. The API URL for nexG is: [https://automate.nexgplatforms.com/api/v1/sms/save](https://automate.nexgplatforms.com/api/v1/sms/save) |
| **Method** | Select **POST** as the HTTP method. |
| **URL Parameters** | Add the URL parameters to be passed to the API as key-value pairs using this option. You can get this information from the API documentation of the sender. For example, if the API URL call uses the GET method, all the parameters, such as API Key, Authorization, and so on, are passed as URL parameters. |
| **Headers** | Add the request headers to be passed to the API as key-value pairs using this option. Make sure to include the following in the request header: - Content-Type as the key and application/json as the value
- Authorization as the key and YOUR\_API\_KEY as provided by NexG.
|
6. Choose the Body Type as **JSON** and add the following details:
```json JSON theme={null}
{
"serviceType": "Transactional"
"msgDetails":[
{
"messageid": "YOUR_MESSAGE_ID",
"contactnumber": "Moesms_destination",
"message": "Moesms_message",
"messagetype": "normal",
"header": "YOUR_HEADER",
"templateid": "Moesms_dltTemplateId",
"campaignid": "Moesms_campaignId"
}
]
}
```
Change the value for these keys:
* header: Replace with the sender ID authorized for your campaigns.
* serviceType: Use the correct route name (like "TRANS" or "PROMO").
* PEID: Replace with your unique Entity ID provided by nexG.
7. **Send a test SMS** to verify your configuration.
8. Click **Save** to save the Sender Configuration.
9. You can configure delivery tracking after creating the sender in the MoEngage Dashboard. For information about Delivery Tracking, refer to [Delivery Tracking for Custom Connectors](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/getting-started-with-sms/configure-custom-connector-for-sms).
10. You can map the attributes of the delivery tracking response manually or automatically.\\
# Next Steps
* Create an SMS campaign using the [Getting Started for creating SMS campaign](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/create-an-sms-campaign).
* Set the [Frequency Capping for SMS](/docs/user-guide/settings/channels/delivery-controls/frequency-capping).
* Set the [Current Service Provider](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/getting-started-with-sms/configure-an-sms-sender).
* [Read more about campaign analytics.](/docs/user-guide/campaigns-and-channels/connectors/analyze/connector-campaign-analytics)