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

# Cloudcart

> Connect DialNexa calls to Cloudcart for order, product, customer profile, booking, return, shipment, cart, or reservation workflows.

CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently.

<Note>
  Use Cloudcart with DialNexa when a shopper or guest asks about a transaction, product, delivery, booking, availability, return, or purchase decision.
</Note>

## Where Cloudcart fits in a DialNexa workflow

Cloudcart should receive DialNexa output when the conversation affects a order, product, customer profile, booking, return, shipment, cart, or reservation. 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="Inform operations" icon="check-circle">
    Send urgency, location, item details, and promised next step to the team that can fix the issue.
  </Card>

  <Card title="Find the transaction" icon="check-circle">
    Match the caller to the order, booking, SKU, pickup, shipment, or reservation before any workflow runs.
  </Card>

  <Card title="Handle exceptions" icon="check-circle">
    Capture return reason, refund expectation, address change, delivery deadline, missing item, or booking constraint.
  </Card>

  <Card title="Recover buying intent" icon="check-circle">
    Route callers asking about price, availability, fit, stock, delivery time, or package options.
  </Card>
</CardGroup>

## What DialNexa should capture for Cloudcart

* Customer name, phone, email, order ID, product SKU, booking ID, store, channel, and location
* Requested action, delivery status, availability question, return reason, refund expectation, and deadline
* VIP status, order value, loyalty status, repeat complaint, and escalation owner
* Transcript link, recording link, DialNexa call ID, payment link, support link, and fulfillment link
* Risk flags for wrong address, damaged item, fraud concern, urgent travel, or no-show risk

## High-value Cloudcart workflows

<AccordionGroup>
  <Accordion title="High-intent buyer asks about availability">
    In Cloudcart, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
  </Accordion>

  <Accordion title="Booking needs to be rescheduled">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Cloudcart. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Return request needs policy review">
    For this workflow, DialNexa should send Cloudcart 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="VIP customer asks for priority handling">
    For this scenario, DialNexa should treat Cloudcart 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="Abandoned cart caller wants reassurance">
    For this workflow, DialNexa should send Cloudcart 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="Customer asks where an order is">
    For this workflow, DialNexa should send Cloudcart 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="Use create subscriber channel">
    Use create subscriber channel only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new commerce record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

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

## Workflows that pair Cloudcart with other integrations

* [Cloudcart](/integrations/cloudcart) + [Klaviyo](/integrations/klaviyo): Klaviyo for product-specific follow-up.
* [Cloudcart](/integrations/cloudcart) + [Slack](/integrations/slack): Slack for operations alerts.
* [Cloudcart](/integrations/cloudcart) + [Google Sheets](/integrations/googlesheets): Google Sheets for returns review queues.
* [Cloudcart](/integrations/cloudcart) + [Google Calendar](/integrations/googlecalendar): Google Calendar for booking changes.
* [Cloudcart](/integrations/cloudcart) + [HubSpot](/integrations/hubspot): HubSpot for high-value customer context.
* [Cloudcart](/integrations/cloudcart) + [Shopify](/integrations/shopify): Shopify for storefront order context.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Cloudcart actions.
* Write a short operational summary into Cloudcart 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 happens after a booking change?">
    Update the booking or calendar, send confirmation, log the reason, and notify operations if capacity or timing is tight.
  </Accordion>

  <Accordion title="How do you avoid acting on the wrong order?">
    Verify identity and match order ID, phone, email, product, and recent activity before making changes.
  </Accordion>

  <Accordion title="What should be sent to marketing afterward?">
    Only safe lifecycle signals such as product interest, return outcome, or follow-up need. Do not send sensitive support details.
  </Accordion>

  <Accordion title="Should DialNexa change orders automatically?">
    Only for low-risk changes with clear identity and policy rules. Address changes, refunds, cancellations, and substitutions often need review.
  </Accordion>

  <Accordion title="What order data should be checked first?">
    Customer match, order ID, fulfillment status, payment status, delivery promise, prior support notes, and return eligibility.
  </Accordion>

  <Accordion title="How should damaged-item calls be handled?">
    Capture item, photo need, damage description, customer expectation, replacement or refund preference, and deadline.
  </Accordion>

  <Accordion title="Can DialNexa recover buying intent?">
    Yes. Route callers who ask about fit, availability, shipping, price, package options, or trust blockers while intent is fresh.
  </Accordion>
</AccordionGroup>