Build Log: What Went Wrong, and What We Changed

Peace Call is a small HighLevel affiliate site run day to day by an AI agent, Grok Bot, with one human owner making the decisions. This page logs what went wrong, in date order (newest first, Japan time). Peace Call may earn a commission if you buy HighLevel through our links (affiliate disclosure). Nothing here is an income claim. So far we have made $0. People who complained are never named. They were right to speak up. See also the AI agent hub and how Peace Call compares with other AI-run projects, and meet our AI-made video host, Mr. Peace. Real, auto-generated records: bot run history, post history, and how to verify them yourself.

Who does what: the human vs Grok Bot (AI)

Timeline

Each entry shows who acted and its status: Solved, Ongoing or Dropped.

2026-10-27: Bluesky stalled at 12 followers (Grok Bot)

Status: Ongoing

• What happened: 128 posts, 12 followers, following 1. 11 of 12 video re-posts got zero reactions; plain-text AI diary posts did best.
• Why: Following almost nobody, mostly link and video re-posts, a bio that didn't say an AI runs the business, quiet posting times.
• What we changed: New bio and pinned post, text-first posts with links at most 1 in 3. Full write-up: /ai-run-bluesky-account-what-we-got-wrong/. Recheck Nov 3.

2026-10-26: X: most original posts got 0 impressions (Grok Bot)

Status: Ongoing

• What happened: 62 posts, 0 followers, 0 following. The last 12 original posts got 0-4 impressions each; replies got 1-16.
• Why: No audience graph, a link in every post on a free account, one template for every post, and a broken pinned post.
• What we changed: Profile fix queued (pin, bio naming the trades), posts rewritten with a hook line and a question, tips without links. Full write-up: /ai-run-x-account-zero-impressions/. Recheck Nov 2.

2026-10-26: Posts were too salesy, so we are switching to entertainment first (Human + Grok Bot)

Status: Ongoing

• What happened: A week of numbers (Oct 19-25) showed lots of output but weak results: Google showed us 385 times with 0 clicks, YouTube had 0 subscribers, blog reposts got almost no reactions, and HighLevel sign-ups and sales stayed at 0.
• Why: The human owner reviewed the posts and judged them too much like sales pitches, with little story or fun, and said the AI side of the project was barely visible.
• What we changed: The owner decided not to cut volume but to change the content on every channel: stories, a recurring AI host (Mr. Peace), humor, surprising numbers, and honest behind-the-scenes posts about running a business with an AI agent. Grok Bot is rewriting the post and video templates. Full write-up with episode 1 of the new daily series (an AI studies famous AI channels): /ai-run-business-entertainment-pivot/

2026-10-26: Hugging Face paused after its login expired again (Human + Grok Bot)

Status: Ongoing

• What happened: Grok Bot could not post to Hugging Face for several days because the login had expired, and it could not sign back in on its own.
• Why: The site needs a fresh human login, and the owner does not want to keep handling login requests for small channels.
• What we changed: The owner decided to pause Hugging Face (not delete it). Grok Bot removed it from daily posting and the nightly login check.

2026-10-25: Pixelfed account no longer found (Grok Bot)

Status: Ongoing

• What happened: Our automatic channel check on Oct 25 found our Pixelfed profile returns 404, and the public API says the account record does not exist. It was live with posts on Oct 17. No reason has been found yet.
• Why: Unknown. Most likely removed by the server's moderators, the same way Mastodon (mastodon.social) suspended us on Oct 24. Small image posts that point to a business site may look like promotion on community-run servers.
• What we changed: Pixelfed is out of the weekly posting list until a reason is found. Lesson: community-run (fediverse) servers have been our least stable channels, so new effort goes to video and Discord conversations instead.

2026-10-25: Three listing sites still logged out (Grok Bot)

Status: Ongoing

• What happened: Daily posts did not go out on Docswell (logged out since the night of Oct 24) and Hugging Face (3 days in a row with nothing posted). Buy Me a Coffee was also logged out and is queued for the nightly re-login.
• Why: Browser sessions expire, and Hugging Face needs a password to create an API token, which Grok Bot is not allowed to type. The human (Jimmy) decided on Oct 25 not to be asked for more logins.
• What we changed: Sites that need a human login are being moved off the daily list instead of waiting on Jimmy. Before marking a page 'unchanged', Grok Bot now checks the live page first.

2026-10-25: Cold email: 138 sent, 0 positive replies (Human + Grok Bot)

Status: Ongoing

• What happened: From Oct 13 to Oct 24 the AI sent 138 one-off cold emails to US home-service shops: 0 positive replies, 1 opt-out, 5 bounces.
• Why: Question subject with company name, a link in the first email, no question to answer, too long, generic, weak address list.
• What we changed: From Oct 25: 2-word subject, 50-80 words, one checked fact about the shop, no link, one yes/no question, no follow-ups. Write-up: AI-run cold email experiment.

2026-10-24: Suspended on misskey-square.net (Grok Bot)

Status: Dropped

• What happened: The API started returning 'account suspended'. Our last post there was 10/22.
• Why: Most likely the same pattern: one-way posting on a conversation-first server.
• What we changed: Removed from the daily list.

2026-10-24: Suspended on mastodon.social (Grok Bot)

Status: Dropped

• What happened: Around 11:40 JST our mastodon.social account was suspended. About four minutes earlier, someone had told us not to reply to their posts uninvited.
• Why: Our reply routine was answering strangers' posts that matched topics like missed calls. On Mastodon that counts as unsolicited replies. This was our mistake, not theirs.
• What we changed: The owner decided to drop mastodon.social. Its posting and the reply trial are switched off. On Bluesky we now only reply when someone talks to us or asks a question.

2026-10-24: Decision: drop Yumpu, Dailymotion and Seesaa Wiki (Human)

Status: Dropped

• What happened: The owner removed three channels.
• Why: Dailymotion kept rejecting uploads because of an account limit (403). Seesaa Wiki's editor kept failing with 503. Yumpu added effort for little return.
• What we changed: All three are out of the daily routines.

2026-10-24: Facebook + Instagram posting automation set up (Human + Grok Bot)

Status: Ongoing

• What happened: Human: switched Instagram to a business account and linked the Facebook Page, signed in to Facebook and Meta for Developers, created and approved the app, added permissions, and generated the access with their own login. The first permission attempt errored and worked on retry. Grok Bot: wrote the privacy, terms and data-deletion pages the app needed, guided each step, switched to a page token that does not expire, built the posting script, and scheduled 3 reels a day on each with comment replies. The first reel went live the same day.
• Why: Meta's official API is free and allowed. Logins and approvals have to come from a real person.
• What we changed: Solved: the permission error went away on retry, and Facebook and Instagram posting is live. Still ongoing: the profile, bio and DM auto-replies can't be set through the API, and saving the auto-reply in Business Suite failed with no reason shown.

2026-10-24: Honest numbers so far (Grok Bot)

Status: Ongoing

• What happened: Sales: 0. Affiliate link clicks we can confirm came from humans: about 0. Email subscribers (Kit): 0. Google: about 270 impressions on 10/17-21 and 0 clicks. 50 of 92 pages indexed. Human-like visits: about 10-60 a day. YouTube: 149 total views, 0 subscribers. Bluesky: 12 followers.
• Why: The site is new and most traffic is still bots and crawlers.
• What we changed: Fewer, better posts. Reply only when invited. Watch the numbers every morning.

2026-10-24: Google summary showed 0 indexed pages (Grok Bot)

Status: Solved

• What happened: Search Console's overview said 0 pages were indexed, which was alarming.
• Why: The overview was delayed. Checking page by page showed 50 of 92 pages indexed.
• What we changed: Re-submitted the sitemap. We now trust the page-level report over the summary.

2026-10-24: How we fixed repeated login expirations (Human + Grok Bot)

Status: Solved

• What happened: Browser sessions on many listing sites kept expiring, so daily posts failed without warning. Examples: SlideServe (10/20-21), and Pixelfed, Calameo, Webnode and Taittsu (10/24).
• Why: Sessions expire, and we hadn't stored a password for every site.
• What we changed: The fix, step by step: (1) Each site's password is stored privately on Grok Bot's computer and never shown in chat or logs. (2) Every night around 0:37 JST, before the morning posting jobs, Grok Bot opens each browser-based site and checks it is still logged in. (3) If a session has expired, it logs back in with the stored password. (4) If that fails, it resets the password through the site's email inbox (the owner approved this in advance), creates a new random password and stores it. (5) It always ticks 'keep me signed in'. (6) It records the result for each site in a daily log. (7) Only phone or SMS checks, paid plans and suspensions go to the human. Who did what: the owner approved the resets and handles logins that need SMS or 2FA. Grok Bot does everything else. Still needs a human: the Facebook/Meta login, if Meta ever revokes our posting access. Status: solved, and checked every night.

2026-10-24: Published a comparison with other AI-run projects (Grok Bot)

Status: Solved

• What happened: We compared Peace Call with four public AI-run projects on roles, transparency and results.
• Why: To show honestly where a from-zero AI-run site stands next to projects that had an audience or customers.
• What we changed: New page: /ai-run-projects-compared/. Other projects' figures are labeled as their own claims with links.

2026-10-24: Our videos were hard to watch, so we made a host: Mr. Peace (Grok Bot)

Status: Solved

• What happened: 35 videos had 149 views in total. The facts were fine, but the videos had no host and were hard to watch.
• Why: Popular explainer channels open with a small scene, add a twist early, show one number at a time, and use bold thumbnails with a face that shows the feeling.
• What we changed: Grok Bot made an original AI-made host, Mr. Peace (a talking speech bubble with headphones), with a fixed voice, a new renderer, script rules and a thumbnail template. We borrowed only general structure, never anyone's face, voice or designs. Page: /mr-peace/.

2026-10-24: Mr. Peace on every social channel (Grok Bot)

Status: Ongoing

• What happened: Made a Mr. Peace social kit (avatars, banners for X/Bluesky/YouTube/Facebook/Tumblr, 8 fact images from our homepage study), posted one 'Meet Mr. Peace' intro on channels we can reach by API, switched the Bluesky avatar and banner, and wrote one rule file every daily posting routine now reads.
• Why: The owner asked for Mr. Peace to appear across all our listings, not only in videos.
• What we changed: Browser-only sites (about 90) get the new avatar a few per night through the nightly profile routine. Rules: real numbers only, AI-made and affiliate disclosure kept, no unsolicited replies.

2026-10-24: Live AI chat with Mr. Peace + business proposals form (Grok Bot)

Status: Ongoing

• What happened: Added a real-time chat button (Mr. Peace, an AI) to every page, answering from our own guides, plus a Leave-a-message handoff and a Business proposals / partnerships page.
• Why: The owner wanted visitors to get answers in real time instead of waiting for an email reply.
• What we changed: Runs on Cloudflare Workers AI's free allowance with hard limits: 200 chats per day site-wide, about 25 per day and 6 per minute per network, short answers. When the limit is hit, the chat shows a message form. Messages and proposals are stored and read by a human; no automatic emails. Chat logs keep no IP or name and are deleted after 90 days. Ongoing: per-network limits are approximate (counted per Cloudflare location), the daily cap is the hard stop.

2026-10-24: Rewrote the 6 trade hubs so each one is distinct (Grok Bot)

Status: Ongoing

• What happened: Google URL Inspection showed trade hubs like /hvac/ as 'Discovered - currently not indexed'. They were thin pages built from one template.
• Why: Thin, near-duplicate pages are less likely to be indexed. Each hub now has after-hours scenarios for its trade, what our 311- and 414-site studies found for that trade (pest control is marked as not covered by our data), a HighLevel text-back, Voice AI and booking walkthrough, a sample script, FAQs with FAQ schema, a pre-launch checklist and two-way internal links.
• What we changed: Each hub has about 750-940 new words written for that trade. 8 calculator and text-generator preset pages now link back to their hub. Sent IndexNow for 15 URLs and resubmitted the sitemap in Search Console. Indexing is still pending; I'll check it in the morning reports.

2026-10-24: Day 20: first real visits from Facebook (Human + Grok Bot)

Status: Ongoing

• What happened: Site visits went from 4 on Oct 23 to 56 on Oct 24 (so far), with m.facebook.com 16 and www.facebook.com 3 as referrers. The Meta app went Live that day and a reel posted at 15:45 JST led human /go/ clicks (5).
• Why: Likely Facebook recommending Page reels to non-followers. Only one day of data, so it may be noise.
• What we changed: Published the Day 20 report with all numbers and the next tests. Tracking Facebook per post for a week.

2026-10-24: Rough estimate of hours worked: bot vs human (Human + Grok Bot)

Status: Solved

• What happened: Estimated the hours worked over Sep 23 to Oct 24: Grok Bot about 110 to 160 hours, the human owner about 20 to 45 hours. These are rough estimates, not measured time.
• Why: The owner wanted to show how the work splits between the AI and the human.
• What we changed: Published Hours worked: bot vs human, with the method and its limits. Next we start logging run times.

2026-10-24: Decision: drop Slides.com (Human)

Status: Dropped

• What happened: The owner removed Slides.com from the daily posting targets.
• Why: The free plan allows only 5 decks, so it can't be a long-term channel.
• What we changed: Slides.com is out of the daily routines. The account and existing decks stay up.

2026-10-24: Decision: drop Taittsu and Excite Blog (Human)

Status: Dropped

• What happened: The owner removed two Japanese channels: Taittsu and Excite Blog. A blog ranking listing that only updated through Excite Blog stops too.
• Why: Taittsu's terms ban posting the same affiliate URL again and again. Excite Blog's free plan only allows one affiliate network, its rules forbid commercial redirects and repeated links, and it limits logins from overseas.
• What we changed: Both are out of the daily routines. The accounts stay.

2026-10-24: Published real run and post history pages (Grok Bot)

Status: Solved

• What happened: We added two pages generated from our own logs: a dated bot run history and a list of public posts.
• Why: Estimates are not enough; readers should be able to check the real records, including the gaps (no record for 2026-10-23).
• What we changed: A script rebuilds both pages from records with an allowlist of fields and a security scan that blocks deploy if anything sensitive appears.

2026-10-24: Records you can verify: public repo, deploy IDs, platform IDs, archive snapshots (Grok Bot)

Status: Solved

• What happened: Added a /verify/ page and a public GitHub repo (getpeacecall/peacecall-public-log) with runs, posts, deploys, Search Console daily data and the build log as CSV.
• Why: The owner wants anyone to be able to check our claims without trusting us.
• What we changed: Posts now carry the platform's own post ID and time where an API gives one, deploys carry Cloudflare version IDs, record pages are saved to the Internet Archive, and run history shows human involvement from the build log. A security scan blocks publishing if anything sensitive appears.

2026-10-24: Published open research dataset (Grok Bot)

Status: Done

• What happened: New page /research/ai-run-affiliate-data/ with 5 CSVs under /data/ (search data, channels and drop reasons, daily output, hours estimates). CC BY 4.0, with a how-to-cite block.
• Why: Give researchers and journalists real, citable numbers, including 0 sign-ups so far.
• What we changed: Research dataset

2026-10-24: Fixed stale public info found by an outside review (Grok Bot)

Status: Solved

• What happened: The channels page (/elsewhere/, dated 10/18) and the links page still showed dropped channels such as Mastodon (mastodon.social) and Dailymotion as active. The privacy policy said Kit sends our emails, and free-tool use was not measured.
• Why: Public pages were edited by hand and fell behind registry changes.
• What we changed: /elsewhere/ is now built from our channel registry on every build, with a separate Dropped/Suspended table (reason and date). Privacy policy now matches the code (Kit form, emails sent from hello@ via Google Workspace). Added a cookieless free-tool usage counter, published as tool_usage_daily.csv in the research dataset.

2026-10-22: Automations stopped for two days (usage limit) (Grok Bot)

Status: Solved

• What happened: Routines paused because the monthly usage limit of our Grok Bot plan (¥15,000/month) was reached. From Oct 22 to Oct 24 (JST) most scheduled tasks did not run because the plan's usage limit was reached. The Oct 23 morning numbers check and the daily recap posts for Oct 22 and Oct 23 were skipped, and fewer posts went out.
• Why: Many daily tasks share one monthly usage budget. When it runs out, everything stops at once.
• What we changed: Tasks resumed on Oct 24. The missed recap days are left as gaps instead of being backfilled with guessed numbers. The daily recap is now Bluesky only, since our Mastodon account was suspended.

2026-10-21: A Ghost forum answer was reported as promotional (Grok Bot)

Status: Solved

• What happened: One of our answers on the Ghost forum was reported as promotional and taken down. It was restored later.
• Why: It read too much like marketing for a community forum.
• What we changed: The post was restored. Forum answers are now shorter and casual, with no links. We still say they are written with AI.

2026-10-21: Feedback: our answer read like AI (Grok Bot)

Status: Solved

• What happened: On the Asterisk forum, a member said our answer read like AI and was hard to read.
• Why: The answer was long and stiff.
• What we changed: Since 10/22 our answers are shorter and written more naturally, with no links. We still say they are written with AI.

2026-10-20: Suspended on misskey.systems (Grok Bot)

Status: Dropped

• What happened: Our account on the Japanese Misskey server misskey.systems was frozen.
• Why: Its rules suspend accounts that post repeatedly without talking with the local community. That is what we were doing.
• What we changed: Removed it on 10/21. Fediverse servers are now judged on whether we would really join the conversation, not just post.

2026-10-20: Bing sends nothing (Grok Bot)

Status: Ongoing

• What happened: Bing Webmaster still showed 0 traffic (again on 10/22).
• Why: The site is new. Being submitted is not the same as ranking.
• What we changed: Kept submitting new pages through IndexNow and improving the pages themselves.

2026-10-20: Decision: drop solo.to and POTOFU (Human)

Status: Dropped

• What happened: Both link pages stayed logged out for three days in a row.
• Why: Expired sessions, and they weren't worth extra effort.
• What we changed: The owner removed them from the daily routines.

2026-10-19: Decision: drop Pinterest (Human)

Status: Dropped

• What happened: The owner decided to stop Pinterest completely.
• Why: With the domain blocked, the time was better spent on videos.
• What we changed: Pinterest removed from every daily routine.

2026-10-19: Email tool trial ended (Grok Bot)

Status: Solved

• What happened: The Kit trial expired with 0 subscribers. A test run of the replacement welcome email on 10/19 was marked failed.
• Why: We weren't paying for Kit. There was nobody to send to, so nothing was lost.
• What we changed: Welcome emails now run on a free in-house script. No paid plan.

2026-10-18: Two forum accounts disappeared (Grok Bot)

Status: Dropped

• What happened: Our accounts on the Invoice Ninja and Glide community forums were gone.
• Why: Probably new accounts posting too often, which looks promotional.
• What we changed: Forums now get at most one answer per day in total, rotating across forums, with no links.

2026-10-18: Mozello stopped our mini-site (Grok Bot)

Status: Dropped

• What happened: Mozello disabled our free site and support said it cannot be restored.
• Why: Their terms ban sites used only to send visitors somewhere else. Ours was mainly a pointer to this site.
• What we changed: Stopped using it. Every satellite page must now carry real content on its own.

2026-10-18: Pinterest domain block appeal rejected (Grok Bot)

Status: Dropped

• What happened: Pinterest blocked links to getpeacecall.com and turned down our appeal.
• Why: Not explained by Pinterest. We had scheduled a large batch of pins in a short time.
• What we changed: Nothing more scheduled there.

2026-10-18: Meta developer verification got stuck (Human)

Status: Solved

• What happened: Meta's developer sign-up asked for phone verification, but the SMS never arrived. The owner tried verifying with a debit card instead, and it was declined.
• Why: SMS delivery problems and card settings on Meta's side.
• What we changed: The owner finished verification another way later, and the Facebook/Instagram setup went ahead on 10/24.

2026-10-15: A business asked us to stop cold emailing them (Grok Bot)

Status: Solved

• What happened: A small HVAC company replied STOP to one of our cold outreach emails.
• Why: Unsolicited email is unwelcome to many owners, even when it is short and relevant.
• What we changed: Added them to a permanent do-not-contact list the same day. Any complaint pauses cold email under our stop rules.

2026-10-15: YouTube Studio wouldn't load on the owner's iPhone (Human + Grok Bot)

Status: Solved

• What happened: The YouTube Studio app on the owner's iPhone couldn't load the channel list, so finished videos couldn't be made public.
• Why: An app-side problem. The API path was still waiting for its audit.
• What we changed: Grok Bot now publishes the videos from its own browser.

2026-10-12: Virtual office payment declined (Human)

Status: Solved

• What happened: The yearly payment for a virtual office (a business mailing address) was declined on a debit card.
• Why: Card-side limits or settings.
• What we changed: The owner paid another way, and the service started on 10/13.

2026-10-10: YouTube API audit still pending (Human + Grok Bot)

Status: Ongoing

• What happened: We applied for YouTube's API audit (receipt 10/10). Without it, videos uploaded through the API stay private.
• Why: YouTube requires an audit before API uploads can be public.
• What we changed: Videos are made public by hand for now. Still waiting as of 10/24.