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

# Supabase

> Connect DialNexa calls to Supabase for charge, invoice, customer balance, subscription, refund, receipt, or finance approval workflows.

Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications.

<Note>
  Use Supabase with DialNexa when the call involves money, billing trust, refunds, payment status, subscriptions, taxes, or invoice documents.
</Note>

## Where Supabase fits in a DialNexa workflow

Supabase should receive DialNexa output when the conversation affects a charge, invoice, customer balance, subscription, refund, receipt, or finance approval. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

<CardGroup cols={2}>
  <Card title="Resolve billing questions" icon="check-circle">
    Identify the invoice, charge, customer, amount, due date, and what the caller believes is wrong.
  </Card>

  <Card title="Route refunds and disputes" icon="check-circle">
    Capture reason, policy context, amount, order or subscription link, and approval requirement.
  </Card>

  <Card title="Send documents safely" icon="check-circle">
    Verify the recipient before resending invoices, receipts, statements, tax forms, or payment links.
  </Card>

  <Card title="Protect revenue workflows" icon="check-circle">
    Escalate VIP payment blockers, failed renewals, duplicate charges, and collections-sensitive calls.
  </Card>
</CardGroup>

## What DialNexa should capture for Supabase

* Customer, account, email, phone, invoice number, payment ID, subscription ID, and tax region
* Amount, currency, due date, payment status, refund reason, dispute reason, and credit request
* Approval threshold, finance owner, escalation reason, promised next step, and follow-up deadline
* Transcript link, recording link, DialNexa call ID, CRM link, support ticket, and payment platform link
* Suppression flag for card numbers, bank details, tax identifiers, and private billing documents

## High-value Supabase workflows

<AccordionGroup>
  <Accordion title="Tax or billing address must be corrected">
    Use Supabase to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="VIP customer has a payment blocker">
    For this scenario, DialNexa should treat Supabase as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
  </Accordion>

  <Accordion title="Collections call requires careful notes">
    For this workflow, DialNexa should send Supabase a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Receipt needs to go to a verified email">
    Use Supabase to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Caller disputes a charge">
    Use Supabase to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Use create new project">
    Use create new project only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new finance record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

  <Accordion title="Use update a project">
    Use update a project when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Supabase record. Include the old value, new value, and reason from the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair Supabase with other integrations

* [Supabase](/integrations/supabase) + [Slack](/integrations/slack): Slack for urgent finance approvals.
* [Supabase](/integrations/supabase) + [Zendesk](/integrations/zendesk): Zendesk for customer-facing billing tickets.
* [Supabase](/integrations/supabase) + [Google Drive](/integrations/googledrive): Google Drive for storing invoices and credit notes.
* [Supabase](/integrations/supabase) + [Google Sheets](/integrations/googlesheets): Google Sheets for exception review queues.
* [Supabase](/integrations/supabase) + [Stripe](/integrations/stripe): Stripe for payment and subscription status.
* [Supabase](/integrations/supabase) + [QuickBooks](/integrations/quickbooks): QuickBooks for accounting records.
* [Supabase](/integrations/supabase) + [HubSpot](/integrations/hubspot): HubSpot for account owner and renewal context.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Supabase actions.
* Write a short operational summary into Supabase and link to the full transcript or recording for audit.
* Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
* Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

## FAQs

<AccordionGroup>
  <Accordion title="How are disputes handled?">
    Capture dispute reason, transaction reference, subscription or order link, urgency, and whether the caller expects a callback.
  </Accordion>

  <Accordion title="Where should tax details live?">
    Use the billing or accounting system with the right access controls, not broad CRM or support notes.
  </Accordion>

  <Accordion title="When should Slack alert finance?">
    Alert finance for VIP payment blockers, duplicate charges, chargebacks, urgent renewal failures, or exceptions needing approval.
  </Accordion>

  <Accordion title="How should collections calls be logged?">
    Keep tone factual, note promises made, avoid sensitive payment details, and link the call to the account balance or invoice.
  </Accordion>

  <Accordion title="Should DialNexa collect payment details?">
    No. Do not capture full card numbers, bank details, or private tax identifiers in notes. Route customers to secure payment flows.
  </Accordion>

  <Accordion title="When can refunds be automated?">
    Only when identity, policy, amount, and approval rules are clear. Route exceptions, high-value refunds, and disputes to finance review.
  </Accordion>
</AccordionGroup>