Turn this customer result into content
customer_result_to_contentConverts a verified customer result sentence into a proof card, case study draft, post, or newsletter section while preserving exact wording and checking approval gaps.
Instructions
Helps you decide how to turn a customer result into a case study, a post and a newsletter while preserving its exact sentence. Needs the exact result sentence with its qualifier and source label, source and date, your role, approval, your own view and a reader action. Returns a proof card, first drafts and a sentence check. Optional proof details expose gaps. Written approval is required for your own customer; without it, returns the card and questions only. Chat collects the facts; the results view shows them. No form. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing or invalid brief fields return field-specific errors. Missing written approval for your own customer returns the proof card and questions only. Use this instead of case_study_generator when you need a proof card and several drafts preserving one exact result sentence.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"exact_sentence": "<exact_sentence>",
"source_url": "<source_url>",
"source_date": "<source_date>",
"source_kind": "<source_kind>",
"source_label": "<source_label>",
"measured_result": "<measured_result>",
"buyer_role": "<buyer_role>",
"relationship": "<relationship>",
"approval": "<approval>",
"as_of_date": "<as_of_date>",
"story_published": "<story_published>",
"customer_name": "<customer_name>",
"product": "<product>",
"call_to_action": "<call_to_action>"
},
"name": "customer_result_to_content"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | Your product or vendor name. Format is text. For example, "invoice review service". | |
| approval | Yes | Format is a JSON object. For example, {"status":"written","approver":"finance director","date":"2026-11-17","uses":["case study"]}. | |
| headline | No | Your own headline, if available. Format is text. For example, "Reducing invoice approval delays". | |
| solution | No | What was done, from the approved story. Format is text. For example, "invoice review service". | |
| challenge | No | The customer problem from the approved story. Format is text. For example, "invoice exceptions delay month-end close". | |
| as_of_date | Yes | The date of this run as year, month and day. Supplied by chat so repeats stay identical. Format is text in YYYY-MM-DD form. For example, "2026-11-17". | |
| buyer_role | Yes | Format is text using one of the listed labels. For example, "vendor". | |
| buyer_view | No | Your own view in whole sentences. The tool will not invent it. Format is text. For example, "Finance teams need a clear owner for each invoice exception.". | |
| source_url | Yes | Public source or approved evidence link, using https. Format is text. For example, "https://example.org/approved-evidence". | |
| source_date | Yes | Publication or evidence date as year, month and day, or not stated. Keep it separate from the measurement period. Format is text in YYYY-MM-DD form. For example, "2026-10-31". | |
| source_kind | Yes | Who stands behind the result. A company report is not independent evidence. Format is text using one of the listed labels. For example, "company_reported". | |
| relationship | Yes | Format is text using one of the listed labels. For example, "own_customer". | |
| source_label | Yes | The source label already inside the exact sentence, for example company-reported. Format is text. | |
| customer_name | Yes | Customer label, including an approved anonymous description. Format is text. For example, "an approved anonymous manufacturer". | |
| proof_details | No | Format is a JSON object. For example, {"qualifier":"in the measured pilot","counted":"120 eligible invoices","definition":"days from invoice receipt to approval"}. | |
| call_to_action | Yes | One action you want the reader to take. Format is text. For example, "book a discovery call". | |
| exact_sentence | Yes | Copy the result exactly, keeping its qualifier and source label inside this sentence. Format is text. For example, "Company-reported pilot reduced approval time from 12 to 9 days in October 2026.". | |
| measured_result | Yes | False for a story with no measured outcome. Never infer an improvement from exposure or scale counts. Format is true or false. For example, true. | |
| published_story | No | The already published story as plain text. Used as source without rebuilding it. Format is text. For example, "Invoice exceptions delay close. Review unresolved exceptions weekly with finance.". | |
| story_published | Yes | Format is true or false. For example, true. | |
| source_checked_date | No | The date you reopened the source, as year, month and day. This is not the publication date. Format is text in YYYY-MM-DD form. For example, "2026-11-17". |