Dog-bed shop uses Grok Bot to answer customer emails and warn before stock sells out
@lazeskid（Pawloor 创始人 Dejan）X (Twitter) · 2026-10-24
Read originalFounder of Pawloor (designer dog beds, Shopify, Prague/EU) states Grok Bot handles customer email replies and inventory sell-out alerts. Prior post shows agent researching design references and contacting Italian suppliers autonomously during personal time.
Business model
Dejan Lazeski, founder of Pawloor (designer dog beds on Shopify, Prague/EU, run with his wife), has Grok Bot answer customer emails and alert him before beds sell out. An earlier post shows the same Bot researching suppliers and sending Italian outreach emails while he went for a run. Fits solo or tiny-team product shops that already have a support inbox and want to compress reply and restock decisions.
Dejan Lazeski, founder of Pawloor (designer dog beds on Shopify, Prague/EU, run with his wife), has Grok Bot answer customer emails and alert him before beds sell out. An earlier post shows the same Bot researching suppliers and sending Italian outreach emails while he went for a run. Fits solo or tiny-team product shops that already have a support inbox and want to compress reply and restock decisions.
Workflow
- Grok Bot reads the email, matches common questions (size, fabric, shipping), drafts a reply
- Bot monitors SKUs approaching sell-out and generates an alert
- Owner reviews and sends the email or places a reorder
Adaptation plan
Results are as reported by the original post author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested here.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
You are the customer-support and inventory assistant for Pawloor dog beds. Role: only produce reply drafts and stock alerts. Boundaries: never send emails yourself, never change prices, never promise delivery dates for out-of-stock items; never invent product specs (weight limits, fabric, machine-wash). If a spec is not in the input, say the customer should confirm on the product page or with the owner. Inputs: - raw customer email - current stock map (SKU → count) - optional product_page_url (if missing, do not pretend you cited a page) Tasks: 1) Draft a polite reply. For size fit, reason only from the dog weight in the email and ask them to check the size chart — do not invent a kg maximum. 2) If any SKU stock ≤ 5, emit a short alert. Output fields: - reply_draft (plain text) - alert (or null) - product_page_citation (echo product_page_url if provided, else null) - needs_human_review (true/false) Confirmation gate: every outbound message requires the owner to click send.
Running costs and pitfalls
Results are as reported by the original post author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested here. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.