Concierge today: Shopify email pilot with reviewed replies and verified order-status answers. The examples below also describe workflows for future planning; Voice and socials are planned. Owner-reviewed commerce actions and storefront chat with team replies or separately authorized public FAQ answers are available.

Which Shopify support workflows are a good place to start?

Choose workflows with a clear source of truth, explicit eligibility rules, and an observable result. Order tracking is a different task from changing an order: one retrieves information, while the other alters a customer’s purchase and needs stronger permission checks.

Example workflows to scope during onboarding
Customer requestContext and policy checksDesired outcome
“Where is my order?”Correct order, fulfillment status, available tracking information.Share the current status without inventing a delivery promise.
“Can I change my address?”Customer verification, edit permissions, fulfillment stage.Confirm the saved address change or follow the exception process.
“Can I swap this for another size?”Exchange window, item eligibility, replacement availability.Arrange an eligible exchange and explain the next steps.
“I’d like to return this.”Return window, exclusions, item condition, refund rules.Start the permitted return process or explain the policy.
“Which product should I choose?”Product catalog, customer preferences, current availability.Give a grounded recommendation and identify missing information.

These are examples for planning, not a promise that every store or connected app permits every action. Confirm your store configuration and integration requirements before enabling a workflow.

Example: changing an order before fulfillment

A customer sends a social message asking to switch a tote from Sand to Olive. The agent first needs to identify the order and verify that the customer can request the change. It then checks the fulfillment stage, variant availability, and any price difference against the brand’s policy.

If the change is permitted, the next step is to update the order and confirm that the update was saved. If Olive is unavailable, the agent should offer permitted alternatives. If the order is no longer editable, it should follow the defined exception process. The same decision should apply if the customer asks by email or phone.

What should you prepare before connecting an AI agent?

  • Policy sources: current return, exchange, cancellation, shipping, and refund rules, including exceptions.
  • Store context: product information, fulfillment stages, and the systems that own each part of the order journey.
  • Permissions: the actions the agent may perform and the circumstances requiring approval.
  • Channel scope: the inboxes, chat surfaces, phone workflows, and social accounts to connect.
  • Test cases: representative customer requests with the expected result for each one.

Resolve conflicting policies before launch. If a public FAQ says one thing and an internal document says another, identify which source governs the action and update the other source. See the policy guide and downloadable worksheet.

How do you roll out AI support without losing context?

Start with a defined set of workflows and test both successful and unsuccessful outcomes. Review the conversation alongside the underlying order state: did the promised change happen, and was it permitted? Expand the scope when the results meet your standards.

For cross-channel requests, decide how customer identity and conversation history are linked. Avoid making a customer repeat the entire story because they moved from chat to email. Also check how the system prevents duplicate work when the same request arrives through two channels.

How does Concierge support Shopify brands?

Concierge is one AI customer experience agent that answers inquiries and makes customer-requested changes according to your operating policies. The current pilot covers support email and a shared review queue. Owner-reviewed address changes, supported capped refunds, and return/exchange creation are available. An owner-enabled storefront chat pilot supports team replies. AI chat, voice, socials and external helpdesk integrations remain planned.

Join the early-access waitlist to discuss your store, policies, and workflows. Specific integrations and permitted actions are confirmed during onboarding. Concierge does not publish a universal automation percentage or a fixed public price; the focus is on the outcomes your brand needs.

MEET YOUR CONCIERGE

A calmer inbox.
Meet your Concierge.

Join the early-access waitlist for AI customer service guided by your operating policies.

Join the waitlist