Skip to Help content

DiMarAg Hub · Public Help

General product guidance for agencies and clients. These guides are pending workflow validation; read each review notice. Access to account information and actions still requires sign-in and permission.

Open Help in a new tab
← All Help topics

Appointments and calls · 3 min read

Publish a call agreement and track the response

Turn the reviewed summary and tasks into a version the recipient can answer.

Pending workflow validation

This guide has been checked against the application code. Its workflow still needs validation in an isolated test account.

What you will achieve

Publish a verifiable agreement version, share it, and distinguish approval, corrections, and later tasks.

Before you start

  • A call for the correct client or lead, Activities edit permission, and an active relationship for a client.
  • An accurate summary, confirmed recipient and email, and reviewed tasks and responsibilities.

Steps

  1. 1. Review and finish the call

    Open its dossier, verify participants, date, and time zone, and finish the call if still active. Opening the workspace does not place a call or record audio. Finishing the call does not publish an agreement or complete follow-up tasks.

  2. 2. Prepare shared content

    Review each linked task, its responsible party, and whether it is shared or internal. An agency-responsibility task can be visible when explicitly shared. Save the recipient name, email, and agreement summary; verify the saved content before publishing.

  3. 3. Publish a version

    Use Publish when the call is finished and the summary saved. Check the version number and history snapshot. If an edit requires revision or the recipient requested changes, prepare and publish the corrected version; do not assume the previous version reflects edits.

  4. 4. Share the current link

    Open the version view and prepare its message with Operator. Check recipient, channel, language, and link before sending. Publishing or copying a link does not deliver it. Check the sending result and keep the shared version reference.

  5. 5. Track the response and tasks

    The recipient reviews the summary and tasks, enters name and email, and can accept with consent or request written corrections. Check status and history: pending, changes, or approved. A version needing revision blocks client actions; even after approval, completing each task is a separate action based on responsibility.

Expected result

A published agreement with version, delivery, and response checked separately. Approval does not prove deliverables were completed or a payment exists.

Questions about this process

Publish is disabled

Check permissions, a finished call, and a saved summary. If a current version already exists without pending changes, do not publish duplicates; check its state and history.

The recipient requests corrections or cannot act

Review comments, email, and current version. Correct the content and publish the required revision before sharing. Do not mark tasks complete or accept on the recipient’s behalf to resolve the block.

Continue learning

Related questions

To report a problem, include the section, steps, and exact message. Screenshots must not include passwords, payment-card data, or complete private links.