Ideas.Bronto.com

\\
\\

Give Feedback

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Implement multiselect fields

    I was a bit surprised to find that Bronto does not support multiselect field types. This would be very useful for us, and I imagine others as well.

    We're asking customers questions such as: which are your favorite brands, please select the ones you like. Right now, we need to make a checkbox field for every brand, and store yes or no for each. We're also asking customers which special types of products they're interested in. With 16 brands and 6 special product types, we need 22 fields for 2 questions. With a multiselect field, we'd only need 2. It…

    20 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Contacts - Fields  ·  Flag idea as inappropriate…  ·  Admin →

    We do plan to create a field type that allows for multiple answers, but do not have an estimated release date right now. This change is a major departure from our current functionality and would impact how fields interact throughout the platform – segments, automation, reporting profiles, etc. It will not be a small project, and will take time to fully complete, but I will keep this ticket updated as more information is available from Engineering.

  2. Realtime producttag usage and preview

    Right now the producttags can only be filled in while sending a message. This gives a big risk, I can only check if the producttags are filled in properly by sending a test message. Though when I send the new message I have to refill all the producttags, if I make a mistake all our subscribers get the wrong product in their newsletter.

    This is a big risk, it also doesn't make sense to not be able to preview the products before the email is sent.

    In this feature using the producttags the products should already be picked within the…

    6 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Contacts - Fields  ·  Flag idea as inappropriate…  ·  Admin →
  3. customsource

    We use the source and customSource fields found in your API documentation to track the source of our customers who have been added to Bronto. Why can't I see these fields in our Contacts Table? Not sure what the point of providing this data to your system if we can't see it within your interface...

    For your reference, this is the API Document:
    http://dev.bronto.com/api/soap/functions/add/addcontacts/

    5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Contacts - Fields  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?
Join the UX Brigade!

Bronto’s User Experience team is interested in hearing from you. Would you like to participate?

Schedule Time Now

Feedback and Knowledge Base