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

# Support

> How to get help with Narrative SDK integration issues.

Use this page after you have worked through the self-service resources and still need help with a Narrative SDK integration issue.

## Self-service resources

<Cards cols={2}>
  <Card title="Troubleshooting" href="/sdk/troubleshooting">
    Start with common integration failures and step-by-step fixes.
  </Card>

  <Card title="FAQ" href="/sdk/faq">
    Review common implementation, authentication, and runtime questions.
  </Card>

  <Card title="SDK integration" href="/sdk/integration">
    Follow the end-to-end implementation path from loader setup to widget boot.
  </Card>

  <Card title="Configuration reference" href="/sdk/configuration">
    Check required token claims, runtime fields, and backend configuration details.
  </Card>
</Cards>

## Before you contact us

* Checked the [Troubleshooting](/sdk/troubleshooting) guide for the issue you are seeing
* Verified token claims such as `iss`, `aud`, `iat`, `exp`, and `jti`
* Checked browser console and network requests for script, CSP, iframe, or token-route failures
* Confirmed that `nsdk-loader.js` loads from the expected SDK origin
* Retested with a fresh Embed Token minted for the current authenticated tenant user
* Confirmed which product area is affected: Coach, Money, Growth, onboarding, or bank connection
* Noted whether the issue happens immediately after onboarding or after a provider connection

## What to include in a support request

<AccordionGroup>
  <Accordion title="Request and error context">
    Include any `request_id` returned in an error response, the exact error message shown in the UI or console, and the approximate time the issue occurred.
  </Accordion>

  <Accordion title="Embed Token details">
    Locally decode the JWT and share only the specific claims relevant to debugging, such as `iss`, `sub`, `aud`, `iat`, `exp`, and `jti`. Never send the raw Embed Token, the raw JWT, or your Connected App secret.
  </Accordion>

  <Accordion title="Browser evidence">
    Include browser console errors, network failures, and screenshots or copied text that show what happened during loader, iframe, or token-route execution.
  </Accordion>

  <Accordion title="Steps to reproduce">
    Describe the exact user flow, page, and actions required to reproduce the problem, including whether it happens consistently or only in specific tenant-user scenarios.
  </Accordion>

  <Accordion title="Environment details">
    Include browser name and version, frontend framework, relevant host application details, and the SDK version or deployment environment you are using.
  </Accordion>

  <Accordion title="Product area and data source">
    Tell us whether the issue affects Coach, Money, Growth, onboarding, or bank connection. For data freshness questions, include when the connection or onboarding step completed.
  </Accordion>
</AccordionGroup>

## Escalation path

Start with self-service before contacting support:

* Check [Troubleshooting](/sdk/troubleshooting)
* Check [FAQ](/sdk/faq)
* Verify token claims, environment configuration, browser console output, and network requests

If the issue remains unresolved, email [support@narrativebanking.com](mailto:support@narrativebanking.com) with:

* Issue summary
* Reproduction steps
* Approximate timestamp
* Error message or request ID
* Browser and environment details
* Product area and connected data source, if relevant

## Contact

* Email: [support@narrativebanking.com](mailto:support@narrativebanking.com)