What an ATS needs from a tour tool
Targeting by hiring role
Your app tells Cueston who is signed in with one call (Cueston.identify), passing the role and permissions it already knows: admin, recruiter, hiring manager, interviewer. Every tour, tooltip and checklist can match all or any of up to 20 rules, so a scorecard tip never reaches recruiters and setup never reaches interviewers. See Who sees it.
Triggers from what people did, or didn’t
Your app reports events such as “scorecard submitted” or “offer approved” with Cueston.track. Audience rules then match people who did an event at least or fewer than some number of times in some days, or not at all, so a nudge reaches interviewers who haven’t submitted feedback lately and stops once they do.
Candidate data stays out of Cueston
An ATS is full of CVs, salaries and interview notes. The snippet sets no cookies and doesn’t record keystrokes, form values, mouse movement or the screen, and the traits you pass for targeting are used in the browser and aren’t sent to Cueston. 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, and you can export or delete one person’s data from the dashboard or the API. Page addresses are recorded, so keep candidate names and emails out of your URLs. See Data handling.
Help for people who arrive from an email
Hiring managers rarely start on your home page; they click a link in a notification and land on a candidate. A page pattern such as */candidates/*/feedback puts guidance on that page however they reached it, and a developer can start a tour from your own “How does this work?” link with Cueston.start. See Where it shows.
Answers without a message to the recruiter
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, so an interviewer who forgot how to submit feedback asks there. On paid plans, when people struggle on a page, such as clicking a disabled button again and again, stuck points shows where, and you can turn each one into a tip that only those people see.
Every language your customers hire in
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.
Proof it worked
Give the scorecard nudge a goal, such as “scorecard submitted”, and hold back a control group of up to 50%. Cueston shows whether the people who saw it 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 ATS you bought to your own recruiting team. 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.
- Candidates apply through job boards and never reach your pages. Guidance only appears on pages that load the Cueston script.
- Your product is a native mobile app. Cueston is for web apps.
Frequently asked questions
Can recruiters, hiring managers and interviewers see different guidance?▾
Yes. Your app passes each person’s role and permissions when they sign in, and every tour, tooltip, checklist and banner has audience rules. Target the admin role for setup, the recruiter role for pipeline tours and the hiring manager role for feedback tips. People who don’t match never see it.
Can a tip show only to interviewers who haven’t submitted feedback?▾
Yes. Your app reports the event, for example with Cueston.track("scorecard submitted"), and the tooltip’s audience rule says the person did it fewer than once in the last 7 days, or not at all. Once they submit, they stop matching and the tip stops showing.
Does Cueston see candidate 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 tooltip 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, and can export or delete one person’s data in Settings, Data & privacy, or through the API.
Can candidates see guidance on our job pages?▾
Yes, if those pages load the Cueston script. Visitors who aren’t signed in only see items without audience rules, so the page pattern decides where they appear. Candidates who sign in to a portal can be targeted like any other user.
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 ATS?▾
Paid plans are $39, $79 and $199 a month, billed yearly, and each includes a number of monthly active users across all your customers. Everyone your app identifies counts once in a month they visit. A visitor who isn’t signed in counts only if they were shown something, so candidates on job pages without guidance don’t count. There’s also a free plan, and the pricing page lists what each plan includes.
Can we use Cueston to roll out an ATS we bought?▾
No. Cueston shows guidance in apps where you can add its script, which means a product you build. To guide your own recruiters through software you bought, you need a digital adoption platform that runs as a browser extension on their computers.