Open the app

Content & Comms

Customer Story Blog

WEBYOUR AIPRO+

Available on Pro and Team.

When to use it

Use it when a customer result should become a narrative blog post that leaves readers with a new belief. It is not a case study reformatted as an article.

Available on Pro and Team. On Free and Solo it sits in the PRO ONLY group.

What to give it

  • The customer, or a consistent way to refer to them if anonymous.
  • The before state: how they lived with the problem. This is required.
  • What changed, with exact numbers if you have them.
  • The moment the result became real.
  • Whether a customer quote is approved.
  • The belief you want the reader to hold at the end.

If your result covers several customers, the tool frames it as a group story and asks only for the customer identity and the before state. Everything else without proof is marked as a gap.

It reads your Voice and Messaging and guidelines from the Brand Box.

Run it on the web

Open the Quick tab, choose Customer Story Blog from the tool picker, and paste your notes. Run it, then copy the briefing, use Open in Claude, or download it, and let your AI write the post. Check the "Brand used" line to see which Brand Box parts shaped the result.

Run it in your AI

"Use pmmagent_elevate for a customer story blog about a Tuskor customer that stopped double-booking technicians. Quote not yet approved."

The reply is the briefing, with the workspace named and a runs-left line. This tool uses a Pro run. Connector access needs Solo or above.

Good output looks like

  1. Opening scene (40 to 80 words): the customer's world before the product appears, built only from your facts.
  2. The before state: the systemic problem and what failed before.
  3. The turn: a short bridge.
  4. The after state: what changed, with your numbers.
  5. Customer voice: the approved quote, or a draft marker.
  6. Closing argument: ends on the belief. It does not end on a call to action.

The target length is about 750 to 950 words.