# Smart Missions: Automatic Detection on Every Mission Run #### Introduction Verkos Detect Anything Agent has always been capable of watching your site from the air. But until now, it only watched when a human told it to. Before this release, starting detection required a person to open the cockpit, pick an agent, click **Start Detection**, run the mission, then click **Stop**. Close the cockpit and the agent was gone. Next flight, repeat. For a security operator running perimeter patrols every two hours around the clock, that meant twelve manual starts a day per drone. For a fleet of five, sixty. Most of those patrols fire at 2am, 4am, 6am, when nobody is at the dashboard. Those flights went out with no detection running. Smart Missions closes that gap

Dashboard Utility View for Verkos Detect Anything AI Agents

#### **What's New** **Assign an Agent Once, Run It Automatically** You now assign a Verkos agent to a mission once. From that point on, the agent runs automatically every time that mission executes, whether you launch it manually from the cockpit, trigger it via an alarm, or the FlytBase scheduler runs it on a schedule. When the mission ends, detection stops on its own. No human in the loop. The unit of assignment is the mission. You can assign the same agent to many missions, different agents to different missions, or leave some missions without any agent. Only missions with an assigned agent run detection, missions without one fly exactly as they always did.

Assign specific agent for different missions individually

#### **How to Use It** The **Smart Missions** tab lives alongside the **Agents** tab inside the Verkos AI page. 1. Open the **Verkos AI** page from your FlytBase dashboard 2. Go to the **Smart Missions** tab 3. Select one or more missions from the list 4. Click **Assign Agent** 5. Configure three things in the panel that opens: * **Agent** - which Verkos agent should run on the selected missions * **Active hours (optional) -** the window of time during which the agent is allowed to run. Outside this window, the mission still flies, but detection is skipped for that run * **Notification recipients (optional)** - who gets alerted when this specific mission detects something. If not set, detections fall back to the global recipients 6. Click **Assign Agent** to confirm Once assigned, the agent runs on the next scheduled or manual execution of that mission, stops when the mission ends, and reports detections through the configured notification channels.

Process for assigning an agent for a mission

#### **Per-Mission Active Hours** A perimeter patrol at 2am and the same patrol at 2pm have different detection needs. The 2am run wants intrusion detection. The 2pm run may not, authorized personnel are on site and motion alerts become noise. Active hours handle this at the assignment level. Set a window, for example, 22:00 to 06:00 and detection runs only during mission executions that fall inside that window. Missions outside the window still fly normally; the agent just doesn't start. Cross-midnight windows are supported. #### **Mission-Level Notifications** Global notification recipients are alerted whenever any detection fires across your organization. This works for a single-site operation, but breaks down for operators running multiple sites, the Site A team shouldn't get pinged for Site B detections, and vice versa. Each Smart Mission assignment can carry its own notification list. When set: * That list takes over entirely for that mission * Global recipients no longer receive alerts for detections from this mission * Only the mission-specific list does * The assignment view shows at a glance whether each mission is using the default or a custom list

Assigning mail to get notifications for any detections throughout the mission

Mail notification which is received upon successful detection

#### **What Didn't Change** Existing agent configurations carry over without any action needed on your end: * Any agent you configured before this release - enabled events, custom prompts, detection frequency, works the same way inside Smart Missions * Assigning an agent to a mission uses that agent's existing setup; it doesn't ask you to reconfigure anything * Global notification recipients still apply to missions without their own list * The default cockpit agent still shows up for manual use when no mission is running Nothing you were doing before stops working. #### **What This Means** * Scheduled and alarm-triggered missions now run detection automatically, no operator required * Detection is no longer missed on overnight or off-hours patrols * Different missions can run different agents, with different active hours and different alert recipients * Fleet operators managing multiple sites can route detections to the right team per mission