E-commerce
September 3, 2026
Are you wondering how to react when a customer reports that their PIN code does not work or that a locker compartment cannot be found? It is imperative to distinguish temporary technical issues from expiration delays to avoid a costly return to the warehouse and a loss of trust. The key lies in the strict application of a carrier matrix and verification procedures before any escalation to the logistics provider.
So how do you manage access codes and incidents on pickup lockers? On the agenda:
Why do PIN code errors generate so many support tickets?
How to effectively classify the eight common incident scenarios?
What structure should be adopted for the reference LOCKER-MAP matrix?
What are the six imperative rules to never promise the impossible?
What macro-responses should be used to handle each type of incident in a single step?
Let's go.
Summary
Why do PIN code errors generate so many support tickets?
When a customer chooses an automated locker during checkout, they commit to automated logistics where human intervention only occurs for exceptions. Support tickets often arise because the customer does not understand the model or because a technical friction occurs at the critical moment of retrieval.
The customer receives an SMS with a code, goes to the location, and the terminal refuses to open or displays an error. Without a defined procedure, the agent risks promising an immediate reshipment without verifying the actual status of the parcel with the carrier, sometimes confusing automated lockers with pickups at classic post offices.
Five typical frictions explain the majority of these incidents. First, the PIN code may seem invalid if the customer is in front of an unmapped terminal or if they have forgotten the retention period. Secondly, the storage period may expire, leading to an involuntary return to the warehouse without the customer being notified.
Opening failures, where the door remains blocked or the compartment is indicated as occupied, create an emergency. Imprecise location via GPS or the tracking status "delivered" which does not yet mean "accessible" also complicate the customer relationship. Rigorous management of these flows is essential to maintain satisfaction.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How to effectively classify the eight common incident scenarios?
To structure your support, requests must be classified into eight distinct scenarios identified by specific codes such as locker_code_access or locker_retention_expired. Each typology requires a precise action and must not be treated in the same way to avoid unnecessary escalation.
The first case, locker_how_it_works, concerns the customer who does not understand the retrieval model offered during the checkout funnel. The second, locker_code_access, occurs when the PIN code or QR code is rejected by the terminal. This may be due to incorrect entry, an expired code, or a mismatch between the terminal and the application.
The third scenario, locker_not_available, occurs when tracking indicates "delivered to locker" but the customer cannot find their parcel. The fourth, locker_retention_expired, happens if the customer exceeds the retrieval deadline, resulting in an automatic return to the warehouse. The fifth, locker_door_malfunction, corresponds to a jammed door or a system failure.
The sixth case, locker_location_find, occurs when the customer cannot find the precise address or access to the locker's parking lot. The seventh, locker_wrong_parcel, occurs if another parcel is in the designated compartment. Finally, the last scenario, locker_redelivery_request, concerns the request for redelivery to another address after expiration.
What structure should be adopted for the reference LOCKER-MAP matrix?
The LOCKER-MAP matrix is the central tool that documents each locker carrier (InPost, Mondial Relay, Amazon Hub) so that your agents and your future bot have a single source of truth. This documentation allows for instant answers to complex questions without improvising a response that might be incorrect.
This matrix is built around essential columns specific to each carrier. The locker_carrier_id column identifies the logistics partner, while code_type specifies whether access is via a numeric PIN or a QR app. The retention_days column indicates the exact storage duration, often varying from 48 hours to 7 days depending on the partner.
It is crucial to include the rules for expired parcels in expired_parcel_rule to know whether the return is automatic or paid. The malfunction_escalate column lists the hotline and the necessary ticket reference in case of technical failure. Finally, tracking_status_map links the carrier's statuses to the actual state of the parcel (available, collected, or expired).
This database must be synchronized with the checkout funnel system and dispatch emails. It also allows for the generation of precise macro-responses that automatically integrate the retention period and the locator URL, ensuring consistent information with every customer interaction.
What are the six imperative rules for never promising the impossible?
To guarantee an impeccable quality of service, six imperative rules must be systematically applied before any response is given to the customer. The first rule, CARRIER-STATUS-VERIFY, requires always verifying the status via the carrier's API before asserting anything to the customer.
The second rule, RETENTION-CITE, mandates quoting verbatim the retention periods and return rules present in the LOCKER-MAP matrix. The agent must never invent a timeframe or promise an extension that does not exist in the carrier's general terms and conditions.
The third rule, MALFUNCTION-ESCALATE-CARRIER, stipulates that in the event of a blocked door or a mechanical breakdown, the agent must direct the customer to the carrier's hotline and not attempt a manual resolution. The fourth rule, CONSIGN623-REROUTE, reiterates that products consigned to the consignment shop must not be treated as standard parcels in the lockers.
The fifth rule, NO-DELIVERED-PROMISE, prohibits confirming to the customer that the parcel is "delivered" until the API has confirmed that the status is actually "available". Finally, the sixth rule dictates that all transmitted information must be anchored in the LOCKER-MAP matrix to prevent inconsistencies between the operational teams and support.
How to structure the agent intervention workflow on an incident?
The agent intervention workflow must follow a strict eight-step procedure to efficiently handle any incident related to pickup lockers. This logical sequence helps prevent human error and saves time on each complex interaction.
The first step, LK-1 Intake, consists of gathering the order number, the locker ID, photos of the broken terminal, and any relevant details. In the second step, LK-2 Carrier lookup, the agent consults the LOCKER-MAP matrix to identify the specific rules of the carrier concerned.
The next step, LK-3 Tracking verify, requires verifying the actual status via the carrier's API to confirm whether the package is available, expired, or in transit. Then, LK-4 Classify allows categorizing the incident according to the previously defined typologies.
At the LK-5 Policy triage level, the agent applies the corresponding retention or escalation rule drawn from the matrix. The sixth step, LK-6 Respond, consists of generating a response based on the matrix, including location information and the exact status.
The seventh step, LK-7 Execute, sees the agent executing the escalation to the carrier, initiating a reshipment, or a refund according to policy. Finally, the last step, LK-8 Close, consists of tagging the ticket as resolved and updating the package status in the internal system.
Which macro-responses should be used to handle each type of incident in a single step?
Support efficiency relies on the use of pre-configured macro-responses that are automatically populated with data from the LOCKER-MAP matrix. These standardized texts allow for precise and rapid responses to each scenario without having to rephrase technical information every time.
The first macro, LOCKER-EXPLAIN-01, is designed to explain the process to the customer from the very beginning: it mentions the carrier, the access method (code or QR), the retention period, and provides the URL of the locator. The second, LOCKER-CODE-01, addresses access issues by indicating the exact status of the parcel and the validity of the code until the deadline.
For mechanical breakdowns, the LOCKER-MALFUNCTION-01 macro guides the customer to the carrier's hotline with a precise ticket reference, while reassuring them that the internal case has been opened. Finally, the fourth macro, LOCKER-REDELIVERY-01, comes into play when the parcel has expired: it explains the expiration rule, potential return fees, and the options offered for the new delivery.
These macros ensure perfect consistency between what the agent says and the carrier's contractual rules. They also reduce average handling time by automating the complex informational part, leaving the agent to manage the emotional aspect of the stressed customer.
What are the specific points of vigilance for returns via pickup lockers?
Support for returns via drop-off lockers has a specific dynamic that requires special attention to avoid disputes and financial losses. Unlike dropping off at a staffed service point, the process is fully automated and demands absolute rigor in verifying statuses.
It is essential to explain clearly to the customer that a parcel dropped off in a locker for return must be placed in the designated compartment without delay. If the drop-off window expires, the refund process may be blocked or delayed until physical receipt at the warehouse.
The return policy via locker must clearly distinguish shipping fees. Some carriers charge for a return if the parcel is not dropped off within the allowed timeframe or if the return label is incorrect. It is therefore necessary to check the matrix to inform the customer of the refund conditions in case of non-compliance with the deadlines.
Support must also handle cases where the return compartment is full or out of service. In this case, the agent must immediately provide an alternative solution, such as a nearby staffed service point or a home collection procedure, to prevent the customer from being left with an unreturned product.
How to avoid confusion between automatic lockers and consignment stores?
A common confusion occurring in support concerns the distinction between parcels dropped off in automated lockers and consigned products in the consignment shop sense. These two mechanisms sometimes use similar terms but rely on completely opposite logistics.
In the context of pickup lockers, the term "consigned" simply means that the parcel has been deposited in a secure compartment for later retrieval by the customer. There is no concept of a deposit or a loaned product as in traditional consignment business models.
Scenario #623, consignment, implies that the product still belongs to the seller or consignor and is stored for later sale. The logistics differ completely because it involves a reverse flow or temporary storage that does not follow the rules of automated lockers.
Your agent must be trained to identify this specific type of request in order to redirect it to the appropriate process #623. Treating a consigned product like a standard parcel in a locker can lead to inventory errors and disputes over ownership of the goods. The strict separation between the two flows is therefore critical for the management of your logistics.
What is the merchant's responsibility for unclaimed deliveries?
The merchant's responsibility for unclaimed deliveries depends heavily on the carrier's general terms and conditions and the clarity of the communications sent to the customer upon shipment. It is vital to clearly define who pays for returns in the event of a collection failure.
If the retention period expires, the parcel is generally returned to the seller's warehouse. According to the LOCKER-MAP matrix, this can result in return fees paid by the customer or by the merchant depending on the terms of the service subscribed to. The agent must know these rules to correctly inform the customer.
The merchant cannot always block the automatic return once the date has passed. The LOCKER-SUP policy states that the return is often unavoidable if the deadline is not met. Therefore, these risks must be communicated right from shipment so that the customer takes responsibility.
To limit losses, it is recommended to integrate automated reminders in the SMS or email delivery notification. These messages must remind the collection deadline and explain what happens in case of non-collection, transforming a potential incident into a preventive action.
Why is API verification crucial before any client explanation?
API verification is the pivotal step that prevents all communication errors with the customer. Before explaining the situation, the agent must absolutely check the actual status of the parcel via the carrier's interface to know if it is truly available or not.
Confirming a "delivered" status without verifying that the parcel is physically accessible in the locker is a common mistake that generates frustration. The "delivered" status often only means that it has been dropped off, but does not guarantee that the compartment status is "ready for collection".
Furthermore, API verification makes it possible to distinguish cases where the parcel was retrieved by the carrier from a technical issue. Without this data, the agent risks telling the customer they can collect their parcel when it has already been sent back to the warehouse.
This validation step ensures that each response provided is factual and based on current logistical reality. It also protects your reputation by avoiding false promises that lead to multiple customer calls and growing dissatisfaction.
How does Qstomy help solve real-time access issues?
Qstomy acts as a Shopify AI agent capable of managing these complex scenarios directly in your customer conversations, connecting to your logistics data to provide instant answers. Unlike classic tools, Qstomy doesn't just give generic answers but uses the LOCKER-MAP matrix to resolve access and code issues.
When a customer reports an invalid code, Qstomy immediately checks if the package is still within the retention period and which terminal is valid. If there is a breakdown, it generates the link to the carrier's hotline while opening an automatic escalation ticket for your team.
This approach significantly reduces ticket processing time and allows your human agents to focus on the most complex cases. Qstomy thus ensures 24/7 coverage for returns, package tracking, and payment issues such as expired cards.
By integrating Qstomy, you transform a point of friction into a seamless customer experience where every incident is resolved with the precision of a human expert without any waiting time. It is the ideal ally to manage your support efficiently and scalably.
What checklist should be followed before communicating about a locker issue?
Before communicating about a locker issue, a strict checklist must be followed to guarantee the quality and reliability of your response. This preparatory step prevents errors in judgment and ensures that all relevant information is gathered.
First, verify the identity of the carrier and consult the corresponding LOCKER-MAP matrix to determine the code_type and the exact retention period. Then, confirm the actual status via the carrier's API before committing to your response.
Ensure that the selected response macro corresponds to the exact scenario: invalid code, expiration, or mechanical failure. Finally, check if specific fees apply for resending in the event of expiration.
To go further: How to handle customer questions about gift cards combined with a card payment - Qstomy, How to handle customer questions about shopping carts funded by multiple payment methods - Qstomy, How to handle customer questions about parcels in pickup lockers - Qstomy, How to handle customer support for returns via locker or service point - Qstomy, How to handle customer questions about in-store pickup without a dedicated app - Qstomy, How to handle customer questions when mixing multiple languages in a conversation - Qstomy, How to handle customer questions about multi-store shopping carts - Qstomy.
Enzo
September 3, 2026
