What's new

Until now Intelligence told you what was going on in a Form in broad strokes. This release lets you get specific: which words people use when they answer a particular question, counted exactly as they wrote them.

What's new(6)

• Word cloud. In any Form’s Settings → Analysis, add a Word cloud widget and it shows up in Intelligence → Analytics: the words that repeat most across the answers, larger the more often they appear. It follows the view’s date range and its Real/Test filter.
• You pick the questions behind it. Every text and choice question, or only the ones you check: one specific open question, or two you want to read together. In choice questions each option counts as a whole.
• A literal count, on your rules. Decide whether “Price” and “price” are the same word, whether accents matter, the minimum length, and which words to leave out — your company name, say. Articles and prepositions are dropped for you, in the Form’s language.
• Track the terms you care about. List words or phrases — “integration”, “too expensive” — and the cloud shows only how often each one comes up.
• By mentions or by people. Size each word by how many times it appears, or by how many submissions mention it, so one very long answer cannot drown out the rest.
• No waiting, no AI cost. The cloud is worked out straight from the answers: it covers the submissions you already had, takes none of the slots for AI-filled widgets, and any change to its setup shows immediately.

Fixes(1)

• In the Pipeline editor, setting a minimum or maximum length on an open question no longer stops you from applying your changes.

When a customer asks what you keep about them, or someone on your team wants their trail gone, the answer cannot be opening a ticket with us. This release puts those operations where they belong: inside Foreby, in your hands, with what is about to happen spelled out before you press the button.

What's new(9)

• Two-step verification. In Settings → Security, a setting that is yours rather than the workspace’s: scan the code with Google Authenticator, 1Password, Authy or whichever app you use, and from then on we ask for a six-digit code when you sign in. If your workspace requires it of its owners, we tell you on the way in.
• Export a whole contact. From any contact’s page, Export their data builds a JSON with everything you hold about that person: submissions, answers, Rooms, chat, deliverables, analysis and memory. It is what you hand over when somebody asks to see their data, complete and without asking us.
• Export the entire workspace. In Settings → Workspace, a JSON with all of your tables — Forms, submissions, contacts, Rooms, deliverables, knowledge and memory. It is prepared in the background and a link lands in your inbox, good for 24 hours, so you are not stuck watching a screen.
• Erase everything about a contact in one go. Before you confirm we show you exactly what will go and how many rows there are of each; you type their email, and all of it goes: Rooms, chat, answers, deliverables, analysis, files and memory. Their submissions stay, anonymised — no email, name, answers or company — so your quota and your numbers do not shift because somebody else exercised a right.
• Close a workspace, with 30 days of runway. It goes read-only, with a notice the whole team can see, and its owner can call the whole thing off during that window. After 30 days it is gone, which is exactly why the export button sits right next to it.
• Delete your account, on the same clock. Also reversible, and the Forms you created stay in their workspaces: they belong to the workspace, not to the person. If you are the only owner of one, we name it before letting you go on.
• A version history for your consent text. Every time you change the wording, the link or whether it is required, it is recorded with its exact version, and every submission keeps the one it accepted. When somebody asks what their visitor agreed to back in March, the answer is on screen.
• Consent in template Rooms. A Room that does not come from a Form can ask its visitor to accept the workspace consent the first time they walk in, and it is recorded the same way, with its version.
• Say when a Form collects sensitive data. One switch in the Form’s settings: turn it on and the capture screen always asks for consent, whatever the Start node says.

Improvements(4)

• Password recovery, end to end. Ask for the link, pick a new password, and you are in. If the link has expired we say so in those words and offer you a fresh one, instead of leaving you on a screen that says nothing.
• Passwords that are harder to guess. At least 12 characters, with a lowercase letter, an uppercase letter and a digit. New passwords only.
• A heads-up when you map fields into an integration. The data you send goes to a provider you picked, and the screen now says so where the decision is made.
• We improved the platform’s architecture and security. It is the bulk of this release and nearly all of it happens underneath: nothing you already use has moved.

✕

Until now a Form’s look was filled in inside a Settings section and checked by opening the Form in another tab. That is now Studio, a module of its own inside the Form, right next to Pipeline: you choose on one side, and in the middle are your actual screens —the ones your visitor will see— changing as you go.

What's new(7)

• Studio, in the Form’s Flow group. Three columns: backgrounds on the left, your Form in the middle, the shape of the interface on the right. What sits in the middle is not a mockup — those are the screens of the journey you just built in Pipeline, and you can walk through them.
• One gallery for every background. Solid colour, a gradient of up to six stops with its angle, your own image, and twelve animated backgrounds in two families: Soft —Orbs, Rays, Horizon, Aurora, Mesh, Silk— and Bold —Fan, Tunnel, Cosmos, Pinwheel, Ribbon, Ripple—. Each animated one has its own intensity and speed.
• The background travels with your visitor. It comes to life as the first screen opens, drifts and pulses every time somebody answers, and flares for half a second before the end. Each of the three is a separate switch, and the stage plays them back whenever you want to watch.
• The shape of the interface is yours too. Corner radius, a Solid, Glass or No card sheet, and Filled, Outline or Soft buttons.
• Ten ready-made themes to start from: Dark, Light, Warm ivory, Corporate blue, Corporate aurora, Editorial, Glass night, Minimal light, Neon fan and Cosmos. Applying one fills the fields in and nothing is saved until you hit Save; the values are copied, so your Form will not change because the catalog does.
• We tell you when text will not be readable. Contrast is measured against what your visitor actually has behind the text —the card, the glass or the background— rather than against a colour on paper.
• Nobody gets seasick. Anyone with reduced motion turned on in their system sees a still gradient in those same colours, and on low-end phones the heaviest backgrounds ease off by themselves.

Improvements(5)

• Dark themes are now readable throughout. Field labels, helper text, the «Other» option and the audio recorders were still painted in fixed greys: on a dark card they came out dark on dark. The whole form now follows the theme you picked.
• Glass and No card are readable. Text colour is now worked out against the surface it actually falls on, which is what made those two options hard to use.
• The progress bar stays put when the Form is embedded in your site.
• The closing screen honours reduced motion instead of animating anyway.
• Visual fixes in the Pipeline editor’s node panel.

Until now a Sales Room only came into being when somebody finished a Form, and it was configured inside that Form. Rooms now have their own place in the sidebar: set up a template once, open it for whoever you like —whether they have filled in anything or not— and watch everyone move along a stage board.

What's new(7)

• Room Templates: set the room up once, use it many times. Stages and steps, its own Knowledge Base, design, links and branding. You pick the archetype by reading what each one does, and start from a preset —Client onboarding, or a blank one.
• Open a room for someone who has not filled in anything. Pick a contact, or create one by typing their email, and the room opens with its access already sent. If that person already has a live room from the same template, you are told before anything is created, and you can just open the one that exists.
• A board by stage. Drag a room card from one column to the next, or use its «Move to…» menu, which does exactly the same with a keyboard or on a phone. On a small screen the board becomes a list grouped by stage. Every move is written into the room’s history.
• Stalled rooms flag themselves. A room that has sat in the same stage for too long is marked on the board, and you can filter down to only those.
• A detail view for every room: where it came from, its access —resend or revoke—, who is taking part, how much it has been opened, and the full stage history. It also spells out, right there, why «Open» and «Copy link» are not the same thing: opening identifies you as a team member; copying gives you the clean link you can send to anyone.
• Automatic stage advance, if you want it. The room moves on once the visitor completes every required step of the current stage. The switch tells you what counts towards that and what does not.
• Your visitor sees the whole plan. Their journey is grouped into stages, and the ones still ahead show dimmed, so they know what is left.

A Form now picks its Room instead of configuring one(3)

• A Form’s room is edited in its Room Template. The Form’s «Room» tab is gone; instead the Form chooses which template to use. One room design can serve several Forms, and you fix it in a single place.
• Nothing to redo. Every Form that already used a room has been given its own template, copying exactly what it had. It shows up in the Rooms list with a tag saying which Form it came from and a link back. Your visitors see the same room as always.
• Rooms that already existed join the board. The ones born from a Form now appear in their template’s list and Kanban, alongside the ones you open by hand.

The whole journey is edited in the Pipeline(8)

• The opening screen is the first node on the canvas. Name, email and phone stop being three fixed fields: they are questions you can remove, reorder and retype, and you can add your own. They drag in and out of the group just like any questions stack.
• Save to contact. Any question can write its answer straight onto the contact record: name, email, phone, company, website or a field of your own. Asking for the email partway through identifies the visitor just as asking for it up front does.
• Several endings, one per branch. A Form can finish differently depending on the path the visitor took. Each ending carries its own copy, its destination, its buttons and its own Room Template.
• Creating the Room and redirecting are two separate decisions, with a switch each. You can create the room and still send the visitor back to your site: the room is created anyway and reaches them by email.
• Minimum and maximum length per question. This used to be one value for the whole Workspace; now every text question sets its own, and zero means any answer will do.
• You can skip the opening screen without losing what you wrote in it. Its questions go dormant —configured, but never asked— and the editor says so plainly, so nobody is caught out.
• The Pipeline’s AI chat now edits the opening screen and the endings, and it can also drop a contact into a Room Template, choosing it by name.
• Settings → Success screen is gone: everything that lived there now belongs to the ending it applies to. Old links land on the Pipeline editor.

Improvements(6)

• A visible document is a downloadable one. The separate switch is gone: if you let a visitor see a deliverable, they can take it with them. To actually hide one, its visibility still does that.
• The editor preview follows what you are typing, as you type it, without waiting for a save.
• A Room’s design preview shows the real room. It could previously promise one look and hand the visitor another.
• A teammate who opens a room can read it, not run it. Step controls now appear disabled instead of disappearing, so it is clear what the visitor will do there.
• Ask AI opens on its latest message rather than at the top of the conversation.
• The «Created with Nirby: Foreby» mark now also appears on a Form’s capture screen. On plans that allow it, one switch removes it from all three surfaces at once: the Form, the Room and the access email.

Fixes(3)

• A Form embedded as a popup opens on the click, not a moment later.
• An anonymous Form that identifies the visitor partway through now creates their Sales Room. If the email arrived later in the journey —or was written by a Pipeline action— the ending behaved as though the response were still anonymous: no room and no access email.
• A stage you left unnamed is labelled by its position everywhere it appears, instead of showing blank in some places.

Sharing a Form used to mean sharing a link. Anyone who wanted it on their own site made do with a fixed-height snippet that never grew, never fitted, and that nobody could preview. Now a Form really embeds: under Share → Embed you pick how it should appear, tune how it looks, and copy the code while watching it run.

What's new(5)

• Three ways to embed. Standard, inline on your page like any other section. Popup, over your content, in a corner or as a centered window. Full Page, taking over the screen. Pick one and the screen shows you the result right away.
• What you see is what you paste. The right-hand panel is not a mockup — it is your Form running inside a sample page, with the very code you are about to copy. Anything you submit from there is stored as a test, never as a real response.
• It fits your page. The Form grows and shrinks with its content as the visitor moves through it, can sit left-aligned for narrow columns, and can let your own background show through while keeping its colors and typography.
• The button that opens it is yours. We plant nothing in the corner of your site — a Popup opens from whichever element you choose, be it a button, a link, or on its own after a few seconds.
• On some platforms the link is enough. Paste a Form’s address into Notion and it embeds itself, name included.

Where each response came from(2)

• Every Submission now tells you how it arrived: through a direct link or embedded, and in that case from which page of your site. You will find it in a new block inside the response’s detail.
• Your site can pass data along. Whatever your page carries in its address — a campaign, a plan, the section it was opened from — travels with the response and shows up right there. Nothing to configure: it just needs to be in the URL, or on the button that opens the Form.

Deciding where it can be embedded(3)

• Under Settings → Embedding you can restrict which domains may embed your Workspace’s Forms. While the list is empty — as it is today — any site can, which is how it has always worked.
• It only covers Forms embedded with the current code. Links you share directly, and pages already running an older snippet, keep working anywhere.
• A change to that list takes up to five minutes to reach every visitor.

Improvements(3)

• Every generated document is now its own stop in the Sales Room, with its own marker and in the position you decide, instead of a grid of attachments buried inside the proposal. No existing room changed: the editor keeps the order they already had.
• While a document is still being generated, the room holds its place in the journey, so the progress counter no longer jumps when it shows up.
• When an embedded Form finishes, the Sales Room opens in a tab of its own. It is where the visitor can come back any time, so it deserves a real window rather than a box inside someone else’s page.

Fixes(1)

• The step that asks for a company website now uses your Form’s colors, instead of a fixed dark background that clashed with everything — and that, inside someone else’s page, showed up as a black rectangle.

Design used to live in two places: a set of Workspace-wide settings, and whatever each Form chose to override on top. Changing one Form’s color meant first working out which of the two was winning. Not any more — a Form’s design is set on that Form, under Settings → Design.

No Form changed how it looks. Every one kept the exact colors, logo and image it was already showing.

What's new(3)

• One place to look. Background, the colors of each zone, the logo and the Sales Room image are all edited on the Form’s Design screen. There are no shared settings left that could be quietly overruling what you see.
• The “use global styles” switch is gone. The color editor is always visible, and leaving a field empty means that color falls back to the Foreby default. The grey text inside each field is exactly what will be used if you type nothing.
• Two Forms in the same Workspace can look nothing alike, with neither one dragging the other along — which is what you want when they speak to different audiences.

Changes(3)

• Clearing the logo or the room image now removes it. They used to fall back to a Workspace-wide value; today the Form is simply left without one, which is what the gesture suggests.
• A new Form starts with Foreby’s default look. Add your branding on its Design screen when you want it.
• The old addresses for the Workspace Design and Onboarding settings now land on Settings, so any bookmarks you kept still work.

Improvements(4)

• The Sales Room welcome is now a card with a surface of its own, and its text uses the colors you picked for cards.
• Your company name and the visitor’s name move up into a header of their own. As a result, a Form with no image no longer draws an empty band — the room starts straight into its content.
• The featured video returns to its thumbnail once it scrolls out of view, and the same player now serves both the welcome and video steps.
• The room starts higher up and breathes better: the header is centred and the spare space at the top is gone.