Skip to main content

[Guide] Proactive DM review

Use for proactive briefings on new Needs reply conversations and conversations new in For Review: due Manual first messages and follow-ups, held DMs and failed sends. Highlight useful next steps and offer help with routine messages.

Written by Oleg Sobolev

For a proactive DM review, help the user see which selected LinkedIn conversations need attention and how to move them forward. Start with the supplied Needs reply list, then For Review. Give useful next steps, not a list of everyone in the inbox.

This Guide covers the conversations selected for a DM briefing. It does not require a general account review. Voice improvements, account strategy and longer-term performance belong to [Guide] Proactive general account review. Reading older messages to understand a selected conversation is part of this DM review; independently sweeping the old inbox is not.

Use the selected DM work

For a scheduled built-in review, start with Selected DM conversations, the two lists Extrovert supplied for this run:

  • Needs reply: conversations where the prospect wrote last and is waiting for an answer, read or unread, with an incoming message after the time shown as Needs reply incoming after. An old unanswered message or an ended snooze alone does not put a conversation here.

  • For Review: conversations where a person needs to act now: a due Manual first message or follow-up, a DM Extrovert held back with a reason, or an automatic send that failed. Only conversations that entered For Review in the last seven days and after the previous DM review are included. These conversations may already be read and need not contain a new incoming message. Each one shows why it is in For Review and since when.

The supplied incoming-message time applies to Needs reply, not to For Review. Do not describe a For Review item as new unless its timestamps support that claim. If a send failed or its result is unknown, the message may already be sent: check the conversation before suggesting to send it again.

The public list tools return current queues, not the next page of this supplied selection. Do not reconstruct the old inbox or fetch additional queues just to lengthen the briefing. An old conversation can be relevant because of a qualifying incoming message or a current For Review entry in the selection. Match overlapping entries by connectionId and discuss each once.

For an on-demand request or an external recurring agent that selects its own work, call dm-conversations_get-list with the selected account's ownerId, once with view=needs-reply and once with view=for-review. Use the user's requested period; for an external recurring task, use its previous DM review as the time reference. The date of a general account review is not a DM boundary. This is a different input path from a scheduled built-in review: a missing supplied block there is not evidence of an empty inbox and does not authorize an unrestricted queue sweep.

Only when selecting work yourself from the ordinary inbox lists: these tools have no since filter. Use incoming-message dates for Needs reply and forReviewSince, the time a conversation entered For Review, for For Review. A recent outgoing message is not a new incoming event.

Review enough relevant conversations to give useful advice; you do not need to cover the entire queue. Do not fetch view=all or include older items solely because they are still in Needs reply or For Review. Do not re-filter the selection supplied for a scheduled built-in review.

Read the conversation before highlighting a person

Use list previews to select threads. Before discussing a conversation individually, call dm-conversations_get with messageLimit=10 and markAsRead=false. Read older messages when needed to understand what the person agreed to, refused or asked for. If the latest message is outgoing, check the relevant incoming message too. Do not ask the user to recover context you can read yourself. If history cannot be obtained, state that limitation instead of presenting the preview as a reviewed conversation.

Establish who last made a meaningful move, what they wanted and what should happen next. Read or unread status is not the next action. Distinguish a reply the user owes from a follow-up to an outgoing message. If the useful next step is to wait, do not present it as a reply to handle now. Do not label someone interested just because they replied.

Choose useful next steps

Distinguish routine work from conversations worth highlighting. A first message or another follow-up in an unanswered outbound sequence is useful routine work. A substantive reply, unresolved question, interest, objection or agreed next step followed by silence may need individual attention. Interpret it in the conversation rather than treating every For Review entry as a hot lead.

When a prospect declines the current outreach, propose removing them from that outreach campaign. If later contact is welcome, offer a suitable existing nurturing campaign instead, after checking its strategy. If none exists, prefer removal; suggest creating a nurturing campaign when there is a clear reason to stay in touch. These are proposals for the user to approve, not actions to perform during the review.

Group routine work instead of inspecting or listing the whole queue. Routine but actionable first messages and follow-ups can be enough for a short briefing; they do not need a hot lead alongside them.

DM drafts are generated on demand. Choose work from the conversations, not from draft availability; missing draft text is not a problem to report. During the review, suggest a next action or brief wording; leave draft creation, editing and sending for the user’s approved follow-up. Enabling DM suggestions does not send messages. For the approved follow-up, use [Guide] Write, review and send DMs; for an approved move or removal of prospects, use [Guide] Import and manage prospects.

Give a short, useful briefing

After a brief greeting, write one short, warm, upbeat sentence that hints at the overall theme of the recommendations below. Connect it to what matters to this user and spark curiosity to read on. Use natural everyday language. Leave the actual recommendations and their details for the body; do not open with account status or statistics. Do not call the email a review, check or report.

Put all conversation triage in one DMs for today section, translated when writing in another language. Extrovert saves a scheduled built-in review in the user's chat and handles applicable email delivery; write for someone reading on a phone. For an on-demand review or an external agent, use the requested channel and keep the same concise, action-first style.

Use bullets for people worth highlighting and a closing offer in its own paragraph. For each person, give the next move and its essential context in one short sentence. Add a second only when needed to understand the decision. Skip the person’s bio and the retelling of the conversation. Do not include long drafted replies or give each person a separate heading and standalone offer. Ask a focused question only when the next step depends on missing context.

Group routine first messages and follow-ups instead of listing everyone. In a separate short paragraph, offer the specific work: help with highlighted conversations and prepare the relevant routine messages. Offer sending only with the user's approval, and respect their preference for manual review. Approval to review drafts is not approval to send.

Keep the offer to one or two short sentences. If the relevant routine work exceeds 50 conversations, offer to handle it in batches.

Use counts only when verified and useful. Each supplied total describes that list's selection for this run, not the whole inbox. Do not add Needs reply and For Review totals: the lists can contain the same people.

Use the user’s stated language preference or the language they clearly use in their own writing, profile and business materials. A name or hosting location alone does not establish it. If the language is unclear or English, use English.

When first naming a person, use a Markdown link with their exact full or display name and the exact HTTPS LinkedIn personal-profile URL returned for that person by a tool. If no verified URL is available, use the available name as plain text. Add the company or role only when needed to distinguish the person. Do not invent name parts, URLs, IDs, avatar links or special person markers. Person links are allowed. You may also link a specific Extrovert page you talk about, such as a campaign or a Voice. Use only the relative app paths from your instructions, with no domain, and only IDs a tool returned. Use the page or object name as the link text. Add no other links. In the app, these links open inside Extrovert. The email removes links and keeps the text, so the sentence must read well without the link.

For a scheduled DM-only review, return a finished, useful briefing on the supplied work; do not omit the entire result. Routine first messages or follow-ups can be useful work without a hot lead or a new incoming reply. For a combined review, use one greeting and opener for the whole message, then place the DM section after the general proposals without repeating them. Do not invent urgency, interest or a reply owed when the conversation supports waiting instead.

For a built-in review, offer help with the specific DM work in the Extrovert chat where the report appears. Extrovert provides the entry point from the email. Do not invite a reply by email. An external agent should use the agreed place for discussing the result.

Did this answer your question?