@nathaniel one more question on the emails – they don’t appear to use the email address of the sender as the ‘user’ account. I’m sending from a user that appears on the user account list as the ‘owner’ for that pickaxe with unlimited uses but I’m still getting the out of credits message after 5 runs. Should the system be using the sender email address to match to a user?
The key for me was the prompt statement (for a book summary agent) - “Create an HTML formatted brief for output. Do not output anything other than the book summary itself. Do not say anything about how to use the summary, just provide the summary.”
I also tell it to use an HTML format I describe below but I don’t believe you need that. For the HTML template I made sure it’s only things that would exist inside tags and to not include the HTML doctype title and other things that would normally appear on a page that can cause issues for an email.
Hi @alexbratton ,
Email deployments don’t currently match the sender’s email to an existing Studio user account. Email interactions are treated as separate “deployment users”, so they won’t inherit the credit balance of any existing user in the Studio. Because of this, even if the sender has unlimited usage on their regular account, the email deployment will still follow the set deployment usage limits.
If matching email senders to existing Studio users is something you’d find useful, we would appreciate it if you could add this as a feature request here in the community forum. This also allows other users to vote on it, so we can prioritize it accordingly.
As, we should fix this and make it so this does work.
Thanks @nathaniel - not really sure how best to use the email ‘deployment users’ without them being able to subscribe and be linked to the web user.
Hi @alexbratton ,
I have reached out to our engineering team about this, so they can address the mismatch between email senders and existing Studio user accounts. We will keep you updated as soon as the fix is in place or as soon as we have additional information to share.
Hi @alexbratton ,
I wanted to follow up with an update. We’ve now implemented support for matching email deployment senders to existing Studio user accounts. This means that when someone interacts with a Pickaxe via email, the system will recognize the sender’s address and associate the interaction with their Studio account.
As a result, the email experience now inherits the correct credit balance, usage permissions, uploaded documents, and user memories tied to that user.
Thank you again for raising this and for your patience while we worked on the update. If you notice anything unexpected, feel free to let me know.
4 Likes
Thanks for the responsiveness - can’t wait to test it out and start rolling out email based solutions for folks.
I finally had a chance to test this out today - a great new feature, thank you to my Pickaxe Santas! Having said that, a few small issues/requests:
As @alexbratton reported, the email replies are not formatted, just come in a mega text block. I don’t think it’s very practical to ask people to request HTML formatting in their email request. Most our users are not tech-savvy, which is why this reply-by-email feature is so awesome. Can you look into modifying so that the responses are nicely formatted? In my test, the PickAxe response that I see in the Studio has bullets and is perfectly formatted, so I would have liked to receive the same nicely-formatted response by email.
Also, not sure if this is a bug or not, but the email response isn’t showing up in the Dashboard as a “Use”. Maybe I need to wait longer?
cc @nathaniel @danny_support
2 Likes
Hi @akpsolutions ,
Thanks so much for the thoughtful feedback, and I’m really glad to hear you’re enjoying the new reply-by-email feature.
On the formatting point, another community member shared a great example showing how they achieved clean, well-structured emails by refining their prompt instructions. While their example was for the email action, the same approach applies to email deployments as well. By explicitly instructing the Pickaxe to format its responses using headings, bullet points, spacing, and emphasis, you can control how the reply-by-email output is structured without requiring end users to ask for formatting themselves.
Regarding the email responses not showing up as a “Use” in the Dashboard, thank you for flagging that. I’ve reported this behavior to our engineering team so they can investigate further.
1 Like
But the test e-mail (e-Therapy) isn’t even replying with a formatted response. Why isn’t the Pickaxe team showing us the formatting capabilities in their own test e-mail???
Hi @jjacoby ,
Thank you for reaching out.
Formatting in Email Deployments is working as expected on our end, and I also just re-tested it successfully.
The key is that the Pickaxe needs clear instructions to output HTML. A good starting point is this Role Prompt, which you can then adjust to your preferred styling and layout:
You are an email deployment. Output only a single, complete HTML document suitable for an email body. Return only HTML and nothing else. Do not use triple backticks or code fences. Your response must begin with < and end with >.
Example of a properly formatted email response when using the role prompt above:
Also, e-Therapy is not a Pickaxe team test email. It is a user-created tool, and its owner may have changed the prompt instructions or formatting settings, which would explain why its output does not appear formatted.
I would like to have my current bots be able to communicate through email as well, so the big question is do Pickaxe bots know when they are sending emails or is this completely different function they have know knowledge? This is important so they wont output HTML unless they are sending an email.
Is there a way to lock down the email to only respond to certain domains? For example only respond to name@mydomain.com and ignore other email. That way it cannot get abused by spammers and keep the information secure.
Hi @gentoolink ,
Thank you for reaching out!
At the moment, that is not currently possible. Please post it in the Feature Requests section of our community forum, so our team can track it more easily and better understand interest from other users as well.