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

Active companies in Current get 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. Which companies qualify is covered under "Which companies get a read" below.

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.

Three things qualify a company, and any one of them is enough:

• ＋It's a partner you bill — a company holding an active recurring contract stays covered even through a quiet stretch, because a paying account should never go unread.
• ＋Something happened there in the last 30 days — a ticket, a synced email, a logged call, note or meeting.
• ＋It has at least one open deal. This is new in July 2026, and it's the one that changes what you'll see: a deal is not activity, so a fresh prospect with a live deal and no tickets or logged notes used to get no read at all, at exactly the point an account executive most wants one.

A company matching none of the three has no read, and one that has gone quiet stops refreshing — that's the cost control, and it's why an account you haven't touched in months shows an older read. Log a call, send an email, or open a deal and it rejoins the cycle. There is also a manual refresh on every company page, which works regardless of any of this.

Reads regenerate twice a week, on Monday and Wednesday mornings, for as long as a company qualifies — including for as long as any deal there stays open. Twice a week rather than nightly is deliberate: an account's story rarely moves enough in 24 hours to be worth re-reading, and a briefing that repeats itself every morning is one people learn to skip. If nothing meaningful changed since the last run, Current skips regenerating rather than spending an AI call on an identical result.

A company's very first read doesn't wait for that cycle. An hourly pass picks up any company that has an open deal and no read yet, so a deal opened on Wednesday afternoon has its first read inside the hour instead of waiting until Monday. That pass only ever does first reads — once a company has one, it belongs to the Monday and Wednesday cycle. You can also trigger a manual refresh from the company page at any time, throttled to a couple of minutes apart so a repeated click can't spend against your workspace twice.

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.