Prepare a draft reply for every support ticket
Each support ticket produces a pre-filled Outlook draft addressed to the customer, ready for an agent to edit and send.
New submission on your support intake form
Create a draft email in Outlook addressed to the customer with their ticket details
One-directional. A submission triggers the action — nothing is written back into your form.
Help desk replies are mostly the same four sentences with one detail changed. Having Outlook build the draft — addressed, subject-lined, with the ticket quoted underneath — leaves the agent doing the only part that needs judgement.
Nothing sends on its own, which is why IT teams accept it. A draft can be rewritten, forwarded to a colleague, or deleted without the requester ever knowing it existed. It also survives the days when the queue gets answered out of order.
Setting it up
- 1
Publish the intake form with Ticket Subject and Issue Description required. Both go straight into the draft, and an empty one wastes the agent's time.
- 2
In Zapier, use the formformform New Submission trigger and select the help desk form.
- 3
Add Microsoft Outlook and choose Create Draft rather than Send Email. The message appears in the connected mailbox's Drafts folder and goes nowhere until a person presses send.
- 4
Connect the mailbox the team answers from: the shared support mailbox if drafts should be visible to everyone, an individual account if each agent owns their own queue.
- 5
Map Work Email into To and build the subject as a reference plus Ticket Subject, for example "Re: laptop will not wake — ticket received".
- 6
Open the body with Full Name, then quote Issue Description and Affected Device or System underneath, so the agent never has to switch to the responses table to read the ticket.
- 7
Use Priority to choose which stock paragraph the draft carries — an hour for urgent, next working day otherwise — with a Zapier path so each level gets its own wording.
- 8
Submit a test ticket, open the draft in Outlook, edit and send it, then turn the Zap on.
What maps where
Using the IT Help Desk Ticket as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Microsoft Outlook |
|---|---|
| Work Email | To field of the Outlook draft |
| Ticket Subject | Subject line of the draft, after the reference prefix |
| Full Name | Greeting at the top of the draft |
| Issue Description | Draft body, quoted back to the requester |
| Affected Device or System | Draft body, under the quoted description |
| Priority | Draft body, choosing which response-time paragraph is used |
Variations worth knowing
Behind a Zapier path on Priority, add an Outlook Send Email to the on-call address for the top level only. The draft still waits for the agent, and the alert makes sure someone knows a severity-one ticket landed at 4pm on a Friday.
Branch on Issue Type and connect a different Outlook account per branch: hardware to the desk-side mailbox, access requests to identity. Each team then opens its own Drafts folder and sees only the tickets it owns.
If something isn't arriving
Look in the Drafts folder of the mailbox connected to Zapier, not the agent's own. If the team needs shared visibility, reconnect the action to the shared support mailbox and confirm each agent has delegate access to it.
The body was sent as plain text. Set the Outlook action's body type to HTML and put line breaks between Issue Description, Affected Device or System and When Did the Issue Start? so the draft is readable before editing.
Frequently asked questions
Where does the draft appear, my Drafts folder or a shared one?
In the Drafts folder of the Outlook account you connected in Zapier. Connect a shared support mailbox and the whole team sees the queue; connect an individual account and only that agent does. Drafts in a shared mailbox need the right delegate permissions.
Can the draft go out automatically if nobody touches it?
Not from this Zap, because Create Draft never sends. If you want unattended replies for one narrow category, build a second Zap using Send Email behind a path on Issue Type, and leave everything else as drafts a person reads first.
Does sending the draft close the ticket in the form?
No. Submissions are never updated from Outlook, since the flow only runs outward. Track status in whatever you already use, or filter the responses list yourself. The draft is a reply-writing shortcut, not a ticket system with states.
Related automations
- Add every event signup to your Outlook contacts
Everyone who registers is written into your Outlook address book with their phone, employer and job title already filled in.
- Confirm every registration by email
Registrants get an instant confirmation from your event mailbox showing their ticket type, and the organiser keeps a BCC copy.
- Email each demo request to your sales inbox
Each demo request arrives in your shared Outlook inbox as a scannable email, so a rep can qualify it without opening another tool.
- Put each booking request on your Outlook calendar
A requested slot becomes a real Outlook calendar event, with the client's reason for the appointment sitting in the notes.
- Send an automatic acknowledgement to every new enquiry
Every enquiry gets a same-minute acknowledgement sent from your own Outlook mailbox, naming what was asked and when a real answer follows.
- Confirm every RSVP with the joining details
Registrants get a confirmation carrying the joining details, and the organiser mailbox is BCC'd on every one.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free