Additional Message Fields

[glenn-sorrentino]

Use Case

• As an admin, a need to define new questions to ask on my message form, so I can tailor Hush Line to my business needs.

Requirements

• In Settings, an admin can navigate to the Message Template tab to change their message form.
• Field options are in accordion sections
• The collapsed state shows the user-defined field label
• The expanded state allows the admin to:
  • Field Type
    • Choice (Radio group)
    • Choice Dropdown
    • Text
  • Optional Toggle
  • Field Label
  • Contextual field options
  • Hidden toggle
  • Question ordering button group

Mockups

Message Template Settings

Left: New fields added, all sections collapsed
Center: One section expanded, field label in focus
Right: All sections expanded, active section shows an active "Update Question" button (after modifying anything in the section). All other sections haven't been modified, and their update buttons are disabled.

Field Settings Mapped to Message Form

[micahflee]

When an admin defines a message template, should this be the default template now for all users on the instance? Or just for this admin user, and the other users stick with the default template?

Thinking about this, I think this should actually be in the settings for all users, not admins, and each user should get to define their own template. The default template is just an optional contact field, plus the message body. This way, users on tips.hushline.app could choose to add extra fields if they want, just to their forms. And an org that runs their own instance could have different forms for different purposes.

What do you think?

[glenn-sorrentino]

When an admin defines a message template, should this be the default template now for all users on the instance? Or just for this admin user, and the other users stick with the default template?

Thinking about this, I think this should actually be in the settings for all users, not admins, and each user should get to define their own template. The default template is just an optional contact field, plus the message body. This way, users on tips.hushline.app could choose to add extra fields if they want, just to their forms. And an org that runs their own instance could have different forms for different purposes.

What do you think?

I think we should make this per user, as a paid feature for subscribers and single tenant instances.

[micahflee]

Separate fields between plaintext metadata, and encrypted extra fields. The encrypted fields will be encrypted with the user's PGP key. The metadata fields will be filterable.