A Reusable Prompt Set For Consistent Weekly Marketing Outputs
· 8 min read
Reusable prompt templates for weekly plans, Google Business Profile posts, and lead follow-up scripts, built on official field and sharing rules.
A practical set of templates for weekly plans, GBP posts, and follow-up scripts that stay usable
Owners and lean marketing leads usually lose momentum in the same place, weekly execution. The plan lives in one place, the Google Business Profile post draft lives somewhere else, and lead follow up depends on whoever has time that day. A prompt library fixes that when it forces the same deliverables every week, in the same structure, with the same required fields.
Below is a reusable prompt set you can copy and treat like an operating system for content publishing, Google Business Profile (GBP) posts, and lead follow up. It is built around two practical constraints from official guidance, keep your non negotiables stable in a reusable instruction block, and force acceptance criteria into the request so outputs stay repeatable.
How To Make Outputs Repeatable
OpenAI’s prompt engineering guidance defines a hierarchy for instructions. It states that developer messages are prioritized ahead of user messages, and user messages are prioritized behind developer messages. For a small business marketing ops prompt library, that maps cleanly to what should stay stable versus what changes week to week.
Use A Stable Developer Block For Non Negotiables
Put the rules you never want to renegotiate into a reusable developer block. Examples: the section order, required tables, validation checks, a do not say list, and the exact output schema. This creates consistent structure even when different people on your team run the prompts.
Use A User Block For Weekly Inputs
Keep the changeable inputs in a user block, location(s), service area, the primary offer this week, audience, FAQs, and the required call to action. This separation lets you reuse the same prompts across branches, service lines, and weeks without rewriting the rules every time.
Force Acceptance Criteria Into Every Request
OpenAI Academy’s Writing with ChatGPT recommends targeted guidance and explicit constraints. In practice, that means you stop asking for vague improvements and start specifying requirements like word count, brand voice, do’s and don’ts, and the final call to action. This is the simplest way to prevent a “good sounding” draft that cannot be published as is.
The Prompt Pack: Copy, Paste, Run
These templates are designed for marketing ops, content planning, GBP publishing, and lead follow up. Each is written as a stable developer block plus a variable user block, so you can create consistent outputs across clients and weeks.
Prompt 1: Weekly Marketing Ops Plan (Content + Local + Lead Follow Up)
Use this when you want one weekly run to produce your plan, your content calendar, your GBP drafts, and your follow up sequences in one place.
DEVELOPER
You are an SMB marketing operations assistant. Produce outputs in the exact sections and tables requested. Ask clarifying questions only if required inputs are missing; otherwise proceed. Follow all constraints given (word counts, do-not-say list, compliance notes). Output must be deterministic in structure.
USER
Business:
- Name:
- Website:
- Location(s):
- Service area (if any):
- Primary offer this week:
- Audience:
- Top 3 FAQs:
- Brand voice (3 adjectives):
Constraints:
- Must avoid: [list]
- Required CTA: [call / book / quote / directions / website]
- Review constraint: Do not include phone numbers in GBP post descriptions unless confirmed as verifiable for the Business Profile (Google notes posts with a phone number “might get rejected” if not verifiable).
Deliverables (output exactly in this order):
1) Weekly Objectives (3 bullets)
2) Content Calendar (Mon-Sun) table with columns: Channel | Theme | Asset | CTA | Owner | Status
3) GBP Posts (3 drafts) each labeled with post type (“Update”, “Offer”, or “Event”) and required fields for that type
4) Lead Follow-up Workflows
- New lead: 3-message SMS sequence
- No-show: 2-message SMS sequence
- Missed call: voicemail + SMS
5) Tracking Checklist (UTM plan + what to measure)
6) “Assumptions” list (anything you had to infer)
Prompt 2: GBP Post Draft Generator (Strict Fields And Scheduling Controls)
This is the one that prevents unusable GBP drafts. Google Business Profile Help documents three post types you can create and customize: Offers, Events, and Update. It also states required fields for Offers and Events, and it documents the scheduling controls and the Repeats dropdown.
DEVELOPER
Generate Google Business Profile post drafts. You must output the fields required by the selected post type exactly, and never omit required fields. If the user selects Offer, include “title, dates, and time” (Google states Offer “requires a title, dates, and time” and “automatically includes a "View Offer" button”). If the user selects Event, include “title, start and end dates, and times” and note that if start/end time are not provided it “shows as lasting 24 hours” (Google statement). For Update, output text + media suggestion + button suggestion. Also output suggested scheduling fields matching Google UI labels “Schedule this post” and “Repeats”.
USER
GBP inputs:
- Post type: [Update | Offer | Event]
- Goal: [awareness | calls | bookings | foot traffic | promo]
- Promo/offer details (if any):
- Event details (if any):
- URL to use (if any):
- Allowed to include phone number in description? [yes/no + confirm verifiable to GBP]
Publishing:
- Schedule this post: [date + time or “none”]
- Repeats: [weekly | monthly | custom schedule | none]
Output format:
A) Draft Post (fields)
B) Media guidance (1 image concept + 1 short video concept)
C) Compliance/QA notes (including phone number rejection risk note if phone number requested)
Non Obvious GBP Pitfall: Phone Numbers In The Description
Google’s GBP post guidance includes a rejection note that matters operationally: posts that include a phone number in the post description might get rejected if they cannot be verified as being connected to the business on which they are posted. If your prompt library inserts phone numbers by default, you can accidentally create review friction and slow down weekly publishing. Add the guardrail once, then stop thinking about it every time.
Prompt 3: GBP Posting SOP Helper (Status Based Troubleshooting)
After publishing, Google states it reviews your post to make sure it meets its posts content policy. It also defines three statuses that show up in operations: Live, Pending, and Not approved. A simple status driven SOP prompt keeps weekly posting from turning into guesswork.
DEVELOPER
Generate a posting checklist and troubleshooting steps using Google’s post status definitions. Use the statuses exactly: “Live”, “Pending”, “Not approved”. For “Pending”, include Google’s stated possible reasons: “upload stage”, “processing stage”, or “profile is unverified”. For “Not approved”, state Google’s note that the question mark indicates which content policy was violated.
USER
- Post URL (if available):
- Current status: [Live | Pending | Not approved]
- Notes from operator:
Output:
1) Pre-publish checklist
2) What this status means (verbatim labels)
3) Next actions (step-by-step)
4) What to document internally
Prompt 4: Lead Follow Up Script Pack (SMS + Email + Call)
This prompt follows OpenAI Academy’s guidance to use targeted instructions and constraints. It is designed to output short scripts with placeholders and variants, so your team can respond to leads consistently without rewriting from scratch.
DEVELOPER
Write short, reusable follow-up scripts. Use targeted instructions and constraints (OpenAI Academy recommends targeted guidance and constraints like word count, brand voice, do’s/don’ts). Output must include variants and placeholders.
USER
Business context:
- Industry:
- Offer:
- Brand voice:
- Primary CTA:
Constraints:
- SMS max length: [X characters]
- Do-not-say list:
Lead scenario:
- Source: [GBP / website / ads / walk-in]
- Lead intent:
Output:
A) SMS (3 touches over 5 days)
B) Email (subject lines x5 + 1 full email)
C) Call script (opening + qualification questions + close)
D) Voicemail (20-30 seconds)
E) CRM notes template
Prompt 5: Client Ready Prompt Pack Deliverable With A Sharing Rule
If you plan to send prompts and drafts to a client using shared links, OpenAI’s Help Center explains two constraints that matter operationally: shared links do not offer recipient by recipient access controls, and shared links do not have configurable expiration dates. Your handoff prompt should include those points so the team treats the link as forwardable and persistent unless deleted.
DEVELOPER
Package outputs as a client-ready deliverable. Include a section that warns about sharing links: shared links “do not offer recipient-by-recipient access controls” and “do not have configurable expiration dates” (OpenAI Help Center).
USER
- Include: [weekly plan / GBP drafts / follow-up scripts]
- Client name:
- Internal-only notes to exclude:
Output:
1) Executive summary
2) Assets
3) Publishing instructions
4) Sharing & access note (include the two quoted constraints above)
5) Next-week inputs needed
Where This Fits In An SMB Growth System
A prompt library only pays off when it connects channels. Prompt 1 intentionally outputs a Content Calendar, GBP Posts, and Lead Follow-up Workflows together so the weekly theme, the local post, and the response scripts all match the same offer and the same call to action. That alignment is what reduces dropped leads and “we posted, but nothing happened” weeks.
If you want these prompts to run as a managed system inside your business, IN-STORE typically treats them as part of AI-assisted content marketing and lead generation systems, with human guided automation and QA wrapped around publishing and follow up so outputs stay consistent over time.
If you implement only one thing from this set, start with the GBP Post Draft Generator and the status based SOP. The official requirements for Offer fields, Event fields, scheduling controls, and post statuses are specific, and a prompt that forces those fields prevents rework.
If you want a monthly marketing partner to operationalize this as an end to end workflow, explore IN-STORE’s services here: marketing, content, and lead generation services.
Ready to operationalize these prompts and automate weekly marketing ops? Contact IN-STORE to learn how we implement the system: Explore IN-STORE services
Sources: