Pylon StrawberryGet four months of support history before the QBR
A companion reads every Pylon issue on the account across the quarter, groups them by what actually happened, and puts tier, ARR and a link behind each claim.
The QBR with Acme is on Thursday and somebody has to answer “how has support been for them”. The true answer is scattered across four months of shared-channel conversations, two escalations resolved on a call, and one feature request raised by three people in three threads.
A companion reads all of it. It lists the account’s issues across the quarter, groups them the way a person would, pulls tier and ARR from the account record, and hands you a page with a link behind every line.
Before the QBR: four months on one page
The companion lists the account’s issues over the quarter and groups them the way a human would: three threads that are all the same integration problem, two onboarding gaps, one genuine bug. Tier and ARR come from the account record. Recurring account reviews fit the operations rhythm.
What lands on your desk is counts, themes, the two things still open, and a link on every claim so the CSM can check anything before saying it out loud.
Why does every issue query need a time window?
Because Pylon requires it.
Listing issues takes a start and an end timestamp, both mandatory, so a companion has to name the period it is asking about. Reads are bounded by construction, and you can see the boundary in the request.
It also makes routines cheap. “Every Monday, the issues from last week, grouped by account, with anything from a tier-one customer at the top” is a bounded query by definition, and it gets looked at every time.
Internal note or customer reply?
A message on a Pylon issue is customer-visible by default and can be marked internal instead.
Internal notes are what a companion should write freely and often: the context, the linked duplicate, the summary of what the engineer said in the thread.
Customer-visible messages are real words from your company, arriving in a shared channel where the customer’s whole team is watching. Those wait for your approval, and so does creating an issue, which both sides see the moment it exists.
Keep the account record worth trusting
Tier changed at renewal and nobody updated it.
ARR is last year’s. A companion patches an account, only the fields you pass, and creates contacts for the people who appear in a shared channel but never made it into the record.
Done as a reviewed batch, that is an afternoon of admin nobody was going to do, and you see the diff first. The broader pattern is in data extraction: read the messy truth, normalise it, then write with a human looking.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents