If the call was in general to the customer, we likely want to find the Shopify Customer by phone or email.

If the call was specifically about an order (like an order confirmation call), we might want to find that Order by number or ID.

If Awaz call didn't have email, but you have phone, you could do a workaround: search customers by phone could require a GraphQL or custom API call. Alternatively, if phone is included in customer record as phone or as default address phone, Zapier's find might not support phone directly. Another approach: use Find Order by phone (if the call was related to an order, but not guaranteed to match).

For simplicity, let’s assume you have customer’s email available (maybe Awaz agent asked it or you had it in Awaz contact). If not, you may skip find and just create note by phone reference, which is tricky. Possibly better to do nothing if we can’t identify or perhaps create an internal record in Shopify via meta.

Shopify find order by Zapier allows search by Order Number or Name, or perhaps by other fields. If phone is present in order contact info, you might try search query as phone. Possibly better: find customer first, then find their latest order.

If your use-case is specifically post-purchase calls, you likely triggered the call from scenario B with order info, so scenario A could instead be triggered by the same event (though that would be redundant). Possibly scenario A is more for an inbound support call and then you'd update something.

Use “Find Customer by Email” if possible. Map Awaz email.

Then “Update Customer” with the ID from find.

Alternatively, create an Order Note if referencing an order. Then you'd do “Update Order” action, providing order ID and then note or tag.

If the customer wasn’t found, Zap might error. You could handle that with Paths: Path A if found -> update; Path B if not found -> maybe create an internal record or skip. For simplicity, ensure your test uses a known customer.

Find by phone fallback: If email isn’t available, and if phone is unique enough, one workaround: use Shopify API via Webhooks or code: There's the “Shopify Admin API” which you could call in a Webhook step to search customers by phone (GraphQL or REST). That’s advanced and requires API credentials and careful use to avoid complexity beyond this guide.

Ensuring no duplicates: If you choose to create new customer when not found (Zapier find has that option), you might inadvertently duplicate an existing one if search criteria misses. Prefer to not auto-create or use robust search.

Mapping correct fields: For update, to add a tag without wiping existing, know that Shopify expects a comma-separated string of all tags. If Zapier’s integration requires explicit tags, you might do: {{find_customer_step.tags}}, AwazCalled in the field.

Limitations: Shopify triggers (like new order) give complete data including customer ID, which could simplify scenario A if we use scenario B’s trigger for scenario A actions. Possibly easier: combine scenario B and A in one Zap triggered by order, then call, then update order or customer. But scenario A as separate makes sense if calls can happen outside just new order events.

Additionally, you could filter by Gateway (maybe only COD orders get confirmation call), or by Tags or any line item property. Example: If upsell call for specific product, filter if product title contains "Premium".

If no filter, just proceed with all (with phone check ideally).

You might want to record that this call was queued or done in Shopify (like scenario A does). But since this triggers right after order, you could directly update the order:

Could send a Slack message to sales team: "Awaz is calling customer X for order #1234 now." so team is aware.
​
​

No phone number cases: If many orders lack phone, maybe you pivot strategy: maybe send an email with a link to schedule a call (pull them into Calendly scenario) rather than immediate call. Or make phone required at checkout for shipping (Shopify allows you to require phone for shipping contact, but many customers prefer not giving phone).

International calling costs: If you have global customers, ensure your Awaz can call those numbers and consider cost. Perhaps filter by country if needed (like maybe don't auto-call international because of language/timezone issues).

Call timing: Middle of night orders would trigger immediate calls – maybe not ideal. You could refine by checking order timestamp vs a window. Possibly use a Filter: if order time (Zapier gives in UTC or store timezone) is within business hours, call immediately; else, schedule for next morning. This is advanced: you can use Zapier Formatter to parse order time and check hour. Or simpler, always delay calls by e.g. 8 hours, or use Delay until a fixed time next day if outside hours. Those require conditional delays or multiple Zaps for day/night. Keep it in mind to not annoy customers at 3 AM.

Agent script limitations: Without feeding exact order details, the agent will speak generally. If you want the agent to reference the product, you might need to integrate deeper (maybe use an Agent Trigger system where you pass the product name via an API call to Awaz right before call, or have Awaz fetch via Shopify API given order ID maybe you passed as contact name). That would require Awaz agent custom development. If not, keep it generic: e.g., "your recent purchase from [StoreName]".

Upsell logic: If upsell, maybe filter which orders to call (like only if they bought product A, call to upsell product B). Or have the agent dynamically decide based on what they bought (again needs item info).

Testing with real orders: Try placing a test order on your store (maybe a $1 product or draft order) with your number, see if you get the call and how it goes. Ensure to disable the Zap or use a filter to avoid calling actual customers until you're satisfied.

Shopify Flow conflict: If you also use Shopify's native Flow automation or other apps, ensure no double contacting. Our Zap triggers on order creation just like those might.