Email and scheduling
Turn the next step into an email your customer can use
A conversation should leave the customer knowing what happens next. With Mailgun sending configured, Bob can turn an approved follow-up into a branded email containing the appointment details, requested information, or service recap the customer needs.
Bob sends the follow-up through your Mailgun domain, using the template and approval step you choose.
Use your established email delivery setup
Mailgun handles the delivery infrastructure; Office 168/52 supplies the business context for the message. Your sending domain, templates, and operational setup remain part of the workflow. Bob helps assemble the right information so staff do not have to copy the same conversation into another email screen.
Workflows
Send an approved confirmation
Populate the enabled template with the actual appointment or request details, then submit the message through your configured Mailgun domain.
Follow up with a useful recap
Send the requested summary, next-step instructions, or approved document link after a conversation reaches the appropriate stage.
Surface delivery exceptions
Use available delivery information to distinguish a queued message from a delivery problem and route exceptions for staff attention.
Example workflow
Example workflow
A customer asks for written instructions after arranging a service visit. Bob prepares the approved checklist with the confirmed date and contact details. The configured workflow sends it through Mailgun, and any reported delivery issue can return to the team for follow-up.
Illustrative example, not a live execution log.
Connection and setup
Configure the Mailgun domain, region, and server-side credentials. Select approved templates and connect the delivery events needed by your workflow.
How Bob turns a conversation into a useful next step
Bob starts with the customer's request and the business information you approve. When the workflow needs a current record, Bob retrieves it from the connected service. When the next step changes a record or sends a message, Bob follows the permissions and approval steps you configure. The customer gets a useful next response, and your team gets a clear handoff when a person needs to take over.
Questions
Is Mailgun the same as connecting Gmail?
No. Gmail is a mailbox and conversation source. Mailgun is an email delivery service used by applications and operational workflows.
Does a successful send guarantee inbox delivery?
No. Acceptance, delivery, and recipient engagement are different states. Bob should report the state returned by the provider rather than assuming an email was read.
Who decides what Bob can change or send?
You choose the records Bob reads and the actions he takes. A reply, a record update, or an outbound message follows the approval step you set for that workflow. See the pricing page for plans. This page does not list prices.
Continue this workflow with
These are related workflows, not prerequisites.
Get started with Mailgun
Tell us how your front office handles this job today. You send the message when you are ready.