Composer initial thoughts

Yes, I have has the same issues. I have also had issues where it just can’t find that a flow exists, even when I give it the link, the flow ID, etc.  One thing that has helped is prompting it to re-audit/re-digest the flow every time I make an update (even if I am actively troubleshooting a flow with it and it should understand that changes are happening). 

I've not tested composer exhaustively but it could become a positive addition - it surfaced some issues with a form in a recent audit - and I like that it's native, and the breadth of data it has access to. I also like ease of the one-click audit for a specific flow.

I've created a couple of basic test flows directly from composer and it did a fairly decent job with on-brand content/copy and with some new images included. Not perfect, but a reasonable starting point.

My main reservation for analysis is not being able to upload markdown to a knowledgebase. This is something I do with Claude/Klaviyo MCP so Claude understands the context and objective of the various campaigns and flows for each client's account I manage e.g revenue generating versus non-revenue generating, parallel flows for customers and prospects, expected flow overlap etc. Claude references that markdown when running an audit so its results are insightful without recommending false ‘fixes’.

To do that with composer, I'd have to add context/objectives to every chat session. If I don't, Composer can incorrectly identify actions to take which clutters its useful recommendations. It's only in beta so hopefully a markdown knowledgebase is something Klaviyo will address at some point.

For more advanced users to incorporate their expertise into the audits, campaign/flow creation, and for consistency of approach, support for something similar to Claude skills would be a nice touch too.

Also interested in what others think.

Regards

Andy

@lgrubb thanks for kicking this off.

On the flow audits: yes, we know Composer sometimes works off stale snapshots of your data, and we're actively fixing that so it's always pulling the latest information. To confirm @shannonjorgenfelt’s comment, in the meantime you can ask Composer for a "re-audit" and it'll pull fresh data.

@bluesnapper on editable knowledge bases: yes, we’ll have this soon! We know that's what makes Composer actually feel like it understands your business. We're also adding memory layers so it learns from how you work over time.

Really excited to see how you all are using Composer so far. It's early days, so keep the feedback coming. Happy to answer anything else.