Skip to content

AllBox Virtual Agent

Use Virtual Agent to configure the conversations and actions available from one AllBox. The policy is scoped to the selected site, post, and AllBox configuration; it is not a blanket authorization for every device or entrance.

Availability

  • Enable the virtual agent for this AllBox activates the policy.
  • Menu label controls the public action name.
  • Menu order accepts positions 1 through 20.
  • Conversation language selects the default language.

If Virtual Agent is selected as the Primary menu option on Overview, the policy must be enabled or the AllBox cannot be saved. Disabling the policy does not automatically choose another primary action.

Workflow permissions

Assistance available selects the conversation flows the agent can handle. At least one flow is required while the policy is enabled.

Record processing the agent may perform limits data-level operations. Select only actions approved by site policy. The Host approval timeout is required for an enabled policy and must be between 30 and 900 seconds.

When assistance cannot be completed chooses the escalation behavior. A phone escalation requires a destination number. Remote Guard escalation depends on the site's Remote Guard configuration and staffed availability.

Recording and retention

Record calls for quality and auditing enables call recording. When enabled, select a transcript and recording retention period: 7, 30, 60, 90, 180, or 365 days.

Warning

Recording, transcripts, identity data, and access approvals can be subject to consent, privacy, retention, and security requirements. Obtain policy approval and publish required notices before enabling recording.

Hardware access

The hardware grid limits the agent to exact targets from the selected post:

  • the AllBox relay;
  • access-control readers configured for remote open;
  • controller outputs available for remote operation.

Use search and the Hardware type and Agent access filters to find a target. Enable Allowed only after confirming the physical name, controller, post, reader port or output number, and pulse behavior. A target that does not allow remote operation cannot be selected.

For a new AllBox, reader and controller-output choices can be staged before the first save. The AllBox relay becomes available only after the AllBox record exists, so save once, reopen the record, and add that relay if required.

Only selected hardware is disclosed to the agent. Portal approval and authorization are still revalidated for each access command; assigning a target does not by itself guarantee that an unlock will be approved.

Danger

Hardware access can operate a real door, gate, or relay. Use precise names, authorize the minimum necessary targets, and conduct supervised success, denial, timeout, and escalation tests.

Save behavior

The main AllBox record saves before its Virtual Agent policy and hardware mappings. If the policy service reports an error, the AllBox may already have been created or updated. Reopen the record, verify the main configuration, correct the policy problem, and save again.

For the host or resident approval experience, see Virtual Agent visitor approval.