Using TacBot for mobile duty

TacBot is the AI assistant built into your management dashboard. It can help you manage mobile duty operations using plain English commands — no need to navigate through menus.

Note: TacBot requires the AI Chat feature to be enabled for your account. Mobile Response must also be enabled for your sites for mobile-duty commands to work.

Putting an officer on mobile duty

You can ask TacBot to activate mobile duty for a specific officer directly from the chat panel. For example:

"Put James on mobile duty"

"Start a mobile duty for Sarah"

"Can you begin mobile duty for Officer Chen?"

TacBot will look up the officer, confirm they are a designated mobile response officer, and show you a confirmation card before making any changes.

The confirmation card

When TacBot is about to perform an action — such as starting a mobile duty — it never acts immediately. It shows a confirmation card that summarises exactly what it is about to do:

• The officer's name and current status.
• The action: Start mobile duty.
• Any relevant site or shift details it has inferred.

The card has a Confirm and a Cancel button. Only once you tap Confirm does TacBot carry out the action. This two-step pattern applies to all write operations TacBot can perform, so there is always a human in the loop before anything changes in the system.

Other mobile-related questions you can ask

• "Which officers are on mobile duty right now?"
• "Show me today's site visits for [officer name]"
• "How many callouts did we have this week?"
• "What is the SLA target for [site name]?"

TacBot can answer these questions directly from live data without any confirmation step, since they are read-only queries.

Limitations

TacBot cannot raise or close a callout — that must be done from the Callouts board. It also cannot change an officer's mobile response officer toggle (that is a profile edit done in Users). For anything TacBot cannot do, it will tell you and suggest where in the system to go instead.