Help CenterPlatform · Meetings

Meeting Follow-ups

Per-client meeting follow-up worklist plus inbound callback recovery with redial, callback-context contact activity, assignment, snooze, and handled tracking.

Updated Jul 20, 2026 13 steps 17 questions answeredOpen this page in the platform
On this page

Overview

The Follow-ups page is a per-client worklist of the meeting follow-ups an SDR still owes, plus an inbound callback recovery queue for missed prospect calls and voicemails. Pick a client in the switcher first. The meeting view is derived live from meeting state and keeps a 14-day completion history; the callback view keeps missed or unanswered inbound calls actionable until they are handled. For a matched active callback, Contact activity opens the contact record with callback context so its Call action can continue recovery in inbound-callback scope.

How to use this page

  1. Open the worklist for a client

    Find Follow-ups under Meetings in the platform nav. The page is deal-scoped, so pick a client in the switcher first. With no client selected you get an empty prompt to choose one. The URL accepts ?tab=done to land on the Done tab, or ?view=callbacks to open the inbound callback queue.

  2. Read the meeting follow-up overview

    The Action needed band at the top shows the total pending meeting follow-ups and four stats: Confirmations, Reschedules, No-shows, and Done for the last 14 days. A stat with a pending count is highlighted. Pending rows are sorted by meeting time, soonest first.

  3. Switch between Pending and Done

    In the meeting view, Pending shows every meeting follow-up still owed for this client. Done shows completions from the last 14 days, newest first, with who did it and the outcome. The counts in the tab labels update with the current data.

  4. Filter pending meeting follow-ups

    On the Pending tab, chips let you narrow to All, Confirmation, Reschedule, or No-show. Each chip carries its count. If a filter has nothing in it, the page says so and suggests trying a different filter.

  5. Read a meeting follow-up row

    Each pending row shows the contact name, company, a type badge, and a meta line with the meeting time, who set the meeting, and what the follow-up is for. Meeting times inside 24 hours are flagged urgent, and past times are flagged overdue, so the rows that need action first read differently from the rest.

  6. Call the prospect for a meeting follow-up

    The Call button on a meeting row opens the dialer scoped to that contact in meeting-followup mode. The button is disabled when the contact has no active campaign enrollment, with a tooltip explaining that the contact needs to be enrolled in a campaign before the dialer can load them.

  7. Mark a meeting follow-up done

    Mark done opens a menu with Completed, Left voicemail, No answer, or Marked done. Picking one logs the outcome against the current meeting slot, shows a confirmation toast with the contact's name, and removes the row from Pending. Use this manual path when you confirmed by email or another channel instead of a call.

  8. Review completed meeting follow-ups

    The Done tab lists follow-ups completed in the last 14 days. Each row shows the contact, type, outcome, who completed it and when, whether it came via a call or was manual, and any notes. It is a read-only history in the UI.

  9. Open the inbound callback queue

    Click Inbound callbacks in the Follow-ups header. The link includes an unread badge when this client has unread callback items. The queue is created automatically for missed inbound prospect calls and voicemails, including calls whose number does not match a contact. It is a separate recovery view; Call History remains the audit trail.

  10. Review a callback item

    The callback view shows pending, unread, and handled counts. Pending includes open callbacks and snoozed callbacks whose snooze time has arrived. Each item identifies the caller when a contact match exists, labels the event as Missed callback or Voicemail, shows the callback time, source number, assigned user, client, and any snooze deadline. An unmatched number is kept as a Review number item with a note to review it before assigning a contact.

  11. Redial a matched callback

    When a callback has both a matched contact and a campaign, click Redial in dialer. The dialer opens on that contact in inbound-callback scope, so the callback can be recovered without waiting for the normal recycle window or the contact's regular dial cap. If the number is unmatched or has no campaign, the card shows Review number instead.

  12. Resolve or defer a callback

    Use Mark handled after the callback has been recovered. Use Snooze to hide it until 1 hour, 4 hours, or tomorrow; it returns to Pending when due. Mark read clears the unread state without handling the callback. If more than one active SDR is assigned to the client, use Reassign to send the item to another assigned SDR.

  13. Jump to related records

    Use Contact activity to open the matched contact record. For an active callback, that link carries the callback context into the record, so Call can open the contact in inbound-callback scope even if normal status rules would exclude it. Use Call History to jump to the associated call audit row, Meeting follow-ups to return to the meeting worklist, or Full Call History to review all calls for the client.

What the buttons do

Pending tab
Shows every meeting follow-up still owed for this client, sorted by meeting time soonest first.
Done tab
Shows completed meeting follow-ups from the last 14 days, newest first, with who did it and the outcome.
All / Confirmation / Reschedule / No-show chips
Filter the meeting Pending list by follow-up type. Each chip shows its count.
Call
Opens the dialer in meeting-followup scope on that contact. Disabled when the contact has no active campaign enrollment.
Mark done
Opens the outcome menu to log a manual meeting follow-up completion without a call.
Completed / Left voicemail / No answer / Marked done
The four outcomes in the Mark done menu. Maps the result onto the current meeting slot.
Inbound callbacks
Opens the recovery queue for missed inbound prospect calls and voicemails. An unread badge appears when unread callback items exist for the client.
Redial in dialer
Opens a matched callback contact in the dialer using inbound-callback scope, which bypasses the normal recycle window and dial cap for recovery.
Mark handled
Marks a callback recovered, clears its unread state, and removes it from the pending queue.
Snooze
Defers a callback for 1 hour, 4 hours, or tomorrow. It returns to Pending when the snooze is due.
Reassign
Assigns a callback to another active SDR assigned to the client. It appears when more than one assignee is available.
Mark read
Clears the unread state while leaving the callback pending for recovery.
Contact activity / Call History
Opens the matched contact record or jumps to the associated call audit row. Contact activity from an active callback preserves callback context so Call can open inbound-callback scope for recovery.

Common questions

The list is derived live from each contact's meeting state, not from tasks anyone created. A contact in meeting_rescheduling needs a Reschedule. A meeting_set contact whose meeting time has passed without a Meeting Held needs a No-show chase. A meeting_set contact whose meeting is inside the next 48 hours needs a Confirmation. A meeting far enough out, or one already held, does not appear.
Confirmations appear inside a 48-hour window before the meeting. A meeting three days out will not clutter the list; one inside two days will.
Two ways. When you dial a booked prospect from the meeting-followup scope and log a call, the outcome is auto-captured as a completed follow-up tied to that call log. Or you can click Mark done to log it manually, for example when you confirmed by email.
Clients can view the worklist for their own account, but Call, Mark done, and delete are staff-only actions. A client who clicks one gets a clear Forbidden message.
The contact has no active campaign enrollment, so the dialer cannot load them. Enroll the contact in a campaign first, then the Call button opens the dialer in meeting-followup scope on them.
The meeting date changes, so a completion logged against the old slot no longer matches. The contact re-enters the Pending list under Reschedule, or Confirmation if the new time is soon, so a moved meeting is never silently marked done.
The Done tab shows completions from the last 14 days, newest first.
The Done tab is a read-only history with no edit or delete button in the UI. Manual entries can be removed by an SDR through the API, but rows auto-captured from a call log are the record of that call and are not deletable here.
Via call means the follow-up was auto-captured when you dispositioned a call in the meeting-followup dialer scope. Manual means an SDR clicked Mark done without a call. The call-linked row also preserves the full disposition on the linked call log.
When a prospect calls one of the client's campaign numbers and the SDR does not answer, SalesHive creates a Missed callback item. If the caller leaves a voicemail, the same item is upgraded to Voicemail. Unknown numbers still create a recovery item so the source number can be reviewed.
The queue is scoped to the selected client. SDR and sales-rep roles see callback items assigned to them, while broader internal roles can review the client's full queue. Staff can mark items read or handled, snooze them, reassign them, and redial matched contacts. Client sessions cannot perform these queue actions.
Redial in dialer appears only when the caller matches a platform contact and that contact has a campaign. An unmatched number stays as Review number so an SDR can verify it before assigning or calling a contact.
For a matched active callback, Contact activity opens the contact record with callback context. The contact's Call action can then open the dialer in inbound-callback scope even if the contact's normal status would be excluded. The contact still needs a campaign and callable phone, and an archived contact cannot be called.
Snooze marks the callback as snoozed and clears its unread state until the selected time. It leaves the active pending list while snoozed, then returns when the time is due. Mark handled removes it from pending permanently.
No. The queue is the action list for recovering missed calls and voicemails. Call History remains the audit trail, and each matched callback can link back to its associated call row.
No. Logging a call on a booked prospect preserves the meeting status against regression, so a lower-rank disposition like Warm Lead, Not Yet Booked, or Asked for Info is recorded on the call log but the meeting state is not rolled back. Forward and lateral moves still apply.
The contact is still in meeting_set status but the meeting time has passed without a Meeting Held being logged. The page treats that as a no-show to chase. Once the meeting is held, the contact leaves the list.
More in Meetings
Booked Meetings Meeting Analysis Potential Meetings
Still stuck?

Get an answer from a real person

These guides cover the everyday questions. For anything they miss, we are easy to reach.

Prefer it done for you?

Everything in these guides is work SalesHive can run for you: US-based SDRs and AI agents working your campaigns, calls, and inbox on one platform.

Explore the platform