# Source: https://docs.avaamo.com/user-guide/configuration/settings.md

# Settings

You can specify the general settings from the `Configuration > Settings` option. Also, note the agent authentication keys generated by the platform, which can help you access specific details about your agent.&#x20;

{% hint style="info" %}
**Notes**:

* Ensure you have met all the [pre-requisites](https://docs.avaamo.com/user-guide/quick-start-tutorials/pre-requisites).
* You can configure the agent immediately after creating an agent. See [Create AI agent,](https://docs.avaamo.com/user-guide/ai-agent/create-an-ai-agent) for more information.
* If you wish to edit an agent, then:
  * In the **Avaamo Platform UI**, navigate to the **Agents** tab in the top menu. Search and open the required agent. See [Search agents](https://docs.avaamo.com/user-guide/how-to/build-agents/manage-agents/other-common-actions#search-agents), for more information.
  * Click **Edit** to unlock the agent before editing.
    {% endhint %}

<figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2FpMhaoU0tNQ803u3FEsoZ%2FScreenshot%202025-10-29%20at%205.10.48%E2%80%AFPM.png?alt=media&#x26;token=b67e5adb-4cb7-47fd-967e-aa64b958166a" alt=""><figcaption></figcaption></figure>

### User authentication handler

You can authenticate users via the agent across web, phone, and SMS channels using this block. Here, you can write any custom JS code based on your requirements, and it gets executed to authenticate the user before the agent loads. This helps secure all communication through the agent by authenticating the user before using the channel.

Refer [User authentication handler](https://docs.avaamo.com/user-guide/how-to/build-agents/configure-agents/define-settings#user-authentication-handler), for more information.

### Error handler

This feature enhances error handling and fallback management within the AI agent. It allows developers to define a custom error handler that dynamically forwards requests when a system error occurs.

Enhanced to support dynamic values in Forward Headers, allowing the use of storage variables or JavaScript blocks for scenarios such as passing the called phone number.

You can add custom JavaScript code in the Error Handler to handle the following situations:

1\. **Call forwarding:** When the system fails, forward the call to a specific number defined in the Error Handler.

Use the function `return SmartCall.forward(<from>, <to>)` to forward a call to a specific number if the system fails to continue the call.

```javascript
console.log("con", context);
if (context.conversationMode == 'voice') {
    return SmartCall.forward("", "+18304453477");
} else {
     {avm_instruction: "Inform user about being unable to forward the call"};  
}
```

2\. **Call hang-up:** When the system fails, gracefully disconnect the call by specifying a return message.

Use the function `return SmartCall.hangup()` to disconnect the call if the system fails to continue.

```javascript
console.log("con", context);
if (context.conversationMode == 'voice') {
    return SmartCall.hangup();
} else {
    return { message: "Something went wrong, please try again" };
}
```

3\. **Return message:** If the bot is text-based, you can also discontinue the session with a custom message.

Use the function `return { message: {} }` to display a message if the system fails to continue the chat.

```javascript
console.log("con", context);
if (context.conversationMode == 'text') {
    return { message: { text: "Hello! How can I help you today?" } };
} else {
    return { message: { text: "Something went wrong, please try again." } };
}
```

### Advanced features

The following options are available in Advanced features:

<figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2FRTrQsRY6Bg6x6p0m2CSG%2FScreenshot%202025-11-11%20at%2012.22.52%E2%80%AFPM.png?alt=media&#x26;token=8270af23-bfa2-485e-9c4b-cc0935ddcdf6" alt=""><figcaption></figcaption></figure>

#### **Enable debug logs**&#x20;

The `Enable Debug Logs` option allows users to enable or disable debug logs at the `agent level`. This feature provides better control over log visibility for troubleshooting and debugging. This is especially useful when masking is enabled, as logs are otherwise suppressed.

See [Enable debug logs](https://docs.avaamo.com/user-guide/how-to/build-agents/configure-agents/define-settings#enable-debug-logs), for more information.

#### **Enable hybrid SDK**&#x20;

If you wish to integrate the Avaamo Platform using the Hybrid SDK, then you must enable the Hybrid SDK in the `Agent > Settings page`. The Platform then opens the channel to listen for requests in the Hybrid SDK integration. By default, this communication is not available unless the **Enable Hybrid SDK** option is enabled.&#x20;

See [Hybrid SDK](https://docs.avaamo.com/user-guide/how-to/build-skills/create-skill/customize-your-skill/how-to/integrate-with-api-1/hybrid-sdk), for more information.

#### **Enable feedback**

The **Enable Feedback** option allows users to collect feedback from end users at the agent level. When enabled, this feature displays a feedback option after each response, allowing users to rate the accuracy or usefulness of the bot’s answers.

This helps administrators and developers assess response quality, identify areas for improvement, and fine-tune the agent’s performance. Disabling this option hides the feedback prompt from users, ensuring a cleaner interface when feedback collection is not required.

<div align="left"><figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2FiLpndOfcg46ZBaRsq3sI%2Fimage.png?alt=media&#x26;token=3fa51a7b-9951-4403-92c7-2785ad2bb97e" alt="" width="375"><figcaption></figcaption></figure></div>

Refer [Collect feedback,](https://docs.avaamo.com/user-guide/overview-and-concepts/advanced-concepts/collect-feedback) for more information.

#### Enable previous context

The **context persistence** capability allows the agent to retain the conversation context even after a period of user inactivity.

When a user resumes a conversation after being idle for an extended duration (for example, an hour or a day), the system preserves the previous session context. This enables the agent to understand and respond based on the earlier conversation history, eliminating the need for the user to repeat previous information.

**To enable this feature:**

1. Go to **Configuration > Settings > Advanced Settings**.
2. Select the checkbox **Enable Previous Context**.

This feature ensures a more seamless and natural conversational experience by maintaining context across sessions and minimizing repetitive interactions.

### Information Masking

Masking allows you to protect PII/PHI/GDPR compliance data within the Avaamo Conversational AI system. There are ways to configure information masking in the Avaamo Platform based on your business requirements.&#x20;

<figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2FQh25C6ZlJoR71fMRlU22%2FScreenshot%202025-10-29%20at%204.50.30%E2%80%AFPM.png?alt=media&#x26;token=559505e3-6c76-4837-8c37-b6d490b0e4a9" alt=""><figcaption></figcaption></figure>

Refer [Enable information masking](https://docs.avaamo.com/user-guide/how-to/build-agents/configure-agents/define-settings#enable-information-masking), for more information.

### Notifications

You can use notifications to send daily usage and error notification reports to the users, as required.

<figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2F2ZQeJDOBvwtyHDw4yWAa%2FScreenshot%2029-10-2025%20at%2016.42.png?alt=media&#x26;token=67c18629-1e91-4839-bc22-7a6b63f0745a" alt=""><figcaption></figcaption></figure>

**Daily usage report:** In this field, specify the email IDs of the users who need to get a daily report on agent usage. The first daily usage report is generated at 1:00 AM in the time zone specified in the Time Zone field, and the next consolidated report is generated after 24 hours, and so on.

**Error notification**: In this field, specify the email IDs of the users who need to receive error notifications if JS errors are encountered during agent interaction. Error notifications are sent with a 15-minute gap between each email.

**Time zone:** Select the time zone to generate the daily usage report. If no timezone is selected in this field, then the UTC timezone is considered.

**Add email IDs for daily usage reports and error notifications**

* Specify the email IDs of the users in the `Daily usage report` and `Error notification` field.
* Click the + icon to add the email ID.
* Click `Save` to save the changes made to the page.

**Error notification emails**

Each error notification email has the following information:

<figure><img src="https://docs.avaamo.com/user-guide/~gitbook/image?url=https%3A%2F%2F2934665269-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-LpXFTiTgns4Ml77XGi3%252Fuploads%252FIgDzfu10GI4xGe7lE06A%252F6.1-js-errors-email.png%3Falt%3Dmedia%26token%3D4c5dcf51-92b9-458d-ad5e-83169410bc5c&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=1a1fed5f&#x26;sv=2" alt=""><figcaption></figcaption></figure>

* The stage in the application in which the errors occurred. Stage refers to development, testing, staging, or production. If errors occurred in more than one stage, separate notification emails are sent for each stage.
* A link to the JS errors page.
* The errors and the corresponding details of each error. The email lists up to 25 errors. If there are more than 25 errors, a link is provided to view all the errors.
* A link to send an email to all the agent owners.

### Agent authentication keys

The following are the authentication keys generated by the Platform for an agent. Typically, these keys are used in an API when you are required to authenticate an agent:

* **Agent UUID**: A unique agent identifier generated by the platform.
* **Agent AccessToken**: This access token is used only for Conversation API and Message API operations.
* **API Token**: This access token is used for all the Dashboard operations except for Conversation API and Message API operations.

<figure><img src="https://2934665269-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LpXFTiTgns4Ml77XGi3%2Fuploads%2FtlqbwerzUaWumz25sZEG%2FScreenshot%2029-10-2025%20at%2016.42%20(1).png?alt=media&#x26;token=1ec76c5e-690a-4662-a754-444f28b455ef" alt=""><figcaption></figcaption></figure>