Testimonial permission and publication

This playbook manages the publication of one customer quote or testimonial from incoming feedback to verified live placement. It covers intake reconciliation, speaker and company permission confirmation, editorial review of the proposed presentation, and read-back verification on the intended destination. It excludes broad brand marketing campaigns, managing paid sponsorship contracts, and direct drafting of customer claims without source feedback. If live website publishing integrations are unavailable, the agent generates staging previews and hands off publication verification to an assigned marketing operator.

• Reconcile incoming feedback from forms such as Fillout against the source record in Notion. Confirm the speaker's name, job title, company affiliation, and original statement. Record whether the submission was an unsolicited comment, a survey response, or a designated testimonial submission. If the original quote contains obvious typos or conversational filler, draft a minimally edited proposal alongside the verbatim source text without altering the speaker's meaning or claims.
• Information request. Send the customer speaker or designated contact a permission request via an approved communication route, presenting the exact proposed final wording, speaker attribution, headshot or company logo assets, and designated publication destinations such as website case study pages, landing pages, or social media. Require explicit confirmation of permission to publish under those specific terms, including authorized corporate communications clearance where company brand or logo usage is requested. If the contact requests wording revisions, asset substitutions, or destination restrictions, update the proposal to reflect their exact approved terms. If the contact withholds permission, declines use on specific channels, or does not reply within the designated follow-up window, move the case to Held or declined and preserve the refusal record in Notion.
• Inspect any quantified performance claims or commercial outcomes mentioned in the quote against supplied operational evidence. Customer permission authorizes publication of the speaker's statement, but does not verify an uncorroborated performance metric; retain clearly attributed personal opinion or qualitative experience, and omit or qualify unsubstantiated quantitative marketing claims unless backed by verified customer data. If non-standard legal terms, NDA restrictions, or enterprise brand usage policies are flagged, escalate the draft to legal counsel for explicit clearance before editorial submission.
• Approval. Submit the confirmed quote, verified attribution details, approved speaker headshot or company logo assets, and proposed layout placement in Webflow to the marketing lead. Request formal approval to publish. If the marketing lead or editor introduces material alterations to the quote wording, attribution, visual assets, or publication scope, route the revised presentation back for renewed customer permission and marketing approval before scheduling release. If the marketing lead rejects publication due to product positioning shifts or redundancy, transition the case to Held or declined with the rationale documented in Notion.
• Exception. If publication to the live site via Webflow fails due to CMS schema mismatches, API rate limits, or permission errors, alert the web operations lead. Inspect existing CMS records before attempting any automated or manual retry to prevent duplicate entries. Provide the approved quote payload, target CMS collection item ID, and error response. If automated publishing remains inaccessible, hand off manual publishing to an assigned web operator and keep the case in Publication decision awaiting owner confirmation.
• A fictional example illustrates this process: a customer submits positive survey feedback via Fillout noting that onboarding turnaround was noticeably faster for their team. Because internal telemetry logs verifying exact turnaround duration are not supplied, the agent removes an uncorroborated two-day metric and frames the proposal around the customer's reported qualitative experience of faster onboarding. The speaker confirms permission via an Information request for the revised qualitative wording and personal title attribution (Senior Operations Manager), but withholds permission for company name and logo display under corporate policy. The agent updates the asset and title-only attribution records accordingly. The marketing lead approves the title-only quote for the operations landing page. The agent publishes the entry to Webflow, checks existing items to avoid duplicates, and verifies live rendering via read-back.
• Once publication is triggered, perform read-back verification against the published Webflow CMS item or live URL. Confirm that the exact approved text, speaker attribution, and visual assets are rendered without truncation or formatting defects. Update the source Notion record with the live URL, publication timestamp, and confirmed permission scope. If the write cannot be independently verified, keep the case in Publication decision with an explicit verification task assigned to the marketing lead until final live placement is verified.