Hear from every visit,
while it is fresh.

135 of 135 capabilities shown

• Emoji face ratingQuestion answered by tapping one of a row of face icons; can be scored as CSAT in the designer.Survey builder

  How it is used

  Customer taps a face; the selected face is highlighted.

  The problem

  Rating scales are slow to read at a busy exit.

  The outcome

  A one-tap rating that needs no reading of numbers.

  For example

  'How was your visit today?' at a branch exit.

  Product screen

  Rating question

• Star ratingQuestion answered on a star scale; can be scored as CSAT.Survey builder

  How it is used

  Customer taps a star.

  The problem

  Different questions suit different scales.

  The outcome

  A familiar rating format for staff or service ratings.

  For example

  'How would you rate the service you received?'

• 0-10 recommendation scaleEleven-point 0-10 scale used for a 'how likely are you to recommend us' question; can be scored as NPS.Survey builder

  How it is used

  Customer taps a number from 0 to 10.

  The problem

  Leadership asks for a recommendation measure comparable across locations.

  The outcome

  A recommendation score captured at the visit.

  For example

  'How likely are you to recommend us?'

  Product screen

  Numeric rating question

• Numeric scale (effort or rating)Configurable numeric scale question, for example an effort question scored as CES.Survey builder

  How it is used

  Customer taps a number on the scale.

  The problem

  Teams need to know how hard a task was, not only whether customers were satisfied.

  The outcome

  An effort measure alongside satisfaction.

  For example

  'How much effort did it take to get your banking done?'

  Product screen

  Survey designer: questions and live preview

• Multiple choiceQuestion with a list of tap-to-select answer options.Survey builder

  How it is used

  Customer taps one option.

  The problem

  Open-ended answers are slow to collect and analyse.

  The outcome

  Structured reasons behind a score.

  For example

  'What stood out?' with options such as speed or staff.

  Product screen

  Multiple-choice question

• Free-text questionOpen question where the customer writes a comment.Survey builder

  How it is used

  Customer types on the on-screen keyboard.

  The problem

  Scores alone do not explain what went wrong.

  The outcome

  Customers describe the experience in their own words.

  For example

  'Anything else we should hear?'

• Comment purpose tagsFree-text questions can carry a purpose (e.g. general, complaint, suggestion, compliment, inquiry).Survey builder

  How it is used

  Administrator selects a purpose in the designer.

  The problem

  Comments mixed together are slow to sort.

  The outcome

  Comments grouped by purpose for review.

  For example

  Separating complaints from suggestions.

• CSAT, NPS and CES scoringEach question can be marked to score as CSAT, NPS or CES.Survey builder

  How it is used

  Administrator chooses the score type per question in the designer.

  The problem

  One vague overall score hides where the experience breaks down.

  The outcome

  Standard satisfaction, recommendation and effort measures from the same survey.

  For example

  Branch survey combining satisfaction, effort and recommendation questions.

  Product screen

  Survey designer: questions and live preview

• Survey list and versionsList of surveys with status (draft/published), version, assigned terminal count and last update; create a new survey.Survey builder

  How it is used

  Administrator searches, filters by status, opens or creates a survey.

  The problem

  Teams lose track of which survey runs where.

  The outcome

  One list showing each survey's status and where it is deployed.

  For example

  CX team managing several branch surveys.

• Survey designer with question listBuilder for adding, ordering and configuring questions, with type, score and required/optional flags.Survey builder

  How it is used

  Administrator adds questions and reorders them with up/down controls.

  The problem

  Changing surveys usually needs IT or a vendor.

  The outcome

  Business teams edit surveys themselves.

  For example

  CX manager adjusting questions for a new service.

  Product screen

  Survey designer: questions and live preview

• Live preview (portrait and landscape)Preview pane showing each survey screen (idle, steps, each question, thanks) at reduced scale, in portrait or landscape.Survey builder

  How it is used

  Administrator steps through preview tabs and toggles orientation.

  The problem

  Surveys published without preview look wrong on kiosks.

  The outcome

  Administrators see what the customer will see before publishing.

  For example

  Checking a survey on a portrait counter tablet.

  Product screen

  Survey designer: questions and live preview

• Welcome and thank-you text editingDesigner tab for editing the welcome and thank-you screens.Survey builder

  How it is used

  Administrator edits text in the 'Welcome & Thanks' tab.

  The problem

  Generic messages do not match the location or brand.

  The outcome

  Opening and closing messages written for each survey.

  For example

  Tailoring the welcome for a hospitality outlet.

  Product screen

  Survey designer: questions and live preview

• Safe versionsEdit the next version of a survey while the current version stays live.Survey builder

  How it is used

  Administrator edits a draft version and publishes when ready.

  The problem

  Editing a live survey disrupts collection.

  The outcome

  Changes are prepared without interrupting live surveys.

  For example

  Updating a question set mid-quarter.

  Product screen

  Survey designer: questions and live preview

• Pre-publish readiness checksPublish dialog lists problems to fix before a survey can go live.Survey builder

  How it is used

  Administrator reviews 'Fix before publishing' items.

  The problem

  Errors reach customers.

  The outcome

  Problems are flagged before any customer sees them.

  For example

  Publishing a new multilingual survey.

  Product screen

  Survey designer: questions and live preview

• Number input questionRespondent enters a number as the answer.Survey builder

  How it is used

  Respondent types a number on an on-screen keypad.

  The problem

  Some questions need a count or amount rather than a rating.

  The outcome

  Numeric answers collected without a free-text field.

  For example

  "How many times have you visited this month?"

• Required or optional questionsEach question is marked required or optional.Survey builder

  How it is used

  Administrator sets the flag; it shows in the question summary line.

  The problem

  Mandatory questions everywhere raise abandonment.

  The outcome

  Only essential questions block completion.

  For example

  Rating required, comment optional.

  Product screen

  Survey designer: questions and live preview

• Scale size selectionChoose how many points a scale has.Survey builder

  How it is used

  Administrator selects the scale size.

  The problem

  One fixed scale does not fit every question.

  The outcome

  The scale matches the question being asked.

  For example

  A five-point rating and a seven-point effort scale in one survey.

• Autosave with saved statusChanges in the builder save automatically and a saved indicator shows the state.Survey builder

  How it is used

  No action; administrator sees "Saved".

  The problem

  Lost edits discourage teams from refining surveys.

  The outcome

  Edits are kept without manual saving.

  For example

  Editing a survey across several sessions.

  Product screen

  Survey designer: questions and live preview

• Publish confirmation of immediate replacementBefore publishing, a confirmation states that the live version will be replaced immediately on assigned terminals.Survey builder

  How it is used

  Administrator confirms the publish dialog.

  The problem

  Teams publish without realising kiosks change at once.

  The outcome

  Publishing is a deliberate step with a clear consequence.

  For example

  Publishing a revised survey during branch hours.

• Publish and assign in one actionA survey can be published and assigned to terminals in the same step.Survey builder

  How it is used

  Administrator selects terminals and publishes.

  The problem

  Separate publish and assignment steps leave surveys live nowhere.

  The outcome

  A new survey reaches the chosen kiosks in one step.

  For example

  Launching a survey to a new branch.

• Tabbed survey builderThe builder is organised in tabs: Questions, Welcome & Thanks, Branding and QR code.Survey builder

  How it is used

  Administrator moves between tabs.

  The problem

  Long single-page editors hide settings.

  The outcome

  Each part of a survey has its own place.

  For example

  Reviewing branding without scrolling past questions.

  Product screen

  Survey designer: questions and live preview

• Inline survey renameRename a survey directly in its header.Survey builder

  How it is used

  Administrator edits the title in place.

  The outcome

  Survey names stay accurate as they evolve.

  For example

  Renaming a pilot survey for wider rollout.

• Interactive test run of a surveyAuthors can click through the full kiosk flow (welcome, language choice, pre-survey steps, questions and thank-you) as a respondent would, trying different answers to test conditional questions, early finish and languages; no answers are saved.Survey builder

  How it is used

  A survey author opens the preview from the builder and taps through it, including leaving it idle to see the time-out prompt.

  The problem

  Logic errors and wording problems are found only after a survey is live on kiosks.

  The outcome

  Surveys are tested end to end without adding test answers to real results.

  For example

  An author checks that a low rating ends the survey early before publishing.

• Survey run dates and time-bound assignmentsA survey can carry start and end dates, and each assignment can have its own start and end dates; kiosks accept responses only while the survey is published, active and within its dates.Survey builder

  How it is used

  An administrator sets dates on the survey or on an assignment row when planning a campaign.

  The problem

  Campaign surveys stay on kiosks after the campaign ends, mixing unrelated feedback into results.

  The outcome

  Surveys collect responses only during their intended period without manual switching.

  For example

  A survey about a seasonal promotion runs at selected branches for its four weeks only.

• Duplicate a surveyAny survey can be copied as a new design, keeping its linked images, to start from an existing one.Survey builder

  How it is used

  An administrator chooses Duplicate on a survey and edits the copy.

  The problem

  Building similar surveys for each campaign or site from scratch is slow and inconsistent.

  The outcome

  New surveys start from an existing design.

  For example

  A team copies its branch survey to create a variant for a new service.

• Custom score for each answer optionEach point on a rating scale carries its own numeric score and can be marked negative; scores are normalised to the scale's range so a five-point face scale and an eleven-point numeric scale feed the same measure consistently.Survey builder

  How it is used

  An administrator sets the score of each scale point when defining a rating question.

  The problem

  Mixing scale types makes satisfaction figures inconsistent or meaningless.

  The outcome

  Different question styles roll up into comparable CSAT, NPS and CES figures.

  For example

  A survey uses a face scale for one question and a numeric scale for another, both feeding CSAT.

• Multiple-choice with multiple selection limitsMultiple-choice questions can allow one or several answers, with a minimum and maximum number of selections and a hint such as 'Choose up to 3'.Survey builder

  How it is used

  An administrator sets the selection limits; the respondent sees the hint and selects options.

  The problem

  Single-answer questions cannot capture several reasons for a visit or complaint.

  The outcome

  Richer answers without free text.

  For example

  Customers choose up to three reasons for their visit.

• Responses tied to the version answeredEach response stays attached to the exact survey version that was on screen, and only answers that match that version's questions and options are accepted.Survey builder

  How it is used

  No action needed; administrators edit and republish as usual.

  The problem

  Changing survey wording mid-year corrupts trend reporting.

  The outcome

  Trends stay trustworthy across survey revisions.

  For example

  A team rewords a question without distorting last quarter's results.

• Smart logic: conditional questionsShow a question only when conditions on earlier answers are met.Conditional logic

  How it is used

  Administrator opens Logic, picks a question, an operator and values.

  The problem

  Asking every customer every question lengthens surveys.

  The outcome

  Follow-up questions appear only when relevant.

  For example

  Ask 'what went wrong?' only after a low rating.

• Smart logic: AND / OR conditionsCombine several conditions with AND or OR.Conditional logic

  How it is used

  Administrator adds conditions and toggles AND/OR.

  The problem

  Simple rules cannot express real service scenarios.

  The outcome

  More precise question targeting.

  For example

  Ask a question only for a low rating at a specific service.

• Smart logic: finish survey earlyEnd the survey when an answer meets a condition, for example a rating within a set range.Conditional logic

  How it is used

  Administrator sets a 'Finish survey if' rule.

  The problem

  Satisfied customers are asked unnecessary follow-ups.

  The outcome

  Shorter surveys for respondents who have nothing more to add.

  For example

  End after a top rating with no complaint.

• Smart logic: target by department or serviceShow a question only for chosen departments or services.Conditional logic

  How it is used

  Administrator selects catalogue items in the question’s conditions.

  The problem

  One survey for all services asks irrelevant questions.

  The outcome

  Questions specific to a service or team.

  For example

  A technical-support-only question.

• Logic validation warningsDesigner flags incomplete logic, for example a condition with nothing selected to match.Conditional logic

  How it is used

  Administrator sees an inline warning and fixes the rule.

  The problem

  Broken rules silently hide questions.

  The outcome

  Logic errors are caught while editing.

  For example

  Editing a long branch survey.

• Conditions on answer rangesA condition can match a range of answers, for example any rating from 1 to 3.Conditional logic

  How it is used

  Administrator sets a range in the condition.

  The problem

  Listing every low score separately is slow and error-prone.

  The outcome

  Follow-ups target a band of answers in one rule.

  For example

  Ask "What went wrong?" for ratings 1-3.

• After-question continue or finish ruleEach question can carry a rule to continue or to finish the survey depending on its answer.Conditional logic

  How it is used

  Administrator sets "After this question: continue / finish if...".

  The problem

  Surveys run past the point where more questions add nothing.

  The outcome

  Short surveys for respondents with nothing more to add.

  For example

  Finish after the first question when the rating is top-score.

• Answered, skipped and comparison conditionsConditions can test whether an earlier question was answered or skipped, as well as is, is not, at least, at most, more than, less than and between.Conditional logic

  How it is used

  An administrator picks the operator when building a condition.

  The problem

  Simple equality rules cannot follow up skipped questions or score bands.

  The outcome

  Follow-up questions appear only when they are relevant.

  For example

  A comment question appears only when the rating question was skipped or scored at most 2.

• Multilingual survey contentAdd survey languages, set order and default, and edit translated strings.Multilingual experience

  How it is used

  Administrator searches and adds languages, sets default, edits strings.

  The problem

  Maintaining separate surveys per language is error-prone.

  The outcome

  One survey offered in several languages.

  For example

  Bilingual English/Arabic branch network.

  Product screen

  Choose your language

• Missing-translation warningLanguage menu shows how many strings remain untranslated before publishing.Multilingual experience

  How it is used

  Administrator sees the remaining-strings count and completes them.

  The problem

  Surveys launch with untranslated text.

  The outcome

  Gaps in translation are visible before customers see them.

  For example

  Adding Arabic to an English survey.

• Custom language entryAdd a language not in the list by custom input.Multilingual experience

  How it is used

  Administrator enters a custom language.

  The problem

  Required languages may not be in a fixed list.

  The outcome

  Languages beyond the preset list can be added.

  For example

  Organisation serving a less common language group.

• Scale point labels per languageEvery point on a scale can carry its own label in each survey language.Multilingual experience

  How it is used

  Administrator types a label for each point, per language.

  The problem

  Unlabelled scales are read differently by different customers.

  The outcome

  Respondents see what each point means in their language.

  For example

  Effort scale labelled from "Very hard" to "Very easy" in English and Arabic.

• Arabic right-to-left renderingArabic surveys render right to left on respondent screens.Multilingual experience

  How it is used

  Respondent selects Arabic; screens mirror for right-to-left reading.

  The problem

  Arabic text in a left-to-right layout reads poorly and looks foreign.

  The outcome

  Arabic-speaking customers get a native layout.

  For example

  A bilingual English and Arabic branch network.

• Per-language editing modeA language switcher in the survey header puts the builder into editing mode for one language.Multilingual experience

  How it is used

  Administrator picks a language in the header and edits its strings.

  The problem

  Translating in a separate file loses context.

  The outcome

  Translations are edited in place, beside the source layout.

  For example

  Adding Arabic to an English branch survey.

• Copy-source helper in translation fieldsA translation field offers the source text to copy as a starting point.Multilingual experience

  How it is used

  Administrator copies the source string into the field and edits it.

  The problem

  Retyping brand names and numbers in each language causes errors.

  The outcome

  Faster, more consistent translation of shared terms.

  For example

  Keeping a product name identical across languages.

• Default survey languageOne language is set as the survey default.Multilingual experience

  How it is used

  Administrator sets the default in the language menu.

  The problem

  Without a default, respondents may meet an unexpected language.

  The outcome

  A predictable starting language for each survey.

  For example

  Arabic default, English offered.

• Language order in the respondent pickerThe order in which languages appear on the respondent language screen can be changed.Multilingual experience

  How it is used

  Administrator reorders the survey languages.

  The problem

  The most common language should be the easiest to pick.

  The outcome

  The language screen matches each location's audience.

  For example

  Arabic first in one region, English first in another.

  Product screen

  Choose your language

• Publish blocked while translations are incompleteA survey cannot be published while any of its languages has missing strings.Multilingual experience

  How it is used

  Administrator sees the block in the readiness panel and completes the strings.

  The problem

  Customers meet untranslated text in a live survey.

  The outcome

  No survey goes live with a missing translation.

  For example

  Adding Arabic and being stopped until every Arabic string exists.

• Live preview in any survey languageThe preview can be switched to any survey language.Multilingual experience

  How it is used

  Administrator toggles the preview language.

  The problem

  Translations are often checked only after publishing.

  The outcome

  Each language is reviewed on the kiosk layout before going live.

  For example

  Checking the Arabic layout before publish.

• Catalogue entries named in every languageEach department and service entry has a name in every survey language.Multilingual experience

  How it is used

  Administrator enters each name per language.

  The problem

  Attribution options in only one language confuse respondents.

  The outcome

  Respondents see attribution options in their own language.

  For example

  Arabic and English service names on the attribution step.

• Searchable language catalogue with Spanish as a configured survey languageSurvey languages dialog lists offered languages (English default, Arabic with "2 strings left", Spanish "Complete") with order arrows, default star and delete, plus "Add a language" search over a long list (Afrikaans, Albanian, Amharic, Armenian, Azerbaijani...). Response log shows responses taken in English, Arabic and Español.Multilingual experience

  How it is used

  Administrator searches and adds languages, sets order and default.

  The problem

  Adding a survey language should not need a new survey.

  The outcome

  Surveys can be offered in languages beyond English and Arabic, as designed.

  For example

  A team adds Spanish to an existing survey and sees which languages are complete.

• Kiosk welcome screenOpening screen that invites a customer to start a survey on a kiosk or tablet.Kiosk and digital feedback

  How it is used

  Customer taps the screen to begin.

  The problem

  Feedback requests at the point of service are easy to ignore without a clear entry point.

  The outcome

  A visible, single-tap start to the survey at the counter or exit.

  For example

  Bank branch counter tablet inviting feedback after a visit.

  Product screen

  Survey welcome screen

• Language choice at survey startScreen where the customer picks the survey language before answering.Kiosk and digital feedback

  How it is used

  Customer taps a language button.

  The problem

  Customers who do not read the default language skip the survey or answer poorly.

  The outcome

  Each respondent answers in a language they choose.

  For example

  Branch serving Arabic- and English-speaking customers.

  Product screen

  Choose your language

• Which service, which teamAn optional step before the questions asks which department or service the customer dealt with, using options from the organisation’s catalogue.Kiosk and digital feedback

  How it is used

  Customer taps an option, or skips if skipping is enabled.

  The problem

  Scores that cannot be traced to a team or service are hard to act on.

  The outcome

  Each response is linked to the department and service involved.

  For example

  Branch with separate billing, customer service and technical support desks.

  Product screen

  Multiple-choice question

• Thank-you completion screenClosing screen confirming the response was received.Kiosk and digital feedback

  How it is used

  Shown automatically after the last answer.

  The problem

  Customers are unsure whether their feedback was recorded.

  The outcome

  A clear end to the survey and a kiosk ready for the next person.

  For example

  Exit kiosk in a retail store.

  Product screen

  Thank-you screen

• Back, skip and progress indicatorRespondent screens show Back and Skip controls and a 'Question N of N' progress indicator.Kiosk and digital feedback

  How it is used

  Customer taps Back to revise, Skip to pass an optional question, and sees progress dots.

  The problem

  Long or rigid surveys cause abandonment.

  The outcome

  Respondents know how much remains and can skip optional questions.

  For example

  Any kiosk survey with optional questions.

  Product screen

  Numeric rating question

• Inactivity session resetWhen a respondent walks away mid-survey, a countdown 'Still there?' prompt appears and the session resets.Kiosk and digital feedback

  How it is used

  Customer taps 'I'm still here' to continue; otherwise the kiosk returns to the start.

  The problem

  Abandoned half-finished surveys block the kiosk and mix answers from two people.

  The outcome

  The kiosk clears itself for the next customer.

  For example

  Unattended kiosk at a busy branch exit.

• On-screen keyboard with Arabic switchKiosk free-text entry uses an on-screen keyboard with a numeric mode and an Arabic layout key.Kiosk and digital feedback

  How it is used

  Customer types directly on the kiosk screen.

  The problem

  Kiosks without a physical keyboard cannot collect written comments.

  The outcome

  Written comments can be collected on a touch kiosk.

  For example

  Tablet on a counter collecting comments.

• Idle screen and promo itemsScreens tab for idle content and promo items shown between customers.Kiosk and digital feedback

  How it is used

  Administrator adds promo images to the idle screen.

  The problem

  Idle kiosks waste screen space.

  The outcome

  The kiosk shows the organisation's message while waiting.

  For example

  Branch promoting a service between respondents.

• QR code and web link surveyThe same survey opens in a phone browser from a QR code or link, with QR in brand colour/logo and PNG/SVG download.Kiosk and digital feedback

  How it is used

  Customer scans the QR code; administrator downloads the code.

  The problem

  Locations without a kiosk cannot collect feedback.

  The outcome

  Feedback from a phone browser, without installing an app.

  For example

  QR codes on restaurant tables or counters.

• One QR code per branchA separate QR code per branch so answers are credited to the right location.Kiosk and digital feedback

  How it is used

  Administrator generates and prints a code per branch.

  The problem

  Web responses without location cannot be compared.

  The outcome

  Phone responses attributed to the correct branch.

  For example

  Multi-branch retailer comparing stores.

• Email survey linkShare a survey link by email from the QR and web link tab, for the whole survey or for one location.Kiosk and digital feedback

  How it is used

  Administrator selects "Send by email".

  The problem

  Teams without a kiosk need a simple way to send the survey to a site or a contact.

  The outcome

  The survey link reaches the people who will display or share it.

  For example

  Sending each branch manager the link for their branch.

• Promo loop timingImages and clips rotate on the idle screen, with a set number of seconds per slide.Kiosk and digital feedback

  How it is used

  Administrator adds promo items and sets the seconds per slide in the Welcome & Thanks tab.

  The problem

  A fixed idle screen is ignored by people passing the kiosk.

  The outcome

  The kiosk shows a rotating set of the organisation's messages between respondents.

  For example

  Branch rotating three service notices on the counter kiosk.

• Configurable idle timeoutSets how long the kiosk waits without input before returning to the idle screen.Kiosk and digital feedback

  How it is used

  Administrator sets the timeout in seconds in the Welcome & Thanks tab.

  The problem

  A half-finished survey left on screen confuses the next customer.

  The outcome

  The kiosk returns to its start state after a set period of inactivity.

  For example

  Busy branch exit where customers often walk away mid-survey.

• Welcome screen switch-offThe welcome screen can be turned off so the survey opens directly on the first step.Kiosk and digital feedback

  How it is used

  Administrator turns off "Show welcome screen".

  The problem

  Some placements need the first question visible immediately.

  The outcome

  Surveys can start without an attract screen where that suits the placement.

  For example

  Tablet handed to a customer by staff at the end of a visit.

• Portrait and landscape renderingThe same survey renders in portrait and landscape without a separate design.Kiosk and digital feedback

  How it is used

  Administrator previews both orientations; the kiosk renders the one it is mounted in.

  The problem

  Different kiosk mounts would otherwise need separate surveys.

  The outcome

  One survey serves portrait kiosks and landscape tablets.

  For example

  Network mixing floor-standing portrait kiosks and counter tablets.

• Skippable pre-survey stepsEach pre-survey attribute step can be marked skippable on its own.Kiosk and digital feedback

  How it is used

  Administrator marks a step skippable; the respondent sees a skip option on that step.

  The problem

  Forcing customers to name a department before rating loses responses.

  The outcome

  Attribution is collected where customers can give it, without blocking the survey.

  For example

  Department step optional, service step required.

  Product screen

  Multiple-choice question

• Automatic reset after thank-youAfter the thank-you screen is shown, the kiosk resets itself for the next respondent.Kiosk and digital feedback

  How it is used

  No action; reset is automatic.

  The problem

  Staff would otherwise have to reset kiosks between customers.

  The outcome

  Each customer starts from a clean survey.

  For example

  Unattended exit kiosk.

  Product screen

  Thank-you screen

• Offline response caching and syncResponses are stored on the device when the connection drops and sent when it returns.Kiosk and digital feedback

  How it is used

  No respondent action; the kiosk keeps accepting answers offline.

  The problem

  Network interruptions at branches lose feedback.

  The outcome

  Answers given during an outage are stored and sent later.

  For example

  Branch with intermittent connectivity.

• Duplicate-safe syncEach cached response carries a device-generated identifier so the server stores it once even if it is sent again.Kiosk and digital feedback

  How it is used

  No user action.

  The problem

  Retries after a dropped connection can double-count responses.

  The outcome

  Results are not inflated by repeated uploads.

  For example

  Kiosk reconnecting several times during a poor-signal day.

• QR code colour stylingThe QR code can be given a custom colour or matched to the brand colour.Kiosk and digital feedback

  How it is used

  Administrator picks a code colour or "Match the brand colour".

  The problem

  Generic black codes look out of place in branded spaces.

  The outcome

  Printed codes match the organisation's look.

  For example

  Table cards in brand colour.

• QR download sizes and formatsDownload the code as PNG at 512, 1024 or 2048 pixels, or as SVG.Kiosk and digital feedback

  How it is used

  Administrator chooses a size and downloads.

  The problem

  Low-resolution codes print poorly.

  The outcome

  Codes ready for print or screen.

  For example

  Printing a large poster.

• Per-location QR actionsEach location's code has its own copy-link, download and send-by-email actions.Kiosk and digital feedback

  How it is used

  Administrator acts on one location's code.

  The problem

  Sending every branch the same file mixes attribution.

  The outcome

  Each site receives its own code.

  For example

  Sending each branch manager their branch code.

• Not-yet-live notice for web linkThe QR tab warns when the survey is not published, so the link will not work yet.Kiosk and digital feedback

  How it is used

  Administrator sees the notice before printing.

  The problem

  Codes printed before publishing lead to a broken page.

  The outcome

  Teams do not distribute codes that do not work yet.

  For example

  Preparing posters before launch day.

• Web survey live previewPreview the web version of the survey as it will appear on a phone.Kiosk and digital feedback

  How it is used

  Administrator views the preview in the QR tab.

  The outcome

  The phone experience is checked before sharing the code.

  For example

  Checking the web survey on a phone layout.

• Images on the survey welcome screenImages can be attached to a survey and shown on its welcome screen; an image cannot be removed while a survey uses it, and one used by a live survey is replaced rather than edited.Kiosk and digital feedback

  How it is used

  An administrator attaches images when designing the survey.

  The problem

  A text-only start screen fails to attract passers-by.

  The outcome

  Branded imagery invites customers to take part.

  For example

  A hotel shows a lobby image on its feedback kiosk's start screen.

• Configurable thank-you display timeThe time the thank-you screen stays up before the kiosk resets is set per survey (5 seconds by default).Kiosk and digital feedback

  How it is used

  An administrator sets the duration in the survey settings.

  The problem

  A thank-you that vanishes too fast or lingers too long confuses the next customer.

  The outcome

  The hand-over between respondents suits the location.

  For example

  A busy counter uses a short thank-you so the next customer can start quickly.

• Run a survey on a signage screenA published survey can be assigned as the content of a Nexus Signage screen with touch or another input method, running full screen with the same kiosk flow, and republishing updates the playing screen without a reconnect.Kiosk and digital feedback

  How it is used

  An administrator publishes the survey in Nexus Surveys and assigns it to the screen in the signage console.

  The problem

  Separate hardware for feedback and signage adds cost and clutter at the point of service.

  The outcome

  Existing touch screens collect feedback alongside signage.

  For example

  A clinic runs its feedback survey on a touch display already used for signage.

• Assign survey to kiosks by branchChoose which kiosks run a survey, branch by branch, and start or stop it.Terminal and fleet management

  How it is used

  Administrator ticks kiosks grouped by branch.

  The problem

  Deploying surveys device by device is slow.

  The outcome

  A survey is deployed to selected locations in one step.

  For example

  Rolling a survey out to a region's branches.

• Kiosk pairing by code or QRPair a new kiosk to the console with a short code or by scanning a QR code.Terminal and fleet management

  How it is used

  Administrator enters the code shown on the device.

  The problem

  Device setup needs technical staff.

  The outcome

  Kiosks are added without specialist setup.

  For example

  Adding a tablet to a new branch.

• Kiosk health and now playingTerminal list and cards show online, offline or never-seen status and which survey each kiosk runs; change or stop it.Terminal and fleet management

  How it is used

  Administrator filters by branch, health and platform; opens a terminal drawer.

  The problem

  Offline kiosks silently stop collecting feedback.

  The outcome

  Operations teams see which kiosks are working and what they run.

  For example

  Weekly check of a branch network's kiosks.

• Needs-attention listA dashboard list naming each terminal that is offline or out of service.Terminal and fleet management

  How it is used

  Administrator reviews items in the console.

  The problem

  Problems that stop collection are noticed late.

  The outcome

  Collection issues are visible in the console.

  For example

  Spotting an offline kiosk.

• Pairing persistence and auto-reconnectA paired terminal stays paired across restarts and reconnects on its own.Terminal and fleet management

  How it is used

  No action after the first pairing.

  The problem

  Re-pairing devices after every power cut needs a site visit.

  The outcome

  Kiosks come back into service without staff intervention.

  For example

  Branch kiosks after an overnight power outage.

• Terminal list and card views with searchView terminals as a list or as cards, and search them.Terminal and fleet management

  How it is used

  Administrator switches view and searches.

  The outcome

  Terminals are easy to find in a large network.

  For example

  Finding one kiosk among many.

• Terminal filters by location, health and platformFilter the terminal list by location, health state and platform.Terminal and fleet management

  How it is used

  Administrator applies filters.

  The problem

  Problems in one region are lost in a full list.

  The outcome

  Operations teams focus on one site or one problem type.

  For example

  Showing all offline terminals in one city.

• Terminal detail drawer and actions menuEach terminal opens a detail drawer and has a per-device actions menu.Terminal and fleet management

  How it is used

  Administrator opens the drawer or menu.

  The outcome

  Device details and actions are one click away.

  For example

  Checking one kiosk's state before a site visit.

• Start and stop a survey on a terminalStart or stop the survey running on a terminal.Terminal and fleet management

  How it is used

  Administrator uses the now-playing menu or the assignment dialog.

  The problem

  A survey may need pausing at one site without unpublishing it.

  The outcome

  Collection can be paused per kiosk.

  For example

  Pausing a kiosk during branch renovation.

• Assignment change previewThe assignment dialog shows each terminal's current survey and how many terminals will change before saving.Terminal and fleet management

  How it is used

  Administrator reviews the change count and saves.

  The problem

  Bulk changes can overwrite surveys at sites nobody meant to touch.

  The outcome

  Bulk assignment changes are visible before they apply.

  For example

  Moving forty branch kiosks to a new survey.

• Unassign from the assignment dialogRemove a survey from terminals in the same dialog used to assign it.Terminal and fleet management

  How it is used

  Administrator clears terminals and saves.

  The outcome

  Assignments are reversible in one place.

  For example

  Removing a seasonal survey.

• Fleet summary on the dashboardCounts of online, offline and not-serving terminals on the dashboard.Terminal and fleet management

  How it is used

  Administrator reads the fleet panel.

  The problem

  Fleet problems are found only in the terminal list.

  The outcome

  The state of the kiosk network is visible on the home screen.

  For example

  Daily check that kiosks are collecting.

• Licence seat counter on terminals, dashboard and usersTerminals page header "10 of 16 seats used - Manage licensing"; dashboard Fleet card shows "Kiosk seats N of N" with a bar; terminal drawer Unpair action says "Unpairing frees this terminal's license seat. Historical responses are kept."; Users page says "Only Admin accounts count against the license seat limit". Sidebar has a Licensing item.Terminal and fleet management

  How it is used

  Administrator reads seat usage and unpairs terminals to free seats.

  The problem

  Seat use is unclear when adding terminals.

  The outcome

  Operators can see licence capacity against deployed kiosks.

  For example

  An administrator sees 10 of 16 kiosk seats in use before pairing another terminal.

• Targeted assignment by department, service or kioskWithin a branch, a survey can be assigned to a specific department, service or individual kiosk rather than the whole branch, and a kiosk can be pinned to one survey; when a pin is cleared the kiosk falls back to its department's and then its branch's survey, and the console shows which level the effective survey comes from.Terminal and fleet management

  How it is used

  An administrator adds assignment rows on a survey's assignment screen, or opens a kiosk and pins or clears its survey.

  The problem

  One survey per branch cannot reflect different service points such as a returns desk and a lobby.

  The outcome

  Each service point shows the survey that fits it, with a clear answer to which survey every kiosk is showing.

  For example

  A store shows a returns survey at the returns desk and a general survey in the lobby.

• Suspend and reactivate a kioskA kiosk can be suspended so it stops showing its survey, shows a suspended message and accepts no responses, while the feedback it has already collected is kept; reactivating brings it back once it next reports in.Terminal and fleet management

  How it is used

  An administrator uses the Suspend or Reactivate action on a kiosk.

  The problem

  A faulty or relocated terminal keeps collecting misleading feedback, and deleting it loses its history.

  The outcome

  Terminals are taken out of service quickly without losing past results.

  For example

  Operations suspends a damaged kiosk until it is replaced.

• Default department and service per kioskWhen a kiosk is registered it is tied to its branch and can be given a default department and service and a name, so every response it collects is attributed to that place.Terminal and fleet management

  How it is used

  An administrator picks the branch and optionally a department and service while adding the kiosk.

  The problem

  Feedback from a kiosk at a specific desk is credited only to the branch as a whole.

  The outcome

  Results are attributed to the exact service point a kiosk serves.

  For example

  A kiosk at a bank's account-opening desk credits all its answers to that service.

• Plain-language pairing messagesWhen pairing fails the console says what to do, for example that no kiosk is showing the code entered, or that a code has already been used and the kiosk should be restarted for a new one.Terminal and fleet management

  How it is used

  An administrator reads the message and corrects the code or restarts the kiosk.

  The problem

  Opaque errors during installation lead to support calls.

  The outcome

  Installers resolve pairing problems themselves.

  For example

  A partner technician restarts a kiosk to get a fresh code after a failed attempt.

• Kiosks online but not running a surveyThe needs-attention list names each kiosk and branch needing action, most serious first, including suspended kiosks and kiosks that are online but have no survey, with critical items counted as 'action now'.Terminal and fleet management

  How it is used

  An administrator reads the list on the dashboard and goes to the named kiosk.

  The problem

  A terminal can look healthy while collecting nothing.

  The outcome

  Idle or misconfigured kiosks are found and fixed quickly.

  For example

  Operations spots a newly installed kiosk that was never given a survey.

• Dashboard: today at a glanceDashboard with responses, CSAT, NPS and CES and their trend.Analytics and feedback insights

  How it is used

  Administrator opens the dashboard and hovers charts.

  The problem

  Managers do not see feedback until monthly reports.

  The outcome

  A current view of feedback across locations.

  For example

  Regional manager's daily check.

• Analytics: CSAT, NPS, CES and completionAnalytics view with scores, completion rate and charts over a period.Analytics and feedback insights

  How it is used

  Administrator selects a period and views charts.

  The problem

  Scores without trends do not show progress.

  The outcome

  Measures tracked over time and by question.

  For example

  Quarterly CX review.

• Drop-off by questionShows where respondents stop answering.Analytics and feedback insights

  How it is used

  Administrator views a drop-off chart.

  The problem

  Long surveys lose respondents without anyone knowing where.

  The outcome

  Questions that cause abandonment are identifiable.

  For example

  Shortening a survey that loses respondents.

• Per-question breakdown and commentsEach question broken down with trend; comments listed in the language written.Analytics and feedback insights

  How it is used

  Administrator opens a question or the comments list.

  The problem

  Free-text feedback is not read.

  The outcome

  Customer comments are reviewable alongside scores.

  For example

  Reviewing comments for one branch.

• Response log with filtersResponse-level list filtered by branch, department, service and other fields.Analytics and feedback insights

  How it is used

  Administrator applies and clears filters.

  The problem

  Aggregate scores hide individual cases.

  The outcome

  Individual responses can be found and reviewed.

  For example

  Investigating a complaint at one branch.

• Compare by location, department and serviceResults segmented by branch, department and service.Analytics and feedback insights

  How it is used

  Administrator selects a breakdown.

  The problem

  Network averages hide weak locations.

  The outcome

  Weak locations and services are identifiable.

  For example

  Comparing branches in a region.

• Score distribution across answersPlaces every scored answer on a scale from negative to positive and shows the share of positive, neutral and negative answers, overall and per metric. Derived from scores;Analytics and feedback insights

  How it is used

  Administrator views the distribution panel in Analytics and filters it by metric.

  The problem

  Separate CSAT, NPS and CES figures are hard to read together.

  The outcome

  One view of how positive or negative scored answers are across all metrics.

  For example

  Monthly review of whether scored answers are trending positive.

• Period-over-period changeEach headline metric shows its change against the previous period, with the number of answers behind it.Analytics and feedback insights

  How it is used

  Administrator reads the change beside each metric.

  The problem

  A score without context cannot show progress.

  The outcome

  Movement is visible, with the sample size it rests on.

  For example

  Monthly review of satisfaction movement.

• NPS split into detractors, passives and promotersThe recommendation score is shown with its detractor, passive and promoter counts.Analytics and feedback insights

  How it is used

  Administrator reads the split.

  The problem

  A single NPS number hides how it was reached.

  The outcome

  Teams see whether a score moved because of detractors or promoters.

  For example

  Quarterly loyalty review.

• Completion with finished and abandoned countsCompletion rate is shown with the counts of finished and abandoned sessions.Analytics and feedback insights

  How it is used

  Administrator reads the completion panel.

  The problem

  Abandoned surveys are invisible in score averages.

  The outcome

  Teams see how many people start but do not finish.

  For example

  Shortening a survey that many abandon.

• Score distribution encodings and metric filterThe score distribution can be shown as a strip or a diverging chart and filtered by metric.Analytics and feedback insights

  How it is used

  Administrator switches chart type and metric.

  The outcome

  The distribution can be read in the form that suits the reviewer.

  For example

  Comparing CSAT and CES distributions.

• Trend over time with daily detailResponses per day and each metric per day over the period, with detail on hover.Analytics and feedback insights

  How it is used

  Administrator hovers a day.

  The problem

  Monthly averages hide bad days.

  The outcome

  Days with unusual results are visible.

  For example

  Spotting a weekday dip.

• Period summaryA summary of total responses, scored answers per response, abandonment rate, busiest day and median duration for the period.Analytics and feedback insights

  How it is used

  Administrator reads the summary panel.

  The problem

  Key facts about a period are spread across charts.

  The outcome

  One panel summarises the period.

  For example

  Preparing a monthly report.

• Response volume by languageShows how many responses arrived in each survey language.Analytics and feedback insights

  How it is used

  Administrator reads the language breakdown.

  The problem

  Organisations do not know which languages customers actually use.

  The outcome

  Language demand is visible per period.

  For example

  Deciding whether to add a third language.

• Minimum-response threshold on group comparisonGroups with fewer responses than a set minimum are excluded from the comparison.Analytics and feedback insights

  How it is used

  Administrator sets the minimum.

  The problem

  Comparing a branch or department on a handful of answers is misleading.

  The outcome

  Comparisons rest on enough responses to be meaningful.

  For example

  Excluding a branch with three responses from a regional ranking.

• Global analytics filtersFilter analytics by date range, location, terminal, survey, language and completion status.Analytics and feedback insights

  How it is used

  Administrator sets filters; the same set applies in Responses.

  The problem

  Network-wide views hide local problems.

  The outcome

  Every chart reflects the same filtered slice.

  For example

  Analysing one survey at one location in Arabic.

• Drill-through from metric to responsesFrom any metric, open the individual responses behind it.Analytics and feedback insights

  How it is used

  Administrator selects "View these responses".

  The problem

  Aggregates cannot explain a score.

  The outcome

  Each number can be traced to the sessions behind it.

  For example

  Reading the responses behind a low score at one branch.

• Dashboard score tiles and response chartSeven-day CSAT, NPS and CES tiles with change indicators and a fourteen-day response chart with its average.Analytics and feedback insights

  How it is used

  Administrator opens the dashboard.

  The outcome

  A current view without opening analytics.

  For example

  Regional manager's morning check.

• Response duration and follow-up markers in the response logResponse log columns include Duration per response (e.g. 42s) and a Follow-up column with comment and email icons on responses that carry them, next to CSAT, CES, NPS, language and Completed/Abandoned status.Analytics and feedback insights

  How it is used

  Analyst scans the list and opens a response.

  The problem

  Responses that need follow-up get lost in the log.

  The outcome

  Analysts can spot rushed or abandoned sessions and responses with follow-up details.

  For example

  A manager sees which responses left a comment or an email and how long each took.

• Comment inbox with review status and internal notesEvery free-text comment is listed with its location, department, service, language, scores and sentiment, and can be filtered by review status or by question. Each comment carries a status of New, Reviewed or Resolved and an internal note recorded with its author and time.Analytics and feedback insights

  How it is used

  A viewer opens the comments tab and filters it; an administrator opens a comment, sets its status and writes a note.

  The problem

  Complaints left in free text are read once and then lost without a follow-up record.

  The outcome

  Each comment has a traceable follow-up status and note.

  For example

  A service manager works through new complaints each morning and marks them resolved.

• Low-score alert rulesAdministrators set a minimum for CSAT, CES or NPS with a severity; when a response falls below it, an alert is recorded against that response with a message stating the value and the threshold.Analytics and feedback insights

  How it is used

  An administrator creates and activates a rule; managers review the alerts raised.

  The problem

  A poor experience is only discovered days later in a report, when the customer has long gone.

  The outcome

  Managers hear about a low score while the customer may still be in the branch, with a record of every breach.

  For example

  A branch manager sees which responses fell below the set CSAT minimum.

• Sentiment per response and sentiment filterEach response is classed as positive, neutral or negative from its overall score, and analytics, response and comment views can be filtered by sentiment.Analytics and feedback insights

  How it is used

  An analyst selects a sentiment in the analytics filters to see only negative responses.

  The problem

  Unhappy customers are hidden among averages.

  The outcome

  Negative experiences can be isolated and investigated directly.

  For example

  A manager reviews only this week's negative responses for one branch.

• Time spent per questionThe completion view shows how long respondents spend on each question, including time before the first question, alongside completion and abandonment.Analytics and feedback insights

  How it is used

  An analyst opens the completion funnel in Analytics.

  The problem

  Confusing or slow questions are hard to identify from scores alone.

  The outcome

  Survey owners can shorten or reword the questions that slow customers down.

  For example

  A team rewrites a question that takes far longer to answer than the rest.

• Today's responses by hour against yesterdayThe dashboard shows today's response count against yesterday's with the change and an hourly chart, with 'today' following the reader's own time zone.Analytics and feedback insights

  How it is used

  A manager opens the home page each morning.

  The problem

  Daily activity is hard to judge without a same-day comparison.

  The outcome

  Unusual drops in feedback volume are seen the same day.

  For example

  An area manager notices that today's responses have fallen behind yesterday's since mid-morning.

• Branding: logo, colours and gradientsBranding tab to apply logo, colours and gradient backgrounds to survey screens.Branding and administration

  How it is used

  Administrator uploads a logo and picks colours.

  The problem

  Off-brand kiosks look untrustworthy.

  The outcome

  Survey screens in the organisation's brand.

  For example

  Bank applying its colours to all branch kiosks.

• Automatic readability (contrast) checkBranding shows a contrast ratio check for chosen text and background colours.Branding and administration

  How it is used

  Administrator sees the ratio update while choosing colours.

  The problem

  Brand colours can make text hard to read.

  The outcome

  Readability problems are visible before publishing.

  For example

  Choosing text colour on a dark gradient.

• BranchesManage branches that own kiosks and catalogue entries.Branding and administration

  How it is used

  Administrator adds and edits branches.

  The problem

  Feedback cannot be compared without a location structure.

  The outcome

  A location structure for kiosks and results.

  For example

  Setting up a branch network.

• Catalogue of departments and servicesMaintain the departments and services used in attribution and logic.Branding and administration

  How it is used

  Administrator adds departments and services per branch.

  The problem

  Attribution options differ per branch.

  The outcome

  Consistent options for who-served-you steps and targeting.

  For example

  Configuring services for each branch.

• Users and rolesConsole users with Admin and Viewer roles.Branding and administration

  How it is used

  Administrator invites users and sets roles.

  The problem

  Everyone editing surveys creates risk.

  The outcome

  Viewers can review results without editing.

  For example

  Giving branch managers read-only access.

• Shared console and sign-in with Signage and QueueOne console and one sign-in across Nexus Signage, Nexus Queue and Nexus Surveys.Branding and administration

  The outcome

  Surveys is managed in the same console as Nexus Signage and Nexus Queue, with one sign-in.

• Logo upload formats and positionsUpload a logo (PNG, JPG, SVG or WEBP, up to 2 MB) or link to one, and place it in one of six positions.Branding and administration

  How it is used

  Administrator uploads or links a logo and picks a position.

  The problem

  Kiosks without the organisation's identity look generic.

  The outcome

  Survey screens carry the organisation's logo in a chosen place.

  For example

  Bank placing its logo top-left on every kiosk.

• Gradient direction controlGradient backgrounds take a from and to colour and one of eight directions.Branding and administration

  How it is used

  Administrator picks two colours and a direction.

  The problem

  A flat colour may not match the brand guidelines.

  The outcome

  Backgrounds follow the organisation's brand style.

  For example

  Brand gradient on all branch kiosks.

• Named colour presetsPreset background colour combinations to start from.Branding and administration

  How it is used

  Administrator picks a preset.

  The problem

  Choosing colours from scratch is slow.

  The outcome

  A quick, consistent starting point.

  For example

  Setting up a first survey quickly.

• Font size controlSet the text size for question text, answer options and helper text separately.Branding and administration

  How it is used

  Administrator enters sizes.

  The problem

  Text that suits a tablet is too small on a floor kiosk.

  The outcome

  Readable text on each kiosk size.

  For example

  Larger question text on a floor-standing kiosk.

• Location rename cascades everywhereRenaming a location updates it everywhere it appears, automatically.Branding and administration

  How it is used

  Administrator renames a location once.

  The problem

  Renamed sites leave old names in reports and filters.

  The outcome

  Reports and filters stay consistent after a rename.

  For example

  Branch renamed after a merger.

• Catalogue scoping to locationsA catalogue entry applies to all locations or to specific ones.Branding and administration

  How it is used

  Administrator chooses all or selected locations.

  The problem

  Branches offer different services.

  The outcome

  Each location shows only the options that apply there.

  For example

  Mortgage desk available at five branches only.

• Active and archived catalogue entriesCatalogue entries can be archived instead of deleted, and filtered by status.Branding and administration

  How it is used

  Administrator archives an entry.

  The problem

  Deleting old services breaks historical reporting.

  The outcome

  Retired options leave the survey without losing history.

  For example

  Archiving a discontinued service.

• User status statesUser accounts show active, inactive or must-change-password status.Branding and administration

  How it is used

  Administrator reads and changes status.

  The problem

  Departed staff keep access when accounts cannot be deactivated.

  The outcome

  Access can be suspended without deleting the user.

  For example

  Deactivating a leaver's account.

• Last-active timestampEach user shows when they were last active.Branding and administration

  How it is used

  Administrator reads the user list.

  The problem

  Unused accounts are a security risk.

  The outcome

  Dormant accounts are visible.

  For example

  Quarterly access review.

• Cloud and on-premises deploymentThe same product deploys in the cloud or on the customer's premises.Branding and administration

  How it is used

  The deployment model is agreed with Nexus Cloud during the evaluation, before rollout.

  The problem

  Some organisations must keep systems and data on their own infrastructure; others prefer a managed cloud service.

  The outcome

  The same product can be adopted under either operating model.

  For example

  A regulated organisation that requires on-premises installation.

• Solid, gradient or image backgroundBranding tab Background control offers Solid, Gradient and Image options; logo can be uploaded (PNG, JPG, SVG or WEBP up to 2 MB) or set from a link ("Use a link instead").Branding and administration

  How it is used

  Administrator picks the background type and uploads or links assets.

  The problem

  Survey screens that ignore the brand look generic.

  The outcome

  Survey screens can carry a brand image as well as colours.

  For example

  A retailer sets a gradient background and uploads its logo for its feedback kiosks.