Bulk member imports, milestone bonuses, and your own email templates
Import members in large batches, award a bonus for finishing a milestone group, build a custom email template, and react to a message from automation.
01 ·Import members in large batches
Importing members from a CSV moved to a queue built for large lists, so a broker can bring in a six-figure batch in one run rather than splitting it into batches of a thousand. When some rows have errors, the import keeps the valid members and reports the rest: an upload through the member list shows a preview of who will come in, and an upload through the API records its progress in the API log, then leaves a table and a downloadable report of which members succeeded and which failed with the reason.
Onboarding a brokerage's existing book of clients is usually the first thing a broker does, and the list runs into the hundreds of thousands. Taking the whole file at once and reporting the bad rows instead of refusing the file lets a broker get the community populated and act on the failures separately.
02 ·Award a bonus for a whole milestone group
A milestone group can now carry its own bonus reward on top of the per-stage rewards. A broker turns on the bonus and sets whether the group is progressive, where a member completes the stages in order, or non-progressive, where they finish them in any order, and the reward lands when the whole group is done. The milestone page shows the bonus alongside each group, marks it earned once the group is complete, and a broker can set the map view as the default. Milestones can also display the badges tied to a group or stage, so a member sees what completing it grants them.
A single milestone is a small pull; a whole group finished is a bigger one. Putting a bonus at the end of the group gives a broker a reason for a trader to see the set through, which is how milestone progress turns into repeat visits.
03 ·Build a custom email template
The email templates gain a Custom category, where a broker starts from a blank template and drags in the blocks they want. Alongside the usual content blocks are blocks for roles, tags, and badges: a broker picks the roles or tags from a dropdown or enters an ID, and adds a badge that renders with its art and name in the preview. The result is a template a broker shapes for a message the built-in categories do not cover.
04 ·React to a message from automation
An automation can now react to a message with an emoji. A step takes the member to react as, the message to react to, and the emoji by its name, so a flow can mark a message with a reaction as part of what it does. It joins the other message actions already available to automations.
The batched email notification for replies, mentions, role mentions, and direct messages was rebuilt so each type sits in its own section with a count, shows up to three items before a more banner, and hides a section whose feature is turned off.
15 JulThe member list gained a User ID column, sortable and placed before the name by default, and the column also appears in the downloaded CSV.
15 Jul