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

# Moco

> Connect DialNexa calls to Moco for task, project, checklist, workspace note, time entry, decision, or internal handoff workflows.

MOCO is a business management software offering project management, time tracking, and invoicing solutions.

<Note>
  Use Moco with DialNexa when a conversation creates work that needs an owner, deadline, context, and evidence.
</Note>

## Where Moco fits in a DialNexa workflow

Moco should receive DialNexa output when the conversation affects a task, project, checklist, workspace note, time entry, decision, or internal handoff. 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="Track promises" icon="check-circle">
    Record callbacks, fixes, quotes, designs, documents, and follow-ups promised during the call.
  </Card>

  <Card title="Escalate blockers" icon="check-circle">
    Flag missing approvals, legal review, customer input, dependencies, or urgent deadlines.
  </Card>

  <Card title="Create actionable tasks" icon="check-circle">
    Turn caller requests into title, owner, priority, due date, acceptance criteria, and visible outcome.
  </Card>

  <Card title="Write better briefs" icon="check-circle">
    Summarize background, decision, constraints, open questions, files, and why the work matters.
  </Card>
</CardGroup>

## What DialNexa should capture for Moco

* Requester, customer, account, project, workspace, owner, priority, due date, and team
* Summary, requested outcome, acceptance criteria, blocker, risk, and promised next step
* Labels, status, board, sprint, section, checklist, dependency, approval owner, and time estimate
* Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and file links
* Review state, escalation reason, and customer-visible update

## High-value Moco workflows

<AccordionGroup>
  <Accordion title="Internal team needs a project brief">
    For this workflow, DialNexa should send Moco 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="Blocked work needs escalation">
    For this scenario, DialNexa should treat Moco 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="Design or document request comes from a call">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Moco. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Manager wants visibility into call-driven work">
    For this workflow, DialNexa should send Moco 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-facing deadline changes">
    DialNexa should send Moco the source, consent state, call outcome, audience impact, and suppression or enrollment decision. The goal is better targeting, not another generic campaign touch.
  </Accordion>

  <Accordion title="Task should link to ticket or deal">
    In Moco, 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="Call creates an implementation task">
    For this workflow, DialNexa should send Moco 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 invoice payment">
    Use create invoice payment only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new work item. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

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

## Workflows that pair Moco with other integrations

* [Moco](/integrations/moco) + [Google Docs](/integrations/googledocs): Google Docs for long briefs.
* [Moco](/integrations/moco) + [Zendesk](/integrations/zendesk): Zendesk for customer support linkage.
* [Moco](/integrations/moco) + [Google Calendar](/integrations/googlecalendar): Google Calendar for follow-up commitments.
* [Moco](/integrations/moco) + [Jira](/integrations/jira): Jira for engineering tasks.
* [Moco](/integrations/moco) + [Google Drive](/integrations/googledrive): Google Drive for files and recordings.
* [Moco](/integrations/moco) + [Notion](/integrations/notion): Notion for knowledge and playbooks.
* [Moco](/integrations/moco) + [HubSpot](/integrations/hubspot): HubSpot for account and deal context.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Moco actions.
* Write a short operational summary into Moco 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="Should DialNexa create tasks automatically?">
    Yes when owner, outcome, and due date are clear. Use review for vague, sensitive, or high-value commitments.
  </Accordion>

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