> ## 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.

# SMS Alert

> Connect DialNexa calls to SMS Alert for file, document, folder, form submission, PDF, extracted field, signature request, or review task workflows.

SMS Alert is a versatile multi-channel communication platform enabling businesses to engage with customers through SMS, RCS, Telegram, and WhatsApp via a unified REST API.

<Note>
  Use SMS Alert with DialNexa when the call depends on a file, form, PDF, signature, contract, storage folder, or document review.
</Note>

## Where SMS Alert fits in a DialNexa workflow

SMS Alert should receive DialNexa output when the conversation affects a file, document, folder, form submission, PDF, extracted field, signature request, or review task. 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="Route signature blockers" icon="check-circle">
    Record who needs to sign, what term is disputed, what changed, and whether legal or finance must review.
  </Card>

  <Card title="Store evidence correctly" icon="check-circle">
    Keep recordings, transcripts, generated PDFs, and signed documents beside the customer or case record.
  </Card>

  <Card title="Prepare document handoffs" icon="check-circle">
    Capture document type, owner, missing fields, requested change, deadline, and approval path.
  </Card>

  <Card title="Extract or verify fields" icon="check-circle">
    Compare caller statements with parsed invoice, ID, contract, form, or PDF data before approval.
  </Card>
</CardGroup>

## What DialNexa should capture for SMS Alert

* Caller, account, document type, file link, folder path, submission ID, signer, and permission level
* Requested change, extracted fields, missing fields, signer details, deadline, and approval owner
* Exception reason, document version, customer expectation, and promised next step
* Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and storage folder link
* Redaction, retention, access, and sensitive-document flags

## High-value SMS Alert workflows

<AccordionGroup>
  <Accordion title="Form submission needs missing fields">
    For this workflow, DialNexa should confirm location details, access notes, timing constraints, and the operational owner before updating SMS Alert. Low-confidence addresses or risky visits should go to review.
  </Accordion>

  <Accordion title="Invoice or ID text must be extracted">
    Use SMS Alert 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="Signature request is blocked">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in SMS Alert. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Customer sends a file as evidence">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in SMS Alert. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Document should be stored with a case">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in SMS Alert. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Reviewer needs a structured exception note">
    For this workflow, DialNexa should send SMS Alert 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="Caller asks for a document resend">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in SMS Alert. Sensitive files should stay behind restricted links.
  </Accordion>

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

  <Accordion title="Use send sms via xml">
    Use send sms via xml only after DialNexa confirms recipient, consent, channel, message purpose, and the exact follow-up promised during the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair SMS Alert with other integrations

* [SMS Alert](/integrations/sms_alert) + [HubSpot](/integrations/hubspot): HubSpot for account and deal context.
* [SMS Alert](/integrations/sms_alert) + [Slack](/integrations/slack): Slack for approval alerts.
* [SMS Alert](/integrations/sms_alert) + [Gmail](/integrations/gmail): Gmail for approved document delivery.
* [SMS Alert](/integrations/sms_alert) + [Zendesk](/integrations/zendesk): Zendesk for support cases tied to documents.
* [SMS Alert](/integrations/sms_alert) + [Google Sheets](/integrations/googlesheets): Google Sheets for extracted-field review.
* [SMS Alert](/integrations/sms_alert) + [QuickBooks](/integrations/quickbooks): QuickBooks for invoice-related documents.
* [SMS Alert](/integrations/sms_alert) + [Google Drive](/integrations/googledrive): Google Drive for storing files and evidence.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running SMS Alert actions.
* Write a short operational summary into SMS Alert 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="What stays private?">
    IDs, contracts, tax documents, payment images, private health or HR files, and full recordings.
  </Accordion>

  <Accordion title="How should document resends work?">
    Verify recipient, document type, and permission before sending. Log what was sent and why.
  </Accordion>

  <Accordion title="What should reviewers see first?">
    The document link, caller explanation, missing or disputed fields, requested outcome, owner, and transcript link.
  </Accordion>

  <Accordion title="Should DialNexa paste full documents into notes?">
    No. Store links, extracted fields, and why the document matters. Keep sensitive files in controlled storage.
  </Accordion>

  <Accordion title="When should a document go to review?">
    Missing fields, low-confidence extraction, signature blockers, legal language, identity files, and money-related changes should go to review.
  </Accordion>

  <Accordion title="What should be captured for signatures?">
    Signer, role, email, agreed terms, disputed terms, deadline, approval owner, and transcript link.
  </Accordion>

  <Accordion title="How are duplicate documents avoided?">
    Match by customer, file ID, document type, version, case, destination folder, and call ID.
  </Accordion>
</AccordionGroup>