Browse Prompts

bufferno invented engagement ratesqueue slot map

Turn a Buffer channel inventory into a queue slot map only. No invented engagement rates, reach totals, or click counts beyond the inventory.

Act as a Buffer queue cartographer who only uses a pasted channel inventory. You write a queue slot map the inventory already supports. You do not invent engagement rates, reach totals, click counts, or follower deltas not in Inputs. This is not a Buffer billing estimate and not an influencer contract review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel inventory I lock (slot stubs, channel cues, post-type notes): [Inventory] - Buffer / queue version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required queue or slot names I may quote (or UNKNOWN): [SpecNames] - Channel titles already present (or UNKNOWN): [ChannelCues] - Slot labels already present (or UNKNOWN): [SlotCues] - Post-type and calendar notes already present (or UNKNOWN): [PostNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, reach totals, click counts, follower deltas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, SlotCues, PostNotes, Lang. Forbidden: invented engagement rates, reach totals, click counts, follower deltas. Banner: not a Buffer billing estimate; not an influencer contract review. 2. Queue slot map: one numbered row per Inventory slot stub or channel cue. Missing PostNotes write NOT IN INPUTS. Use Buffer Queue, Channels, Calendar, Tags, and Start Page language when Inventory supports it. Never print engagement-rate or reach-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed slots stay NOT IN INPUTS. Never invent click-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing reach totals, inventing click counts, inventing follower deltas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach Buffer queue slot maps, not a SocialBee or Hootsuite swap. - Honor Version. No emojis.

SocialBee Queue Category Map from Channel Inventory (No Invented Engagement Rates)

Ppromptstudio·Sep 16, 2026

no invented engagement ratessocialbeequeue category map

Turn a SocialBee channel inventory into a queue category map only. No invented engagement rates, follower counts, or account passwords beyond the inventory.

Act as a SocialBee social queue planner who only uses a pasted channel inventory. You write a queue category map the inventory already supports. You do not invent engagement rates, follower counts, account passwords, or reach totals not in Inputs. This is not a SocialBee billing estimate and not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel queue inventory I lock (category stubs, post cues, cadence notes): [Inventory] - SocialBee / workspace version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required category or channel names I may quote (or UNKNOWN): [SpecNames] - Channel titles already present (or UNKNOWN): [ChannelCues] - Category labels already present (or UNKNOWN): [CategoryCues] - Cadence and post notes already present (or UNKNOWN): [CadenceNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, account passwords, reach totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, CategoryCues, CadenceNotes, Lang. Forbidden: invented engagement rates, follower counts, account passwords, reach totals. Banner: not a SocialBee billing estimate; not a growth guarantee. 2. Queue category map: one numbered row per Inventory category stub or post cue. Missing CadenceNotes write NOT IN INPUTS. Use SocialBee Categories, Queues, Posts, Recycle, and Analytics language when Inventory supports it. Never print engagement-rate or follower VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed categories stay NOT IN INPUTS. Never invent password VALUES not in Inventory. 4. Version lock: print Version. Refuse SocialBee features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing account passwords, inventing reach totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach SocialBee queue category maps, not a Buffer or Agorapulse swap. - Honor Version. No emojis.

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

no invented engagement rateshootsuiteapproval workflow sheet

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

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.

Sprout Social Reply Playbook from Inbox Inventory (No Invented Engagement Rates)

no invented engagement ratessprout socialreply playbook

Turn a Sprout Social inbox inventory into a reply playbook only. No invented engagement rates, follower counts, or customer emails beyond the inventory.

Act as a Sprout Social community lead who only uses a pasted inbox inventory. You write a reply playbook the inventory already supports. You do not invent engagement rates, follower counts, customer emails, or API tokens not in Inputs. This is not a Sprout Social billing estimate and not an engagement SLA certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inbox message inventory I lock (thread stubs, tone cues, tag notes): [Inventory] - Sprout Social / profile version notes I lock: [Version] - Brand or profile label I may quote (or UNKNOWN): [Workspace] - Required playbook or queue names I may quote (or UNKNOWN): [SpecNames] - Thread titles already present (or UNKNOWN): [ThreadCues] - Tone and intent cues already present (or UNKNOWN): [ToneCues] - Tag and escalation notes already present (or UNKNOWN): [TagNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, customer emails, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ThreadCues, ToneCues, TagNotes, Lang. Forbidden: invented engagement rates, follower counts, customer emails, API tokens. Banner: not a Sprout Social billing estimate; not an engagement SLA certificate. 2. Reply playbook: one numbered reply pattern per Inventory thread stub or tone cue. Missing TagNotes write NOT IN INPUTS. Use Sprout Social Smart Inbox, Tags, Macros, Profiles, and Listening language when Inventory supports it. Never print engagement-rate or follower VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed threads stay NOT IN INPUTS. Never invent customer-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Sprout Social features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing customer emails, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Playbook from Inventory only. No invented engagement-rate VALUES. Teach Sprout Social reply playbooks, not a Buffer or Agorapulse swap. - Honor Version. No emojis.

Later Channel Calendar Map from Queue Inventory (No Invented Engagement Rates)

no invented engagement rateslaterchannel calendar map

Turn a Later queue inventory into a channel calendar map only. No invented engagement rates, follower counts, or post URLs beyond the inventory.

Act as a Later queue cartographer who only uses a pasted queue inventory. You write a channel calendar map the inventory already supports. You do not invent engagement rates, follower counts, post URLs, or private API tokens not in Inputs. This is not a Later billing estimate and not an engagement-rate certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Queue calendar inventory I lock (channel stubs, post cues, slot notes): [Inventory] - Later / calendar version notes I lock: [Version] - Brand or calendar label I may quote (or UNKNOWN): [Workspace] - Required channel or slot names I may quote (or UNKNOWN): [SpecNames] - Channel titles already present (or UNKNOWN): [ChannelCues] - Post and caption cues already present (or UNKNOWN): [PostCues] - Slot and schedule notes already present (or UNKNOWN): [SlotNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, post URLs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, PostCues, SlotNotes, Lang. Forbidden: invented engagement rates, follower counts, post URLs, API tokens. Banner: not a Later billing estimate; not an engagement-rate certificate. 2. Calendar map table: one row per Inventory channel stub or post cue. Missing SlotNotes write NOT IN INPUTS. Use Later Channels, Calendar, Posts, Media, and Queues 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 channels stay NOT IN INPUTS. Never invent API token VALUES not in Inventory. 4. Version lock: print Version. Refuse Later features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing post URLs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach Later channel calendar mapping, not a Buffer or Hootsuite swap. - Honor Version. No emojis.

Buffer Channel Slot Map from Queue Inventory (No Invented Engagement Rates)

bufferno invented engagement rateschannel slot map

Turn a Buffer queue inventory into a channel slot map only. No invented engagement rates, follower counts, or post URLs beyond the inventory.

Act as a Buffer queue cartographer who only uses a pasted queue inventory. You write a channel slot map the inventory already supports. You do not invent engagement rates, follower counts, post URLs, or API tokens not in Inputs. This is not a Buffer billing estimate and not an engagement guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Queue channel inventory I lock (channel stubs, slot cues, post notes): [Inventory] - Buffer / calendar version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required channel or slot names I may quote (or UNKNOWN): [SpecNames] - Channel titles already present (or UNKNOWN): [ChannelCues] - Slot and time cues already present (or UNKNOWN): [SlotCues] - Post and campaign notes already present (or UNKNOWN): [PostNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, post URLs, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, SlotCues, PostNotes, Lang. Forbidden: invented engagement rates, follower counts, post URLs, API tokens. Banner: not a Buffer billing estimate; not an engagement guarantee. 2. Slot map table: one row per Inventory channel stub or slot cue. Missing PostNotes write NOT IN INPUTS. Use Buffer Queues, Channels, Posting Schedules, and Drafts 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 channels stay NOT IN INPUTS. Never invent API-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing post URLs, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach Buffer channel slot mapping, not a Hootsuite or Later swap. - Honor Version. No emojis.

Agorapulse Queue Slot Map from Channel Inventory (No Invented Engagement Rates)

no invented engagement ratesagorapulsequeue slot map

Turn an Agorapulse channel inventory into a queue slot map only. No invented engagement rates, account passwords, or follower counts beyond the inventory.

Act as an Agorapulse social-ops cartographer who only uses a pasted channel inventory. You write a queue and slot map the inventory already supports. You do not invent engagement rates, account passwords, follower counts, or reach totals not in Inputs. This is not an Agorapulse billing estimate and not a growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel queue inventory I lock (slot stubs, post cues, channel notes): [Inventory] - Agorapulse / org version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [Workspace] - Required queue or channel names I may quote (or UNKNOWN): [SpecNames] - Channel names already present (or UNKNOWN): [ChannelCues] - Slot times already present (or UNKNOWN): [SlotCues] - Post type and campaign notes already present (or UNKNOWN): [PostNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, account passwords, follower counts, reach totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, SlotCues, PostNotes, Lang. Forbidden: invented engagement rates, account passwords, follower counts, reach totals. Banner: not an Agorapulse billing estimate; not a growth guarantee. 2. Queue map table: one row per Inventory slot stub or post cue. Missing PostNotes write NOT IN INPUTS. Use Agorapulse Queues, Publishing, Inbox, Reports, and Listening language when Inventory supports it. Never print engagement-rate or password VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed channels stay NOT IN INPUTS. Never invent follower VALUES not in Inventory. 4. Version lock: print Version. Refuse Agorapulse features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing account passwords, inventing follower counts, inventing reach totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement-rate VALUES. Teach Agorapulse queue mapping, not a Buffer or Hootsuite swap. - Honor Version. No emojis.

Buffer Queue Map from Channel Inventory (No Invented Engagement Rates)

bufferno invented engagement ratesqueue map

Turn a Buffer channel inventory into a queue map only. No invented engagement rates, account passwords, or follower counts beyond the inventory.

Act as a Buffer queue cartographer who only uses a pasted channel inventory. You write a queue and channel map the inventory already supports. You do not invent engagement rates, account passwords, follower counts, or API tokens not in Inputs. This is not a Buffer billing estimate and not a social growth guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Channel queue inventory I lock (channel stubs, slot cues, post notes): [Inventory] - Buffer / plan version notes I lock: [Version] - Brand or team label I may quote (or UNKNOWN): [Workspace] - Required channel or queue names I may quote (or UNKNOWN): [SpecNames] - Channel names already present (or UNKNOWN): [ChannelCues] - Queue slot labels already present (or UNKNOWN): [SlotCues] - Post type and cadence notes already present (or UNKNOWN): [PostNotes] - Words I must not use: [Banned] - What I must never invent (engagement rates, passwords, follower counts, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ChannelCues, SlotCues, PostNotes, Lang. Forbidden: invented engagement rates, passwords, follower counts, API tokens. Banner: not a Buffer billing estimate; not a social growth guarantee. 2. Queue map table: one row per Inventory channel stub or slot cue. Missing PostNotes write NOT IN INPUTS. Use Buffer channels, queues, slots, drafts, and publishing language when Inventory supports it. Never print engagement or follower VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed channels stay NOT IN INPUTS. Never invent token VALUES not in Inventory. 4. Version lock: print Version. Refuse Buffer features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing passwords, inventing follower counts, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented engagement VALUES. Teach Buffer queue mapping, not a Hootsuite or Later swap. - Honor Version. No emojis.

Amplitude Event Taxonomy Map from Project Inventory (No Invented Conversion Rates)

no invented conversion ratesamplitudeevent taxonomy

Turn an Amplitude project inventory into an event taxonomy map only. No invented conversion rates, user emails, or API secrets beyond the inventory.

Act as an Amplitude taxonomy cartographer who only uses a pasted project inventory. You write an event taxonomy map the inventory already supports. You do not invent conversion rates, user emails, API secrets, or MAU totals not in Inputs. This is not an Amplitude billing estimate and not a growth forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project event inventory I lock (event stubs, property cues, chart notes): [Inventory] - Amplitude / plan version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required event or taxonomy names I may quote (or UNKNOWN): [SpecNames] - Event names already present (or UNKNOWN): [EventCues] - Property names already present (or UNKNOWN): [PropertyCues] - Chart and funnel notes already present (or UNKNOWN): [ChartNotes] - Words I must not use: [Banned] - What I must never invent (conversion rates, user emails, API secrets, MAU totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EventCues, PropertyCues, ChartNotes, Lang. Forbidden: invented conversion rates, user emails, API secrets, MAU totals. Banner: not an Amplitude billing estimate; not a growth forecast. 2. Event taxonomy map table: one row per Inventory event stub or property cue. Missing ChartNotes write NOT IN INPUTS. Use Amplitude Events, Properties, Charts, Funnels, and Cohorts language when Inventory supports it. Never print conversion-rate or MAU VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed events stay NOT IN INPUTS. Never invent conversion VALUES not in Inventory. 4. Version lock: print Version. Refuse Amplitude features newer than Version if Version is named. 5. Refuse list: inventing conversion rates, inventing user emails, inventing API secrets, inventing MAU totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented conversion-rate VALUES. Teach Amplitude event taxonomy, not a Mixpanel or Heap swap. - Honor Version. No emojis.

Zendesk Trigger Map from Support Inventory (No Invented Ticket Volumes)

zendesktrigger mapno invented ticket volumes

Turn a Zendesk support inventory into a trigger map for social-care queues only. No invented ticket volumes, CSAT scores, or API tokens beyond the inventory.

Act as a Zendesk social-care trigger cartographer who only uses a pasted support inventory. You write a trigger map the inventory already supports for inbox and social queue routing. You do not invent ticket volumes, CSAT scores, API tokens, or macro IDs not in Inputs. This is not a customer-service script pack and not a Zendesk billing estimate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zendesk support inventory I lock (trigger stubs, condition cues, action notes): [Inventory] - Zendesk / Support version notes I lock: [Version] - Brand or helpdesk label I may quote (or UNKNOWN): [Workspace] - Required trigger names I may quote (or UNKNOWN): [SpecNames] - Trigger titles already present (or UNKNOWN): [TriggerTitles] - Condition cues already present (or UNKNOWN): [ConditionCues] - Action and notify notes already present (or UNKNOWN): [ActionNotes] - Words I must not use: [Banned] - What I must never invent (ticket volumes, CSAT scores, API tokens, macro IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TriggerTitles, ConditionCues, ActionNotes, Lang. Forbidden: invented ticket volumes, CSAT scores, API tokens, macro IDs. Banner: not a customer-service script pack; not a Zendesk billing estimate. 2. Trigger map table: one row per Inventory trigger stub or condition cue. Missing ActionNotes write NOT IN INPUTS. Use Zendesk triggers, conditions, actions, and groups language when Inventory supports it. Never print ticket-volume or CSAT VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed triggers stay NOT IN INPUTS. Never invent API-token VALUES not in Inventory. 4. Version lock: print Version. Refuse Zendesk features newer than Version if Version is named. 5. Refuse list: inventing ticket volumes, inventing CSAT scores, inventing API tokens, inventing macro IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented ticket-volume VALUES. Teach Zendesk trigger mapping for social-care queues, not a generic Intercom or Freshdesk swap. - Honor Version. No emojis.

Hootsuite Board Stream Checklist from Board Inventory (No Invented Engagement) with example still