How to Handle Recipient Not Home: A Guide for Delivery Service in Southeast Asia
The Operational Context
Delivery Service businesses frequently receive calls when delivery attempt failed, recipient not available. This scenario requires staff to contact recipient when delivery attempted but no one home, which is essential for maintaining customer satisfaction and operational efficiency. In Southeast Asian markets, these calls often occur across multiple languages and may involve mobile-first communication channels like WhatsApp Business.
This SOP addresses a common scenario for Delivery Service businesses operating in Malaysia, Singapore, Thailand, and Brunei. According to Erzy Inc.'s analysis of SEA SMEs, this type of call occurs regularly throughout the day and requires excellent communication skills and product knowledge to handle effectively.
When delivery attempts fail because recipients are not home, Transportation and Logistics service providers across Malaysia, Singapore, Brunei, and Thailand increasingly rely on phone voice calls to arrange redelivery, confirm alternative arrangements, or coordinate pickup options. Across all four target countries, the management of recipient-not-home scenarios via phone calls represents a significant operational and customer experience challenge, with first-attempt delivery success rates hovering between 70-85% depending on market maturity.
In Malaysia's rapidly growing e-commerce market (projected to reach US$13.43 billion by 2029), phone calls remain a critical operational tool when delivery attempts fail due to recipient absence. The Malaysian approach to recipient-not-home phone calls reflects broader cultural communication patterns emphasizing relationship-building and indirect communication, with drivers typically employing courteous language that acknowledges inconvenience while offering flexible solutions.
Who Handles This Call: Driver / Customer Service - This call type is typically handled by Driver / Customer Service who must have access to dispatch system, tracking database, driver management platform and knowledge of Transportation & Logistics industry standards, customer service protocols, delivery routes, traffic conditions.
The Standard Operating Procedure (SOP-TL-030)
Step 1: Call Reception & Verification
When the call is received, the Driver / Customer Service should:
- Answer promptly with a professional greeting
- Identify the caller's need by listening actively
- Verify any required information (customer ID, order number, etc.)
- Access relevant systems (CRM, inventory, booking system)
Step 2: The Resolution Script (SOP Simulation)
Staff: "Good morning, thank you for calling. This is Driver / Customer Service speaking. How may I help you today?"
Customer: "Hi there, I'm calling about delivery attempt failed, recipient not available."
Staff: "Of course. Let me assist you with your recipient not home. I'll just need a moment to check our system."
Customer: "Yes, that would be great. Thank you."
Staff: "You're welcome. Is there anything else I can help you with today?"
Localization Notes: Use appropriate greeting based on time of day and customer preference. In Malaysia/Singapore: Mix of Bahasa Malaysia, English, Mandarin, or Tamil. In Thailand: Thai primary, English secondary. Reference local services when relevant (Grab, Foodpanda, DuitNow, WhatsApp).
Step 3: Documentation & Next Steps
After resolving the call:
- Log the interaction in CRM or call tracking system
- Document any commitments made to the customer
- Set follow-up reminders if needed
- Update relevant systems (inventory, booking calendar, etc.)
- Escalate if required to manager or specialist
Key Documentation Fields: Caller name and contact information, Nature of inquiry/request, Resolution provided, Follow-up actions required, Date and time of call.
Automating this SOP with Erzy
This specific workflow has a Medium automation potential (65% automatable). The primary manual bottleneck in this SOP is manually contact recipient when delivery attempted but no one home. This typically requires 8 minutes of staff time per call and can create delays during peak hours.
Erzy's trucktalk.io platform can automatically handle delivery attempt failed, recipient not available calls. The AI voice system can verify delivery details, check shipment status, and coordinate with drivers in real-time. For logistics businesses in Malaysia and Singapore, this eliminates the need for manual dispatcher intervention for routine inquiries.
FAQ
Related Operations
Within Transportation & Logistics:
Proof of Delivery - Customer requests proof that shipment was delivered
Delivery Status Inquiry - Customer inquires about delivery status
Delivery Scheduling - Retail Trade
Delivery Time Complaint - Food & Beverage
Back to Pillar Page:
Ultimate Guide to Transportation & Logistics Phone Operations - View all 30 SOPs for Transportation & Logistics



