Existing-customer correspondence

Create a CRM task from a sent letter

Open the native task modal with the letter ID as the related record.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

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

Before you begin

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 this guide covers

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.

Exact step-by-step process

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

Fields, choices and supported possibilities

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.

Code-backed validations and workflow rules

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.

Expected result and verification

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.