Add custom text to a Lync meeting invitation

A recurring customer request in the Lync 2010 period was to add organization-specific text to meeting invitations. My original note described an Exchange transport-rule workaround rather than a change to the Lync invitation template.

Understand where the change happens

The approach acts on the message as it passes through the Exchange transport service. It does not add an editable template to the Lync client. That distinction matters when explaining the result to a customer or troubleshooting why a recipient sees different text.

The original environment used Exchange 2007 or Exchange 2010 Hub Transport. This article preserves that context; it does not establish equivalent behavior in current Teams or Exchange Online meeting experiences.

Inspect the invitation identifier

The historical note used this marker to recognize the relevant invitation content:

[!OC([1033])!]

Treat it as the literal marker recorded in the original example. Inspect an actual invitation from the intended client and language before using it as a condition. Do not assume that every meeting message, locale or client version contains the same text.

Build a narrowly scoped transport rule

1. Capture a representative test invitation and inspect its message content.
2. In the Exchange Management Console, create a transport rule with a subject-or-body text condition appropriate to the observed marker.
3. Limit the pilot to the intended sender or recipient scope.
4. Choose the transport action that adds the required text, and define the applicable exceptions.
5. Send new test invitations and verify the recipient experience before widening the rule.

The subject-or-body condition is a way to identify a message. It does not by itself specify the text placement or guarantee how a calendar client renders the result.

Test the complete meeting workflow

Check new invitations, meeting updates and forwarded messages. Confirm that the join information remains usable and that the added text is not repeated unexpectedly. Include the Outlook or calendar clients actually used by the pilot group.

Compare messages inside and outside the rule’s scope. If the workaround does not produce a consistent result, retain the evidence and reconsider the condition or action rather than broadening the match blindly.

Keep the workaround distinct from the requirement

The business requirement is a clear invitation. The implementation in this note is a historical transport-layer technique. Keeping those separate makes it easier to evaluate a supported replacement when the communications platform changes.