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

# HTML to Image

> Connect DialNexa calls to HTML to Image for record, request, case, lookup, approval, workflow run, or operational task workflows.

HTML to Image is a service that converts HTML and CSS into images or captures screenshots of web pages.

<Note>
  Use HTML to Image with DialNexa when the call creates a specialized follow-up that needs owner, urgency, and clear operational context.
</Note>

## Where HTML to Image fits in a DialNexa workflow

HTML to Image should receive DialNexa output when the conversation affects a record, request, case, lookup, approval, workflow run, or operational 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 niche requests" icon="check-circle">
    Send specialized calls to the person who knows the system, product, policy, or customer context.
  </Card>

  <Card title="Build review queues" icon="check-circle">
    Hold unclear, sensitive, high-value, or low-confidence cases for human review.
  </Card>

  <Card title="Measure recurring issues" icon="check-circle">
    Tag repeated call reasons so operations can see where customers keep getting stuck.
  </Card>

  <Card title="Create structured handoffs" icon="check-circle">
    Capture caller identity, request, affected object, owner, urgency, and decision needed.
  </Card>
</CardGroup>

## What DialNexa should capture for HTML to Image

* Caller identity, account, source, owner, category, urgency, and related object ID
* Call summary, requested outcome, missing information, blocker, and promised next step
* Status, priority, deadline, approval requirement, duplicate key, and review reason
* Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and file links
* Sensitive-data flag and routing note for human review

## High-value HTML to Image workflows

<AccordionGroup>
  <Accordion title="Customer promise needs tracking">
    For this workflow, DialNexa should send HTML to Image 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="Low-confidence match needs review">
    For this workflow, DialNexa should send HTML to Image 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="Owner should be alerted quickly">
    For this workflow, DialNexa should send HTML to Image 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 creates an operational request">
    For this workflow, DialNexa should send HTML to Image 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="Specialist review is required">
    For this workflow, DialNexa should send HTML to Image 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="Missing information blocks progress">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in HTML to Image. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Approval is needed before action">
    For this workflow, DialNexa should send HTML to Image 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="Recurring issue should be categorized">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into HTML to Image. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Use get html to image">
    Use get html to image before answering, routing, or creating follow-up. DialNexa should verify the lookup result against the caller and send low-confidence matches to a human queue.
  </Accordion>

  <Accordion title="Use check html to image account usage">
    Use check html to image account usage 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 HTML to Image with other integrations

* [HTML to Image](/integrations/html_to_image) + [Google Docs](/integrations/googledocs): Google Docs for operational briefs.
* [HTML to Image](/integrations/html_to_image) + [Gmail](/integrations/gmail): Gmail for approved customer follow-up.
* [HTML to Image](/integrations/html_to_image) + [Google Calendar](/integrations/googlecalendar): Google Calendar for scheduled callbacks.
* [HTML to Image](/integrations/html_to_image) + [HubSpot](/integrations/hubspot): HubSpot for customer context.
* [HTML to Image](/integrations/html_to_image) + [Slack](/integrations/slack): Slack for owner alerts.
* [HTML to Image](/integrations/html_to_image) + [Google Sheets](/integrations/googlesheets): Google Sheets for review queues.
* [HTML to Image](/integrations/html_to_image) + [Zendesk](/integrations/zendesk): Zendesk for support follow-up.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running HTML to Image actions.
* Write a short operational summary into HTML to Image 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 makes a task actionable?">
    A clear title, customer context, acceptance criteria, owner, deadline, evidence links, and next step.
  </Accordion>

  <Accordion title="How should promises be tracked?">
    Capture who promised what, to whom, by when, and where the customer should get the update.
  </Accordion>

  <Accordion title="When should a call become a project brief?">
    When the conversation includes background, constraints, files, decisions, and multiple follow-up steps.
  </Accordion>

  <Accordion title="How do teams avoid task spam?">
    Create tasks only for actionable work. Tag informational calls and resolved questions without opening work items.
  </Accordion>

  <Accordion title="What should be linked?">
    Transcript, recording, CRM account, support ticket, files, calendar event, and downstream task URL.
  </Accordion>

  <Accordion title="When should managers be notified?">
    Notify managers for blocked work, VIP customers, missed commitments, urgent deadlines, or repeated operational issues.
  </Accordion>

  <Accordion title="How should completed work close the loop?">
    Update the task, notify the owner, and trigger the customer-facing follow-up that was promised on the call.
  </Accordion>
</AccordionGroup>