Skip to content
Choose a language (English)
Sign up for the beta
Voice commands

Create tasks, log hours and request leave by voice, in English and Italian

29 commands, spoken the way you’d say them to a colleague. Before saving anything, bagai reads back what it understood, with the real client names and dates: nothing goes in without your yes.

From your iPhone’s Action button and from your computer. Android follows soon, Apple Watch by the end of the year.

Why voice

People working in the field have their hands full. That’s where time goes unlogged and tasks never get opened: nobody fills in a form on their phone at the top of a ladder or in front of a fuse box. With voice, you just say it.

  • It does the same work as the forms, with the same rules.
  • It’s most useful on a phone, which is why it’s designed for the apps.

Nothing is written before you say yes

A spoken sentence produces a proposal, not an action. A transcription can get a word wrong, and one client’s name can sound almost like another’s: the read-back is when you notice. That’s what makes it safe to speak instead of typing.

  • Only a clear yes confirms: “yes, but change the date” is a correction.
  • If you cancel, nothing is left behind: no draft, no half-made task.

29 commands

Everyday work, plus some admin tasks. For each one, an example sentence: you don’t have to say it word for word.

Tasks, time and timers

Create a task “Create an urgent task for the client Cattaneo Costruzioni: fix the servers by Friday, two hours.”
Edit a task “Set the due date on T-142 to Monday.”
Change the status “Put T-88 in progress.”
Add a comment “Comment on T-142 that the client has approved the quote.”
Add a checklist item “Add to the checklist on T-142: check the backups.”
Log time “Log two and a half hours on T-142, done yesterday.”
Start the timer “Start tracking time on T-142.”
Stop the timer “I’m done, stop the timer.”
Search for tasks “Show me the open tasks for Cattaneo Costruzioni.”
Delete a task “Delete task T-142.”

Clients

Create a client “Add the client Elena Sulmoni, private individual.”
Edit a client “Change the address of the client Cattaneo Costruzioni to Via Cantonale 12, Lugano.”
Delete a client “Delete the client Impianti Fontana.”

Projects

Create a project “Create a project called Brochure website for the client Cattaneo Costruzioni.”
Edit a project “Move the deadline of the IT support project to the end of November.”
Delete a project “Delete the IT support project.”

Your companies

Create a company “Create the company Pagani Servizi Italia.”
Edit a company “Rename the company Pagani Servizi to Pagani Servizi SA.”
Delete a company “Delete the company Pagani Servizi Italia.”

Tags

Rename a tag “Rename the tag super urgent to urgent.”
Delete a tag “Delete the tag old price list.”

People

Invite a person “Invite Giulia Rezzonico, email giulia.rezzonico@example.com.”
Deactivate a person “Deactivate the user Marco Induni.”
Reactivate a person “Reactivate Marco Induni.”
Change someone’s level “Make Giulia Rezzonico an administrator.”

Absences

Request an absence “Request annual leave from 21 to 24 December.”
Approve a request “Approve request A-57.”
Reject a request “Reject request A-58.”
Search absences “Show me the pending absence requests.”

Tasks are referred to by their code, for example T-142: that’s how people name them when talking, and it’s why a code is never reused. A task without a project takes your company, unless you name one.

Talking in turns

Dictating is a conversation: bagai remembers what you’ve just been talking about.

  • Among the tasks just mentioned, there’s only one “backup”. Across all your data there might be twenty: that’s why titles are only matched against the tasks in play.
  • If the title matches two tasks, bagai doesn’t pick one: it tells you and asks for the code.
  • “That one”, “the first one” and “the last one” don’t work, by design: after a few commands, nobody knows what they point to any more. A code or a title always means the same thing.
  • The context lasts a working day and is renewed with every sentence.
  • It’s per device: the phone in the warehouse and the browser in the office are two separate conversations.

Correct it without starting over

At the read-back, you can reply with a correction, which counts as neither a yes nor a no: bagai changes the proposal and reads it back again, with the rest of your first sentence still in place.

  • A correction doesn’t carry anything out: you confirm the second time.
  • You can’t switch to a different command with a correction. If you meant something else, cancel and say it again.
  • You can’t clear a field: “remove the client” can’t be told apart from “I didn’t say one”.

Deletions sound different

By voice you can delete a task, a client, a project, a company or a tag. The read-back for a deletion doesn’t sound like the others: it names what’s about to disappear and says it can’t be undone.

  • For other commands, the read-back is a courtesy: a task closed by mistake can be reopened, a wrong date can be corrected. For a deletion it’s the only safety net, and you need to hear the difference before you say yes.
  • Comments, time entries and attachments can’t be deleted by voice: you remove them from the detail page, where you can see what you’re removing.

“I’ll delete T-155 Renew certificates. This can’t be undone: shall I go ahead?”

What bagai doesn’t guess

When something wasn’t said, or wasn’t understood, it stays empty, and the read-back tells you so before you confirm.

  • A client, project or person that isn’t in your records is left empty.
  • A name that matches two entries: bagai doesn’t pick one.
  • Assignees aren’t inferred: the person speaking isn’t assigned the task just because they spoke.
  • A date or duration that wasn’t understood stays empty, and isn’t made up.

Only with your permissions

Every command checks the speaker’s permissions. Someone who can’t delete a client can’t delete one by saying it either, and isn’t even offered that command.

  • Permission is checked when you confirm, not when the sentence is understood: if someone revokes it in the meantime, the command doesn’t go through.
  • The same rules apply. Closing a task with open subtasks by voice is refused just as it is manually, and the refusal says what’s in the way.
  • Your role’s visibility applies too: if you only see your own tasks, voice only searches among those.

What you can’t dictate, and why

Two things are left out of voice commands, on purpose.

Roles

A role bundles dozens of permissions. It’s the one case where a misheard sentence could grant permissions instead of just using them. Roles are managed on the Roles page, where you can see the whole permissions table.

An invited person’s roles and companies

Someone invited by voice starts with no roles, and the read-back says so: “I’ll invite Giulia Rezzonico, as a user, with no roles”. You assign their roles and companies on the Users page, where nobody can grant more than they have.

Where you use it

Today you can try it in the browser: you speak, read the read-back, confirm. Voice commands are designed for the apps: the iPhone app comes out in beta in November, the Android app in December, the Apple Watch app by the end of 2026.

  • Web

    You can try it today: speak in the browser, check the read-back, confirm.

  • iPhone

    Start from the Action button and see the read-back in the Dynamic Island, on models that have them. Beta in November.

  • Apple Watch

    Dictate and confirm from your wrist, for when your hands are full. By the end of 2026.

  • Android

    The same voice commands, with the same rules and the same read-back. Beta in December.

English and Italian

Voice commands understand English and Italian and use your account’s language, for the read-back too.

Recordings

While we’re still fine-tuning the feature, recordings are kept for a few days, to understand why a command was misunderstood. Then they’re deleted automatically.

  • They aren’t attachments, they don’t appear on any page, and they can’t be played back from bagai.
  • If you use your phone’s own speech recognition and send bagai only the text, bagai keeps no recording.
  • If your staff use voice commands, let them know the audio is kept for those few days.