Cue for Onboard: Clearer Answers and Verified Actions

Cue handles Onboard requests through focused capabilities, and confirms the result of an action before reporting it as done.

Cue answered Onboard questions through one broad assistant, and it could describe a write, a send or a status change as successful before the result had been checked. A message that never went out could still read as sent.

What's new

• Focused capabilities — Onboard requests are routed to narrower capabilities covering flow authoring, flow and task lookup, workforce actions, worker notifications, pending tasks, and setup planning.

• Tighter tool boundaries — each capability is scoped to the tools its job needs, which reduces ambiguous choices and unnecessary tool use.

• Verified results — Cue does not report that a write, send or state change succeeded until the result is supported by tool output or a check afterwards.

• More precise wording — responses distinguish between submitted, queued, verified, completed, partially completed and unverified.

• Focus on high risk actions — worker messaging, task flow creation and edits, task completion, document template creation, and task manager or bag creation are prioritized for stronger confirmation.

Why it matters

Onboard work through Cue is usually a write: creating a task flow, completing a task, messaging a group of workers. Knowing that a confirmation reflects a checked result, rather than a request that was merely sent, is what makes it safe to act on.

What to expect

Where Cue cannot confirm an outcome, it says so rather than reporting success. That wording is deliberate, and it means the action is worth checking in Onboard before you move on.

Availability

Available to all Onboard customers.