What have you tried with Composer so far?

Happy to kick things off!

Ask it why an abandoned cart flow dipped and it starts with the numbers. Deliveries, conversions and value per email, flow-level rates calculated in the open, so you can check its work instead of just trusting it. 

Last run it caught something the dashboard didn’t. Deliveries down 9% across the flow, conversion value down 8%, nearly all of it on a short delay email in a cart abandonment flow. Click and conversion rates flat. The next email doubled its value because its coupon caught conversions an earlier email lost.

Composer gave us three follow-ups, focused around traffic sources, the delay itself, and the offer. We fixed everything in a few minutes.

Three things that make it work for us:
- Give it real inputs rather than screenshots or panicked prompts.
- Force structured output with evidence, or it drifts into summarising when you wanted answers.
- Composer flags, the strategist decides.

I deliver Klaviyo tutorials to a group of Shopify store owners. It’s an annual program. In the upcoming program instead of teaching how to set up flows I’ll be delivering via API preconfigured flow skeletons with triggers, filters, drag and drop templates with some dynamic blocks preconfigured, and webhooks (thank you, ​@Kim from Cadence). It means they’ll get their flows running and generating revenue faster.

A prompt in the first flow message is available to populate the entire flow’s content. I originally thought they’d use the prompt with their own AI to generate the flow content.

I tested the prompt in Composer and I was happily surprised to see that on its own Composer cloned the flow and populated the message content, subject, and preview lines. (The brand guide and voice was first set up in Klaviyo.)

Composer definitely could not do that a couple of months ago!