Veeva specialist
Veeva Approved Email, hand-coded to render.
Responsive Approved Email templates and fragments with tokens—built to Veeva requirements and checked across the email clients your HCPs actually use.
Template anatomy
AE
Header · logo
Dear {{accTitle}} {{accLname}},
{{insertEmailFragments}}
Body · CTA button
ISI · footer · unsubscribe
What I build
Approved Email that reps can send with confidence.
Email templates
Responsive, hand-coded Approved Email templates from your approved design.
Email fragments
Modular fragments reps can add, built to sit cleanly inside the template.
Tokens & dynamic content
Account, user and content tokens set up correctly, including fragment insertion.
Responsive layouts
Designs that hold up from desktop Outlook to a phone screen.
Client compatibility checks
Rendering checked across major clients before delivery.
Updates & production support
New versions, content changes and fixes after review.
Under the hood
Email HTML, the hard way—on purpose.
Email clients don’t behave like browsers. The build accounts for that from the start.
- Hand-coded table layouts
- Inline CSS where clients need it
- Outlook, Gmail and Apple Mail checks
- Veeva token syntax and fragments
- Bulletproof buttons and fallbacks
- Optimised images and alt text
Approved Email FAQ
Can you build both templates and fragments?
Yes—full templates, standalone fragments, or a template designed around a set of fragments.
Why does my Approved Email look different in Outlook?
Outlook on Windows uses a Word-based rendering engine with limited CSS support. Hand-coded table layouts and Outlook-specific fallbacks keep it consistent.
Can you fix an existing template?
Yes. Send the HTML and a note on what’s breaking; rendering and token issues are a common fix.