How does requalification work in the Bot? – Fastory

Requalification lets the Bot skip any question it already knows the answer to for a given visitor. The result: a shorter journey, and returning participants who are never asked again for information they have already shared.

What is it for?

When the Bot is about to ask a question, it first checks whether it already knows the answer for this visitor. If it does, the question is silently skipped: neither the question nor the answer is displayed, and the Bot moves straight on to the next step. For the visitor, it is completely seamless.

The known answer is still recorded in your customer knowledge: the participant's contact fills in Audience as if they had answered. However, a skipped question never earns the player any points or prizes.

This is the foundation of progressive profiling: each new campaign only asks for what is still missing, and your loyal participants enjoy an ever smoother journey.

If you are just getting started with the Bot, first check out our article How do I create and set up my Bot?

How the Bot recognizes an already known answer

Each Bot question feeds an attribute of the contact: first name, last name, birth date, postal code, phone number, and so on. These are the same attributes you find on contacts in Audience. The Bot recognizes an already known answer through this attribute, not through the wording of the question.

Direct consequence: within the same workspace, customer knowledge is shared across all bots, all games and the Fanzone. A player who gave their first name in one game will not be asked for it again by the bot of another game in the same workspace, even if the two questions are worded differently, as long as they target the same attribute.

The already known information can come from two sources:

the visitor's previous participations on the same device: they are recognized from one game to the next, even without an account;

their account, if they are signed in: recognition then also works across devices, from mobile to desktop for example.

However, nothing ever travels from one workspace to another. A player who shared their information on one workspace remains a complete stranger on another workspace, even when signing in with the same account: every question will be asked again. The same goes for consents.

Which questions can be skipped?

A question is only skipped when every condition is met: it targets the same contact attribute, the known value is usable (not empty, in a valid format), the Always re-ask this question setting is disabled, and the visitor stays on the same workspace. If a single condition is missing, the question is asked normally.

Question type	Behavior
Free text, first name, last name, birth date, postal code	Silently skipped as soon as the answer is known and valid
Phone number	Skipped only if the known number is stored in international format, with the country code: for example +33 6 12 34 56 78. A number in local format (06 12 34 56 78) is asked again
Single choice	Skipped only if the known answer is still among the available choices
Multiple choice	Skipped only if each known answer still exactly matches one of the available options
Opt-in / consent	Skipped only if the player has already given every consent offered by the question, without unsubscribing since
Terms and conditions	Skipped only if the visitor has already accepted them for this specific game and is signed in to their account
Email	Never skipped: when the email is known, the field is prefilled and the visitor only has to confirm
Rating, barcode scan, media upload, referral code, leaderboard nickname, Instant Win, prize draw and display bubbles	Always displayed. One exception: the leaderboard nickname is prefilled if the player is already identified on the Fanzone

The special case of consents

An opt-in question can offer several checkboxes, each linked to a consent of your workspace: for example Newsletter and Partner offers. The Bot cannot display half a question: it is only skipped if the player has already given every consent it offers. If even one is missing, the whole question is asked again.

Two rules to keep in mind:

unsubscribing removes the consent: the question will be asked again on the next visit;

a consent deleted and then recreated in the workspace settings is a new consent, even if it has the same name: the question will be asked again to everyone. Renaming an existing consent, on the other hand, changes nothing: the agreements already given remain valid.

To review how to create these questions, check out our article How to create and collect opt-ins?

Force the Bot to ask a question again

You always stay in control. Each eligible question has a dedicated setting in the Bot editor:

open the question in the Bot editor;

enable the Always re-ask this question setting;

publish your Bot for the setting to take effect.

Once enabled, the Bot asks the question on every visit, even when it already knows the answer. It is the right tool to re-qualify data that changes over time: preferences, consents to refresh, or information you want to confirm with every campaign.

The setting applies question by question, not globally to the Bot, and it is disabled by default.

What happens in Audience

A silently skipped question counts as a real answer: the contact fills in or updates in Audience, even though the player typed nothing.

Your segments and filters based on attributes (first name, postal code, and so on) and on opt-ins work as usual with requalified answers.

Requalification never creates any points, prizes or extra participations: your leaderboards and prize statistics stay reliable when a player goes through a journey again.

Audience shows one row per visitor and per device: the same player coming back on another browser appears on a new row.

Data takes a few dozen seconds to appear: right after a participation, a row may briefly show up incomplete before filling in on refresh.

When the Bot still asks the question

In some cases, the Bot asks a question even though it already knows the answer:

another workspace: customer knowledge never travels from one workspace to another;

the editor preview: requalification is always disabled there, so you can review your entire journey;

the Always re-ask this question setting enabled on the question;

doubtful information: an empty value or an invalid format is treated as unknown, so the question is asked;

a very fresh answer: an answer just given can take up to 30 seconds to be taken into account. If the player restarts the journey immediately, the question comes back;

an unidentified visitor: if identification fails, because of a network issue for example, the Bot asks every question rather than blocking the player.

Good to know: when a player signs in mid-journey, the Bot replays on screen the answers they just gave, already filled in. This is the normal behavior of visit resume, not a flaw: from their next visits on, these questions will be silently skipped.

Conversely, a question may not be displayed for reasons unrelated to requalification: a conditional journey that routes the visitor down another path, or the skip button when you have enabled it and the visitor chooses to use it.

Best practices

Link each question to the right contact attribute: this is what lets the Bot recognize an already known answer from one experience to the next.

Keep the same attribute from one campaign to the next: changing a question's attribute means starting from scratch, and the question will be asked again to everyone.

Enable Always re-ask this question on data that changes over time: preferences, or a consent to refresh with every campaign.

Rename a consent rather than deleting and recreating it: a recreated consent is a new consent, and the opt-in question would be asked again to your entire audience.

Test requalification in real conditions, outside the preview: in the editor, every question is always displayed.

Concrete use cases

If you want to shorten the journey for your loyal participants

Use the same contact attributes across all the games of your workspace. A player who already gave their first name, postal code and phone number in a first campaign will not have to type them again in the next ones: only their email will be shown, prefilled, for confirmation.

If you want to enrich your customer knowledge campaign after campaign

Add new questions as your experiences go live: already known questions are silently skipped, and each campaign only asks for what is missing. Your database gets progressively qualified, with no friction for participants.

If you want to refresh a consent with every campaign

Enable Always re-ask this question on your opt-in question: the Bot will ask it on every visit, even if the consent was already given.

If you want to keep two brands or entities separate

Use two distinct workspaces: customer knowledge never travels from one workspace to another. Each brand keeps a fully independent database, consents included.

FAQ

What is Bot requalification in Fastory?

Requalification lets the Bot skip a question it already knows the answer to for a given visitor. The question is silently skipped, the journey is shorter, and the known answer is still recorded on the participant's contact in Audience.

Why doesn't the Bot ask a participant some questions?

If the Bot already knows the answer for this visitor, thanks to a previous participation on the same device or to their account if they are signed in, the question is silently skipped. To ask it every time, enable the Always re-ask this question setting in the Bot editor.

How do I force the Bot to ask a question on every participation?

Open the question in the Bot editor, enable the Always re-ask this question setting, then publish your Bot. The setting applies question by question and is disabled by default.

Does requalification work across different games?

Yes, within the same workspace. Customer knowledge is shared across all bots, all games and the Fanzone of the workspace: an answer given in one game benefits the others, as long as the questions target the same contact attribute.

Do a participant's answers travel from one workspace to another?

No, never. Customer knowledge is specific to each workspace: on another workspace, even a player signed in with the same account is treated as a stranger, and every question is asked again.

Can the email question be silently skipped?

No. The email is never silently skipped: when it is known, the field is prefilled and the visitor only has to confirm.

Does a silently skipped question earn the player points?

No. The known answer enriches the contact in Audience, but it never creates any points, prizes or extra participations. Your leaderboards stay reliable when a player goes through the journey again.

Why are all the questions displayed in the editor preview?

Requalification is always disabled in the preview, so you can review your entire journey. Test your experience in real conditions to see questions being silently skipped.

What happens if several people use the same device?

As long as they do not sign in, a visitor is recognized through the device they use. If someone else uses the same browser without signing in, the Bot may skip questions using the previous visitor's answers. This is the normal behavior of device-based recognition.