Form notifications need to reach the right person or team, and a lot of sites default to sending every submission to one inbox regardless of what the form was actually about — this configures routing so a support enquiry, a sales lead, and a general contact message each reach whoever should actually see them.
Form notification routing configuration
Form notifications routed to the right person, not one inbox catching everything.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of which forms need routing configured, and the intended recipient for each
- Any conditional routing logic (a specific field value should route to a specific person)
- Confirmation of who currently receives notifications, so we know what’s being replaced
This or something else?
| You want form notifications routed to the correct person or team, based on form or field values | This fix covers it |
| Notifications aren’t arriving at all, not a routing preference issue | Worth checking Email & Deliverability category fixes, a different point of failure |
| You want the notification email’s content or design changed, not just where it’s sent | A different, related task — worth describing what you want changed |
| You want spam filtered out before notifications are sent, not routing itself | Form spam flood – anti-spam configuration |
What we do
- Confirm the intended recipient for each form, and any conditional routing rules
- Configure routing so submissions reach the correct destination
- Set up conditional logic where a specific field value should determine the recipient
- Test each routing path with a real test submission
- Verify notifications arrive correctly and promptly for each configured path
- Provide a written summary of the routing configuration
What is included
- Form notifications configured to route to the correct recipients
- Conditional routing logic implemented where specified
- Tested confirmation of each routing path with real submissions
- A written summary of the configuration
Not included
- Fixing an underlying email deliverability issue if notifications aren’t arriving at all — a separate, related fix
- Redesigning the notification email’s content or visual template
- Anti-spam configuration, a separate, related fix if spam volume is also a concern
- Ongoing routing changes as your team structure changes
Questions about this fix
Can different fields on the same form route to different people?
Yes, if you specify the logic (for example, a dropdown selecting "Sales" versus "Support"), we can configure routing that sends the notification to the appropriate person based on that answer.
What if I want more than one person to receive certain notifications?
That's a straightforward configuration — we can set multiple recipients for a given form or condition rather than limiting it to a single person.
Will this affect what data is included in the notification email itself?
Not unless separately requested — this fix addresses where the notification goes, not what information it contains, though we can discuss content changes as a related, additional task.
What happens to notifications that were misrouted before this fix?
This addresses routing going forward — past notifications already sent to the wrong recipient aren't retroactively redirected, though the underlying form entries themselves remain safely stored regardless.
How do I update routing myself later if my team changes?
Depending on how it's configured, this is sometimes something you can adjust yourself afterward — we can document how, or handle updates as a small, separate fix when your team structure changes.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.