The short answer
Write down, for every office, which page its request form is on and which inbox gets the requests. Use inboxes the group owns and more than one person can read, and give each office a backup.
Make sure the service that sends form email is allowed to send for your domain, so notifications do not land in spam. Send from the group's own address, not the patient's.
Then send a test request to every office on a schedule and after every site or email change. A form can stop working without anyone seeing an error.
Where requests get lost
With one office, the form and the inbox are easy to keep track of. Across many offices, the same few problems come up.
The wrong office
A form copied from one office page to another still sends to the first office.
A person, not an inbox
Requests go to one staff member's mailbox, and stop being read when that person is out or leaves.
The spam folder
The notification email fails the checks mail services run, so it lands in spam or never arrives.
A quiet break
A site update, a plugin change, or a new domain stops the form from sending, and no one notices until someone asks why requests dropped.
None of these show up as an error on the website. The patient sees a thank-you message either way, which is why a written route list and regular tests matter.
One route per office
Here are three setups that work. Pick one on purpose, and use it for every office.
| Setup | How it works | What to watch |
|---|---|---|
| A form on each office page | Each office page has its own form, set to send to that office's inbox. | The setting is easy to miss when a page is copied to build a new office page. Check the inbox each time a page is added. |
| One form with an office choice | A single form asks which office the patient wants, and either sends to that office or to a central team. | The office question has to be required, and the office name has to appear in the email subject so the right person picks it up. |
| Online booking instead | Patients pick a time in the scheduling tool, so there is no request to route by email. | Each office still needs its own booking link. That setup is in the online booking guide. |
Booking links by office are covered in online booking links for dental groups. If calls go to a central team too, the same choice is laid out in a central call team or office phones.
Inboxes the group owns
Send each office's requests to an inbox on the group's own email system, such as a northpark-requests address on your own domain, not to a person's mailbox or a free personal account. When people change jobs, the inbox and its history stay with the office.
Microsoft 365 and Google Workspace both have a way to do this. In Microsoft 365, a shared mailbox lets several people read and answer one address, such as a front desk mailbox, without a license of its own, up to 50 GB. Microsoft caps it at 25 users and suggests a Microsoft 365 group above that.
In Google Workspace, a Google Group set up as a collaborative inbox lets members take a request, assign it to someone else, and mark it complete, so two people do not answer the same one. Either way, give each office a backup inbox or person for days off.
Getting the email delivered
A form notification is an email sent by your website or form service, using your domain. Mail services check whether that sender is allowed to send for the domain. If not, the message may go to spam or be rejected.
Google's SPF setup page lists "Contact us" forms among the senders a domain's SPF record should include, and notes that a record can hold up to 10 include tags. Gmail's sender guidelines require every sender to set up SPF or DKIM, and say messages without them may be marked as spam or rejected.
DMARC adds one more rule: the domain that passes SPF or DKIM has to match the domain in the From line. A form that sends "from" the patient's own address fails that, and Gmail's guidelines say not to impersonate Gmail From headers and to list only actual senders in From.
So send notifications from the group's own address, through a service listed in SPF and set up for DKIM. If your form tool has a reply-to setting, put the patient's address there so the office can answer. Who manages the domain's records is covered in domains and DNS for dental groups.
What the form asks
The W3C's forms tutorial says people prefer short forms, and that asking for more than a task needs makes them more likely to give up. Ask for what the office needs to call back and book, and leave the rest for the visit.
The same tutorial covers the basics that make a form usable for everyone: a visible label on every field, instructions before the form, error messages that say what to fix, and a clear message when the request has gone through. Our accessibility guide for groups has more on testing shared templates.
What the form may ask, where requests are kept, and what an automatic reply may say are questions for your compliance lead. Settle them once for the group, then use the same form on every office page. This is marketing and web guidance. It is not legal advice.
Spam checks without puzzles
Public forms attract junk submissions, and junk can bury real requests. A common fix is a CAPTCHA, but the W3C's note on CAPTCHA says the interactive kind shuts out many people with disabilities, and that many popular versions are no longer very effective anyway.
The same note describes checks that run without asking the visitor to do anything, such as filtering on the server. Prefer those. During each test request, look in the spam folder as well as the inbox, because a filter can catch real requests too.
Office form routing check
Paste one line per office. The check flags offices with no inbox, typos in addresses, personal mail accounts, missing or repeated backups, one inbox or one form page shared by several offices, http pages, and tests that are missing or overdue for the interval you pick.
Sending a test request
- Tell the office a test is coming, so no one tries to book it.
- Open the office page on a phone and fill in the form with a made-up name that says Test and an office email address. Never use a real patient's details.
- Check that the thank-you message shows and that its page address does not contain anything you typed.
- Confirm the request reached the office inbox and the backup, with the office name in the subject. Look in spam too.
- Reply to it and check that the reply goes to the address you entered, not back to the website.
- Write down the date, then remove the test from any system it landed in.
If the form also fires a GA4 event, check that it carries the office label and nothing the patient typed. That setup is in calls, forms, and bookings in GA4 without patient details.
When to test
On a schedule
Pick an interval your team will keep, such as once a month, and put it on someone's calendar.
After a website change
A new template, a form plugin update, or a page move can change where a form sends, or stop it sending.
After an email or domain change
Moving email services, changing DNS, or moving to a new domain can break the records that get notifications delivered.
When staff change
When the person who watches an inbox leaves or changes offices, confirm someone else is reading it.
When an office opens, moves, or closes
A new office page needs its own route, and a closed office's form needs to go away or point to the nearest open office.
Red flags
No one can say where an office's requests go
Write down the inbox for every office before anything else.
Requests sent to a personal mail account
The group may lose them when the account holder leaves.
The patient's email address in the From line
Gmail's sender guidelines say not to impersonate Gmail From headers, and only actual senders belong in From.
No test request in months
A form can stop sending without any error a visitor or the office would see.
A puzzle the patient has to solve
The W3C notes that interactive CAPTCHA tests shut out many people with disabilities.
Form answers in page addresses or analytics
Google Analytics policy says page URLs and form entries sent to Analytics must be free of personal details.
Checklist
Office form checklist
0 of 12 done
Related guides
Building the office pages the forms sit on is in location pages for a multi-office website. Reporting requests by office is in a per-office marketing report.
The map of the other group jobs is marketing a multi-location practice or DSO.
For a multi-office group
DDS Web Solutions builds websites and runs search, ads, and reporting for dental practices. Our team has been building websites since 2014, we have served 100+ practices, and our offices are in Sacramento and San Mateo.
For a group, we can list every office form and where it sends, move requests to inboxes the group owns, fix the SPF and DKIM records for the service that sends form email, and send a test request to each office after every site change.
FAQ
Should each office get its own inbox, or should one team get everything?
Either can work. An inbox per office keeps requests with the people who book them. A central team can cover more hours. With a central team, make the office question required and put the office name in the subject line, so nothing has to be read twice to be routed.
Why do form emails land in spam?
A common cause is that the service that sends them is not listed in the domain's SPF record or is not set up for DKIM, so the message fails the checks mail services use. Another cause is a form that puts the patient's own address in the From line. Send from the group's address and put the patient's address in reply-to.
Is an email inbox the right place to keep appointment requests?
That depends on what the form asks and on the tools you use, and it is a question for your compliance lead. Some groups send requests into a scheduling or patient communication system instead of email. This is marketing and web guidance. It is not legal advice.
What should a test request look like?
Use a made-up name that says Test, an office email address, and a note such as test request, please ignore. Never use a real patient's details. Tell the office before you send it, and remove the test from any system it lands in.
Do we still need a request form if we have online booking?
Not always. Some patients and some visit types do not fit a booking slot, so some groups keep both. If you keep a form, it needs the same routing and testing as the rest.
Can the form send its answers to Google Analytics so we can see which office was picked?
Send the office label only, never what the patient typed. Google Analytics policy says personal details must not be sent to Analytics, including through form fields and page addresses. The office label setup is in the GA4 guide for groups.
Sources
- Gmail Help: Email sender guidelines
- Google Workspace Admin Help: Set up SPF
- Google Workspace Admin Help: Set up DKIM
- Google Workspace Learning Center: Use a group as a Collaborative Inbox
- Microsoft Learn: About shared mailboxes in Microsoft 365
- W3C Web Accessibility Initiative: Forms Tutorial
- W3C: Inaccessibility of CAPTCHA
- Google Analytics Help: Best practices to avoid sending personally identifiable information