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

# Project Bubble

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

ProProfs Project is a project management tool that helps teams plan, collaborate, and deliver projects efficiently.

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

## Where Project Bubble fits in a DialNexa workflow

Project Bubble 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 Project Bubble

* 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 Project Bubble workflows

<AccordionGroup>
  <Accordion title="Customer-facing deadline changes">
    DialNexa should send Project Bubble 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 Project Bubble, 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 Project Bubble 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 for a promised follow-up">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Project Bubble. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Internal team needs a project brief">
    For this workflow, DialNexa should send Project Bubble 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 Project Bubble 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 Project Bubble. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Use get record by id">
    Use get record by id 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 data api get objects">
    Use data api get objects 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>
</AccordionGroup>

## Workflows that pair Project Bubble with other integrations

* [Project Bubble](/integrations/project_bubble) + [Google Drive](/integrations/googledrive): Google Drive for files and recordings.
* [Project Bubble](/integrations/project_bubble) + [Notion](/integrations/notion): Notion for knowledge and playbooks.
* [Project Bubble](/integrations/project_bubble) + [HubSpot](/integrations/hubspot): HubSpot for account and deal context.
* [Project Bubble](/integrations/project_bubble) + [Slack](/integrations/slack): Slack for owner notification.
* [Project Bubble](/integrations/project_bubble) + [Google Docs](/integrations/googledocs): Google Docs for long briefs.
* [Project Bubble](/integrations/project_bubble) + [Zendesk](/integrations/zendesk): Zendesk for customer support linkage.
* [Project Bubble](/integrations/project_bubble) + [Google Calendar](/integrations/googlecalendar): Google Calendar for follow-up commitments.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Project Bubble actions.
* Write a short operational summary into Project Bubble 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="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>

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