Shopify Support During BFCM With AI
BFCM is a typed-ticket storm. Heroes lose.
BFCM is a typed-ticket storm. Heroes lose.
When to use this list
Freeze policy Monday, raise caps, QA daily. Do not launch new collections without articles. Print it or put it in the ticket you open with the vendor. If they cannot walk it, you are in a demo, not a trial.
The checklist
- Write the definition of support during bfcm with ai in one sentence the agent can test against an order.
- List the Shopify fields it must read before it replies (status, tags, tracking, refunds already issued).
- Write the allowed actions and the cap. If there is no action, write the exact escalate condition.
- Add two examples: a yes case and a no case. Agents learn more from the no.
- QA ten live tickets after a week. Change the article or the cap, not the vibe.
What you can skip
Migrating the entire macro museum on day one. Move the five types that are the volume.
Automatic fail
- They will not refund a test order.
- They need a solutions engineer for a 400-ticket store.
- The only metric they show is conversations started.
Load this rule into Relay and stop solving support during bfcm with ai by hand at midnight.

