Workflow Template

Safety incident reporting call app template

Captures incident facts, location, injuries, witnesses, hazards, and immediate controls for safety teams.

View output schema

Best fit

  • Construction
  • Warehouses
  • Schools
  • Events

Do not use it for

  • Emergency response replacement
  • Legal liability analysis

Call flow

1. Ask if emergency help is needed

Is anyone injured or in immediate danger?

2. Capture location and time

Where and when did it happen?

3. Record injury or hazard

What hazard needs attention now?

4. Ask witnesses

Is anyone injured or in immediate danger?

5. Escalate

Where and when did it happen?

Prompt template

Collect safety incident reports by phone. Ask if emergency help is needed, capture location, time, injury, hazard, witnesses, immediate actions, and escalate serious risks.

Questions asked

  • Is anyone injured or in immediate danger?
  • Where and when did it happen?
  • What hazard needs attention now?

Human handoff

  • Injury, ongoing danger, regulatory notification need
  • Caller requests a safety officer

Structured output schema

{
  "outcome": "Safety incident reporting outcome",
  "fields": [
    {
      "description": "reporter name captured during the call.",
      "name": "reporter_name",
      "required": true,
      "type": "text"
    },
    {
      "description": "phone number from caller id captured during the call.",
      "name": "phone_number_from_caller_id",
      "required": true,
      "type": "text"
    },
    {
      "description": "location captured during the call.",
      "name": "location",
      "required": true,
      "type": "text"
    },
    {
      "description": "incident time captured during the call.",
      "name": "incident_time",
      "required": true,
      "type": "date"
    },
    {
      "description": "injury captured during the call.",
      "name": "injury",
      "required": true,
      "type": "text"
    },
    {
      "description": "hazard captured during the call.",
      "name": "hazard",
      "required": false,
      "type": "text"
    },
    {
      "description": "witnesses captured during the call.",
      "name": "witnesses",
      "required": false,
      "type": "text"
    },
    {
      "description": "immediate action captured during the call.",
      "name": "immediate_action",
      "required": false,
      "type": "text"
    }
  ]
}

Transcript example

AI: Hi, I am an AI call workflow for Safety incident reporting. Is anyone injured or in immediate danger?

Caller: I need to report a slip near the loading dock.

AI: Where and when did it happen?

Caller: No one is badly hurt, but the floor is still wet.

Recommended integrations

Google SheetsSlackNotion

Launch review

Caller promise

Make the first screen and opening line match what the caller will actually get. For Safety incident reporting, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.

Required outcome

Decide which fields are required before the call can be considered complete. A practical first version should capture reporter name, phone number from caller id, location, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.

Human review

Write down the cases that should not be automated. Use human review for injury, ongoing danger, regulatory notification need, caller requests a safety officer so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.

FAQ

When should I use a safety incident reporting Call App?

Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for construction, warehouses, schools.

What should the AI ask first?

The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "Is anyone injured or in immediate danger?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.

What output fields should be saved?

Save a structured result with reporter name, phone number from caller id, location, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.

What should trigger human handoff?

Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: injury, ongoing danger, regulatory notification need, caller requests a safety officer.

Clone this template

The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.