Country selection organizes the website. It does not establish service availability, change billing currency or guarantee a local number.
QuickWA product preview. Sample data.
Local workflow guide
WhatsApp retail returns workflows for UK teams | QuickWA
Create a clear retail returns enquiry workflow for UK teams, with order context, evidence review, decision ownership and factual customer updates.
The QuickWA Team · 2 October 2026
A UK retailer handling a return enquiry needs to distinguish what the customer requests from what the business has checked. A message about an unsuitable size, a damaged item or a missing parcel starts a different conversation. Record the request accurately, consult your current published policy and assign any decision to the appropriate colleague.
Open the case with useful context
Ask for the order reference, item and reason for contacting you. Check what is already in the conversation before requesting it again. Collect relevant photos only when they help review the issue, and avoid asking for unrelated personal information. Keep the customer's preferred outcome visible: exchange, return enquiry or help locating an order.
For an explicitly illustrative example, imagine a footwear shop in Leeds receiving a WhatsApp enquiry about exchanging a pair for another size. An agent checks the order, records the requested size and asks the stock team to verify the alternative. This hypothetical case is a process example, not evidence of product availability or a QuickWA customer result.
Keep policy checks separate from promises
Use working stages such as information needed, policy review, stock check, decision pending and customer updated. Consult the policy relevant to that purchase before giving instructions. This guide does not determine legal rights or create a returns policy. Have the appropriate colleague review cases where the policy or decision is unclear.
A return label, replacement or refund should be described as issued only after the relevant source record confirms it. If commerce tools, API access or integrations are configured, verify the information they provide. Connector behaviour is not guaranteed. The ecommerce order updates workflow offers a practical way to connect messages with checked order events.
Make shop and fulfilment handovers precise
Leave a short note containing the order reference, requested outcome, evidence already supplied, decision owner and next update. If a shop colleague and warehouse colleague both contribute, keep one person responsible for the customer reply. Avoid making the customer interpret separate internal conversations.
Maintain reviewed templates for requesting missing details, acknowledging a pending check and explaining an approved next step. AI drafting, where enabled, should use maintained policy information and pass uncertain cases to a person. A draft must not invent a refund date, stock position or policy exception.
At the end of the shift, inspect cases waiting for a decision or returned parcel check. Follow up internally before sending another generic acknowledgement. Once the case is resolved, record the outcome so a later agent can understand what actually happened.
Match the plan to the process
QuickWA features, including shared inbox, contacts, pipeline, campaigns, forms, templates, AI, commerce, appointments, API and integrations, depend on eligible plans and configuration. QuickWA plans start at $5/month; see details in dashboard Billing. AI and provider fees are separate. Free Virtual Number for WhatsApp is one USA number on eligible paid plans while subscribed, subject to availability, verification and registration requirements; UK or other local numbers are not guaranteed.
Prepared by the QuickWA Team.
Can this workflow decide whether a customer qualifies for a return?
No. Use the relevant purchase details and current policy, and have an appropriate colleague review the decision; this guide does not determine legal rights.
When should an agent say a refund or replacement has been issued?
Only after checking the relevant source record; otherwise describe the request as pending and name the next action without inventing a completion date.
Business tools
Shared inbox
Assign conversations, keep customer context and hand work to the right person.
Campaigns and templates
Organize relevant audiences and approved messages. Every send remains subject to policies and plan quotas.
AI and automation
Build focused workflows and keep a clear human handover. Availability depends on the plan and configured providers.
Commerce and integrations
Connect order enquiries, bookings and business systems where the configured integration supports your workflow.
Plans start at $5/month.
Detailed prices, feature access and message limits are shown in dashboard Billing. Provider usage is separate.
No QuickWA markup on Meta messaging fees. Subscription, AI usage, calling, optional number rental and applicable external charges remain separate.
Free Virtual Number for WhatsApp - One USA virtual number included on eligible paid plans while subscribed. Availability, verification and WhatsApp registration requirements apply.
ISO country / territory code: GB / GBR. Make dates and amounts unambiguous. Plan a reply in the customer's timezone.
ISO country / territory code
GB / GBR / 826
Language references
English, French, Welsh, Irish, Scottish Gaelic
Currency references
British Pound (GBP)
Timezone references
Europe/London
Language and currency references come from Unicode CLDR locale data. They are not a statement about every resident, current legal status, market demand or supported checkout currencies. Timezone identifiers come from IANA. Ask your customer which language, currency and location apply to their conversation.
Make dates and amounts unambiguous
A customer-facing quote should include the currency code, units and a full date. The examples below illustrate local formatting only; they are not QuickWA prices, exchange rates or payment offers. Keep order references and quantities unchanged when translating a reply. Ask a person to review any ambiguity before confirming the order.
Illustrative date: 3 October 2026 (en_GB)
3 October 2026
Illustrative amount: 1,234.50 (GBP)
£1,234.50
Plan a reply in the customer's timezone
Choose a timezone and a date and time in your browser's timezone to see the corresponding customer time. Agree on actual opening hours with the business. Do not assume a country's capital represents every customer, and check the date as well as the hour when handing a conversation across borders.
Customer date and time
Build an inbox handover that another person can use
Record the customer's preferred language, location, enquiry reference, last confirmed decision and next action. Assign an owner rather than leaving a conversation with an unnamed team. If a message needs translation, keep the original beside the reviewed reply. Use the local time reference above when promising a callback or collection window; a template must not invent stock availability, a booking or a delivery commitment.
Keep service messages and promotions separate
Ask for permission for the relevant message purpose and record how it was obtained. An order question is not a reason to add someone to every campaign. Respect stop requests across scheduled audiences as well as the current chat. Follow Meta's current messaging and template requirements, and check applicable rules with the responsible business before launching. Using WhatsApp Cloud API does not prevent account restrictions.
Give automation a clear boundary
Use forms for the details needed to handle an enquiry, templates for approved wording, and workflow steps for a checked next action. Escalate complaints, uncertain translations and changes to accepted orders to a person. Before launch, check plan access and test with sample records without sending paid messages or collecting real customer information. Monitor unresolved cases instead of treating an automated reply as a completed sale.
Launch checklist
This checklist stays in this page only. It does not configure your account or authorize messages or payments.
Sources and limits
This reference covers ISO countries and territories, including locations without a permanent resident market. Listing a location is not an endorsement, a local office, a local-number offer or a statement that providers can serve it. Dataset references are useful for preparation; customer preferences and current provider requirements take priority.
Does selecting United Kingdom change billing or guarantee a number?
No. Website country and language selections do not change account billing, plan permissions or provider eligibility. Review actual checkout terms in your account. An included virtual number is a USA number on eligible paid plans, subject to availability and registration requirements.
Can this reference guarantee that WhatsApp will not restrict my account?
No. Consent, content, business eligibility, message quality and platform rules still apply. Keep a human escalation route and follow Meta's current requirements.