How to create and review a batch

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

This guide explains how issuers create and review a batch in Namirial Notify. The screenshots illustrate the current New EviNotice Batch flow, but the overall wizard pattern is used as the reference example because the process is similar for other services that support batch sending.

Prerequisites

• You are signed in as an issuer.
• Batch sending is enabled for your environment and account.
• You are creating a batch for EviNotice, EviMail, or EviSMS.
• You have the batch description, content, recipient data, and scheduling information ready.
• If you want to add recipients from saved contacts, your contact list is available in Contacts.

Supported services and differences

Batch sending is available for EviNotice, EviMail, and EviSMS. EviSign and EviPost are handled through their individual creation flows in this guide set.

The wizard pattern is similar across supported batch services, but some fields differ:

Open a new batch

1. Sign in to Namirial Notify.
2. In NEW SUBMISSION, open the area for the service you want to use in the batch.
3. Select the option to create a new batch.
4. In the screenshots used for this guide, this opens New EviNotice Batch.

After the wizard opens, complete each step in sequence.

Complete the Description step

1. Open Description.
2. Enter a value in Description.
3. Click Create.

Use a description that makes the batch easy to identify later in the batch list.

Complete the Content step

1. Open Content.
2. Enter the Subject.
3. Enter the message body in the rich-text editor.
4. Use dynamic variables if you want to personalize the content for each recipient.
5. Add shared files in Attachments if needed.
6. Click Next.

Key points in this step:

• The screen text explains that the subject and body can use dynamic variables, including system variables and user variables.
• The editor supports formatted content and can include HTML elements such as links and images.
• Files added in Attachments are shared with the batch content configured in this step.
• For EviSMS batches, the content is the message text rather than a subject plus rich-text body.

Complete the Recipients step

1. Open Recipients.
2. Select the Delivery channel for the notification.
3. Choose how you want to add recipients.
4. Add the recipients using one of the available methods.
5. Click Next.

The screen shows these recipient-entry methods:

• Manual entry
• Using the contact list
• Add recipients using a CSV file

Key points in this step:

• The wizard text states that you first define the notification delivery channel, such as email or mobile.
• In Manual entry, recipients are entered in the text area using the indicated headers.
• In Using the contact list, recipients are selected from saved contacts.
• In Add recipients using a CSV file, recipients are loaded from a CSV file with the required structure.
• CSV imports use ; as the column separator.
• If needed, use the on-screen help referenced in this step.

For API and CSV-based batch imports, the required recipient columns depend on the service:

Extra columns prefixed with *, such as *orderid, can be used as custom fields and are stored as recipient extra data.

Complete the General step

1. Open General.
2. In Basics, select the Notification language.
3. Select the Appearance.
4. Set the Tracking period (minutes).
5. In Processing and Affidavits, select the Certification and security level.
6. Select the Affidavit Language.
7. Review the selected Affidavits.
8. In Agreement possibilities, select the agreement mode you want to use.
9. Decide whether to enable Comments are allowed.
10. Enter Reasons for acceptance if your process uses them.
11. Enter Reasons for rejection if your process uses them.
12. Decide whether to enable Reason for acceptance required.
13. Decide whether to enable Reason for rejection required.
14. Decide whether to enable Allow notification refusal.
15. Click Next.

Key points in this step:

• The screen says these are the basic features shared by all sends in the batch for the EviNotice example shown here.
• The selected certification level affects the default affidavits shown in the Affidavits cards.
• Agreement possibilities controls whether recipients can accept, reject, or do both in services that support recipient-interaction options.
• The comments and reason fields apply to the recipient interaction model used by the batch when those options are available.

For more detail on generated evidence and affidavit kinds, see Evidence and affidavits.

Complete the Advanced step

1. Open Advanced.
2. In Sender information, select Email to use as sender.
3. Enter Reply-To email header if replies should go to a specific mailbox.
4. Decide whether to enable Do not send the Sender header in notification emails.
5. In Filters for Push Notifications, enter Url for event notification if your process uses callbacks.
6. Decide whether to enable Enable push notifications.
7. Select the push-notification events you want to receive.
8. In Other data, select the Cost Centre.
9. Select the Notification template if your environment uses templates.
10. Click Next.

The push-notification filter list shown in the wizard includes these events:

• Processed
• Delivered
• Replied
• AffidavitPublished
• Sent
• Received
• Closed
• Dispatched
• Read
• Failed

Key points in this step:

• The screen states that these settings are shared by all shipments in the batch.
• The sender fields define how the batch notifications are sent.
• The callback URL and event filters are propagated to the evidences generated from the batch. They do not push the batch object's own lifecycle.
• Cost Centre and Notification template are shared settings applied across the batch.

Complete the Schedule step

1. Open Schedule.
2. Decide whether the batch should run immediately or at a specific date and time.
3. If you want to schedule it, set Schedule date and Sending time.
4. If you want immediate execution, enable Process now.
5. Click Finish.

The screen text explains that this final step is used to choose between immediate execution and scheduled execution.

Expected result

Namirial Notify creates the batch with the configured content, recipients, shared settings, and schedule. The batch is then ready to run immediately or at the selected time, according to the option chosen in the final step.

If push notifications are enabled, generated evidences can send the normal per-evidence callbacks for the selected events. Track the batch itself from the batch list or details view.

Review an existing batch

Use the batch list when you need to check whether a batch is still editable, scheduled, processing, processed, invalid, or failed.

1. Sign in to Namirial Notify.
2. Open the service area for the batch, such as My EviNotice batches, My EviMail Batches, or My EviSms Batches.
3. Search or filter the list using the information you have, such as the batch description, creation date, scheduled date, or state.
4. Open the batch row or select Details if that action is available.
5. Review the batch state, progress, and totals, including sent and failed item counts when the batch has started processing.
6. Review the recipient or item list to identify which entries were processed into evidences and which entries failed validation or processing.
7. Open the generated evidence from the relevant transaction list when you need the final delivery, opening, reply, closure, or affidavit status for a recipient.

Batch progress reports whether batch items were processed into evidences. It does not replace the transaction status of each generated EviNotice, EviMail, or EviSMS.

Batch lifecycle

A batch has its own processing lifecycle, separate from the lifecycle of the evidences created from its recipients. Batch items also have their own state progression.

Batch-level states

Invalid usually means the batch configuration or recipient data must be corrected before the batch can continue. Failed means processing failed after the batch was submitted or started; review the error details and follow your operational recovery process.

Per-item states

Each recipient or item in a batch moves through its own item-level lifecycle. The Sent item state means that the item was successfully processed into an evidence, not that the final evidence was delivered to the recipient.

Troubleshooting

You cannot move to the next wizard step

Problem: The wizard does not let you continue after completing a step.

Cause: One or more required fields in the current step may still be empty or invalid.

Solution:

1. Review the fields in the active step.
2. Confirm that all required values were entered.
3. Check the page for validation messages and correct the reported issue.
4. Try the step action again, such as Create or Next.

Recipient import or entry fails

Problem: The Recipients step does not accept the entered data or the uploaded CSV file.

Cause: The delivery channel, headers, or file structure may not match the format expected by the wizard.

Solution:

1. Confirm that the correct Delivery channel for the notification was selected first.
2. For manual entry, review the indicated headers shown by the wizard.
3. For CSV import, confirm that the file follows the required structure.
4. Use the on-screen help in the Recipients step if you need the expected format.

The batch cannot be finished

Problem: The batch is configured, but Finish does not complete the process.

Cause: The schedule settings or one of the previous shared settings may still be incomplete or invalid.

Solution:

1. Review the Schedule date, Sending time, and Process now settings.
2. Confirm that the previous steps were completed successfully.
3. Return to the earlier wizard steps if needed and correct any missing data.
4. Retry Finish after the reported issue is resolved.

The batch is invalid or failed

Problem: The batch list or details view shows the batch as Invalid or Failed.

Cause: The batch may contain invalid configuration, invalid recipient data, or a processing error detected after submission.

Solution:

1. Open the batch details view.
2. Review the validation or failure information shown for the batch and its items.
3. Correct the configuration or recipient data if the batch is still editable.
4. If the batch is no longer editable, create a corrected batch or follow your operational recovery process.

Related

• Issuer User Manual
• Contacts
• How to create a new EviNotice
• Evidence and affidavits
• States and outcomes
• Callbacks and webhooks

API reference for batch sending

If you are integrating batch sending programmatically, see the batch operations sections in the service API references:

• EviNotice batch operations
• EviMail batch operations
• EviSMS batch operations
• Integration workflows — Workflow 4: Batch sending