We use markdown and placeholders extensively in our agent signatures. This works great in tickets however, side conversations do not currently render either markdown or placeholders. Additionally, the Collaboration add-on automatically adds the agent's signature (with unrendered markdown and placeholders) when a new side conversation is created. This means that in order to effectively use side conversations, our agents would have to delete the automatically populated signature and manually add their own.
We like the idea of automatically adding the signature to side conversations, but it's only useful if those signatures are rendered correctly. For those who aren't using markdown or placeholders in their signatures, I can see the current functionality being extremely helpful but, for us, it becomes a nuisance as it creates more work for our agents.
We would like to see the Collaboration add-on support markdown and placeholders. This could be useful for all kinds of potential workflows but is essential for including signatures in side conversations.
Short of adding markdown and placeholder support, we would like the option to stop signatures from automatically being added to the side conversation so our agents don't have to delete the unrendered signature every time.
Hey Mike -
Apologies for the delayed response here, it took me a little while to track down the information. At the moment, side conversations doesn't enable you to turn signatures off. But the product manager did want me to ask how critical this is for your organization?