The AI company read: what it analyzes and when it refreshes

Every active company in Current gets a short, AI-written read: a one-sentence summary, a handful of highlight bullets, and a sentiment read. It's built to answer one question fast — "is this account healthy, or does someone need to look at it?" — without you having to open the ticket queue, the contract, and the deal board separately.

The read is grounded in real data from the past week, not a vague vibe check. It's the same evidence you could pull yourself, just synthesized:

• ＋A 7-day ticket deep dive — every ticket touched that week, including how it opened, whether it's still open and for how many days, and when it was first responded to.
• ＋Repeat-issue clusters — when three or more tickets that week point at the same system, device, site, or person, the read calls it out by name (for example, "4 tickets on the Edina print server this week").
• ＋Escalation tone — language like "again," "still down," "urgent," or a frustrated tone across tickets, emails, and notes, not just ticket counts.
• ＋Aging items — anything still open for 5+ days, or open and high-priority, is flagged explicitly rather than buried in a list.
• ＋Seat and headcount trend — growth reads as an expansion signal, shrinkage reads as a churn-risk signal.
• ＋Upcoming renewals — contracts ending within the next 120 days are called out by name and date.
• ＋Open deals, recent activity, and active projects, for a rounded view of delivery and pipeline alongside support.

When there's a genuinely notable shift — an expansion, a renewal coming up, a churn-risk pattern, or an upsell opening — the read adds a growth chip. If nothing stands out, it leaves that off rather than manufacturing a signal.

The company read regenerates automatically overnight. It's smart about cost and staleness: if nothing meaningful changed since the last run, it skips regenerating rather than burning an AI call for an identical result, and it treats a read as fresh for about 24 hours. You can also trigger a manual refresh from the company page, though repeated manual refreshes are throttled to a couple of minutes apart so you can't accidentally spam it.

Not every ticket queue or service board is meaningful for a health read — some tenants sync queues that are purely internal or administrative. Under Integrations → your PSA's Manage drawer, you can turn individual queues or boards on or off. Turning one off does two things: it stops its tickets from syncing at all, and it excludes any of its already-synced tickets from every AI read — the deep dive, the repeat-cluster detection, all of it.