📱 Social Media

Hootsuite Approval Workflow Sheet from Queue Inventory (No Invented Engagement Rates)

Turn a Hootsuite queue inventory into an approval workflow sheet only. No invented engagement rates, follower counts, or response times beyond the inventory.

0.0
0Reviews
P
September 15, 2026

Prompt

Act as a Hootsuite social ops lead who only uses a pasted queue inventory. You write an approval workflow sheet the inventory already supports. You do not invent engagement rates, follower counts, response times, or API tokens not in Inputs. This is not a Hootsuite billing estimate and not an influencer contract.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Queue inventory I lock (post stubs, approver cues, status notes): [Inventory]
- Hootsuite / org version notes I lock: [Version]
- Org or brand label I may quote (or UNKNOWN): [Workspace]
- Required workflow or queue names I may quote (or UNKNOWN): [SpecNames]
- Post titles already present (or UNKNOWN): [PostCues]
- Approver and stage cues already present (or UNKNOWN): [ApproverCues]
- Status and channel notes already present (or UNKNOWN): [StatusNotes]
- Words I must not use: [Banned]
- What I must never invent (engagement rates, follower counts, response times, API tokens): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PostCues, ApproverCues, StatusNotes, Lang. Forbidden: invented engagement rates, follower counts, response times, API tokens. Banner: not a Hootsuite billing estimate; not an influencer contract.
2. Approval workflow sheet: one numbered row per Inventory post stub or approver cue. Missing StatusNotes write NOT IN INPUTS. Use Hootsuite Composer, Approvals, Streams, Planner, and Teams language when Inventory supports it. Never print engagement-rate or follower-count VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed posts stay NOT IN INPUTS. Never invent response-time VALUES not in Inventory.
4. Version lock: print Version. Refuse Hootsuite features newer than Version if Version is named.
5. Refuse list: inventing engagement rates, inventing follower counts, inventing response times, inventing API tokens.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Sheet from Inventory only. No invented engagement-rate VALUES. Teach Hootsuite approval workflows, not a Buffer or Sprout Social swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Hootsuite Approval Workflow Sheet from Queue Inventory (No Invented Engagement Rates) - Result

Examples

Example Input

Inventory: post Harbor Quay Launch teaser as pasted approver cue Brand Lead as pasted status notes Pending legal as pasted; post River Ops FAQ reel as pasted approver cue Social Manager as pasted. Engage invent NONE. Follower invent NONE.
Version: Hootsuite 2025 as pasted (do not invent unreleased AI approval writer)
Workspace: Harbor Quay Brand org as pasted
SpecNames: Launch approval workflow as pasted; FAQ approval workflow as pasted. Token UNKNOWN.
PostCues: Launch teaser as pasted; FAQ reel as pasted. Live AMA UNKNOWN.
ApproverCues: Brand Lead as pasted; Social Manager as pasted. Legal counsel UNKNOWN.
StatusNotes: Pending legal as pasted. Engagement rate VALUES NOT IN INPUTS.
Banned: guaranteed engagement, engage invent, follower invent, token invent
Never: invent engagement rates, invent follower counts, invent response times, invent API tokens
Format: ledger + sheet + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: post Harbor Quay Launch teaser approver cue Brand Lead status notes Pending legal; post River Ops FAQ reel approver cue Social Manager. Engage invent NONE. Follower invent NONE. Version Hootsuite 2025. Workspace Harbor Quay Brand org. SpecNames Launch approval workflow; FAQ approval workflow; Token UNKNOWN. PostCues Launch teaser; FAQ reel; Live AMA UNKNOWN. ApproverCues Brand Lead; Social Manager; Legal counsel UNKNOWN. StatusNotes Pending legal; Engagement rate VALUES NOT IN INPUTS. Lang English. Banner: not a Hootsuite billing estimate; not an influencer contract. Forbidden: invented engagement rates, follower counts, response times, API tokens, guaranteed engagement, engage invent, follower invent, token invent.

2. Approval workflow sheet.
1. Harbor Quay Launch teaser | PostCues Launch teaser as pasted | ApproverCues Brand Lead as pasted | StatusNotes Pending legal as pasted | engage VALUES NONE | follower VALUES NONE | Hootsuite approval workflow sheet only.
2. River Ops FAQ reel | PostCues FAQ reel as pasted | ApproverCues Social Manager as pasted | StatusNotes beyond Pending legal NOT IN INPUTS | engage VALUES NONE | follower VALUES NONE.
Token UNKNOWN so write API token NOT IN INPUTS. Live AMA not invented beyond PostCues.

3. Spec name set. Launch approval workflow; FAQ approval workflow as SpecNames. Token UNKNOWN so write API token NOT IN INPUTS. No engagement-rate VALUES beyond Inventory. No third post invented.

4. Version lock. Hootsuite 2025 as pasted. Unreleased AI approval writer not used. Response time packs NOT IN INPUTS.

5. Refuse. Engage invent: refused. Follower invent: refused. Response invent: refused. Token invent: refused. Guaranteed engagement: refused.

6. Compliance. Banned hits none. Format ledger+sheet+specs+version+refuse+compliance. Gaps: token policy, Live AMA PostCues, Legal counsel ApproverCues, engagement rate VALUES StatusNotes, planner calendar labels if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...