Problem: Rovo's voice transcription isn't accurate enough, so people fall back on other dictation tools like Wispr Flow. That adds an extra step, interrupts your work, and means what you say goes through a tool outside Atlassian.
What we want: A full voice conversation mode in Rovo, like ChatGPT and Claude have. You'd speak naturally, Rovo would answer out loud in real time, and you could keep talking back and forth.
Requirements:
- Accurate transcription, including Australian accents and terms specific to my Atlassian tenant, project names, Jira keys and people's names.
- Live two-way conversation that takes turns naturally and lets you interrupt.
- Spoken answers, with an option to show the text alongside.
- Everything Rovo can already do, done by voice: searching Jira and Confluence, creating work items, drafting pages and running skills.
- Works in the browser, the desktop app and on mobile.
- Hands-free use for site visits, travel and walking between meetings.
Why it matters: No more relying on outside dictation tools. Voice stays inside Atlassian, where our privacy and data rules already apply. Ideas and actions get captured faster, and Rovo catches up with the leading AI assistants.
How we'll know it's done: You can have a full spoken conversation with Rovo without other tools, and you rarely need to fix the transcription.
While I have you
I would also like to be able to give my Rovo a bit of personality, like talking to me in a thick Australian accent.
I would like to schedule interviews with Rovo for project team leaders and members to gather context, and create updates outside of Loom meetings.
Simulated interview: Rovo voice check-in with Marc
Setting: Marc is walking back from a site visit and opens Rovo on his phone in voice mode.
Rovo: Afternoon, Marc. You've got four active items across the Leadership team and Spatial Intelligence work. Do you want to run through updates now, or just get something down quickly?
Marc: Let's do updates. I've got about ten minutes.
Rovo: Great. Let's start with the Canberra bid. The digital data storage section is due Friday. Where's it at?
Marc: It's drafted. I've written up the common data environment approach. We're using Autodesk Construction Cloud for the BIM side and SharePoint for everything that isn't a model. Andrew still needs to review it.
Rovo: Got it. Should I move it to "In Review" and assign Andrew as the reviewer?
Marc: Yes. And add a note that Aconex might come up if the client wants it for document control.
Rovo: Noted. I'll add a comment: "Client may require Aconex for document control. Confirm at the clarification stage." Is that a risk for the bid, or just something to keep an eye on?
Marc: Just something to keep an eye on for now.
Rovo: Okay, I'll log it as an open question rather than a risk. Next is the QA System Review. The last update was two weeks ago.
Marc: Yeah, that's stalled a bit. We agreed the QA checklists will live in Confluence as templates, one per project stage. But we haven't decided who owns the templates.
Rovo: That sounds like a decision and a blocker. Let me check I've got it right:
- Decision: QA checklists will be Confluence templates, one per project stage.
- Blocker: No one owns the templates yet.
Is that right?
Marc: Yes. Actually, make a task for me to raise ownership at the next Leadership team meeting.
Rovo: Done. I'll create "Raise QA template ownership at Leadership team meeting", assign it to you and link it to the QA System Review. Do you want the decision recorded on the QA System Review page too?
Marc: Yes, please.
Rovo: Will do. Next is the Revit-to-video proof of concept. Any progress?
Marc: Some. We tested a short walkthrough. The output was okay, but the materials looked flat, especially timber and glazing. We learnt the prompt needs the material callouts from the Revit model, not just the camera path.
Rovo: That's a useful lesson. I'll capture it as: "Image-to-video output improves when you include material callouts from the Revit model in the prompt. Without them, timber and glazing render flat." Should that go on the proof of concept page under Lessons Learned?
Marc: Yes. And the next step is to test with a Rhino export to compare.
Rovo: I'll add a subtask under the proof of concept: "Test the Rhino export as input for the video pipeline". Who's doing it?
Marc: Chris, if he's got time. Put it on him, but flag it as tentative.
Rovo: Okay. I'll assign it to Chris and add a comment saying it depends on his availability. Last one is the Employee Privacy Policy. It's waiting on board approval.
Marc: No change. The board meets on the third. Brian's presenting.
Rovo: Should I set a reminder to follow up with Brian on the fourth?
Marc: Yeah, good idea.
Rovo: Done. Before I make any changes, here's a summary of everything:
Jira updates
- Canberra bid, data storage section: move to In Review, assign Andrew as reviewer, add the Aconex comment.
- QA System Review: add the blocker. New task for you to raise template ownership at the Leadership team meeting.
- Revit-to-video proof of concept: new subtask for Chris to test the Rhino export, marked tentative.
- Employee Privacy Policy: no status change. Reminder to follow up with Brian on the fourth.
Confluence updates
- QA System Review page: record the template decision.
- Revit-to-video page: add the material-callout lesson.
Should I go ahead with all of these?
Marc: Yes, go. Actually, what's the ID for the Canberra one? I need to send it to Andrew.
Rovo: It's LT-101. Want me to send Andrew the link?
Marc: No, I'll do it. Go ahead with the rest.
Rovo: All done. That's four work items updated, two new tasks, two pages updated and one reminder set. Anything else before you get back?
Marc: No, that's it. Thanks.
Rovo: No worries. Safe travels, Marc.