What I can share
Customer-facing ordering work where the job was reducing friction between menu selection, pickup intent, and store handoff.
Operational work focused on cleaner handoffs, clearer failure states, and fewer loose ends when customer actions need restaurant follow-through.
Experience with fast ordering, repeat purchase behavior, pickup context, limited attention spans, and store-level execution constraints.
What I cannot share
I cannot send Subway proprietary code, screenshots, internal documents, credentials, dashboards, private performance data, or anything owned by Subway or its vendors. The useful part for Slushie Kang is the playbook: capture intent quickly, clean up the handoff, follow up automatically, and give the owner a daily operating summary.
How this maps to Slushie Kang
- Missed calls and catering questions become a lead log with automatic follow-up.
- Flavor, hours, location, and event questions get answered consistently before a customer disappears.
- Repeat customers can be segmented into simple winback and VIP lists.
- Inventory watchlists can flag low-stock items before a busy weekend.
- Owner summaries can show yesterday's leads, unresolved customer requests, review items, and stock watchouts.
Fastest paid next step
For $49, send me one current bottleneck: missed calls, catering inquiries, flavor inventory, loyalty follow-up, reviews, or daily owner reporting. I will map the first automation and send back the workflow outline today. If it is worth implementing, the $499 setup pilot applies the same map to the real menu, inventory, and order flow.