# Custom Welcome email for new users

**URL:** <https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450>\
**Category:** Feature Requests\
**Tags:** email-marketing\
**Created:** [July 3, 2025, 11:09pm UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450 "2025-07-03T23:09:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![akpsolutions](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@akpsolutions](https://community.pickaxe.co/u/akpsolutions)\
**Post date:** [July 3, 2025, 11:09pm UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/1 "2025-07-03T23:09:07Z")

</div>

If I understand correctly: currently, users receive emails from Pickaxe when:

1. they first sign up to a studio (email from studioname@studio.mail to activate their message), and
2. after purchase of any paid product (Stripe purchase confirmation email/invoice.)

I would like to send new users a custom Welcome email once they sign up to a studio. This would be a great opportunity to onboard them, provide custom support/training links and info, etc.

Wishlist/requirements:

- Message body would be rich text, so we can add formatting, links, etc.
- Nice-to-have: Send from custom domain\* or, at least customize the reply-to address

This is what I mentioned to @nathanielmhld during Office Hours last week. Curious to see what others think. For me, I think it would really help conversion. Most people have signed up to gain free Trial credits, but then don’t actually go to the studio/site to use any of the Pickaxes 😢

---

<div class="post-metadata">

**Author:** ![ab2308](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/ab2308/32/1542_2.png) [@ab2308](https://community.pickaxe.co/u/ab2308)\
**Post date:** [July 4, 2025, 2:20am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/2 "2025-07-04T02:20:35Z")

</div>

@akpsolutions, you can achieve this with the APIs (pro plan required). What I do is to run an automation with Make once a day to check if there is any new subscriber (or you can trigger the automation when you receive an email notification from Pickaxe).

I then verify the email, and if legit, I enrol the user into an email sequence

---

<div class="post-metadata">

**Author:** ![akpsolutions](https://avatars.discourse-cdn.com/v4/letter/a/d6d6ee/32.png) [@akpsolutions](https://community.pickaxe.co/u/akpsolutions)\
**Post date:** [July 4, 2025, 2:41am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/3 "2025-07-04T02:41:08Z")

</div>

Great reply @ab2308 I can see how that would work and I was planning to do something similar… using Zapier/Make/n8n (or Zero Work or TaskMagic… so many options!) when we receive the notification email to trigger our send. But that feels like a workaround and not an ideal or long-term solution IMHO.

I think we need something that doesn’t require PRO subscription, as user communication/messaging/welcome is a very important part of the overall CX. Plus, I do think notifications/messages should be immediate.

As Pickaxe is a no-code or low-code solution for non-tech folks, I’d like to see something that doesn’t require additional integrations, automations or subscriptions.

---

<div class="post-metadata">

**Author:** ![ab2308](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/ab2308/32/1542_2.png) [@ab2308](https://community.pickaxe.co/u/ab2308)\
**Post date:** [July 4, 2025, 3:05am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/4 "2025-07-04T03:05:28Z")

</div>

@akpsolutions I hear you. Until then, the only solution without a pro subscription would be triggering the automation when the email about a new subscriber is received

---

<div class="post-metadata">

**Author:** ![felipesuarez](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/felipesuarez/32/4489_2.png) [@felipesuarez](https://community.pickaxe.co/u/felipesuarez)\
**Post date:** [October 4, 2025, 12:03am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/5 "2025-10-04T00:03:51Z")

</div>

custom emails would be awesome.

---

<div class="post-metadata">

**Author:** ![danny\_support](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/danny_support/32/3492_2.png) [@danny\_support](https://community.pickaxe.co/u/danny_support)\
**Post date:** [October 6, 2025, 5:37pm UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/6 "2025-10-06T17:37:11Z")

</div>

Custom Studio emails functionality is on our roadmap. We appreciate your feedback and support.

---

<div class="post-metadata">

**Author:** ![stevecole](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/stevecole/32/550_2.png) [@stevecole](https://community.pickaxe.co/u/stevecole)\
**Post date:** [October 7, 2025, 1:55pm UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/7 "2025-10-07T13:55:33Z")

</div>

This is paramount and basic marketing. It’s why I and a lot of other purchased pickaxe, so we can gain trust and nurture the conversationl. We need to be ablke to do this on the ■■■■■■■ tier as well? I am a tier 3, with add ons.

---

<div class="post-metadata">

**Author:** ![Ned.Malki](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/ned.malki/32/5918_2.png) [@Ned.Malki](https://community.pickaxe.co/u/Ned.Malki)\
**Post date:** [October 21, 2025, 5:20am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/8 "2025-10-21T05:20:20Z")

</div>

I think Nathaniel mentioned during an office hours meeting that they are working on finding a solution to email.

---

<div class="post-metadata">

**Author:** ![dougfresh](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/dougfresh/32/1885_2.png) [@dougfresh](https://community.pickaxe.co/u/dougfresh)\
**Post date:** [October 21, 2025, 10:47am UTC](https://community.pickaxe.co/t/custom-welcome-email-for-new-users/6450/9 "2025-10-21T10:47:56Z")

</div>

I would love this. The workarounds are frustrating
