Social: Daily Posts And A Weekly Plan

What this bot is for

The Social bot plans the week and drafts the posts. It does not publish to Facebook or anywhere else on its own. Captions stay in draft until you approve them. Photos come from real shop pictures or from the article you are actually linking — never from an invented image, and never from an old logo you have already retired.

If you have tried to "just post something" at 9:30 PM, you already know why this bot exists. A weekly plan removes the daily blank page. A three-slot day (morning, midday, evening) gives each post a job. Approval keeps a draft from becoming a public mistake.

Build a week plan on Monday

This shop's pattern is already in use: Designer starts the social package Monday morning; Social owns the captions. The Monday plan should look back at last week (what you actually posted, which real photos are still fresh) and look forward at what is safe to link — only published pages and articles, not unpublished drafts.

A useful week grid has, for each day:

  • A morning useful tip (phone care, a simple how-to, or a short AI/help note when that is the topic).
  • A midday local engagement post, with a booking link to the appointment page — never a phone number in the post.
  • An evening post that points at a real, live blog or product-line article on your site.
  • A suggested photo type for each slot, drawn from photos you actually have.

The plan is a draft. If Monday is a holiday or you are slammed at the counter, you can cut a slot. The bot should not scold you for a skipped post, and it should not backfill with a made-up photo.

Three daily slots and what each is for

Morning is for usefulness. Teach one thing a customer can do today. Keep it short. Do not turn it into a sales pitch.

Midday is for the neighborhood: a real local angle and a clear path to book. The call to action is the appointment page. Putting a phone number in a social post looks convenient and turns into typo risk, after-hours texts, and a number that is hard to change later. Use the booking link.

Evening is for your own library. If you published a guide last month, this is how people find it. Link the real URL. Use the article's own image when you have one, or a shop photo that actually matches the subject.

If you do not have a fresh live article, do not invent one. Repeat a strong older guide, or skip the evening slot and say so in the plan.

Caption ownership and approval

Designer can start the package. Social writes the captions. You approve, then you or a designated person post. That chain is on purpose. A caption is where banned words, a wrong price, and a casual "we can do it today" promise sneak in.

When Social drafts a caption it should:

  • Stay inside the copy rules (no vendor names, no part costs, no factory-official or maker-endorsed quality claims).
  • Match the posted price only if you asked it to mention a price, and only the public number.
  • Use the booking link, not a phone number.
  • Stay in draft, clearly marked, until you approve the exact text.

If you change one word, the posted version is your version. The bot should not silently "fix" your edit later.

Photo rules

Photos are real or they do not go out.

  • Use Steve's own shop photos, or the image that already belongs to the article you are linking.
  • Keep a simple rotation so the same photo is not reused too soon. The bot should track what was used last week and suggest the next unused real photo.
  • No old logo art.
  • No invented photos, no stock that pretends to be your bench, and no customer-device photos that you do not have permission to share.
  • No credentials, tickets, or screen-side customer information in the frame.

If the bot cannot find a fitting real photo, it should say "needs a photo" and leave the slot open. That is better than a fake bench shot.

What never goes in a post

  • Phone numbers.
  • Supplier or wholesaler names.
  • Unverified claims, copied from another shop or invented for engagement.
  • Customer names, device passcodes, or ticket details.
  • A price that is not the posted public price.
  • A promise of timing you cannot keep.

The Social bot should treat those as hard stops, not style suggestions.

Sample prompts

Draft this week's social plan for a San Diego phone repair shop: three posts a day, one week. Morning = useful phone or AI tip, midday = local engagement with a booking link to our appointment page, evening = a real published article on our site. Suggest a photo type for each, and leave captions as drafts for me to approve. Do not invent a photo we don't have.

Write three caption drafts for tomorrow's slots using this week's plan. Use the appointment page as the only call to action. Do not include a phone number, a vendor name, or a price I did not give you. Leave them unpublished.

Review last week's posts and tell me which real shop photos were used, which ones are still fresh, and which live articles we have not linked in the last two weeks. Do not draft a post that needs a photo we do not have.

Audit this caption draft for copy-rule breaks and for any promise we cannot keep the same day. Give me a cleaned version and keep both in draft.

How this bot works with the rest of the team

Designer starts the Monday package and helps with images. Localizer can suggest a live article or a neighborhood page that is safe to link. Cortana only needs a line in the brief when a plan is waiting on your approval or when a post was skipped on purpose. Social never asks R&D to invent a pretty fake part photo, and it never posts a price the Designer has not already posted on the site.

Back to blog