---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Manage Walk-up Experience interactions manually

# Manage Walk-up Experience interactions manually {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Agents supporting walk-up locations can manually manage queue requests with several
Walk-up Experience interaction-related modules.

## Before you begin

Role required: sn_walkup.walkup_technician

## About this task

Manage interactions manually using the Walk-up Experience Technician modules found in the application navigator. To manage automatically assigned interactions from the Agent Workspace inbox, refer to [Manage automatically assigned Walk-up Experience interactions](https://servicenow-prod.fluidtopics.net/OFb5ZfHAOIo7kj4ABK_lYw "The agents supporting Walk-up Experience locations can view and manage interactions automatically pushed to the Agent Workspace inbox.").

Walk-up queues support requesters in the order that they check into the queue
--- first come, first served. The agents supporting the queue can decide who will work
on the first interaction. As new requesters enter the queue and submit interactions,
technicians share the workload, assigning queued interactions to
themselves.

Certain requesters are considered VIPs. The system recognizes this
when they check into the queue. An interaction for a VIP shows
true for VIP in the Interactions
list. The agents can move VIP requesters to the front of the queue by assisting them
first.  
Note:  
Creating walk-up type interactions manually is not supported. A walk-up
interaction is considered valid for check-in or appointment only if created via
the check-in or appointment booking interfaces, and not via a table. Agents
cannot check-in to a walk-up location on behalf of an end-user.

View walk-up queue interactions using several Walk-up Experience
modules:  
{#view-assigned-walkup-requests__table_x1b_z4b_qdb__entry__2}

| Module | Description |
|-|-|
| My Assigned Walk-ups | Interactions you assign to yourself when you accept an active interaction or that are assigned to you. Agents assign interactions to themselves when they accept a queued interaction. Managers can assign interactions to specific agents. These interactions are in a Work in Progress state. Once assigned, an agent can transfer the interaction to another agent or queue to complete the work, if necessary. |
| Open --- Unassigned | All open but unassigned interactions associated with your specific walk-up queue location. When a requester checks into a walk-up queue, an interaction is created. The interaction is Queued until an agent accepts it or is assigned the interaction. At that point, the state changes to Work in Progress. |
| Closed Walk-ups | All Closed Complete and Closed Abandoned interactions assigned to a specific walk-up location queue. Agents can abandon an interaction when a requester leaves the queue before receiving support. |
[Table 1. Walk-up Experience interaction modules]

{#view-assigned-walkup-requests__table_x1b_z4b_qdb}

## Procedure

1. Navigate to Walk-up ExperienceAgentOpened - Unassigned.
2. Find the requester name under the Opened for column of the Interactions list.
3. Click the interaction Number associated with the requester.
4. Enter your name in the Assigned to field on the form, change the State to Work in Progress, and select Update.
   1. To close an interaction if the requester has left the queue, click Abandon in the form header or choose Closed Abandoned from the State form field and click Update
   2. Alternatively, you can associate the interaction with another record by clicking the Associate Record button in the interaction header.
   {#view-assigned-walkup-requests__substeps_iw5_42n_3gb}
5. To resolve the interaction, navigate to Walk-up ExperienceAgentMy Assigned Walk-ups.
6. Click the interaction number from the list to open the Walk-up Interaction form.
7. Resolve the issue or fulfill the request.
   1. Change the interaction status to On Hold if the requester is not present for an appointment or if the interaction entails a lengthy process, for example, an OS upgrade.
   2. To view the walk-up location stockroom for fulfillment requests, click the Stockroom Consumables related link.
   3. If you cannot resolve the issue or fulfill the request, click either the Create Incident or Create Request related link to create an incident or access the Service Catalog.

   {#view-assigned-walkup-requests__substeps_rbk_t2n_3gb}  
   When you create an associated incident or request through the Service Catalog, the associated related lists on the form populate accordingly. Related lists include the following details:
   * Incidents for Interaction: Incidents associated with the interaction
   * Requests for Interaction: Service Catalog requests associated with the interaction
   * Incidents by Same Caller: Incidents created for a walk-up requester
   * Requests by Same Caller: Requests created for a walk-up requester
   {#view-assigned-walkup-requests__ul_qck_bfn_3gb}
8. Set the interaction State to Closed Complete and select Update to update the interaction, when you are finished resolving the interaction.  
   Alternatively, you can click Close to complete the interaction.
**Related tasks**   

* [Use platform view to fulfill a Walk-up Experience request from a stockroom](https://servicenow-prod.fluidtopics.net/6Z3T7XX~yncjHkDHFRlqSw "Walk-up Experience agents can access an associated stockroom and fulfill user requests directly from an interaction in platform view.")
* [Create an incident](https://servicenow-prod.fluidtopics.net/ZV5TUfs~ylIDsvcsk8LY6g "Create an incident record to document a deviation from an expected standard of operation.")

*[\>]: and then