Getting the most from Cue comes down to how you frame your requests. This article covers the principles that consistently produce faster, more accurate results, as well as the patterns that slow things down.

The most common mistake when using Cue for the first time is describing a process instead of a goal. Cue is built to work from intent, so leading with the outcome you want, rather than a list of actions, lets Cue determine the best path.

Instead of: "Go to the openings list, filter by state, find the ones in Indiana, then change the age minimum field to 16."

Try: "Change the screening option for openings in Indiana that asks for age minimum to 16 years old."

The second version gives Cue a clear objective. Cue figures out the rest.

Cue uses your current page context and account data to scope its responses, but it cannot read your mind. When your request involves a specific opening, location, time frame, or subset of records, say so directly. Vague scope produces vague results.

Less specific: "Show me the applicants."

More specific: "Show me applicants in the Warehouse Associate opening who are in Interview Scheduled."

Even more specific: "Show me applicants in the Warehouse Associate opening who are in Interview Scheduled and have been in that stage for more than 5 days."

The more precisely you define the target, the more precisely Cue can act on it.

If your request has a rule attached, such as a rejection Reason that must be applied, a Referral condition that must be met, or an exception that should be flagged, include it in the prompt. Cue applies conditions you specify, but it does not invent constraints you leave out.

Without constraint: "Move everyone in Phone Screen to Rejected."

With constraint: "Move everyone in Phone Screen to Rejected and use reason 'Failed screen'."

Another example: "Message all candidates in stage 'Offer' who have not responded in 3 days. Draft the message first."

The phrase "draft the message first" tells Cue to pause for review before sending. This is an important control for any action that reaches candidates.

When Cue needs more information before it can act, it will ask clarifying questions. Answer conversationally and completely. The more precisely you respond to what Cue asks, the faster it can execute.

If you already have the details Cue is asking for, include them all in a single follow-up rather than answering one question at a time. Cue will process everything you provide and move forward.

For anything that sends a message, moves a large number of records, or makes a configuration change across multiple openings, ask Cue to show you a draft or preview first.

Cue's plan and approval step is built for this. You can always edit the plan conversationally before giving the go-ahead.

Cue's support capability is free and doesn't require a plan or approval step. It just answers. When you're unsure about a setting, a metric definition, or a process, ask Cue first rather than exploring settings manually.

This is the fastest way to build confidence before making a change, and it costs nothing.

You don't need to start a new prompt for every step. Cue retains context throughout the session, so follow-ups build on what it already knows.

Sequence example:

Each step narrows the scope. By the time you reach step 4, Cue has all the context it needs to act precisely.

If you shift to a completely different task within the same session, give Cue a brief reset so it doesn't carry over assumptions from the previous request.

Clear reset: "Separate question — show me all unassigned shifts for next week at Location X."

A short transition phrase signals a fresh scope without requiring you to start a new conversation.

Cue can move from analysis to execution in a single conversation. You don't need to get an answer first and then ask separately for action. You can request both at once.

When Cue encounters steps that require your input or approval, it will pause and ask rather than proceeding.

A few patterns consistently produce longer back-and-forth before Cue gets to the right result:

"Show me the applicants" with no opening, stage, or time frame requires Cue to ask clarifying questions. Add the scope upfront.

Telling Cue which buttons to click or which menus to navigate adds noise. Describe the outcome instead.

If you have five different things to do, tackling them one at a time, or as a clearly labeled list, gives Cue better opportunity to plan and confirm each step correctly.

If you want to review before Cue sends or applies something, say so in the prompt. Adding "draft first" or "show me before you proceed" ensures Cue pauses at the right moment.