Rollups, field history, flow versions, reply times and Slack

The tools teams moving from GoHighLevel or HubSpot look for on day one.

• Rollup fields. Count, total, average, smallest, largest or most recent of a field across linked records: total open deal value on a company, number of tickets on a contact. Optionally only the linked records that match a condition.
• Field history. Every field on a record shows who changed it, when, from what, and whether it was a person, a flow, an import or the API.
• Views. Private, team and everyone views, pinned to the top; totals and averages in a list's footer over every matching record; boards split into swimlanes by a second field.
• @mentions in record notes tell the teammate, but only if they can open the record.
• Notification summaries. Each kind of notification email can come as it happens, in a daily summary or a weekly one, and quiet hours hold email until they end, in your own time zone.
• Flows. Ten starter flows on New automation. Every publish is kept with what changed, and an older version can be restored as a draft. A run can be replayed with the same event to check a fix. A wait can follow a date on the record when it moves.
• Campaigns. A/B results now say whether the leading variant is really ahead, the gap is within chance, or there isn't enough data yet. Review has a Check links button that finds links leading to an error page.
• Inbox. A mailbox can promise a reply time: when a customer waits past it, whoever has the conversation is told and it shows under Reply overdue. Assignment rules (words in the subject, the sender's domain, the channel) decide who a conversation goes to and can label it. Customer messages and your replies can be translated.
• Slack, Zapier and Make. Post deals won, new tickets, meetings booked and more to Slack channels, or post your own message from a flow. Zapier and Make can subscribe to any CRM event.