Author: FaxCore Technical Engineering Team (Enterprise Solutions Architecture & Systems Engineering)

Published: October 19, 2026 Updated: October 19, 2026 Verified Architecture

Enterprise & Regulatory Compliance Notice: This documentation is authored and maintained by FaxCore certified engineers for enterprise administrators. For formal regulatory audits (HIPAA, SOX, GDPR, PCI-DSS), verify your configuration with your organization's compliance officer. Read our full Compliance Disclaimers & Terms.

Notification Engine & Delivery Templates

FaxCore features a multi-protocol notification engine that dispatches status alerts and completed documents across email, network file folders, webhooks, FTP servers, and printers.

---

Supported Notification Events

Event Name	Trigger Condition	Notification Recipient
Send delivery	Outbound message sent via Web Client/SDK	Destination Recipient
Message send success	Outbound fax successfully delivered	FaxCore Originator
Message send error	Outbound fax transmission failed	FaxCore Originator
Message receive success	Inbound fax routed to user inbox	FaxCore Recipient
Message receive error	Inbound transmission failed	FaxCore Recipient / Admin
Message assign receive	Orphaned fax assigned from Unrouted queue	Assigned User
Message forward receive	Fax forwarded between colleagues	Forward Recipient
Send password	"Forgot Password" self-service request	User
Approval request	Outbound fax requires manager approval	Designated Approver
Approved / Rejected reply	Manager decision on pending fax	Requesting User

---

Delivery Protocols & Token Syntax

Delivery templates control the layout and payload of notifications. Templates support dynamic configuration tokens ($$CONFIG...$$) and message tokens ($$MESSAGE...$$).

Protocol Targets

• Email: Delivers an HTML/text message containing transmission summaries and attached PDF/TIFF documents. Outbound email delivery is powered by the SMTP Relay Engine (supporting SMTP Classic, Microsoft 365 Modern Auth, Mailgun, Amazon SES, and SendGrid).
• File: Saves document images and structured text metadata files to local or network UNC paths.
• HTTP POST: Posts transactional JSON/form data and document streams to enterprise APIs or SharePoint endpoints.
• FTP: Uploads images and control files to remote FTP servers.
• Printer: Dispatches hard-copy banner pages and attachments to physical Windows print devices.

---

Implementation Scenario: Dropping Inbound Faxes to C:\Infax\

To automatically save every incoming fax as a PDF along with a metadata .txt receipt to a server directory:

1. Navigate to Domain Management > Delivery Templates and select the MessageReceiveSuccess template.
2. Click the File tab:
   • Image File Name:

     $$MESSAGE.ID$$.$$MESSAGE.XSACT.ADDRESS_FORMAT_TYPE$$
     

   • Report File Name:

     $$MESSAGE.ID$$.TXT
     

   • Report Body:

     Message Received: $$MESSAGE.ID$$
     Remote CSID: $$MESSAGE.XSACT.XMIT.REMOTE_CSID$$
     Pages: $$MESSAGE.XSACT_PAGE_COUNT$$
     

3. In Domain Management > Users, edit the SYS-UNROUTED account (or individual recipient profile).
4. On the User Profile tab, set the primary file delivery address to:

   C:\Infax\
   

5. Incoming faxes will now immediately write 20261007.pdf and 20261007.txt to C:\Infax\.