Use PD Agreements reminders when a customer still owes a signature. Review the intended customer and request before sending: the pending list, individual send action and scheduled reminder selection do not have identical scope.

Review outstanding requests

Open PD Modules → Agreements → Awaiting signature. Check the customer and Not yet signed column, using the page navigation when needed.

This list includes applicable required agreements for active customers, including required on-demand documents. Agreements labelled At checkout can appear here because Blesta requests acceptance on a later account visit after ordering, rather than stopping checkout. An optional document does not become a required reminder simply because it is available to sign.

Send one customer a link

On the intended row, use Send signing link. The action sends a reminder email; it is not a preview or a copy-to-clipboard button. Check the result before sending again.

The reminder’s named document list is built from required On next login agreements. If you are helping with an on-demand or after-order request, confirm the actual outstanding item and signing destination separately. Do not assume the email names every item shown in the pending list.

The client profile’s Agreements row also offers Copy signing link for an outstanding request. Use that when you intend to share a link in an existing support conversation, after checking the recipient. Copying a link is separate from sending an email.

Understand the bulk action

Email everyone their signing link asks for confirmation before sending. Its recipients are selected from customers owing required On next login agreements. It is not restricted to the current page of the list, and it does not necessarily include every request type displayed there.

Review that scope before confirming. A sent result means the mail system accepted the message for delivery, not that the customer received, opened or signed it. Manual sends are not postponed by the automatic reminder interval; avoid accidental repeats.

Enable scheduled reminders

1. Open Agreements → Settings.
2. Review Email reminders automatically, which is off by default.
3. Set Days between reminders to the intended interval, then save the settings.
4. Check that the normal Blesta cron and the Agreement reminders job are running.

The automatic job uses the same required On next login selection. Its interval is measured from the previous module-wide reminder run, not separately from each customer’s first outstanding agreement. Do not expect a guaranteed first reminder one day after a particular customer becomes eligible.

Diagnose an absent reminder

Check the agreement’s published state, required flag, On next login trigger, audience and existing valid acceptance. Then check the licence, automatic-reminder switch, last job result, email delivery and PD Agreements Reminder email template.

An unsuccessful run can still advance the recorded reminder interval. Inspect the result before enabling repeated sends or changing the schedule. Your hosting team should retain the document/version reference, job result, original attempt time and redacted error while checking the request selection and delivery stage. Keep recipient addresses, customer records and private agreement text out of public screenshots.

Check reminder eligibility and delivery

Your hosting team should compare the published required On next login request, target match and existing acceptance with the automatic-reminder switch, licence, last Agreement reminders job result, module-wide interval and normal cron. Review the mail template and delivery result through your normal administrator controls; a sent result is not proof of delivery or signing. Manual sends and the pending list have the different scopes described above. Do not repeatedly email customers to test delivery.

See the PD Agreements Blesta guide for related tasks, or explore PD Agreements.