template-fixtures.ts10.9 KBView on GitHub /**
* Sample email templates — PRESERVED, DELIBERATELY UNREACHABLE.
*
* These came out of the old onboarding modal, which has been deleted. The
* fixtures are kept because the template shapes (AI variables, `@Knowledge
* Base` / `@Calendar` notation, the source-emails provenance) are the design
* we intend to reuse, and re-deriving them from scratch would lose that work.
*
* Nothing imports this. It is not routed and appears in no menu. If you are
* here to build the real templates surface, start from these and wire it up
* properly — do not add an import to make the old page reachable again.
*/
export interface EmailTemplateSourceEmail {
id: number;
subject: string;
from: string;
date: string;
preview: string;
}
export interface EmailTemplate {
name: string;
content: string;
sourceCount: number;
sourceEmails: EmailTemplateSourceEmail[];
}
export const EMAIL_TEMPLATE_FIXTURES: EmailTemplate[] = [
{
name: 'General Rules',
content: `General Email Response Guidelines:
1. **Tone & Voice**
- Always maintain a professional yet friendly tone
- Match the sender's level of formality
- Use {my_name} for consistent signature
2. **Response Timing**
- Acknowledge receipt within 2 hours during business hours
- For complex requests, send quick acknowledgment: "Thanks for your email. I'll review this and get back to you by {specific_time}"
- Use {@Calendar: suggest meeting times} for scheduling requests
3. **Information Gathering**
- Reference {@Knowledge Base: company information} for accurate details
- Always verify facts before sharing company information
- For pricing questions, use {@Knowledge Base: current pricing}
4. **Follow-up Protocol**
- Set reminders using {@Calendar: follow-up reminder}
- Track important conversations in {@Notion: conversation log}
- For deals, update {@Notion: sales pipeline} after each interaction
5. **Escalation Rules**
- Forward urgent technical issues to {@Slack: engineering}
- Cc {@Slack: legal} on contract discussions
- Loop in {@Slack: customer-success} for customer issues
6. **Common Variables**
- {first_name} - Recipient's first name
- {company} - Their company name
- {our_product} - Reference to CedarMail
- {my_name} - Your signature name
- {current_date} - Today's date`,
sourceCount: 156,
sourceEmails: [
{
id: 100,
subject: 'Email best practices for the team',
from: '<email>',
date: '2024-03-16',
preview:
'Team, here are the email guidelines we discussed. Please make sure all external communications follow these standards...',
},
{
id: 101,
subject: 'Response time expectations',
from: '<email>',
date: '2024-03-15',
preview:
'Quick reminder about our 2-hour response commitment during business hours. For complex requests, acknowledge first...',
},
{
id: 102,
subject: 'Template variables cheat sheet',
from: '<email>',
date: '2024-03-14',
preview:
'Here are the most commonly used template variables and when to use them. This should help standardize our responses...',
},
],
},
{
name: 'Schedule Meeting',
content: `Hey {first_name},
Does {@Calendar: suggest 3 times next week} work for you?
Or feel free to schedule directly here: https://calendly.com/jesse-cedarcopilot/30min
Best,
{my_name}`,
sourceCount: 23,
sourceEmails: [
{
id: 1,
subject: 'Quick sync on Q4 planning?',
from: '<email>',
date: '2024-03-15',
preview:
'Hey Jesse, would love to connect about our Q4 roadmap planning. Are you free for a quick 30-minute call next week?',
},
{
id: 2,
subject: 'Meeting request - Product integration',
from: '<email>',
date: '2024-03-12',
preview:
'Hi Jesse, I saw your recent post about AI automation. Would be great to discuss potential integration opportunities...',
},
{
id: 3,
subject: 'Coffee chat about CedarMail?',
from: '<email>',
date: '2024-03-10',
preview:
"Jesse, heard great things about what you're building. Free for coffee sometime next week to learn more?",
},
],
},
{
name: 'Outreach Follow-up 1',
content: `Hi {first_name},
Following up on my previous email about {our_product}. I noticed {company} is in the {industry} space - we've helped similar companies like {@Knowledge Base: similar company we sell to} achieve {specific benefit}.
Would love to show you how we could help {company} with {their_main_challenge}.
Worth a quick 15-minute chat?
Best,
{my_name}`,
sourceCount: 41,
sourceEmails: [
{
id: 4,
subject: 'Following up on CedarMail demo',
from: '<email>',
date: '2024-03-14',
preview:
'Hi David, following up on our conversation about email automation. I noticed GlobalTech is scaling rapidly...',
},
{
id: 5,
subject: 'Quick follow-up - AI email solution',
from: '<email>',
date: '2024-03-11',
preview:
'Hi Maria, wanted to circle back on our email management solution. Saw that FinanceFirst just raised Series B...',
},
{
id: 6,
subject: 'Re: Email automation for sales teams',
from: '<email>',
date: '2024-03-08',
preview:
'Hi Tom, thanks for the initial interest! I noticed your team at SalesForce Pro is handling 500+ leads daily...',
},
],
},
{
name: 'Outreach Follow-up 2',
content: `Hi {first_name},
Hope you had a great {day_of_week}! I wanted to circle back on {our_product} for {company}.
I came across some interesting insights about {@Knowledge Base: specific compliance issue customer of size and industry might be struggling with} that I thought might be relevant to your team.
Happy to share these findings - would a brief call this week work?
Best,
{my_name}`,
sourceCount: 35,
sourceEmails: [
{
id: 7,
subject: 'Second follow-up - compliance insights',
from: '<email>',
date: '2024-03-13',
preview:
"Hi Jennifer, hope you had a great Monday! Wanted to share some compliance insights we've gathered...",
},
{
id: 8,
subject: 'Circling back - email security',
from: '<email>',
date: '2024-03-09',
preview:
'Hi Robert, hope your week is going well! I came across some interesting data about email security trends...',
},
],
},
{
name: 'Outreach Follow-up 3',
content: `Hi {first_name},
Last follow-up from me! I know {company} is likely focused on {current_business_priority}, but I wanted to share one quick insight.
Companies similar to yours typically see {specific_metric_improvement} when they implement {our_solution_category}.
If this resonates, I'm happy to chat. Otherwise, I'll leave you be!
Best,
{my_name}`,
sourceCount: 28,
sourceEmails: [
{
id: 9,
subject: 'Final follow-up - 60% productivity gain',
from: '<email>',
date: '2024-03-07',
preview:
'Hi Alex, last email from me! I know TechStartup is focused on scaling, but wanted to share one insight...',
},
{
id: 10,
subject: 'Last follow-up - email efficiency',
from: '<email>',
date: '2024-03-05',
preview:
'Hi Rachel, final follow-up from me. Companies like CloudCorp typically see 40% time savings...',
},
],
},
{
name: 'Polite Sales Decline',
content: `Hey {first_name},
Thanks for reaching out! We're all set with {their_product_category} for now.
If anything changes, I'll keep you in mind.
Best,
{my_name}`,
sourceCount: 67,
sourceEmails: [
{
id: 11,
subject: 'Re: CRM solution for your team',
from: '<email>',
date: '2024-03-16',
preview:
"Hey Marcus, thanks for reaching out about your CRM solution! We're all set with our current setup for now...",
},
{
id: 12,
subject: 'Re: Marketing automation platform',
from: '<email>',
date: '2024-03-14',
preview:
"Hi Sophie, appreciate you thinking of us for your marketing automation platform. We're good with our current tools...",
},
{
id: 13,
subject: 'Re: Analytics dashboard proposal',
from: '<email>',
date: '2024-03-12',
preview:
'Hey Kevin, thanks for the analytics dashboard proposal! We have our analytics needs covered at the moment...',
},
],
},
{
name: 'Customer Follow-up',
content: `Hi {first_name},
Hope you're enjoying {our_product}! I wanted to follow up on {previous_topic}.
{@Knowledge Base: relevant feature that solves their need}
Let me know if you have any questions.
Best,
{my_name}`,
sourceCount: 52,
sourceEmails: [
{
id: 14,
subject: 'How are you finding CedarMail?',
from: '<email>',
date: '2024-03-15',
preview:
"Hi Patricia, hope you're enjoying CedarMail! Wanted to follow up on the template customization we discussed...",
},
{
id: 15,
subject: 'Following up on your onboarding',
from: '<email>',
date: '2024-03-13',
preview:
'Hi James, hope the team is settling in well with CedarMail! I wanted to check in on the integration setup...',
},
{
id: 16,
subject: 'Quick check-in - email categorization',
from: '<email>',
date: '2024-03-11',
preview:
"Hi Amanda, hope you're finding value in the email categorization features! Wanted to follow up on...",
},
],
},
{
name: 'Partnership Interest',
content: `Hi {first_name},
I came across {company} and noticed you're {role}. We work with {@Knowledge Base: similar company we sell to}, and I think there could be a great fit for collaboration.
Would love to explore how {our_product} could complement {their_product}.
Interested in chatting?
Best,
{my_name}`,
sourceCount: 19,
sourceEmails: [
{
id: 17,
subject: 'Partnership opportunity - AI + Productivity',
from: '<email>',
date: '2024-03-16',
preview:
"Hi Daniel, came across WorkflowPro and noticed you're the VP of Partnerships. We work with several productivity companies...",
},
{
id: 18,
subject: 'Potential collaboration - CedarMail + TaskManager',
from: '<email>',
date: '2024-03-14',
preview:
"Hi Emma, I noticed TaskManager's recent integration announcements. As the Head of Business Development...",
},
],
},
];