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

# Bolt Iot

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

Bolt IoT is an integrated platform that enables users to build IoT projects by connecting sensors and actuators to the internet, offering cloud-based control and monitoring capabilities.

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

## Where Bolt Iot fits in a DialNexa workflow

Bolt Iot 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="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>

  <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>
</CardGroup>

## What DialNexa should capture for Bolt Iot

* 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 Bolt Iot workflows

<AccordionGroup>
  <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 Bolt Iot. 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 Bolt Iot. 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 Bolt Iot. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Reviewer needs a structured exception note">
    For this workflow, DialNexa should send Bolt Iot 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 Bolt Iot. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Use analog read">
    Use analog read when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.
  </Accordion>

  <Accordion title="Use bolt iot digital write">
    Use bolt iot digital write when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.
  </Accordion>
</AccordionGroup>

## Workflows that pair Bolt Iot with other integrations

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

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Bolt Iot actions.
* Write a short operational summary into Bolt Iot 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="Can DialNexa generate PDFs after calls?">
    Yes for approved templates such as confirmations, quotes, or summaries. Use review for legal, billing, or high-value documents.
  </Accordion>

  <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>
</AccordionGroup>