Hi,
I created a workaround to do this but it has its drawbacks. I'll describe it and if you are interested, I can share more details here.
- Because you can use HTML in the inbound flow, in the inbound flow, I create an HTML template and assign it to a variable. (e.g. flow.template1)
- I use Set Participant data to "attach" that template to the call. (e.g., Attribute Name: replyTemplate1, Value: flow.template1) - NOTE: You can combine steps 1 and 2 together but I use the template to send an auto reply, so I store it in a variable).
- In my Canned Response(s), I use the substitution functionality and insert the Participant Data attribute. (e.g. {{replyTemplate1}})
A couple of drawbacks to this:
- In order to create or update the template, a user must have Architect permissions and edit the flow or, I just had a thought that you could store the HTML in a Data Table but I am not sure whether there is a limit to the number of characters allowed.
- Same point as the above, you cannot edit the template in Genesys Cloud Canned Responses.
- You cannot view the template in Canned Responses until you are attached to an interaction that uses that flow that creates the content for the template.
- You need to create, edit, and validate your HTML in an editor outside of Genesys Cloud.
Let me know if you would like additional details.
------------------------------
Dan Fontaine
Altivon - a ConvergeOne Company
------------------------------