store reply models?

[tttp]

For each campaign, the politician should be able to write a subject + message

this should be used to automatically send reply emails to the supporters

Beside the text (markdown?) we might want to give them the opportunity

may be let them choose a template (eg header with their picture + contact details/positions)

should we add some rules on how to process the replies? eg:

• as fast as possible
• wait until office hours to reply
• wait until date, eg 1 week before the vote

[1v4n4]

some rules on how to process the replies?

an we offer all as a choice with first next office hours as default

may be let them choose a template (eg header with their picture + contact details/positions)

ideally, they can save it and update as they please

[tttp]

an we offer all as a choice with first next office hours as default

yes

ideally, they can save it and update as they please

post MVP ;)

[debiB]

1. Database Updates

• reply_templates Table: Add layout_type (e.g., "Standard", "Official Header") to support template selection. Ensure send_timing supports "Immediate", "Office Hours" (default), and "Scheduled".
• messages Table: Add tracking fields reply_status (pending, scheduled, sent) and reply_scheduled_at to manage the queue.

2. Backend Logic

• Scheduling Logic: Update message_processor.ts to calculate the send time based on the selected rule (e.g., if "Office Hours", calculate next valid slot; if "Scheduled", use specific date).
• Sending Worker: Create a background process (or cron job) to poll for due messages, render the email (Markdown body + Layout), and send via SMTP.

3. Defaults (MVP)

• Office Hours: Default to Mon-Fri, 09:00-17:00 (Server Time/CET) unless configured otherwise.
• Layouts: Provide 1-2 hardcoded options (e.g., "Text Only", "With Header Image").

Questions

Here are the questions you requested to clarify requirements without assumptions:

1. Office Hours Definition: "What specific hours and timezone should be used for 'Office Hours' by default? (e.g., 9am-5pm CET?)"
2. Sender Identity: "Should the automated reply come from the politician's personal email address or a generic campaign address (e.g., campaign@... on behalf of the politician)?"
3. Layout Assets: "For the 'Header with picture' template, where should this picture come from? Is it the politician's profile photo, or do they need to upload a specific campaign image?"
4. Editing Scheduled Replies: "If a politician updates a template, should the changes apply to already scheduled (but not yet sent) emails, or only new ones?"
5. Drafts vs. Active: "Is a simple 'Active/Inactive' toggle sufficient for MVP, or do you need a separate 'Draft' state for templates?"

[tttp]

Here are the questions you requested to clarify requirements without assumptions:

Office Hours Definition: "What specific hours and timezone should be used for 'Office Hours' by default? (e.g., 9am-5pm CET?)"

let's do 8-19 CEST

Sender Identity: "Should the automated reply come from the politician's personal email address or a generic campaign address (e.g., campaign@... on behalf of the politician)?"

• sender: the technical email for the campaign (the one where the email was received)
• reply to: email of the politician (configurable)

Layout Assets: "For the 'Header with picture' template, where should this picture come from? Is it the politician's profile photo, or do they need to upload a specific campaign image?"

let's skip for the MVP, we will know when real users will ask for it

Editing Scheduled Replies: "If a politician updates a template, should the changes apply to already scheduled (but not yet sent) emails, or only new ones?"

no opinion, whatever the easiest technically

Drafts vs. Active: "Is a simple 'Active/Inactive' toggle sufficient for MVP, or do you need a separate 'Draft' state for templates?"

active/inactive is enough

[tttp]

for the sending, easier to use jmap than smtp (it's a REST API)