Notion-Based Customer Satisfaction Email Automation

Customer Satisfaction Email Automation – Notion Tickets 1. Context Notion database: “Tickets servicio al cliente” (Customer Service Tickets) Relevant properties: Status (Type: Status) Possible values: Sin empezar En curso N/A Prueba Cerrado/Resuelto (Trigger status – please confirm this is final) Email field: Mandatory Always present No domain validation required 2. Objective Automatically send a satisfaction email via Brevo when a ticket status changes to: Cerrado/Resuelto The email should be triggered immediately when the status changes (event-based, not batch-based). 3. Tech Stack Notion (Trigger) Make (Automation platform) Brevo (Transactional email) Email template already created in Brevo Same sending domain currently in use 4. Required Make Scenario Flow Trigger Notion → Watch Database Item (Updated) Filter Status = “Cerrado/Resuelto” Action Brevo → Send Transactional Email Use existing template Map fields: Email Customer name Order ID (Optional: Company name) Recommended (to prevent duplicate emails) Add a checkbox property in Notion: Satisfaction email sent Filter condition: Status = Cerrado/Resuelto AND Satisfaction email sent ≠ true After sending: Update checkbox to true (Optional) Store send date 5. Error Handling Basic error handling required Retry once if sending fails Log error in Make execution history No advanced monitoring required 6. Operational Considerations Expected usage: Approx. 300 closed tickets/month ~3 operations per ticket (trigger + send + update) Estimated ~900 operations/month This is low volume and does not require batch processing. 7. Deliverables Expected from Freelancer Fully configured Make scenario Clear documentation of: Trigger Filters Variables mapping Exported scenario backup Short maintenance guide (1 page) Proper naming conventions in Make

Project ID: 40250895