Existing-customer correspondence

Create a CRM task from a sent letter

Follow this guide to open the native task modal with the letter ID as the related record. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Sent Letters History → Create Task icon

Before you start

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What you’ll accomplish

Open the native task modal with the letter ID as the related record. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Find the letter.
Select the green task icon.
Complete the native task form, assignees, due date and description.
Save the task.
Go to the task and verify its relation information.

Fields and options to review

Action scopeOpen the native task modal with the letter ID as the related record.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Create Task icon

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules the system enforces

The JavaScript calls new_task with rel_id={letter_id} and rel_type=letter.
The module does not register a separate letter relation renderer in the supplied files; verify how the host CRM displays the relation.
If the native new_task function is unavailable, the page shows Task function unavailable here.

How to confirm it worked

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.

Was this guide useful?Your response is stored only in this browser.