February 2026 — Salesforce, a public API, and version history

You can now connect Salesforce Account Engagement, manage RightMessage from your own software or AI assistant, and recover an earlier project setup without rebuilding it. February also brings a closer look at individual flow answers and less repetitive work when setting up surveys.

Connect website answers to Salesforce Account Engagement

Save visitors’ answers to Account Engagement prospects and use their existing fields to personalize your website. Choose Salesforce/Pardot in your integrations, connect through Salesforce, and enter your Business Unit ID. Updates to Salesforce leads and contacts use the field mappings you configure in Account Engagement. Connect Salesforce Account Engagement.

Enlarge

Salesforce Account Engagement connection controls in RightMessage, with no credentials enteredOriginalOriginal

Build with your own tools or AI assistant

The new public REST API lets your software manage questions, flows, widgets, campaigns, forms, offers, and segment groups, plus read analytics and export answers or leads. Create credentials under API Tokens; configuration edits stay in your draft until you publish.

The new MCP connection lets an AI assistant build those changes, inspect visitor profiles and activity, and help design a branching survey. It can also review version history, undo changes, and publish when you ask. Connect your AI assistant.

Bring an earlier setup back into your draft

Automatic version history records saved changes from the app, Righty, the API, and connected assistants. Open Project Backups to review earlier versions and restore the one you need; your current setup is backed up before the restore. Restoring brings that version into your draft, so you can check it before publishing. Restore a version.

Read each visitor’s flow answers together

Use View engagement data in the flow builder to see visitors’ answers together in a table, search by email, and choose a date range. The table includes anonymous visitors who answered questions, readable question headings, and the text people entered for “Other.” Use Export CSV to take those answers with you. Read flow engagement data.

Enlarge

Survey Flow response table with date and outcome filters, recorded answers, and Export CSVOriginalOriginal

Edit personalized pages with clearer controls

The visual editor has a redesigned layout, a Style tab for CSS changes, and Smart Match targeting that identifies elements using more than a CSS selector. Typing no longer repeatedly rescans the page, and your selected element stays highlighted while you edit. Pages built with Next.js, Gatsby, and Nuxt also load more reliably in the editor. Explore the visual editor.

Enlarge

Visual editor Style controls for the WorkForge homepage headline personalizationOriginalOriginal

Set up several answer mappings at once

The flow builder now warns you when questions aren’t connected to your email platform. Click Fix this. to open Sync Questions to Custom Fields, review the proposed fields, and set up the missing mappings together. This is available for integrations that support creating custom fields or accepting new field names. Map several questions at once.

Assign a segment from a flow step

A Set Data step can now use Set Segment to assign a visitor to a segment without asking another question. You can also add several actions to the same step, including adjustments to different scores. Use Set Data actions.

Smaller improvements and fixes

• Number questions can display currency, percentage, or unit decorations while saving a plain number for syncing.
• Custom-field updates made before a visitor identifies themselves are saved for syncing after identification.
• Liquid templates can read nested values from custom fields containing JSON.
• Righty recognizes older email-platform connections instead of incorrectly saying they aren’t connected.
• Flow reporting counts unique visitors who actually reached visible content, rather than inflating totals with repeat visits or routing-only activity.
• Router branches stay in step when you reorder segments or delete their group.
• New widgets start flows from the beginning by default rather than skipping known questions.
• Question options with widget-specific visibility rules no longer break the question.
• Publishing in the app after an API or assistant publish no longer brings back an older configuration.
• Links in widget content are underlined so visitors can recognize them as clickable.