Quickbase in-product messaging
Quickbase leverages in-product messaging channels to reach our administrators and users. All messages are as targeted as possible. For example, if we are making a security improvement that may impact customers, only the accounts impacted and administrators who can act would see the message.
There are four categories of audience we may target.
Note: Being in one group does not exclude a user from being in another.
- Account Administrator: A user logged into Quickbase with support or full administrative permissions to the account and/or realm that a specific app lives within
- App Administrator: This may refer to an app administrator in an application, or a person that has ever had administrative rights in any application
- App Developer (i.e. Builder): A user with create permissions to create / edit / update applications, who may or may not also be an account or app administrator
- User: A consumer of a Quickbase application built by a builder
We aim to keep messaging to a minimum to ensure that users are focused on getting work done.
Regardless of the type of message and audience, Quickbase has a rigorous process to ensure messages are timed appropriately and not overwhelming in quantity to users.
In-product messages generally fall into two categories:
Information surrounding new features or capabilities that are directly related to the task being done by the user, or critical alerts. Examples include:
- security alerts or browser updates needed
- retirement of features
- new feature walkthroughs - only on accounts with the feature active
- announcement of availability of a feature that is included with the user’s subscription - usually in a place that is contextually relevant
- resources available to help customers get more value from the product and could include things like upcoming events or webinars, tools, or relevant content
Asking for information
Quickbase takes feedback very seriously as it ensures that our product is serving the needs of our users. The most valuable type of feedback is feedback that we can gather at the time that a user performs an action relevant to what we are studying. For example, feedback on adding widgets to dashboards is most valuable when a builder is adding one, as opposed to an email survey days or weeks later. This feedback is always optional, and Quickbase will never prevent or impede a user’s ability to get work done in the product.
Additional user opt-ins
Quickbase most often solicits feedback from builders and we have strict controls in place to ensure prompts are spread out to not overwhelm any one person. Additionally, we work with many of you offline to conduct user studies and talk to your users about their experiences and workflow.
To help make this process as smooth as possible and ensure all customers have an opportunity to participate, account administrators can allow Quickbase to extend invitations for feedback to users directly in the product.
Prompts will be as subtle and unobtrusive as possible, never prohibiting a user’s ability to continue getting their work done.
Prompts are hyper-targeted. For example, user studies on dashboards would target only people with appropriate dashboard use.
Prompts are spread out over the course of several weeks automatically.
The opt-ins presented are only for feedback and have no impact on critical alerts or product awareness/walkthroughs.
For more information on Quickbase’s messaging policies, please contact your account team.
Did this page help?
© 1999-2022 Quickbase, Inc. All rights reserved. Legal Notices.