> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuroncx.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Neuroncx AI Frequently Asked Questions

> Answers to the most common questions about logging in, managing leads, messaging channels, workflows, and AI configuration on the Neuroncx AI platform.

Whether you are just getting started with Neuroncx AI or running into a specific behaviour you want to understand better, this page collects the questions we hear most often — along with clear, actionable answers. Browse by category or use your browser's find function (Ctrl+F / Cmd+F) to jump straight to the topic you need.

## Channels & Transactions

> [accordion] How do I set up a new source so I can track where a transaction came from (e.g. a new phone number or ad campaign)?
>
> You can create a **channel source** — a labeled origin point like WhatsApp, Phone, Web Ads, or a custom integration — and attach it to your transaction pipeline so it shows up correctly in the Transactions Console.
>
> This is configured under **Channels → Settings → Transaction Rules & Policies**, and involves three steps: creating the source, attaching it to a webhook with an exam rule, and verifying it in the Transactions Console.
>
> Full walkthrough: [Creating a Channel Source for Transaction](https://docs.neuroncx.in/getting-started/channels/settings.md#creating-a-channel-source-for-transaction)

> [accordion] How do I find leads with a failed payment and check why the payment failed?
>
> `PY_FAILED` is an order status that flags leads where a payment was attempted but did not complete — for example, due to an invalid card number, expired card, or a gateway error. There are two ways to investigate a failed payment.
>
> **Finding PY\_FAILED leads in the Transactions Console**
>
> 1. Go to **Transactions** from the left navigation.
> 2. In the filter bar, click **5 Orders** to expand the order status filters.
> 3. Select **PY\_FAILED**, then click **Apply Filter**.
> 4. The console now shows only leads with a failed payment.
>
> ***
>
> **Method 1 — Check the fail reason via the Orders tab**
>
> 1. Click the **expand icon (⤢)** to the left of the lead name to open the Lead Detail View.
> 2. Click the **Orders** tab at the top of the detail panel.
> 3. Under **Payment for Order #XXXXXX**, expand the **FAILED** entry.
> 4. The **Fail Reason** field shows the exact error returned by the payment gateway.
>
>    ![Method 2](https://mintcdn.com/neuroncx/vWDFi1kIl24WPXyL/images/method-2.png?fit=max\&auto=format\&n=vWDFi1kIl24WPXyL\&q=85\&s=357bf8c76a48597b8ef3882819a07302)
>
> ***
>
> **Method 2 — Check the full payment timeline via the Activity Log**
>
> 1. Click the **arrow (→)** to the right of the lead name in the Transactions Console.
> 2. This opens the Activity panel on the right.
> 3. Click the **Activity Type** dropdown and select **Payments**.
> 4. The log shows the complete payment sequence in order: `INITIATED` → `LINKGENERATED` → `FAILED` — with the failure reason and gateway details inline.
>
> ![Method 1](https://mintcdn.com/neuroncx/vWDFi1kIl24WPXyL/images/method_1.png?fit=max\&auto=format\&n=vWDFi1kIl24WPXyL\&q=85\&s=1508115e77d58bcc39893775dd3efec7)
>
> > [!NOTE]
> >
> > The Activity Log also captures discount adjustments and the exact payment gateway used (e.g. Razorpay), which is useful when escalating a payment issue to your finance or tech team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.