Storage, plans and feedback

The places where the product talks to the user about the account itself rather than about what is in it: how much room is left, what a larger plan would add, and what the user makes of the whole thing. All three belong to the provider rather than to any one app, and all three ship with the Provider Edition.

See how much storage is used

Summary A bar at the foot of the folder tree showing how much of the account's storage has been used against what it is allowed, with a line underneath giving the percentage and what is left. Mail and Drive each have their own. In Mail it also warns when a separate limit on the number of messages is getting close.

Why it matters Running out of storage is not gradual from the user's side: mail simply stops arriving, or an upload fails with an error that says nothing about the cause. By then the mailbox has already turned away messages whose senders believe they were delivered. A bar that changes color on the way up makes that visible in advance, with enough warning to delete something or to buy more room. The message-count limit needs a warning of its own, because an account can sit well under its size limit and still be full.

Description

Shown at the foot of the Mail folder tree for mail storage, and of the Drive folder tree for the storage the selected folder belongs to
In Drive the widget names the storage it reports on, so an external space is not labeled File storage
The bar changes color as usage rises, at thresholds the deployment sets — 80% and 90% by default
A line underneath states the percentage used and how much room is left
In Mail, a warning when the account is near its separate limit on the number of messages, by default at 90%
Hidden altogether where there is no limit, except on the dashboard tile, which then says Unlimited

Availability Since 7.10.6 or earlier. Part of the Provider Edition. The thresholds, the bar colors and the wording of both the description line and the count warning are configured per trigger — see the quota widget section of Upsell triggers.

Upsell

Summary A set of places in the interface where an offer to upgrade can appear: a box under a folder tree or in the side panel, a button in the top bar, an entry in the account menu, a message under the storage bar, and a tile on the dashboard. Each is switched on separately and carries its own wording, icon and color. Clicking one takes the user into a checkout.

Why it matters For a provider this is the commercial surface of the product. Somebody on a free mail tier never goes looking for a price list, so the offer has to appear where they meet the limit — at the calendar they cannot open, at the storage bar that has turned red. Choosing each place separately is what keeps that from turning into nagging: the same deployment can show one discreet button, or make every locked app an invitation. Leaving locked features visible rather than hiding them is what lets a user see what they would be buying.

Description

A box under the Mail, Calendar and Address Book folder trees, on desktop and tablet
The same box in the side panel of the apps named in the trigger's app list
An upgrade button in the top bar and an entry in the account menu, on desktop and tablet
A message and a call to action under the storage bar, escalating as the account fills up
An upgrade tile on the dashboard
Apps and actions the user has no capability for stay visible, marked with an upsell icon, and open an upgrade offer when used
A click routes the user into a checkout in one of four configured ways, with the user's context passed through in the URL
An externally hosted checkout page can be shown inside a modal dialog, or the available plans put side by side in a dialog with price, discount, feature list and an upgrade button for each
Every trigger has its own enabled flag, condition, title, description, icon and color, with per-language overrides

Availability Since 7.10.6 or earlier. Part of the Provider Edition. The concept, the checkout options and the configuration are described under Upsell, and the individual trigger ids and their properties under Upsell triggers. The older location io.ox/core//features/upsell/<id> is deprecated but still read.

In-app survey

Summary A dialog that asks the user to rate the product, either on a zero-to-ten recommendation scale or from one to five stars, with a comment field beside it. The question, the notice above it and the comment prompt all come from the OX Count service, which is also where the answers go. It is reached from a floating Feedback button, from the Help menu on desktop, from the account menu on a phone, and from the side panel.

Why it matters A provider who cannot tell whether a release landed well is guessing. A satisfaction survey sent by email reaches the people who answer surveys; asking inside the product, while the user is actually using it, reaches everybody else and gets an answer about the session they are in rather than about what they remember. The rate limiting is what makes that bearable — somebody who has just answered is not asked again, and a quota caps how often anyone is approached at all — so the question stays something people answer instead of something they learn to dismiss.

Description

Two survey types: a zero-to-ten recommendation score (NPS) and a one-to-five star rating
The survey question, the notice text and the comment question come from the service, and the comment field can be switched off
Reached from a floating Feedback button, the Help menu on desktop, the account menu on a phone, and the side panel
A cooldown, a response quota and a survey cycle limit how often any one user is asked, all of it tracked in that user's own settings
Answers are posted to the OX Count service rather than to the Middleware
A survey can be previewed before release, with the URL hash surveyPreview=<id>
This is the current feedback mechanism; it switches itself off where the older feedback capability is present, so the two never run side by side. The older dialog is described under Feedback

Availability Since 8.49. Part of the Provider Edition. Feature toggle surveys, on by default, but it also depends on the count telemetry feature, which is off until the deployment configures the OX Count service.