Quick Answer
In Mailgun, open Receiving and create a Catch All route. Enable forwarding to https://msgsndr.com/mailgun/inbound_webhook, set the priority to 99, and save the route.
Route Email Replies into BizStackPro
Sending an email is only one part of the conversation. Mailgun also needs a receiving route and the proper DNS configuration to capture inbound replies and forward them into BizStackPro.
Without the receiving route or required MX records, replies may not reach your BizStackPro conversations.
Basic workflow: Confirm your Mailgun plan → create a Catch All receiving route → forward messages to the inbound webhook → set Priority 99 → confirm the route → test an email reply.
At a Glance
Mailgun Area
Receiving
Expression Type
Catch All
Route Priority
99
Required DNS Records
MX records
Before You Begin
Confirm that your Mailgun account and sending domain support inbound reply routing.
- Confirm that your Mailgun account has a paid plan that supports receiving routes.
- Make sure the sending or reply domain has been added to Mailgun.
- Confirm that you can edit the domain’s MX records.
- Verify that you are working in the correct Mailgun account or project.
- Keep the BizStackPro inbound webhook address available for the route setup.
Plan requirement: The source instructions specify that reply routing requires at least Mailgun’s Foundation plan and is not available on a free plan.
Create a Receiving Route
The receiving route tells Mailgun how to handle incoming replies. For this setup, Mailgun will forward inbound messages to the BizStackPro webhook.
Step 1: Open Receiving
Log in to Mailgun and open the Receiving tab.
Step 2: Start a New Route
Click Create Route.
Step 3: Select Catch All
Set Expression Type to Catch All.
Step 4: Enable Forwarding
Enable Forward and enter the following webhook address:
https://msgsndr.com/mailgun/inbound_webhook
Step 5: Set the Priority
Set the route’s Priority to 99.
Step 6: Add an Optional Description
Add a recognizable description, such as MG Receiving Route, if you want the route to be easier to identify later.
Step 7: Save the Route
Click Create Route to save the configuration.
Confirm That the Route Was Created
After saving, check the receiving-route list. The new route should show a Catch All expression, Priority 99, and the inbound webhook forwarding action.
catch_all() Priority: 99
forward("https://msgsndr.com/mailgun/inbound_webhook")
If the route does not appear, refresh the page, confirm that the setup was saved, and make sure you created it inside the correct Mailgun account or project.
Important: WIX and MX Records
Inbound Mailgun routing requires MX records. Some WIX configurations may not provide the DNS control needed to add those records correctly.
Step 1: Move DNS Management When Necessary
If WIX does not allow the required MX configuration, move DNS management to a provider such as Cloudflare or another provider that supports the required records.
Step 2: Add the Mailgun Records
Add the MX records and any other Mailgun DNS records required for your sending or reply domain.
Step 3: Verify the Records
After the DNS changes propagate, return to Mailgun and verify the domain’s DNS settings.
If you use a Mailgun subdomain such as mg.example.com, confirm that its MX records are added to that same subdomain.
Test Your Reply Routing
Step 1: Send a Test Email
Send an outbound test email through the configured Mailgun domain.
Step 2: Reply to the Message
From the recipient’s inbox, reply to the test email.
Step 3: Check BizStackPro
Confirm that the reply appears in the appropriate BizStackPro conversation.
Step 4: Review Mailgun Logs if Needed
If the reply does not appear, review Mailgun’s inbound logs, receiving route, and MX records to determine where delivery stopped.
Reply Routing Tips
Confirm the Mailgun Plan
If the Receiving options are unavailable, verify that the account plan supports inbound routing.
Check the MX Records
Inbound routing will not work correctly without the required MX records on the Mailgun domain.
Label Routes Clearly
Use recognizable route descriptions when managing multiple domains or environments.
Review Inbound Logs
Mailgun’s inbound logs can help confirm whether a reply was received and forwarded to the webhook.
Frequently Asked Questions
Do I need a paid Mailgun plan to set up replies?
Yes. The source instructions specify that reply routing requires at least the Foundation plan. Free plans do not support this feature.
How do I create a receiving route in Mailgun?
Open Receiving, click Create Route, select Catch All, and forward messages to https://msgsndr.com/mailgun/inbound_webhook. Set Priority to 99 and save the route.
What should I do if Mailgun replies don’t work with WIX?
If your WIX configuration does not allow the required MX records, move DNS management to a provider such as Cloudflare and add the necessary Mailgun DNS records there.
What will I see once the route is created?
You should see a Catch All route with Priority 99 and a forwarding action that uses the BizStackPro inbound webhook address.
