Q: Can we edit more of the content in the transactional emails.
I love this tool so far, but I have a few major hangups that are making it a little difficult. I despise the fact that, though I can have in-person or hybrid events, everything is referred to as a talk. That leads into my next point. I understand that not all components of transactional emails can be edited, but not all of my "talks" have a link to log in and view, yet the transactional emails imply as much. Is there any way to actually change some of that text? It makes some of the emails unusable, and then I can't create new emails because I'm not on the "Success" plan.
Next, is there any way I can actually get the number of tickets purchased after a completed registration via the API. Right now, I can see the types of tickets purchased, but I can't get the quantity.
Lastly, is it on the roadmap to update the registration fields?
Ben_HeySummit
Jun 20, 2025A: Hey there, thanks so much for reaching out. I'm glad to hear that you're enjoying the tool, albeit with a couple of frustrations along the way.
Firstly, to address your point about everything being referred to as "talks," while this is the default, you can absolutely override this if you need to. To do this, head over to the content area in the dashboard and then go to translations. From there, search for "talks" or "talk" and replace it with whatever word you want to use. So if you want to refer to it as "sessions," "tutorials," etc., you can certainly do so.
In terms of the transactional emails linking to the talks, but not wanting that to happen in some cases, would you mind sharing a bit more information on your use case? Presumably, even with in-person events, you still have a talk page for each talk so that it can be part of the schedule and showcase what will be spoken about. Are you saying that in an in-person scenario, you just don't want any links to that talk at all in emails and simply want to state that it's starting? If you can clarify that, it would be super helpful. We may be able to roll out an update to support this.
Thirdly, in terms of updating the API to include the qty of tickets purchased after a completed registration - would you also mind clarifying your use case here and what you are trying to achieve? Are you saying that you would like to have an API endpoint to query on demand for the total number of tickets sold for the event as a whole, along with a breakdown per ticket type? Essentially, you want to expose this data via our API so that your developers can write code to query it. Is that what you are asking for? If so, please confirm, and we may be able to roll this out for you in the coming days.
Finally, regarding the update of the registration fields, would you mind clarifying what you're trying to achieve here? By default, HeySummit will only ask for a first name and email, plus any payment fields if it's a paid ticket. If you need additional registration fields, you can absolutely add as many as you need via the Setup > Registration Fields. From here, you can create as many fields and field types as you want, whether they're mandatory, dropdown lists, free text fields, etc. Just wanted to double-check that you're aware of that part of the platform? If you were and you're trying to achieve something else, please do share, and I'll see if there's something we can look into in a future update.
Many thanks - really appreciate you sharing your feedback.