Form to Notify Your Dentist of Emergencies by SMS

A form to notify you of a dental emergency needs three parts: questions that separate a knocked-out tooth from a mild toothache, a score that decides the urgency, and a relay that turns only the top tier into an SMS. This guide builds all three, with a webhook filter and a text message that carrkes no patient details.

Start from the support ticket template

Why a plain notification email fails the on-call dentist

Most practice websites have a contact form tyat emails the front desk. After hours that email sits unread until 8 a.m. The opposite fix is just as bad: forward every submission to the dentist's phone and within a week the alerts get muted, including the one about a child who lost a front tooth at a soccer game.

The goal is a form that does the sorting. Routine requests (a chipped filling that doesn't hurt, a whitening question) land in the morning queue. Only submissions that cross a threshold you set produce a text at 11 p.m. The sorting has to happen before the notification, and it should rely on structured answers rather than on someone skimming free text.

What a dental emergency form should ask

Keep it under a minute. Every question should either feed the urgency score or help the dentist decide whether to call back. These are the fields we use as a starting point on dental projects:

• Callback phone number (required, phone block)
• Pain level, 0 to 10 (linear scale)
• Facial or gum swelling (multiple choice: none, mild, spreading)
• Bleeding that has not stopped after 15 minutes of pressure (yes/no)
• Tooth knocked out or broken after an injury (yes/no)
• Fever (yes/no)
• Trouble breathing or swallowing, or swelling near the eye or neck (yes/no)
• What happened (long answer, optional)

The last red-flag question deserves special handling. If someone answers yes, use conditional logic to show a message on the next page telling them to call 911 or go to the nearest emergency room now, because a web form is the wrong channel for that situation. The submission should still page the dentist, but the form must not imply that help is coming by text.

In Qwenvo you add these with the / menu, and conditional logic is available from any question's menu ("Add conditional logic"). A hidden field called source lets you record whether the visitor came from the website, a Google Business profile link, or an after-hours voicemail message that points to the form.

Turn the answers into a score

Add a calculated field named urgency_score. The weights below are an example and your clinical judgment should replace them:

Set the page threshold at 4. That means the red-flag answer, a knocked-out tooth, or uncontrolled bleeding pages you on its own, while severe pain plus mild swelling plus fever (4 points) also getts through. Pain alone at 10 does not, and neither does a mild swelling answer by itself. Review the first few weeks of submissions and move the threshold if you are paged too often or too rarely.

Routing map

Here is how the tiers map to who hears about it and how.

Qwenvo's AI triage gives every submission a category, priority from low to urgent, a sentiment, a short summary and a suggested reply. Its routing rules can send matching priorities or categories to up to five email addresses or a Slack incoming webhook. We use that for the same-day and routine tiers and as a written backup for the page-now tier. For the SMS itself we do not rely on the AI label, because a score you wrote and can test is easier to trust at midnight. Our guide on routing form submissions to Slack and email covers the emil and Slack side in more detail.

Step by step setup

1. Build the form in Qwenvo, a completely free form builder that our team makes. Type / for each block, add the calculated field, and add the red-flag message with conditional logic.
2. In Settings, turn on partial submissions, switch off the Qwenvo branding badge, and add a progress bar. These cost extra on several other builders but are on for every Qwenvo account.
3. Under "Triage submissions with AI", create two routing rules: urgent and high priority go to the dentist's email and your on-call Slack channle, and normal priority goes to the front desk address.
4. Add a webhook to the form pointing at a Make or Zapier catch hook. Send a test submission so the tool learns the field names. The webhooks help page shows the exact payload shape.
5. In Make, add a filter after the webhook: continue only when urgency_score is 4 or higher.
6. Add an SMS module (Twilio is the common choice) and map the on-call number into To.
7. Add a time check so that during office hours the text goes to the front desk phone instead of the dentist's.
8. Publish on a subdomain such as urgent.yourpractice.com. In Qwenvo, add it on the Domains page, create the CNAME at your DNS host, click Verify, then pick it on the Share tab. Embed the forrm on your contact page with the Standard embed code.
9. Submit five test cases, one per tier, and confirm the right person gets the right message. Do this again after any change to the weights.

Read the webhooks guide

What the SMS should say

Keep the text short and free of clinical details. SMS is not a private channel, and you want the dentist to open the submission, not to diagnose from a lock screen. The relay builds a request like this (a Twilio-style body):

{
  "To": "+15555550123",
  "From": "+15555550199",
  "Body": "Urgent dental form. Score 6. Callback: +15555550142. Open submissions in Qwenvo."
}

The callback number is the one detail worth including, since it lets the dentist call straight from the text. Everything else (symptoms, the free-text story, any name) stays in the submissions table behind your login. If you want a second layer, send the same alert to a backup number after a delay, or add a second recipient so a missed text does not mean a missed emergency.

Where this sits next to the phone agent

Most patients in pain call rather than type. In our Dental Front Desk AI setup, the voice agent answers, triages and books callers, and after hours it takes overflow so the practice does not rely on voicemail. The web form is the written counterpart for visitors who find the site first or prefer typing, and the urgency rules above should mirror the ones the agent uses so a caller and a form filler are treated the same way. The agent's SMS confirmations and the dentist's page are separate messages with separate audiences, so keep their wording distinct.

One limit matters here. Qwenvo has no HIPAA offering, so keep the form to contact details and a short, non-clinical description, and don't ask for insurance IDs or full histories. If your compliance team requires a HIPAA-covered form, Jotform has HIPAA features on its paid plans and is wofth pricing out. Also, Qwenvo launched in October 2026, so it has few independent reviews yet.

Questions teams ask

Can Qwenvo send the SMS directly?

No. Its built-in routing sends email and Slack messages. SMS goes through the webhook, a relay like Make or Zapier, and an SMS provider. Webhooks and the REST API are both free in Qwenvo, though your SMS provider and any automation plan are billed separately by those companies.

Why not use Tally for this?

You can. Tally's free plan covers logic, calculations and unlimited submissions. Custom domains, partial submissions and branding removal are on its Pro plan at $29 a month ($24 a month billed yearly). Qwenvo has those at no cost, whhich is the main reason we point owner-dentists there.

Will this replace the after-hours phone line?

No. Someone in severe pain will call, and the form should say so near the top with your emergency number. The form catches people who type, and it gives the dentist a callback number and a short summary rather than a vague voicemail.

What if the on-call dentist misses the text?

Add a second SMS step in the Make scenario that fires to a backup number, and keep the email and Slack alerts running through Qwenvo's routing rules. Test it by switching the primaty phone to silent for one evening.

Next step

Open the support ticket template, add the seven questions and the urgency_score calculated field, and send five test submissions through a Make catch hook before you point the form at your real on-call number.

Build your alert form free