1. **Analyze the Request:** * **Keyword:** "Uber Customer Service Number Nz" * **Context:** Some fragmented text ("Here's how to", "Need", "How To", "Drive smarter...", "Do you have an issue with a passenger..."). The context seems to be about solving issues with Uber, likely for drivers or passengers, and hints at a specific resource (Solo) but focuses on problem-solving. * **Format:** Concise, factual, SEO-friendly HTML. * **Allowed Tags:** h2, h3, p, ul, ol, li, strong, em. * **Constraints:** No markdown fences. 600-900 words. Natural headings. Avoid unsupported claims. No AI mention. * **Goal:** Write an original article optimized for the keyword, using the provided context where it fits naturally. 2. **Determine the Intent:** * Users searching for "Uber Customer Service Number Nz" are likely experiencing a problem (lost item, charge dispute, safety issue) and want to speak to a human immediately. * *Fact Check:* Uber generally does not have a direct public phone number for general support in New Zealand (or most places). They rely on the in-app Help system. * *Strategy:* Explain that there isn't a direct phone number for most issues, guide them on how to get help via the app (which is what "Uber Customer Service" actually means today), and mention specific scenarios (Critical Safety Response Line) where a number *does* exist. This provides factual, helpful information while satisfying the SEO intent. 3. **Outline the Article:** * **H1 (implied):** Uber Customer Service NZ (Heading 2 in HTML structure) * **H2: Is there a direct Uber customer service number in NZ?** (Address the immediate question). * **H2: How to contact Uber support via the app** (The primary method). * **H3: For Riders** (Steps). * **H3: For Drivers** (Steps). * **H2: When to use the Critical Safety Response Line** (The exception where a number exists). * **H2: Common issues and how to resolve them** (Using context: "Do you have an issue with a passenger...", "lost items"). * **H2: Tips for a smoother resolution** (Context: "Drive smarter...", "Need..."). * **H2: Conclusion** 4. **Drafting Content (Iterative refinement for word count and keywords):** * *Intro:* Acknowledge the frustration. State clearly that a direct phone number isn't the standard way to get help. * *Section 1 (The Number):* Explain that Uber operates digitally. Mention the phone number is usually reserved for emergencies. * *Section 2 (The App):* Detailed steps. "Here's how to" find the Help section. * *Section 3 (Drivers vs. Riders):* Differentiate the flows. Use the context "Do you have an issue with a passenger" for drivers. * *Section 4 (Critical Safety):* Mention the 24/7 safety line. * *Section 5 (Specific Issues):* Lost items, pricing. Use "Need" and "How To" naturally here. * *Section 6 (Efficiency):* "Drive smarter" context (though the link provided is for a specific product, I should focus on the *concept* of working smart or resolving issues efficiently, as I can't insert an external affiliate link unless it's part of the specific "context" instructions. The prompt says "Use this context when useful". The context includes the link. I should probably weave the *text* of the context in naturally, but maybe not the affiliate link if it looks spammy, or just use the text as inspiration. Actually, looking at the prompt "Use this context when useful... Drive smarter...". I will use the *textual phrases* provided in the context list to shape the sentences, but I will avoid pasting the raw affiliate link unless it fits a "resource" section, as SEO articles usually don't like random affiliate links unless it's