Exclaimer Cloud deployment. Users compose and send messages from any client/browser/device, without signatures. The message is then routed to our Cloud service, where the first applicable signature is applied.

-and/or-

Outlook client deployment. Users synchronize signatures from Exclaimer Cloud to Microsoft Outlook, so their signature is displayed when they compose messages from their Outlook client. The message is then routed to Exclaimer Cloud, where text matching ensures that a duplicate signature is not applied.

Choose whether the specified exception text should be matched anywhere in the entire message thread, or only in the most recent thread.

In which case

By default, signature processing will stop if an exception is triggered. If preferred, switch on the Add next applicable signature... option to continue signature processing subsequent signatures in the event that an exception is triggered here.