What You Can Be Notified About
While a survey is in the field, Domandata can tell you when something worth acting on happens, in the notification bell and, if you choose, by browser or phone push and by email. These are the same events an AI assistant connected over MCP can watch, with the same options:
- First Response. The survey's first complete.
- Response Milestones. Every N completes, for example every 50th or every 250th. Pick 1 to hear about every complete. Test, preview, screened-out, over-quota, and abandoned responses don't count.
- Response Quality Flags. A new response tripped a data-quality check when it was submitted, such as speeding, straightlining, a failed attention check, a bot score, or a VPN or proxy. Choose Critical Only or Warnings and Critical. Checks that compare a response with the whole sample, like duplicate devices or duplicate open-text answers, only run in Export.
- Quota Nearly Full. A quota crossed a share of its target, 90% unless you pick another level from 50% to 99%. It's an early warning to slow recruitment, rebalance, or tell your panel provider before the cell closes.
- Quota Reached. A quota hit its target and its full action now applies.
Quota alerts follow the same count the quota itself uses, so if a quota has Count completes only on, screen-outs don't move it closer to an alert either. If you raise a quota's target, you're alerted again when it reaches the new target.
Notifications never include respondents' answers: they carry counts, quota names, and quality-flag names only. Open the survey to see the responses themselves.
Milestones and quota warnings use the count recorded when each response was saved, so a burst of simultaneous submissions does not skip a threshold. AI-assistant watches use the same counts.
Set Your Defaults In Settings
Settings → Notifications sets what happens on every survey you own. Turn each event on or off for browser notifications and for email, and once an event is on, set its threshold under Fieldwork Thresholds: how many completes per milestone, the lowest flag severity, and the nearly-full percentage.
Out of the box, milestones (every 50 completes), quota nearly full (90%), first response, and quota reached are on for browser notifications. Quality flags are off, because a survey under a bot attack could otherwise send you one for every submission.
Settings: Notifications
Change It For One Survey
Open a survey's Deploy tab and expand My Notifications. Each event has three choices:
- Use My Default follows your Settings. On a survey you don't own, this means off.
- On notifies you on this survey with the push and email choices and the threshold you set right there, for example milestones every 500 on a large panel study, or warnings as well as critical flags during a soft launch.
- Off silences that event for this survey only.
Each row shows what will actually happen now, so you can check the result without opening Settings. Changes save as you make them.
Open The Deploy Tab
Follow A Survey You Collaborate On
Fieldwork notifications go to the survey's owner by default. Any collaborator who can open the survey, including viewers and commenters, can follow it too: open My Notifications on that survey and set the events they care about to On. These settings belong to you alone; they don't change what the owner or anyone else receives, and they stop if you lose access to the survey.
Your browser and email master switches in Settings always apply. If both are off, notifications still appear in your notification bell.
Set It Up From An AI Assistant
An assistant connected over MCP can read and change your own My Notifications settings for a survey, for example “email me every 100 completes on this survey.” That changes the notifications you receive. To have the assistant itself react to fieldwork, ask it to watch the survey instead; see Connect AI Assistants With MCP.