Skip to main content
All CollectionsBest Practices
How to Create a High-Quality Template
How to Create a High-Quality Template
AI-Bot avatar
Written by AI-Bot
Updated over a month ago

A well-structured template is key to ensuring your entire campaign maintains a high level of quality. While placeholders are useful, the AI relies on a solid base template to generate error-free messages. For example, the AI can add punctuation, but this isn't always perfect.

It's worth investing time upfront in creating a strong template to ensure hundreds of polished emails later!

7 Tips for Creating High-Quality Templates:

☑️ Add a Comma After Greetings: Make sure to place a comma after "Dear Mr./Ms. Smith" or "Hello Kyle" as correct punctuation is crucial for the AI's clarity.

☑️ Use Placeholders When Possible: Always use placeholders, even for your own name, to avoid misunderstandings, especially with names that have other meanings (e.g., Cook).

☑️ Incorporate Placeholders Into Sentences: Placeholders like "Solution" or "USP1" must fit naturally within sentences. Only "Full Sentence" placeholders generate complete sentences.

☑️ Don’t Forget the "CTA": Ensure the "CTA" placeholder is included in every email to guide leads toward the desired action. Include only one CTA per message to clearly guide recipients to the desired action, boosting conversion rates.

☑️ Use Paragraphs: Break up your email into paragraphs to improve readability and help the AI structure your message better.

☑️ Check the Sign-Off: If you don’t add a custom sign-off, the AI will automatically insert one (e.g., "Best regards"). Ensure your email signature doesn’t already include a sign-off to avoid duplication.

☑️ No hyperlinks: Do not add hyperlinks in the template text; the AI might modify them. Instead, use the CTA-Placeholder to add links. If you must use a link in the template text, set the AI Modification Settings in your campaign to Not modified.

☑️ Final Template Check: Before launching, double-check for any missing punctuation, paragraphs, or layout errors.

Did this answer your question?