Updates

Updates is the queue where you review CRM changes Tempo wants to make. It’s the second item in the left sidebar of the web app, at /app/dashboard/updates. Tempo reads your meetings, email, and other connected sources, and proposes new values for the fields it tracks on your opportunities. Those proposals wait here until you approve or reject them.

​

Where updates come from

Each field has its own update mode, and the mode decides whether the field ever reaches this queue: Fields and CRM objects is the authority on update modes, including how to change one and who can change it. If a field you expected to see never appears in this queue, that page is where to start.

​

The queue

The page has three tabs:

• Pending — proposals waiting on you, with a count badge showing how many there are.
• Approved — proposals you’ve already accepted.
• Rejected — proposals you’ve turned down.

Use the Find an update box to search the queue. Reject All and Approve All act on the pending updates visible in the current search. Updates are grouped by date under headings like Yesterday, Monday, August 3, and Friday, July 31, so the most recent context is at the top.

​

Reading a collapsed update

Each row in the list is one update — a set of proposed field changes on a single opportunity. Before you expand it, the row tells you:

• A count badge — how many proposed field updates the update contains.
• The opportunity name, with the account name beneath it. For example, an opportunity on the Acme account.
• Source icons — small marks showing where the underlying context came from, such as Granola, Gmail, Slack, or Notion.
• A timestamp — reading “as of” a date and time, so you know how current the proposal is.

​

Reading an update in detail

Expand a row to see a table of the proposed changes, one row per field: Always check Show current before approving. A proposal that looks correct on its own may still be worse than what’s already in the field. The Reason column is what makes a proposal auditable. If a proposed champion on the Jaffle Inc opportunity looks wrong, the citation and source badge point you back to the meeting, message, or email that produced it. Use Quick Add at the bottom of an expanded update to propose a change for another field on the same opportunity. Select the field, enter the proposed value, and add it to the pending update.

​

Approving and rejecting

Each pending update has controls for editing, approving, and rejecting its proposed field changes.

• Approve writes the proposed values to your CRM.
• Reject discards them, and the update moves to the Rejected tab.
• Propose edit lets you change a proposed value before you approve it.

Select individual field rows when you only want to act on part of an update. A selection bar lets you approve or reject the selected rows. The action in an update’s header applies to every field in that update.

​

Acting in bulk

Approve All and Reject All at the top right apply to the pending updates visible under the current search. Approve All writes all visible proposals to your CRM, including proposals you have not expanded. Review the visible set before confirming.

​

Approved and rejected history

The Approved and Rejected tabs are your record of what you decided. Use them to check whether a value reached your CRM, or to see what Tempo proposed on a deal and what happened to it. Approved and rejected updates are read-only. To reconsider a rejected proposal, restore it to Pending, then edit, approve, or reject it again.

​

Review updates for one opportunity

Open an opportunity and select Updates to review proposals for that deal. A count on the tab shows when proposals are pending. The same pending, approved, and rejected workflow applies there.

​

When an integration needs reconnecting

A warning banner can appear at the top of the page — for example, Reconnect Granola, with the explanation that one or more integrations need to be reconnected before Tempo can resume syncing source data, and a Reconnect button. This is how a broken integration surfaces to you. Until you reconnect it, Tempo stops syncing data from that source, so no new context flows in and no new proposals are generated from it. The queue quietly goes stale: what’s in front of you still reflects the last successful sync, not what’s happened since. Click Reconnect and re-authorize the source. Treat the banner as urgent — the longer it sits, the further your CRM drifts from what your calls and email actually say.

​

When a value exceeds the CRM field limit

Your CRM can reject an approval when the final field value is too long. Tempo reports the affected field, the merged character count, and the field’s maximum length. The merged value includes the existing CRM value when the field’s Write Mode is Append or Prepend. Retrying the same approval does not reduce that value. If the value is already within the stated limit, contact support with the opportunity name and field label.