Workflow guide
Recurring work in a small business often spans the inbox, stock records and payment dashboard. These three firsthand accounts show different handoffs: handling customer messages, organising repair requests and reporting operational exceptions. Start with the task closest to your own work, then decide what to delegate.
| Situation | Information needed | Agent contribution | Human responsibility |
|---|---|---|---|
| Product shop | Customer messages, product and stock information | Reply to customer emails and flag stock running low | Restocking, pricing and commitments outside the agreed scope |
| Computer / phone repair | Symptoms, device models and known errors | Organise checks, draft follow-up and research parts | Inspect devices, confirm findings and review customer messages |
| Solo product business | Support inbox and Stripe activity | Draft replies and check payment / subscription changes | Resolve exceptions, edit and send messages |
Dejan · Pawloor · Grok Bot
Pawloor’s founder reports using Grok Bot for customer replies and alerts before stock sells out. The useful question is whether an alert helps the owner make a timely decision, rather than simply adding another notification.
The available summary does not disclose thresholds, reply volume or time saved. It does not establish automatic purchasing.
@xCB06fr · Nice · Grok Bot
The owner separates symptom notes, follow-up drafts and parts research between bots. The useful distinction is the purpose of each output: questions to check, a message to edit or parts to assess.
A diagnostic checklist is not a confirmed diagnosis. The author describes reviewing drafts before customer-facing use.
Kyohei · labelmake · Grok Bot
The author describes scheduled checks of support email and Stripe, with notifications for matters requiring attention. They still edit and send replies themselves. The transferable idea is to reduce dashboard checking while keeping final decisions with the operator.
Existing product revenue is not revenue added by the bot. Choose a notification schedule for your own business rather than treating the author’s timing as a universal setting.
Choose a recurring task with accessible source information. Agree on inputs, outputs and when the agent should ask you. Assess the drafts or alerts before granting permission to send messages or write to systems.
For example, a customer asks why an order has not arrived. The order and tracking records are the evidence. An agent can identify missing information and draft a reply for review. If tracking is unavailable, return a question rather than inventing an arrival date. This example is an AgentFlow adaptation suggestion.
These are accounts from different operators, not one proven end-to-end workflow. Author claims are not independently verified, and labelmake’s product revenue does not establish revenue added by the agent.
