Release 2.7.7
This release is about protecting the advocates you rely on — and getting more of your Base data into the systems your teams already work in. Advocate availability now reflects marketing and sales together in one signal, with a rest window sized by how much each ask actually costs the person. Levels can require a genuine mix of asks instead of a raw count. And three more objects — ask participation, the sales reference funnel, and email engagement — flow out through Data Sync. Plus two everyday fixes in the action center.
One availability signal across marketing and sales
Every advocate now carries an Availability recommendation — Ready or Cooling down — computed from everything they’ve actually completed, marketing activities and sales reference calls alike. You set an Engagement effort on each activity type and each reference type (None · Light · Medium · Heavy), and every completed item opens a rest window sized by that effort. The recommendation shows up as a column on the Reference locator and the Referenceability search, on the advocate’s info card, in both report drawers and CSV exports, and as a filter you can search and sort by.
Availability was calculated from sales reference calls only. Marketing and sales drew from the same pool without seeing each other’s activity — so an advocate could finish an analyst interview on Monday and be asked for a sales reference on Wednesday, and nothing in the product would show it. Teams either over-asked their best advocates, or held back from launching marketing programs at all for fear of burning them out.
Advocate goodwill is finite, and it’s the one thing an advocacy program can’t buy more of. Making rest visible — with the reason and the date someone is ready again — turns “who can I ask?” from a guess into a judgment call, and lets marketing and sales draw from one pool without stepping on each other.
Under Settings → Customize → Activity settings, edit an activity type and set its Engagement effort; do the same for your reference types under Settings → Customize → Workflows. Then open Reports → Reference locator or Reports → Referenceability search — the Availability recommendation column is there, sortable, filterable to Ready or Cooling down, and included in the export.
Effort maps to a rest window: Light = 2 weeks, Medium = 1 month, Heavy = 1 quarter; None means the type doesn’t count. Recommendations keep themselves current as advocates complete work, but changing an Engagement effort applies overnight — use Recalculate availability on the activity-types or reference-types table to apply it right away (once every 24 hours across the account; you’ll get an email when it finishes). The existing Available for call is completely unchanged — it stays specific to sales reference calls, and now says so in its tooltip. And the recommendation is a judgment aid, not a wall: nothing is blocked, and you can still reach out to anyone.
Require a mix of asks, not just a count
The Completed asks by tags required condition now takes multiple requirement rows, combined with And. Each row is a number of asks plus a set of tags — so a level can ask for 3 education asks and 2 advocacy asks and 1 research ask. Tags inside a row still behave as “any of these”; the rows themselves each have to be satisfied on their own.
The condition already supported ask completion, but only as a single rule: one count across one set of tags, all OR’d together. That let a lopsided advocate clear a “5 asks across all these tags” bar with five of the same kind. Programs that wanted a real mix — some of each — had no way to express it.
Levels are how you shape behavior, not just measure it. Being able to say “some of each” is the difference between rewarding raw volume and rewarding the balanced participation your program is actually built around.
Under Settings → Levels, open a level and turn on Completed asks by tags required. Fill the first row — a number and at least one tag — then choose + Add requirement for the next one. The optional Limit to a specific timeframe is a single shared window that applies to every row.
Nothing changes for levels you’ve already set up — a single rule is simply a list with one row in it. You can add up to 20 requirements, each with up to 50 tags, and the next row unlocks once the current one is complete. Internal tags stay selectable and keep their Internal marker. On the advocate’s side, the Counts toward your next level marker now follows the rows that are still unmet: an ask stops being marked once the only requirement it was feeding is satisfied, and no asks are marked once every row is met.
Three more objects flow out through Data Sync
Ask participation, the sales reference funnel, and email engagement can now sync from Base to your destination — each source-only, one row at a time, exactly like Activities.
Sync ask participation to your destination
Ask Records is now a source-only Data Sync object — one row per advocate per ask. Push participation out to your warehouse or CRM with the ask, the advocate, their account, where the record currently stands, and the dates behind each step.
Ask participation is the raw material behind every advocacy metric you care about — response rate, time to complete, who is genuinely engaged and who has gone quiet. In your warehouse it becomes something your analytics team can build on directly, instead of a request for another export.
When Base is the source, add Ask Records to a sync job. Each row carries the record and ask ids, the ask type, the status (Targeted, Viewed, Accepted, Processing, Attempted, Completed, Approved, Second approval, Rejected), the viewed / accepted / completed / approved / created / updated dates, and links by id to the advocate (with their CRM contact id where we have it), the account, and the journey where the ask was delivered through one.
Source-only — read out of Base, never written back and never offered as a destination object. The ask’s name isn’t carried on the record; join to the ask in your destination if you need it on the row.
Sync the sales reference funnel to your destination
Reference Requests is now a source-only object — one row per request, carrying its position in the funnel from Registered through Received Reference, plus the rejected and cancelled outcomes. It pairs with References Provided, which shipped last release, so the ask and its outcome sit side by side in your destination.
Reference requests are where advocacy meets pipeline. With the request and the delivered reference both in your warehouse, revenue ops can measure how long references really take, where they stall, and which deals they touched — without anyone opening Base.
Add Reference Requests to a sync job when Base is the source. Each row carries the current status and type, the subject and notes, the requesting salesperson’s name and email, the deadline, the created / last-status-change / reference-provided dates, and links by id to the opportunity, the account, the prospect contact (and their email), the reference manager, and the matching References Provided record.
Source-only, like Activities. Joining to References Provided on the linked id reconstructs the full funnel — request in, reference out — in whatever tool you report from.
Sync email engagement events to your destination
Email Events is now a source-only object — one row per engagement event, covering processed, delivered, opened, clicked, bounced, dropped, deferred, spam report and unsubscribed.
Email engagement is the earliest signal you get that an advocate is drifting — or that they’re warm and ready for more. In your warehouse it can feed engagement scores, churn models and segmentation that Base on its own can’t express.
Add Email Events to a sync job when Base is the source. Each row carries the event type and timestamp, the recipient’s email address, the clicked link on click events, the failure reason where there is one, and links by id to the email and — where the recipient resolves to a known advocate — to that advocate and their account.
This is by far the highest-volume object of the three, so it syncs incrementally: the first run starts from the moment you switch it on rather than extracting your entire email history, and every run after that picks up where the last one finished. Events that don’t resolve to an advocate still sync — you keep the recipient address on the row.
Quality-of-life improvements
Two changes in the action center that take a support ticket and a trip to your inbox out of everyday work.
Approve and Reject now explain themselves
On the Nominations queue, Approve and Reject grey out when none of the rows you’ve selected can actually be actioned, and the tooltip says why in plain language. The old blocking pop-up — “No eligible nominations. Only managed non-terminal nominations are eligible.” — is gone, along with the support ticket it usually produced.
Nothing to configure — select rows on Action center → Nominations as you always have. Mixed selections behave the same as before: Approve stays active and confirms how many will go through and how many are skipped (“Approve 3 of 5?”). Delete is unchanged and still works on any selected row.
Contact the reference without a detour through your inbox
When a reference request reaches the approve-on-behalf stage, its Details tab now has a Contact reference button next to Approve, Decline, Change reference contact and Cancel this request. It takes you to the same reference send page the approval email links to — already set up for this request.
Every other step of this workflow was one click in the action center. This one wasn’t: the only way in was to leave Base, find the approval email in your inbox, and click through from there.
Open Action center → Sales references, expand a request sitting at the approve-on-behalf stage, and choose Contact reference in the footer. The send page opens in a new tab with the same email preview and mute controls you have today — you still review and send.
Like Approve and Decline, the button follows the stage: once contacting moves the request forward, the stage no longer applies and the button drops away on its own. Nothing new to switch on, and no separate “already contacted” flag to keep in sync.