What should happen when a PI lead calls after hours?

After hours does not justify a looser workflow. It makes the fallback more important. The system must know what it can collect, which facts trigger an approved escalation, when it may schedule and who owns the record before the office opens.

Begin with safety and contact

If the caller describes immediate danger or a life-threatening emergency, the system should direct them to local emergency services under the firm-approved wording. Otherwise it should establish language, identity, callback safety and the caller’s reason before collecting deeper facts.

Capture the useful minimum

The after-hours path should capture the same core incident facts as the daytime path. It may use a shorter first stage when the caller is tired or distressed, preserve progress and create a specific resume task rather than losing the call or forcing a long interview.

Use an operational priority reason

The firm may identify caller-stated facts that require immediate notification, such as hospitalization, death or a severe injury description. The system records the reason and follows the approved contact tree. It does not call the matter high value or promise representation.

Make transfer failure a real path

If the on-call person does not answer, the system must return to the caller, explain the next available option, book if allowed and create a timed task. A transfer attempt without a deterministic fallback is not a workflow; it is another way to lose a lead.

Close the loop

Confirm what will happen next, who will contact whom and whether a confirmation may be sent. The CRM record should be visible before the next business period begins. Operations should monitor overdue follow-up rather than assume the intake alone solved the problem.