Power Automate form to email for dental recall requests

A Power Automate form to email flow for dental recall requests takes four actions: a Microsoft Forms trigger, a response lookup, a formatted message, and a send to a shared front desk mailbox. It works for web requests that can wait until morning. Phone calls, same-day openings, and after-hours overflow need something that answers back.

What the flow does and where it stops

If your practice already runs on Microsoft 365, this is the cheapest recall intake to stand up. A patient fills in a short Microsoft Form from the reminder card, your website, or a text link. Power Automate catches the submission and drops a clean email into a shared inbox. The front desk calls or texts the patient and books the visit in the PMS.

The flow does not book anything, check availability, or confirm a time. Someone still has to read the email, open the schedule, and reply. That is fine at 10 a.m. on a Tuesday. It is a problem when the request lands at 7 p.m. and the patient has moved on to the next practice by morning.

Compare form builders free

Build the recall form first

Keep the form short. Every exrra field costs completions, and recall requests do not need clinical detail. Ask for no symptoms and no insurance numbers. Anything clinical should happen on the phone or inside your PMS.

Make name, phone, and the text consent question required. The rest can stay optional.

Step by step: the Power Automate flow

1. In Power Automate, creaet an automaated cloud flow and pick the trigger When a new response is submitted (Microsoft Forms). Select your recall form from the Form Id list.
2. Add Get response details. Set Form Id to the same form and Response Id to the dynamic value from the trigger. The trigger only hands you an ID, so this step is what pulls the actual answers.
3. Add Send an email (V2) from Office 365 Outlook. Put your shared front desk mailbox in To, not a person's address.
4. Build the subject from dynamic content: recall request, patient name, and preferred time of day. A subject the desk can scan beats a generic "New form response".
5. Build the body from the fields in the tabke above (template below).
6. Optionally add a Condition before the send. If "Approximate last visit" is over a year, send with High importance (under the advanced options of the email action). If not, send normally.
7. Save, submit a trst response yourself, and check the run history for the flow. Confirm the email arrived in the shared mailbox and that every dynamic field filled in.

Here is a body template that works for most front desks:

Subject: Recall request: [Full name], prefers [Preferred time of day]

Patient: [Full name]
Phone: [Mobile phone]  (OK to text: [OK to text me])
Email: [Email]
Existing patient: [Existing patient]
Last visit: [Approximate last visit]
Preferred days: [Preferred days]
Preferred time: [Preferred time of day]
Submitted: [Submission time]

Each bracketed item is a dynamic content token from Get response details. Plain text with one fact per line is easy to scan while someone is on the phone with another patient.

Try the free contact form template

Where this flow breaks

Most failures in a flow this small come from ownership, not logic.

• The connection belongs to one person. Flows run under the account that created the connections. If that employee leaves and the account is disabled, the flow stops, and nothing tells the front desk. Build it under a service account or a shaed mailbox identity, and put a reminder in your offboarding checklist.
• The form was copied. The trigger is tied to a specific Form Id. Duplicate the form to "update it" and the old flow keeps listening to the old form.
• Nobody watches the shared mailbox after hours. The email arrives at 7 p.m. and sits there. The flow worked, and the patient still got no reply.
• Failed runs go unnoticed. Power Automate records failures in run history, but nobody opens it. Check it weekly at first.
• Duplicates. A patient who submits twice creates two emails. The desk needs a habit of searching the inbox for the phone number before calling.

What to measure: time from submission to first contact, and how many requests turn into booked appointments. If you cannot answer those two from your inbox, the flow is only moving mail around.

Where an AI agent should take over

Email works as a handoff to a human. It does not work as a booking system. The gaps show up in three places.

Calls that never become forms. Most recall happens by pohne. A patient who rings back after a reminder wants a time, not a web form.

After-hours requests. A form submitted at night waits for staff. An agent can answer the call or chat, offer open slots, and confirm by SMS.

Triage. A "Not sure" on existing patient, or a note that mentions pain, needs different handling than a routine cleaning. Someone has to read each message to find that out.

This is the part of the workflow our Dental Front Desk AI covers. It answers, triages, and books new-patient and recall calls intto the practice calendar or PMS, with after-hours overflow and SMS confirmations. The form stays useful as one entry point, and the agent handles everything where a reply has to happen in real time. Setup is $1,500 plus a $399 monthly care plan, with delivery in 2 to 14 days. A practical way to start is to keep your Power Automate flow running as the written channel and let the agent take the voice channel and the after-hours queue.

When a different form builder helps

Microsoft Forms is a good fit when everything lives inside Microsoft tools, and for a basic recall email it is enough. It gets limiting when you want to send submissions to something other thaan Outlook, push data to a webhook, or sort requests automatically.

Our team builds Qwenvo, a completely free form builder, so weigh this as coming from the maker. Every account gts webhooks, a REST API, an MCP server, partial submissions, a custom domain, no badge, unlimited teammates, and Slack, Google Sheets, Notion, and Airtable integrations at $0. Several other builders charge for some of those. Tally's Pro plan ($29/month) covers custom domains, partial submissions, teammates, and branding removal. Typeform's Plus plan ($79/month) removes branding. Fillout's Business plan ($89/month) is where custom domains and partial submissions appear.

The relevant feature here is AI triage. Qwenvo gives each submission a category, priority, sentiment, and a short summary, than routing rules send matching ones to up to 5 email addresses or a Slack incoming webhook. That means an urgent-looking request can go to a different inbox than a routine cleaning, without a flow.

Two honest limits. Qwenvo has no HIPAA offering, and it is hosted in the United States. If your form would ever collect protected health information, keep it to name, phone, and scheduling preferences, and check your own compliance obligations before choosing any builder. Qwenvo also launched in October 2026, so there are few independent reviews yet. If you are fully inside Microsoft 365 and only need one email, Forms plus Power Automate is a reasonable choice.

Questions teams ask

Do I need a paid Power Automate license for Forms to email?

The Microsoft Forms trigger and Outlook email actions are standard connectors, but licensing depends on your Microsoft 365 plan and tenant policy. Check with whoever administers your tenant before you build.

Can the flow check the schedule and offer a time?

Not by itself. The flow only moves the answers into an email. Offering open slots means connecting to your PMS or calendar, which is the job of a booking agent rather than a notification flow.

Should the email go to one person or the whole front desk?

Send it to a shared mailbox the whole desk can open. A personal inbox turns a day off into a missed request.

What should the form never ask?

Skip diagnoses, symptoms, insurance IDs, and anything clinical. Collect contact details and scheduling preferences, then handle the rest in a call or inside your PMS.

Next step

Build the eight-field form today, wire it to a shared mailbox with the four actions above, and submit three test responses. Then look at your last week of voicemails and after-hours calls. If most recall requests arrive by phone, that is where an agent pays for itself.