🎯 What you'll have at the endYou'll have a bot that reads customer comments every week and turns them into a clear, numbered to-do list for you to approve, plus a Monday bot that drafts and queues your posts.

⚡ One-click install

Checked install pages (app stores, official sites and template pages): tap to get it straight away.

⬇️ Get Grok Bot on iPhoneApp Store ⬇️ Get Grok Bot on AndroidGoogle Play ⬇️ Download for desktopOfficial download page

🧰 Before you start

A plan that includes Grok Bot (The X Subscription Premium from USD 30/month or higher; older SuperGrok and paid Cursor plans still work) and the Grok Bot app on your phone or computer
Somewhere your customers comment: reviews, a shop page, an app store page or an email inbox
A to-do list the bot can write to: GitHub issues (if you have code), Trello or a Google Sheet
Optional: a free Buffer account connected to your social pages

⏱️ Time neededAbout an hour per bot, then a few minutes a week to approve

💵 Rough costIncluded in your Grok Bot plan (Bot usage is counted separately); Buffer and Google Sheets have free plans

🪜 Step by step

🐣 Beginner mode: showing the 7 essential steps only. Extra steps are hidden; tap 🚀 Advanced at the top to see all 8.

✅ 0 of 8 steps done 📄 Printable page

1
☐
Pick where comments arrive
List the places customers leave feedback (review page, shop listing, email). Then decide where the tidy to-do list will live: GitHub issues, Trello or a Google Sheet.
Mark as done
2
☐
Create a Feedback bot
In Grok Bot, create a new Bot and name it after its job, for example 'Feedback'. One bot per job keeps things clear.
Mark as done
3
☐
Connect only what it needs
Open the Bot's connectors and add the comment source (or Gmail) and your to-do list. Don't give it access to anything else.
Mark as done
4
☐
Paste the feedback prompt
Copy the 'Comments to tasks' prompt below, fill in the [brackets] and send it. Ask it to make this a routine (a job that repeats on a schedule), for example every Saturday at 10am.
Mark as done
5
☐
Keep the decisions yourself
Anything that changes your product, prices or promises to customers waits for you. Arda says 'taste stays with me': the bots draft and measure, he decides.
Mark as done
6
☐
Check before anything gets fixed
Whoever fixes the task (you, a helper or a coding AI such as Claude Code) should check it against reality first. One of Arda's 'bugs' turned out never to have been built at all.
Mark as done
7
☐
Add a Monday posts bot
Create a second Bot, connect Buffer, and paste the 'Monday roundup' prompt. It drafts posts from the week's news and queues them for your OK.
Mark as done
8
☐
Optional: audit your bots every month
Bots pile up. Use the 'Bot audit' prompt to find overlaps, idle bots and routines that all fire at the same time on Monday morning.
➕ Extra step: hidden in 🐣 Beginner mode Mark as done

💬 Copy-paste prompts

Tap Copy prompt, paste it into your AI (Grok, ChatGPT, Claude or Gemini), then replace the [yellow bits] with your own details.

💬 Comments to tasks

You are my Feedback bot for [business name], which sells [product or service].
Every [Saturday at 10am], read new customer comments from [review page / shop listing / Gmail label 'feedback'].
Split every comment into one task per problem. For each task write: a clear title, what the customer said (quote them), any details they gave (device, order number, date, version), whether it is a bug, a feature request or a question for me, and how sure you are.
Add each task to [GitHub issues on repo X / my Trello board / the 'Feedback' Google Sheet] with the label [customer-feedback]. Don't create duplicates of tasks that already exist; add a note to the existing one instead.
Never reply to customers, never promise anything, and send me a short summary when you're done.

💬 Monday roundup

Every Monday at [9am], gather last week's news for [business name]: [sales or downloads from X], new reviews, finished tasks from [to-do list], and anything coming up in my Google Calendar.
Work out the 1-3 things worth telling customers. Draft one post per network [X, LinkedIn, Instagram] in my voice: [describe your tone, e.g. friendly, plain, no hype]. Add a link to [page] with tracking tags so I can see which post worked.
Queue the drafts in Buffer as drafts only. Message me a list to approve. Never publish without my yes, and never state figures you can't see in the data.

💬 Bot audit

Look at all my bots, their instructions, connectors and routines. Draw me a simple map: which bot does what, which bots message each other, and when each routine runs.
Then list: bots that do the same job, bots that haven't been used in 2 weeks, routines that all run at the same time, connectors that need signing in again, and anything you couldn't check. Suggest what to merge, move or delete, but don't change anything until I approve.

⚠️ Tips & common mistakes

Use a to-do list, not chat, as the hand-over between bots and people. Arda says a ticket 'can be read, closed, argued with and linked', while a chat message disappears.
Read every post before it goes out: in Arda's own blind test, Grok scored lowest on social media copy.
Never let a bot answer a customer's big question for you. In Arda's case, whether a full version would come out was 'still mine to answer'.
Start with one bot and one routine. Arda warns that 'bots accrete': 14 bots added at different times made a Monday morning he never designed.

🌟 Why it's worth it

💡 Why it mattersCustomer feedback usually sits unread. Here a comment became merged fixes in about 19 hours, and his part was 'reading a few measurements and saying yes or no', he writes. Fewer missed complaints means fewer lost customers.

🏷️ Real exampleArda Karaduman, Gand (one-person studio): a player's comment on the itch.io page became eight GitHub issues on a Saturday morning; two fixes were merged by Sunday. A Monday 'Social' bot asks his 'Games Research' bot for Steam numbers, drafts posts, gets the website updated and queues the posts in Buffer.

🔌 Connects to:GitHubGmailGoogle CalendarGoogle DriveBuffer

🙋 Proof level: Personal postOne person's own account on X, Reddit, YouTube or a blog. Nobody has checked it: treat any numbers as their results, not a promise.

📰 Found via Blog · blog.arda.tr: Coze blog (Arda Karaduman): How I use Grok Bot to automate my business ↗