(a) a client-specific USPTO customer number (if the client has one), or the firm's customer number (if the client doesn't have one) (Some of my clients want me to use their customer number, rather than mine. I have templates for responses to Office Actions, etc. that include a customer number in the document headers)

(b) a client-specific USPTO deposit account number (if the client has one), or the firm's deposit account number (if the client doesn't have one). (My template responses include boilerplate language authorizing charges to a deposit account, in case of a missed extension of time.)

(c) actual filing date or official filing date or priority date, depending on what is available. (For example, when calculating due dates for foreign applications.)

Thanks,
George

Sorry for the delay in following up. We hope this helps.

Thank you for your suggestion. We will pass this on to engineering for future consideration.

• AppColl Support

1. a client-specific USPTO customer number (if the client has one), or the firm's customer number (if the client doesn't have one) (Some of my clients want me to use their customer number, rather than mine.)
2. a client-specific USPTO deposit account number (if the client has one), or the firm's deposit account number (if the client doesn't have one)
3. actual filing date vs official filing date vs priority date.

Please consider adding syntax that enables run-time selection of alternative text, such as when a first field is blank.

@RichardS3059 posted a possible syntax:
{{Matter.ClientContact.Nickname},{Matter.ClientContact.FirstName}}
and he suggested a more generalized IF syntax be created, which is a great idea.

I suggested syntax along the lines of:
{!{Matter.Client.PrimaryContact.First}!Matter.Client.PrimaryContact.Nickname}

Thanks,
George

Thank you for these suggestions. We have added this to our engineering list.

• AppColl Support

Although your approach would be more flexible in case similar substitutions are needed in other cases.