Sales manager runs daily ops with Grok Bot: inbox scans, client briefings, supplier follow-ups, ERP quotes
Alexandre de Oliveira BorgesX (Twitter) · 2026-11-17
Read originalI'm a sales manager at a cutting tools company, and I use Grok Bot to run the routine side of my work: Inbox: it checks my two work inboxes every 30 minutes on workdays, flags replies, bounces and open items, and keeps my prospecting CRM up to date. Daily briefing: every Sunday to Thursday at 7 pm I get a briefing for the next day, built from my calendar and email, with a client dossier whenever I have a meeting. China suppliers: overnight it follows up with my Chinese suppliers and prospects, and at 6 am it sends me a summary, but only when there's news. Sales ops on demand: distributor prospecting campaigns with follow-ups, RFQs and margin comparisons, PDF quotes, master catalog upkeep, purchase orders, and invoices and stock entries in our ERP. Industry news site: for Usinagem360, the machining news site I co-founded, it triages sources every day and schedules 4 draft posts for the next workday. It also drafts a daily rare metals price update and a weekly recap that becomes a LinkedIn carousel.
Business model
A sales manager at a cutting-tools company uses Grok Bot for routine work: every 30 minutes on workdays it checks two inboxes, flags replies/bounces/open items and keeps the prospecting CRM updated; Sunday–Thursday at 7 pm it delivers a next-day briefing from calendar and email with a client dossier when a meeting is scheduled; overnight it follows up with Chinese suppliers and prospects and sends a 6 am summary only when there is news; on demand it handles distributor prospecting, RFQs, margin comparisons, PDF quotes, catalog upkeep, purchase orders, invoices and stock entries in the ERP; it also triages sources daily and schedules four draft posts for the co-founded machining news site Usinagem360, plus a daily rare-metals price update and a weekly LinkedIn carousel recap. Readers can reuse the “scheduled monitoring + briefing generation + conditional summaries + on-demand ops” pattern.
Workflow
- Bot scans inboxes every 30 minutes on workdays, flags replies, bounces and open items, and updates prospecting CRM
- Generates next-day briefing every Sunday–Thursday at 7 pm; includes client dossier when a meeting exists
- Performs overnight follow-ups; sends 6 am summary only when there is news
- On demand: prospecting follow-ups, RFQs, margin comparisons, PDF quotes, catalog maintenance, PO/invoice/stock entries (human confirmation assumed before final submit)
- Daily source triage and scheduling of 4 draft posts; daily price update and weekly carousel recap
Adaptation plan
Results and process description are as reported by the original post author (dual-inbox scans every 30 minutes, Sunday–Thursday 7 pm briefings with client dossiers, overnight China supplier follow-ups with conditional 6 am summaries, on-demand prospecting/RFQ/quote/ERP entries, daily source triage with 4 draft posts for Usinagem360 plus a rare-metals price update and weekly carousel recap). The post says nothing about human confirmation before sending, ERP submission, or publishing; the confirmation requirement in step 4 is our assumption, marked as such, and the freePrompt confirmation boundary is a safety tightening. The post is a reply to a @parkersmith thread prompt, with no attached image or video. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here.
Prompt
AgentFlow draft · Untested.
You are my sales-ops assistant. I am a sales manager at a cutting-tools company.
- Work email and CRM access notes: {{EMAIL_CRM_ACCESS}}
- Tomorrow’s key meeting client: {{TOMORROW_CLIENT}}
- Current task: {{TASK}} (inbox summary / client briefing / supplier follow-up / RFQ quote / content draft)
- Relevant materials (RFQ details, catalog excerpt, news sources, etc.): {{MATERIALS}}
Using the information I provide, do one of:
1. Generate a structured next-day briefing; include client-dossier points if a meeting is scheduled.
2. Summarize supplier or prospect follow-up status (list only items with new progress).
3. Draft RFQ reply or PDF quote points (including margin comparison).
4. Triage provided sources and draft 1–2 industry news posts.
- Clear structured output (lists or briefing paragraphs).
- Separately mark every action that requires my confirmation before sending, ERP submission, or publishing.
- If information is missing, list the gaps and stop; do not invent prices, contacts, or commitments.
If client history, pricing, or authorization is missing, ask explicitly. If data conflicts, flag it and request my decision.
You only prepare and draft. Any email send, ERP entry, quote issuance, or content publish requires my reply “confirm”. Do not autonomously promise price or delivery dates.
This prompt is an AgentFlow reconstruction and has not been live-tested.Running costs and pitfalls
Results and process description are as reported by the original post author (dual-inbox scans every 30 minutes, Sunday–Thursday 7 pm briefings with client dossiers, overnight China supplier follow-ups with conditional 6 am summaries, on-demand prospecting/RFQ/quote/ERP entries, daily source triage with 4 draft posts for Usinagem360 plus a rare-metals price update and weekly carousel recap). The post says nothing about human confirmation before sending, ERP submission, or publishing; the confirmation requirement in step 4 is our assumption, marked as such, and the freePrompt confirmation boundary is a safety tightening. The post is a reply to a @parkersmith thread prompt, with no attached image or video. Workflow steps, freePrompt, 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.