Setting up a looping Digest email. We will at times have a section that has upcoming announcements. The goal is for Help Desk to be able to handle this without ever having to dig into campaign builder, which seems possible just by updating the contact’s field before the email goes out for that week.
Another goal I would have is the option to format that dynamic text…
I tried added html to the textarea to see if the email builder would do the formatting and just got ugly HTML when putting the contact’s text area merge field in the text area and code area for email builder.
Do text areas support formatting? or is there a work around for getting the text to have some formatting?
Lastly, I am imagining how Help Desk would update the fields. I believe they would have to choose the option Mass Update Contacts. Is that correct? Or is there another way that’s even easier on a non-Infusionsoft trained person?
Hey Chris, great questions. Sounds like you’re pretty clear on this already:
Text Areas SHOULD support formatting (paragraph breaks, etc). Several years ago they did not - then they fixed it and they DID - but then a few weeks ago I saw a thread where someone was saying it was broken, and that they no longer supported formatting. I just tested it, and it worked for me.
So I guess the answer is to test it yourself. And if it doesn’t, raise a ticket - because it SHOULD.
Yes, the easiest way is probably to use the Mass Update Contacts action. Another option would be to perform a Modify Existing Records import; though for a non-Infusionsoft trained person, I don’t imagine this process would be any easier. Here’s an article that may help if you’re interested in this idea: How to perform a Keap Import without creating duplicate contacts
Great thanks Greg! That nifty little action set work around helped a lot.
What I see regarding formatting is that I can have returns, but cannot bold/italicize/underline. It appears URL’s work when typed normally (no html, like < a href=“link.com”>click here) <–space between a and < to leave as plain text.
If your app handles bold/italicize/underline, I’d love to know what you are doing.
Otherwise, it seems an easy workaround is to have 2 fields, one for headline and the other for body. Then format the merge field for headline inside the email.
The attempt to add HTML for bold/italic/etc font/text formatting didn’t work when adding HTML text to a text section or Code section in Email Builder. Alas, I will make due with 2 custom fields (1 for Header, 1 for Body) and instruct support that only text, returns, and links are allowed.