Jarvis voice

The Jarvis screen is the workspace you can talk to. Ask "how many tasks are left on Storefront?" and it answers out loud. Say "create a task to fix the cart total and put the Laravel Engineer on it" and it files the ticket and starts the agent. Longer requests, like setting up a new client, become a short spoken conversation that asks for each detail in turn.

Voice is a convenience on top of the same workspace. It follows the same permissions as the screens, it cannot do anything the screens would refuse you, and it cannot approve or deploy anything.

#Getting to it

Open Jarvis from the navigation. If you do not see it, your group does not include it; ask your administrator.

Press the microphone and speak. When you finish, Jarvis answers in speech and in text. Sample tasks offers ready-made requests if you want to see what it can do, and when Jarvis offers choices (a list of projects, say) you can tap one instead of saying it.

Listening and speaking happen in your browser. Only the words you said, as text, are sent to the workspace; no recording of your voice is uploaded. Speech recognition needs a browser that supports it, such as Chrome, Edge or Safari. If your administrator has set up a custom voice, Jarvis uses it; otherwise your browser's own voice reads the replies.

#Asking about the work

Questions about the workload are answered from the workspace's own records. The counts of open tasks, tickets waiting for approval, runs asking for permission and so on are looked up directly, and an AI model only puts them into a sentence. The numbers never come from the model.

If no AI model is connected, Jarvis still answers with a plain spoken summary of the same numbers.

Examples:

• "How many tasks are left?"
• "What is waiting for my approval?"
• "How is the Storefront project doing?"

#Taking actions

A sentence that asks for an action is matched to one item from a fixed list. Anything not on the list is simply not done, however it was phrased.

Action	Example
Create a task	"Create a task on Storefront to add a delivery note field."
Create a task and assign an agent	"Create a task to fix the cart total and put the Laravel Engineer on it."
Create a project	"Create a project called Mobile App for Acme."
Create a client	"Add a new client called Northwind."
Change a task's status	"Move the cart total task to blocked."
Set priority	"Make the delivery note task urgent."
Set a due date	"The delivery note task is due next Friday."
Move to a sprint	"Put the cart total task in the next sprint."
Assign an agent	"Put the QA Engineer on the checkout tests task."
Sync	"Sync Jira for Storefront." Also Trello and GitHub issues.

Approving and deploying are not on the list. If you say "approve it" or "deploy the cart fix", Jarvis tells you that approvals stay with you on the run screen. A spoken word is too easy to mishear, and the gate needs a person reading the change. See Runs and the approval gate.

Agent work started by voice is the same as any other: it happens on the ticket's branch and stops at the gate. It never has permission to run commands; that can only be granted from the assign dialog.

#Guided conversations

Some requests need several details. Rather than expecting them all in one sentence, Jarvis asks for each in turn.

Conversation	Steps
New task	project, the brief, whether to draft acceptance criteria, assignee, sprint (skipped when the project has none), priority, story points, due date, then a read-back to confirm
New client	name, contact person, email, then confirm
New project	client, name, description, then confirm

A few things make these easier:

• What you say is read in context. "Storefront" is a project when Jarvis asked for a project. Once a conversation is running, your answer goes to the question being asked.
• Optional steps can be skipped. Say "skip" or "no", or tap the skip choice. "Unassigned" is offered when Jarvis asks who should own the task. A "no" only counts as skipping when it is the whole answer, so "no, the customer portal" is kept as an answer.
• You can always get out. Say "cancel", "go back" or "start over" at any step.
• Nothing is guessed. Priority words ("urgent", "low"), numbers ("about five points"), dates ("tomorrow", "next Friday") and spelled-out emails ("anna at example dot com") are understood. Anything Jarvis cannot make out is asked again, because a wrong due date is worse than none.
• Nothing is created until you confirm. The read-back at the end lists what will be created.

If you start with a request that is missing something, such as "create a task" with no title, Jarvis starts the guided conversation with whatever you did say instead of giving up.

#Permissions

Jarvis checks that you are allowed to do something when the conversation starts, and again at the moment it is about to do it. If your access changes mid-conversation, or the project you picked is removed, Jarvis tells you rather than carrying on.

The choices it offers are only ever ones you are allowed to see.

Next: Connectors.