Skip to main content
The Admin Console is Neuroncx AI’s system-level configuration hub, giving platform administrators granular control over automation logic, external integrations, scheduling rules, data pipelines, and notification behaviour. It sits intentionally behind a layer of access restriction because changes made here affect the entire platform — not just a single team member’s view or a single conversation thread. Understanding each component before you make changes is essential to keeping your deployment stable and your data consistent.
The Admin Console is intended for advanced configuration and is typically accessed by platform administrators or the Neuroncx AI implementation team. Incorrect settings can alter automation behaviour, disrupt integrations, or affect data routing across the entire platform. If you are unsure about a setting, contact support@neuroncx.in before making changes.

​
Accessing the Admin Console

Log in to your Neuroncx AI dashboard at https://dash.neuroncx.in and navigate to Admin Console from the main sidebar. You will see a list of configuration panels, each covering a distinct area of platform behaviour. The sections below describe each panel and how to use it.

​
View Cluster List

Clusters are logical groupings of audiences, locations, departments, or operational units that Neuroncx AI uses to segment transaction routing, reporting, and automation. For example, a healthcare organisation might define clusters for each hospital branch, while an enterprise might cluster by product line or sales territory. The View Cluster List panel lets you review all currently defined clusters, check their associated attributes, and manage membership rules. Use this panel to:
  • Audit which clusters exist and what criteria define them
  • Identify clusters that are no longer in use and can be retired
  • Confirm that new leads or transactions are being assigned to the correct cluster based on their attributes
If transactions are routing to the wrong team or appearing in the wrong reporting segment, the first place to check is the cluster assignment logic in this panel. A mismatch between an attribute value on incoming transactions and the expected cluster filter is the most common cause.

​
Auto Trigger / User Journey

Auto Triggers define the automation rules that fire when a user reaches a specific point in a workflow, submits a form, or meets a combination of attribute conditions. Together, these triggers compose the User Journey — the sequence of automated actions Neuroncx AI takes on behalf of your team as a lead or patient moves through your engagement funnel. From this panel you can:
  • Create new triggers tied to form submissions, attribute changes, or stage transitions
  • Set conditions (e.g., fire only if channel = WhatsApp AND stage = New) to avoid over-triggering
  • Chain triggers to build multi-step user journeys — for example, send an appointment confirmation message, wait 24 hours, then send a reminder if the appointment has not been confirmed
  • Enable or disable individual triggers without deleting them, which is useful when testing changes in a live environment
Auto Triggers respect the channel and audience filters you set. If a trigger appears to be firing unexpectedly or not firing at all, open the trigger definition and verify that the conditions match the attribute values present on the transactions you are targeting.

​
Third-Party Integration

The Third-Party Integration panel is where you configure API-based connections between Neuroncx AI and external platforms. This includes CRMs such as Salesforce or HubSpot, Hospital Information Systems (HIS), Electronic Medical Records (EMR) platforms, payment gateways, and any other system your organisation accesses via a REST or SOAP API. Each integration entry in this panel stores:
  • The external API endpoint URL
  • Authentication credentials (API key, OAuth tokens, or basic auth — stored encrypted)
  • Data mapping rules that translate Neuroncx AI fields to the external system’s schema
  • The trigger conditions under which the integration fires
You can view the status of recent outbound API calls from this panel, including HTTP response codes and timestamps, which helps you identify delivery failures quickly. For a full walkthrough of setting up a new integration, see the Third-Party APIs guide.

​
All Cron Tasks

Cron tasks are scheduled background jobs that run automatically at defined intervals. Neuroncx AI uses cron tasks for a range of housekeeping and automation functions — examples include syncing data to an external data lake, running periodic lead scoring calculations, triggering batch messaging campaigns, and refreshing dashboard metric aggregates. The All Cron Tasks panel gives you a complete view of every scheduled task in your deployment:
  • Task name and description — what the job does
  • Schedule expression — the cron schedule (e.g., 0 9 * * 1 for every Monday at 09:00)
  • Last run time and status — whether the most recent execution succeeded or failed
  • Next scheduled run — so you can plan around it
From this panel you can pause, resume, or manually trigger a cron task. If a task has been failing repeatedly, the failure reason is logged alongside the task entry.
Pausing a cron task that feeds data to an external system or drives campaign delivery can cause data inconsistencies or missed communications. Always verify the downstream impact before disabling a task, and re-enable it as soon as your maintenance window closes.

​
Admission Schedule / Calendar Schedule

For healthcare deployments, the Admission Schedule (also referred to as the Calendar Schedule) defines the operating rules that govern when appointments, admissions, or consultation slots are available. Neuroncx AI uses these rules to control bot availability, slot allocation in booking flows, and capacity management for individual clinics or consultants. Configuration options in this panel include:
  • Working hours — define the days and time ranges during which a clinic or bot accepts bookings
  • Slot duration and capacity — set how long each appointment slot runs and how many concurrent bookings are permitted
  • Blackout dates — mark public holidays, maintenance windows, or planned closures so the booking flow does not offer unavailable slots
  • Calendar linking — connect the schedule to a specific channel or consultant profile so availability rules apply only to the relevant context
If patients or users are receiving confirmation messages for slots that are actually unavailable, review the calendar schedule for the affected clinic or bot. Overlapping rules or an incorrect timezone setting are frequent causes of booking conflicts.

​
External Data Lake JSON View

When Neuroncx AI is configured to push transaction data or event logs to an external data warehouse or data lake, the External Data Lake JSON View panel lets you inspect the raw JSON payloads that have been sent. This is primarily a diagnostic and validation tool — it helps you confirm that the data leaving Neuroncx AI matches the schema your data engineering team expects. Use this panel to:
  • Preview the JSON structure of recent outbound records
  • Validate that all required fields are present and correctly typed before a new pipeline goes live
  • Diagnose schema drift if a downstream query or dashboard breaks after a Neuroncx AI update
  • Cross-check event timestamps and identifiers against records in your data warehouse
This panel provides a read-only view of outbound data. It does not allow you to edit or resend records. If you need to replay a failed delivery, contact support@neuroncx.in.

​
Alerts, Flags, and Modular Tile Settings

This panel consolidates three related configuration areas:

​
Alerts

Define the conditions under which Neuroncx AI raises a system alert visible on the dashboard’s Critical Alerts tile. You can set thresholds — for example, alert when a WhatsApp channel’s quality score drops below a defined level, or when the number of unresolved transactions in a cluster exceeds a set count. Each alert can be configured to notify specific users via the dashboard notification system.

​
Flags

Behavioural flags are boolean switches that modify how Neuroncx AI processes certain events. Examples include flags that enable or disable specific routing rules, activate experimental features for a subset of users, or override default stage-transition logic for a particular channel. Flags are typically set during the implementation phase and should only be changed with guidance from the Neuroncx AI team.

​
Modular Tile Settings

The Neuroncx AI dashboard surface is composed of configurable tiles. The Modular Tile Settings section lets you control which tiles appear, their order, and the data sources they pull from. You can tailor the dashboard layout for different roles — for example, showing the appointment funnel tile prominently for clinical coordinators while surfacing the lead pipeline tile for sales managers.

​
Initialize

The Initialize function triggers a controlled reset or re-bootstrapping sequence for your Neuroncx AI environment. It is used in two main scenarios:
  1. Environment setup — after a new deployment or major configuration change, Initialize ensures all base workflows, default routing rules, and system defaults are applied correctly
  2. Reset after misconfiguration — if experimental changes to triggers or flags have produced unexpected platform behaviour, Initialize can restore the baseline configuration without requiring a full redeployment
Running Initialize in a live production environment will reset certain base configurations and may temporarily interrupt automation workflows. This function should only be used during a planned maintenance window or at the explicit direction of the Neuroncx AI implementation team. Always take a configuration backup — via the support team — before proceeding.
If you believe an Initialize is necessary, contact support@neuroncx.in first so the team can guide you through the process and confirm that a backup of your current configuration is in place.