Back to home

Cueston for HR software

Your HR software has three kinds of users who want different things from it: HR teams who set it up, managers who approve, and employees who log in a few times a year. Cueston shows each of them the right tour, tooltip or checklist, in their own language, without an engineer for every change.

Why HR software teams use Cueston

HR products are learned by role and forgotten between uses. Cueston targets guidance by the role and permissions your app already knows, translates it into 11 languages, and stays out of the people data on screen: it sets no cookies and doesn’t read form values. Your product team writes and changes the guidance; your engineers add one snippet.

Why HR software is hard to learn

Few products have as many kinds of users. An HR admin configures leave policies, approval chains and payroll settings. A manager approves requests and writes reviews. An employee books a day off and downloads a payslip. They log in to the same product and see different screens, so one onboarding tour can’t fit them all.

Most of them use it rarely. An employee opens HR software when they need something, a day off, a payslip, a review, and by the next time they’ve forgotten where it was. Help has to be on the page when they need it, not in a welcome tour they saw months ago.

And it arrives all at once. When a new customer goes live, the whole company is invited in the same week. Every question the product doesn’t answer becomes a ticket for the customer’s HR team, and then for your support team.

What a new employee sees the first time they open Time off: the first of three tour steps, pointing at the real button. Managers and HR admins on the same page don’t see it.

The rules behind it, set in the editor:

  • User role equals employee
  • First seen less than 14 days ago
  • Pages: */time-off*
  • Frequency: once

Who uses your HR software, and what to show them

WhoWhere they get stuckWhat to show them
HR admins setting up the accountDozens of settings before anyone else can log in: leave types, approval chains, holiday calendars, the employee import.A setup checklist whose items tick off when your app reports them done, such as employees imported, with a tour behind each item.
ManagersApproval queues and review forms they open a few times a month, or twice a year.Tooltips on the approve buttons and the review form, shown to people whose role or permissions include approving.
EmployeesSelf-service tasks they do rarely: booking time off, updating bank details, finding a payslip.A three-step welcome tour on first login, tooltips that stay on the page, and a help hub to restart a tour or ask the AI assistant.
Payroll and financeA monthly run where a missed step is expensive.A tour that walks through the run in order, shown only to people with payroll permissions.
New hires after launchJoining months after launch, when nobody is running training any more.The same onboarding, targeted by “first seen less than 14 days ago”, so every new hire gets it, not only the first wave.

A go-live plan for a new customer

Five moments, each with the Cueston item that fits it. You build them once, and every customer that goes live gets them, because they’re targeted by role and by when each person first signed in, not by customer.

  1. Before go-live: a checklist for HR admins

    Four to six setup tasks, each opening a tour and each ticked off when your app reports it done. Shown only to the admin role, so employees never see it.

    Built with: Checklist, tours

  2. Go-live: a welcome tour for each role

    Three steps for employees and a separate tour for managers, shown to people first seen in the last 14 days. It greets every new user whenever their company launches.

    Built with: Tours, audience rules

  3. First weeks: tooltips where the tasks are

    On the time-off form, the payslip page and the approval queue. They stay on the page, so the employee who comes back in March still finds them.

    Built with: Tooltips

  4. Review season: a tour of the review form

    Shown to managers the first time they open a review, once per person. It works for every customer’s cycle, whenever they run it.

    Built with: Tour, page pattern, frequency

  5. After a month: one question for HR admins

    An NPS survey with a follow-up question when the score is low. You hear which customers are struggling while there’s still time to help.

    Built with: Survey

What HR software needs from a tour tool

Targeting by role and permissions

Your app tells Cueston who is signed in with one call (Cueston.identify), passing the role, permissions and plan it already knows. Every tour, tooltip and checklist can then match all or any of up to 20 rules: role is manager, permissions include payroll, a plan with performance reviews, or a custom attribute such as country. See Who sees it.

People data stays out of Cueston

The traits you pass for targeting are used in the browser and aren’t sent to Cueston. The snippet sets no cookies and doesn’t record keystrokes, form values, mouse movement or the screen. What it does keep, such as which guidance someone saw, the page address and their user ID, you can keep for anywhere from 30 to 1,095 days. When an employee makes a GDPR request, you can export or delete their data from the dashboard or the API. Page addresses are recorded, so keep personal data out of your URLs. The details are in Data handling.

Turn on identity verification too. Your server signs each user ID, so nobody can claim to be a colleague from the browser console.

Every language your customers’ employees speak

Guidance can be in English, Ukrainian, Polish, Spanish, Portuguese, German, Russian, French, Italian, Japanese and Chinese. Translate by hand, let machine translation write a first draft, or export a CSV or XLIFF file for your translators. People see their browser’s language, and English when there’s no translation. See Languages.

Customers on their own subdomains

If each customer has acme.your-hr-app.com, one allowed-domains entry, *.your-hr-app.com, covers them all, and a page pattern such as */time-off* matches on every one of them. See Allowed domains.

A second pair of eyes on every change

HR guidance often explains policy, so mistakes matter. Turn on approvals and every change to production needs a second person. Try changes on your staging app before production, and roll back to the last good version in one click if something slips through.

Fewer tickets for your customers’ HR teams

The help hub puts an AI assistant, checklists, what’s new and help articles behind one button. The assistant answers from your help docs and can point at the right button; it’s on every paid plan. Help articles in the hub are readable by anyone on the site, so keep internal policy out of them.

Proof it worked

Give a tour a goal, such as “time-off request submitted”, and hold back a control group of up to 50%. Cueston shows whether the people who saw the tour reached the goal more often, and whether the difference is significant at 95% confidence. See Goals and experiments.

When Cueston isn’t the right fit

  • You’re rolling out an HR system you bought to your own employees. Cueston runs where you can add its script, which means a product you build. For software you bought, look at a digital adoption platform that runs as a browser extension for every employee.
  • Your product is a native mobile app. Cueston is for web apps.

Frequently asked questions

Can employees, managers and HR admins see different tours?▾

Yes. Your app passes each person’s role and permissions when they sign in, and every tour, tooltip, checklist and banner has audience rules: role is manager, permissions include approving, plan, or any custom attribute your app sends. People who don’t match never see it.

Does Cueston see our customers’ employee data?▾

Not the data on screen. The snippet sets no cookies and doesn’t record keystrokes, form values, mouse movement or the screen, and the traits you pass for targeting stay in the browser. It records guidance events, such as a tour step seen, with the page address and the user ID your app passes. You choose how long that is kept, from 30 to 1,095 days.

Can we answer an employee’s GDPR access or deletion request?▾

Yes. Look the person up by user ID in Settings, Data & privacy, then download what’s stored as JSON or delete it. The same export and delete are in the API, so your own privacy tooling can call them.

Does it work when each customer has their own subdomain?▾

Yes. One allowed-domains entry such as *.your-hr-app.com covers every customer’s subdomain, and page patterns with wildcards match the same page on all of them.

Which languages can guidance be in?▾

English, Ukrainian, Polish, Spanish, Portuguese, German, Russian, French, Italian, Japanese and Chinese. Each person sees their browser’s language when there’s a translation, and English otherwise.

How much does it cost for an HR product?▾

Paid plans are $39, $79 and $139 a month, billed yearly, for up to 500, 5,000 and 50,000 monthly active users. In HR software that includes employees, so estimate from the people across all your customers who use it in a month. There’s also a free plan with one live item of each kind.

Can we use Cueston to roll out an HR system we bought?▾

No. Cueston shows guidance in apps where you can add its script, which means a product you build. To guide your own employees through software you bought, you need a digital adoption platform that runs as a browser extension on their computers.

Put the first tour in front of your customers’ employees

Free to start. Add the snippet, pass the role, and publish a tour for one role this week.