Suggested updates

Foreslåede opdateringer is a review queue for CRM updates suggested by Dealy or a connected assistant, for example from a meeting transcript or an email. A suggestion waiting for review has not changed the CRM record. Approval applies the reviewed change; rejection leaves the record alone. This queue is separate from Dealy's conversational approvals and undo: Approving and undoing what Dealy does.

Review a suggestion

1. 1Open Foreslåede opdateringer. It starts on Til gennemsyn.
2. 2Read Hvorfor denne ændring, the affected record, and the Før and Efter values. Click the record's name when you need the rest of the record.
3. 3The card names the meeting or email the suggestion came from. The card's Flere handlinger menu has Åbn kildemødet for a meeting and Vis kilde-e-mail for an email; an email can only be opened by someone with access to that mailbox.
4. 4Choose Godkend og udfør to apply that version, or Afvis. Rejection can include a Begrundelse (valgfrit); confirm with Afvis forslaget.

You need access to both the proposal page and the affected record. Being able to read a suggestion does not necessarily let you approve it. Guests cannot review proposals. New activities also respect assignment and linked-record permissions. A connected assistant may propose and read outcomes; it cannot approve through its API credentials.

Correct a suggestion before approving

Choose Rediger forslag. Select the changes you want to keep and correct the values, owner, deadline or linked record. Use Gem og vurder igen to save an amendment, then review the updated before-and-after before approving. Saving an amendment does not apply it. Earlier suggestions remain available through Tidligere versioner in the card's Flere handlinger menu.

Text replaces the displayed old text. Custom-field objects and other collections replace their visible contents: omitted values are removed. Internal integration bookkeeping is preserved. Adding a person's note is a separate timeline-note suggestion, not an update to a hidden notes field.

Unsupported fields and invalid values cannot be approved. Subscription terms that require the subscription change workflow must be changed on the subscription itself.

Handle changed, expired or failed suggestions

If someone changes the relevant record values, approval stops instead of silently overwriting them. Choose Opdater forslaget, review the newly loaded values, and decide again. Older suggestions without a recorded starting point also need this explicit refresh.

Expired suggestions leave Til gennemsyn and appear under Udløbet. Refreshing one starts a new review period. A failed attempt made by the current approval flow leaves the record unchanged; correct or refresh it and review again.

An older attempt labelled Resultatet skal kontrolleres (under Skal kontrolleres) may have an uncertain result. Inspect the current record first. You can then edit the suggestion, confirm that you checked the outcome, and choose Klargør et nyt forslag. This creates a separate suggestion for another review; it does not rerun the earlier approval. If the activity or note already exists, the fresh suggestion changes that record instead of creating a duplicate. The earlier decision stays in history.

A lost response does not require another write: retrying the same completed approval returns its recorded result.

Find decisions and follow-up work

Use Søg i forslag, Alle posttyper and Alle kilder to narrow the queue. The row of buttons under the filters switches between Til gennemsyn, Alle afgjorte and each single outcome, such as Udført or Afvist. Outside Til gennemsyn you can also pick a Bedømmer. The arrows below the list reach the remaining pages. Decided suggestions show who decided, when, the rejection reason where supplied, and the actual saved result for an applied change. Kopiér link in the card's Flere handlinger menu copies a link to that one suggestion.

If preparation of meeting or email suggestions was interrupted, Ufærdige forslag fra kilder shows how much was prepared. Choose Fortsæt med manglende forslag to prepare missing suggestions. Existing suggestions, approvals and rejections are retained. A source with no suggestions prepared yet can also appear here. Failed or expired suggestions already prepared are handled through their own history cards.

Integrations and delivery

A saved CRM change and delivery to a connected integration are different results. The card reports matching registered outbound subscriptions and, when the approval has a delivery receipt, whether those deliveries succeeded, are pending or need attention. Failed deliveries do not mean you should approve the CRM change again. Ask an administrator to inspect the integration's delivery queue.

This is not a promise that every configured workflow runs, or that no external action occurs when no receipt is shown. The approval uses the supported CRM service operation and its outbound events. Effects already delivered outside DealJourney cannot be undone here. For external assistants' direct changes and their separate undo flow, see See what an external AI assistant did. For connection permissions, see Connect an AI assistant to your CRM.