Review and send replies to support enquiries
Writes a reply to each new support email, asks you to approve it, and sends it or leaves it as a draft.
What it does
Each integration step this workflow runs, in order, what it is for, and the conditions and loops that decide when it runs.
- 1GmailList emailsReads the unread messages in your inbox that match your support search and carry neither label, a few at a time, checking again before each one.
For each
enquiryTry
- 2GmailList emails
- 3GmailAdd label to messageLabels each enquiry 'Reply awaiting approval' while it waits on you, then 'Reply handled' once its reply is sent or drafted.
- 4AnthropicGenerate model responseAsks the AI to write a reply from your business description, or a short acknowledgement when the answer is not in it.
If
replyBodyis not emptyIf
review.approvedis true- 5GmailReplySends the approved reply in the customer's own email conversation, under the original subject, only after you approve it.
Otherwise
- 6GmailCreate draftSaves the reply as a draft in the customer's conversation when you reject it or nobody decides in time.
- 5
- 7GmailRemove label from messageTakes the 'Reply awaiting approval' label off once the enquiry is dealt with, or if it could not be handled, so it is tried again.
If a step fails
If
deliveredis not true andclaimedis true- 8GmailRemove label from message
- 8
- 2
How it works
What happens on each run, in plain English.
Every hour, the unread support mail matching a Gmail search you choose is read, and a reply to each message is written by AI from a description of your business and tone that you provide once. Anything it cannot answer from that description becomes a short acknowledgement saying a colleague will follow up, rather than an invented answer.
Before anything reaches a customer you are asked to approve the reply, shown in full next to what the customer wrote. Approve it and it goes straight away, as a reply in the customer's own email conversation; reject it, or leave it, and it is saved as a Gmail draft in that conversation instead, so nothing is lost and nothing is sent that a person did not approve. Unless you name approvers on the approval step, anyone in your Lodol workspace can approve. A message waiting on you is labelled 'Reply awaiting approval' and a handled one 'Reply handled', so no enquiry is taken twice, and the batch is kept small because each enquiry waits for you. One enquiry that fails is skipped while the rest are still handled, and the run is marked as failed with a note naming it.
You need a Gmail connection and an Anthropic connection, a Gmail search that finds your support mail, and a short description of what your company does, the tone to write in and anything a reply must never promise.
You may also be interested in
Turn emailed feature requests into Notion tasksReads new Gmail email for feature requests and logs the ones it finds in Notion as tasks, with a summary of who asked and why.Draft a reply to every new email in your voiceEach new email gets a reply drafted in your voice and filed under the original message in Gmail, with blanks where a fact is missing.
Voice-note reminders for tomorrow's appointmentsEmails each client booked for tomorrow a spoken reminder as an audio attachment, and never reminds the same booking twice.
Draft replies to customer emails in OutlookWrites a reply to each new customer email in your Outlook inbox, in your business's voice, and saves it as a draft to check and send.Start from a workflow that already works.
Add "Review and send replies to support enquiries" to your workspace, connect its apps, and make it yours.
Free plan, no credit card