Pay for what your teams actually need.

Your own objects and fields are first-class in the sidebar. Teams whose real process lives on custom objects do not have to leave it behind to get activity captured.

The user chooses what gets filed and where, including to custom and related objects, rather than everything being captured and sorted out afterwards.

Title, phone and company are lifted from the sender's signature when a contact or lead is created, so the record starts complete instead of starting empty.

One licence covers both inboxes and both mobile apps. Mixed-client organisations do not have to standardise first.

Sales, Service, Financial Services, Experience and the rest. No edition gate, no minimum tier.

Rules-based matching files an event against the opportunity, case or custom object it actually belongs to — not just the contact it was sent to.

Events the user marks private never leave the calendar. The rule runs before anything is written, so the CRM never sees what it should not.

Restrict the sync to events whose attendees match a lead or contact in Salesforce. Internal standups and personal appointments never reach the CRM, so activity reporting counts customer time rather than calendar volume.

Backfill past activity into Salesforce for a defined period, so reporting starts with history rather than starting from today.

Sync is configured per object, per field and per related record. The usual alternative is a single switch that captures everything or nothing, which is why teams end up turning it off.

Activity lands on the records your existing reports already read. Nothing sits in a separate store with its own retention clock and its own reporting.

The rep decides what belongs in the CRM. Capture-everything produces a CRM nobody trusts and a security conversation nobody wants.

Restrict the sync to mail with a matching lead or contact. Everything else stays in the inbox, which is what makes a capture-everything policy unnecessary and the security review short.

A conversation nests under the most relevant related object rather than scattering across whichever contact replied last.

Thread continuity survives a change of object relationship, a change of owner, or several owners on the same deal.

Load an inbox's past activity into Salesforce for a defined period. Inquire for scope.

Activity reaches Salesforce in near real time, against a fifteen-minute floor previously.

A booking made in Salesforce has to reach the calendar before the next person books over it. On a fifteen-minute cycle that window is wide enough to double-book; on five minutes it is not.

Finishing a task in the inbox closes it in Salesforce, so the CRM reflects reality without a second visit.

Every booking creates or updates the Salesforce record as it happens. A booking that does not reach the CRM is a meeting your pipeline never sees.

Availability and booking exposed as an API so scheduling can be embedded in your own product or workflow.

Team bookings create the same CRM records as personal ones — the pipeline view does not have a hole where the team calendar is.

Leads are matched against who is actually loaded, so work spreads instead of piling onto whoever has an open slot.

Route by the criteria your business actually uses, defined as your own workflow groups.

A qualified lead books a live calendar in the same session, with no SDR triage in between.

Campaign, channel and industry travel with the booking into Salesforce Key Interactions, so meetings are reportable back to the spend that made them.

Cirrus attends because the meeting exists, not because someone remembered to start a recorder.

Zoom, Teams, Google Meet and the rest. Capture does not depend on which tool the customer picked.

The stream is processed during the call rather than uploaded after it. That is what makes live meeting AI possible at all — anything that waits for a finished file can only ever report on a conversation that is already over.

Not queued, not overnight. The reason that matters is commercial: follow-up written at 6pm competes with everything else that happened that day, and the ones that slip are the ones that go cold. Sending while the customer is still warm is the whole point.

New people on a call are identified and enriched into the CRM without anyone typing them in.

Six recorded hours per licensed user per week, pooled across the organisation so heavy weeks borrow from quiet ones. An exposure cap, not a meter on your team.

An open question in the call is answered from your knowledge base and collateral while you are still in the room — phrased in your language and against this customer's situation, not read out of a generic card.

The prompt arrives while the conversation can still change. A summary produced afterwards cannot save the meeting it describes.

Coverage is measured against the qualification model your team actually runs, not a generic scorecard.

Researched and in the inbox before the day starts — no dashboard to remember to open. The standard it sets is that nobody walks into a customer meeting cold, whether they are your best rep or six weeks in.

What was said, what was agreed and what changed, without anyone taking notes. The record exists whether or not the rep had time to write one, which is what makes pipeline reviews argue about the deal instead of about the data.

Written from your collateral and your knowledge base, cited, ready to review and send. Same-day follow-up is the cheapest lever on pipeline velocity there is, and it is the one that slips first when a rep has back-to-back calls.

The follow-up carries what your team has decided a follow-up should carry. That is the difference between a standard and a preference — it holds at forty reps, not just at four.

Talk ratio, engagement and discovery coverage, so a manager can coach the call without sitting in it. Coaching capacity stops being bounded by the manager's calendar.

Calls measured against your own qualification framework, so what separates a closed-won from a stalled deal is visible while the deal is still open.

Not a generic recap — the notes are assembled against the structure your team has agreed, so every record reads the same way regardless of who was on the call.

The output lands on the record itself, as a note or an attached file, reportable and searchable with everything else rather than sitting in a separate tool.

The opportunity, the case, the custom object the conversation actually moved — surfaced as changes to accept, not typed out by hand afterwards.

Stage, next step and close date stop drifting from what was actually said.

The templates already governed in Salesforce, with merge fields resolved, rather than a second library that drifts from the first.

Write and edit templates in Cirrus instead — rich text, merge fields, your own folders. Salesforce stops being a prerequisite for having a governed template library, which matters for the teams who do not live in it.

The same template list wherever you are writing, with recent and most-used surfaced in both.

Answering takes the prospect out. Nobody gets chased after they have replied.

Cadence steps appear as activity on the record, so outbound effort is visible in the same reports as everything else.

Send to a report or a list view without exporting a CSV and hoping it is current.

Which collateral was opened, by whom and for how long — the deal influence of a document rather than the fact it was sent.

Replace the file behind a link you already sent, instead of sending an apology and a v2.

Engagement is visible where the deal is managed, and reportable alongside it.