Submission notifications
What happens when someone submits a form: in-app inbox and email to your team.
In-app inbox
Every new submission, publish change, signature, and webhook failure is stored in Notifications.
Email to your team
GRTforms emails the form's To / CC / BCC list (default To: the account owner). Add field-based routing rules in the builder. Failed sends are never stored as delivered.
Team alerts are sent separately from sign-in mail, so a delay on notifications cannot block signing in.
SMS and WhatsApp (not available yet)
SMS and WhatsApp alerts are built but not turned on yet. Each form's notification settings already show SMS and WhatsApp, marked not available yet.
When they are turned on, SMS and WhatsApp will need a verified phone number. GRTforms will text a one-time code to enter in Settings, or the recipient can reply YES.
Each text will be a short summary: the form name, the main field names, and a link to the entry. By default no answers will be included. If you opt in, answers will be included, including email, phone, files, and signatures.
Recipients will be able to reply STOP to opt out, and we will stop texting that number. If sending a text fails on our side, we will email the form's notification list instead.
Respondent confirmation
Forms can send a receipt to the person who submitted. The toggle is off by default and needs an email field. See respondent confirmation email.