Once an AI assistant is connected to the systems your team works in, the bottleneck moves from "can it do this?" to "what should I ask?". The best requests are short, name the thing precisely and say what done looks like. Below are ten we see work well with Orbiz MCP, grouped by where the work lives, with a note on why each is phrased the way it is. They work in Claude, ChatGPT and Claude Code; how to connect them is in our setup guide.
Sprints and issues in Cadence
- "Report a bug in ORB: exporting an empty month returns a 500 on staging. Steps: open Reports, pick September, press Export. Expected an empty CSV." Naming the project key, the environment and the expected result gives the assistant everything a good bug report needs. It files a BUG with the steps laid out, as you.
- "Turn these meeting notes into issues in the WEB project, one per action item, assigned to whoever is named." The assistant looks people up by name, then creates the issues in one batch, up to fifty at a time. Paste the notes underneath.
- "Move ORB-142 to In Review and add a comment that the fix is on the release branch." Statuses can be named the way your board names them. If the name does not exist, the assistant is told the real ones and asks you.
- "What is in the active sprint for ORB that is still To Do and unassigned?" A read-only question that saves opening the board, filtering and counting. Sprint managers can also ask the assistant to create, start and complete sprints.
Everything here happens in Cadence under your name, with your permissions. An employee’s assistant can file and update issues; only people who manage sprints see the sprint actions at all.
Hours and projects in Trackline
- "Log 2.5 hours on the Acme redesign for yesterday, against the Beta milestone, for the checkout work." Hours, project, day and what it was for: the four things a time entry needs. The assistant needs your role to allow logging time.
- "How many hours did I log this month, by project, compared with last month?" The summary returns hours only, never rates or costs, so it is safe for anyone to ask about their own time.
Trackline keeps the delivery view: projects, milestones and the hours behind them. If you are deciding between attendance, time tracking and timesheets for your team in the first place, read attendance vs time tracking vs timesheets.
Leave and attendance in AMS
- "How much annual leave do I have left, and is anything still pending?" Two questions in one. The assistant reads your balance and your open requests.
- "Request casual leave for next Friday, full day, reason: family event." Leave type, dates, portion and reason are exactly what the AMS leave form asks for. The request goes to your approvers as usual, and you can cancel it the same way.
- "Show me the leave requests waiting on my approval this week, then approve the ones that do not overlap." For approvers. The assistant lists the queue; a rejection always needs a note, which keeps the person on the other end informed.
What an assistant cannot do in AMS is clock you in or out. Attendance is a record of what a person did, so the timer stays with the person, on the web or the desktop app.
Notes, the glue between them
- "Save the release steps we just agreed as a checklist note called Release 2.4." Notely keeps the list where the team can see and tick it, and the assistant can update it later without overwriting someone else’s edit: if the note changed in the meantime, it gets the latest version and merges instead.
When to do it yourself
Some work is faster by hand: dragging a dozen cards into priority order, scanning a board to get a feel for a sprint, or anything you need to see laid out to judge. And some work should stay human on purpose. Nothing can be deleted through Orbiz MCP, salary changes need explicit confirmation from payroll managers, and shared credentials are never reachable. The assistant is best at the typing between decisions, not the decisions.
Built for your industry
