> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/managing-subscriptions/sending-roadmap-emails-from-your-own-address.md).

# Sending Roadmap emails from your own address

Have the emails Roadmap sends on your store's behalf, like the Payment Method Update email, come from your own email address: how to request it and verify your sender.

When Roadmap emails a customer on your store's behalf, the most important being the **Payment Method Update** email in the $1-checkout payment recapture flow, the email is sent through Roadmap's email provider, SendGrid.

Until you set up your own sender, these emails go out from Roadmap's default address, `noreply@roadmap.gadget.app`, and inboxes like Gmail show them as **roadmap** *via gadget.app*.

If you'd rather those emails arrive from your own address, for example `hello@yourstore.com`, Roadmap can register your address as a verified sender. The setup is done for you by Roadmap support; your part is a single verification click.

### Set up your sending address

{% stepper %}
{% step %}

#### Contact Roadmap support

Message support through the in-app chat with the email address you want Roadmap to send from. Use an inbox you can access, since the verification email lands there.
{% endstep %}

{% step %}

#### Watch for the verification email

Once support registers your address, SendGrid emails it directly: subject **Please Verify Your Single Sender**.
{% endstep %}

{% step %}

#### Click Verify Single Sender

Open the email and click **Verify Single Sender**. The link stays active for 48 hours; if it expires, ask support to resend it.
{% endstep %}

{% step %}

#### You're done

Once the sender is verified, Roadmap's emails send from your address.
{% endstep %}
{% endstepper %}

### If your domain needs verifying too

Some stores also need to verify their sending domain before the address can be used. This is about deliverability: it proves to inboxes that Roadmap is allowed to send email for your domain. If your store needs this step, Roadmap support will let you know and guide you through it.

### The emails this affects

The sending address applies to the emails Roadmap sends to your customers on your behalf. The one most stores care about is the **Payment Method Update** email: when a subscription payment fails, or a customer's card needs replacing, you can send them a checkout link to capture a new payment method via the $1-checkout flow.

* [Updating a customer's payment method](/subscriptions/managing-subscriptions/updating-a-customers-payment-method.md): when and how to trigger the recapture flow
* [Customizing the Payment Method Update email](/subscriptions/managing-subscriptions/customizing-the-payment-method-update-email.md): edit the subject and body of the email itself

### Related guides

* [Updating a customer's payment method](/subscriptions/managing-subscriptions/updating-a-customers-payment-method.md)
* [Customizing the Payment Method Update email](/subscriptions/managing-subscriptions/customizing-the-payment-method-update-email.md)
* [Failed payment retries](/subscriptions/pricing-and-billing/failed-payment-retries.md)
* [Email notifications and templates](/forms/email-notifications-and-templates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roadmap.so/subscriptions/managing-subscriptions/sending-roadmap-emails-from-your-own-address.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.