Personal response task
The outreach link opens a focused availability page rather than asking the responder to navigate the Command workspace.
AIGIS Command · Staffing & Availability
Know who can respond.
Choose responders, define the dates, and send an incident-scoped request by SMS and email. Responders select the specific dates they report as available from a personal link; Command tracks the replies and keeps assignment work in the same workspace.
Fixture-data product view. “Suggested” and Fit are operator-review cues derived from responder-reported requested dates and maintained record attributes. They are not AI recommendations, credential verification, readiness determinations, or assignment decisions.
AIGIS Command · Staffing & Availability
Availability and assignment
Collect availability before assigning responders.
Choose recipients, request specific dates, review replies, and open the incident personnel workflow when command is ready to assign someone.
Deliberate recipient targeting
Reach the right roster.
Select a responsible entity, review its people, and use maintained attributes to narrow the list when that supporting data is available. The final audience remains visible and explicitly selected before outreach is sent.
Focused responder experience
Make the reply simple.
The personal outreach link opens the request context and its date window. A responder selects every date they report as available, reviews the selection, and confirms before the response is recorded.
Date-by-date selection
Responders can mark every available date in the requested window, confirm the selection, and update it while the request remains open.
Narrow link access
The link authorizes the staffing-response task only. It is not a general platform session or a responder account.
Requested-date coverage
Compare the dates, not the guess.
Command groups delivery and reply rows by responder, compares selected dates with the requested window, distinguishes full requested-date coverage, and can include maintained record context in response ordering. Current incident assignment state remains visible, and operators can open the assignment workflow from the response view.
Scope
Start inside the incident.
Each campaign is tied to the active incident and a responsible entity, keeping the request with the response record.
Audience
Choose the people deliberately.
Narrow the directory with maintained person attributes when that data is available, then explicitly select every recipient before sending.
Window
Ask for exact dates.
Define a start and end date. Each responder selects the dates they report as available instead of returning an unstructured yes or no.
Action
Keep assignment human.
Review the response and requested-date coverage, then open the incident personnel workflow to create or edit an assignment.
Operational continuity
Keep staffing replies with the responder record.
Staffing outreach and replies appear in supported recent activity. Once assigned, the incident personnel record tracks role, status, shifts, and response history.
Workflow scope
What this staffing workflow covers.
It collects responder-reported dates and supports incident assignments. It does not verify credentials, approve deployment, or replace workforce scheduling.
Filters do not establish eligibility
Filters use maintained person attributes to help narrow the directory. They do not independently verify credentials, readiness, or deployment authority.
Availability is not a deployment commitment
Selected dates record what a responder submitted for that request. They do not guarantee attendance, travel, acceptance, or continued availability.
Delivery status does not prove a message was read
AIGIS can retain sent, skipped, failed, or partial-failure delivery state. A successful send does not prove that a recipient opened or understood the request.
Coverage data does not make assignments
Requested-date coverage helps operators compare replies. A person is assigned only when an authorized operator completes the incident personnel workflow.
Incident staffing is not workforce scheduling
The workflow coordinates incident availability and assignments. It is not payroll, timekeeping, overtime, benefits, or a complete workforce-scheduling system.
The response link is personal
The bearer link is limited to the response task and can become unavailable or expire. Recipients should treat it as sensitive until the request is closed.
AIGIS Command
Walk from outreach to assignment.
See recipient targeting, SMS and email outreach, the personal date-selection experience, response coverage, and the operator-controlled incident assignment workflow using your organizational structure.