Help CenterPlatform · Meetings

Meeting Follow-ups

Per-client meeting and Asked for Info worklists plus inbound callback recovery, with current confirmation milestones, stage-aware completion tracking, explicit follow-up dialing from active or paused campaign shells for enrolled and unenrolled contacts, and weekday SDR confirmation digests.

Updated Jul 24, 2026 11 steps 21 questions answeredOpen this page in the platform
On this page

Overview

The Follow-ups page is a per-client action list for meeting work and contacts who are currently Asked for Info, plus a separate inbound callback recovery queue. Pick a client in the switcher first. Pending meeting rows are derived live from booked meeting state, the Asked for Info tab keeps current information-request contacts visible even without enrollment and can open an explicit follow-up dial when an active or paused campaign supplies settings, and Done keeps the last 14 days of meeting follow-up history. Confirmation work is cleared only by a completion for the current stage and meeting slot. Standard accounts have one 24h confirmation; accounts with two-touch enabled have separate 48h and 24h confirmations. A missed 48h milestone is marked on the current 24h work. An earlier slot, different stage, or different follow-up type does not suppress work currently due. Active SalesHive SDRs with pending confirmations also receive one weekday Slack digest at 8:30 AM in their resolved timezone, with meeting and SDR timezone details plus a direct call action when an active or paused campaign is available. Completed current-slot work is omitted from later digests.

How to use this page

  1. Open the worklist for a client

    Find Follow-ups under Meetings in the platform navigation and select a client in the switcher. The page is deal-scoped, so no client selection shows a prompt instead of the worklist. Use ?tab=afi to open Asked for Info, ?tab=done to open Done, or the Inbound callbacks link to open the callback recovery view.

  2. Read the action-needed overview

    The Action needed band combines pending meeting work with the current Asked for Info contacts. Its stats show Confirmations, Reschedules, No-shows, Asked for Info, and Done for the last 14 days. Pending meeting rows are sorted by meeting time, soonest first, while the two active queues stay separate below.

  3. Work the meeting Pending tab

    Pending lists meeting follow-ups still owed for the client. Use All, Confirmation, Reschedule, or No-show to filter the meeting queue. Confirmation rows show a 24h confirmation for standard accounts or the current 48h or 24h confirmation stage for two-touch accounts. A two-touch row can also show 48h missed when the first milestone was not completed before the 24h milestone became due. A row clears only when the current stage and meeting date and time both match a completion, so an old confirmation cannot clear a reschedule. Each row shows the contact, company, meeting timing, who set the meeting, and the reason the follow-up is needed.

  4. Call or mark a meeting follow-up

    Use Call on a meeting row to open the dialer in meeting-followup scope for that contact. Call is disabled only when no active or paused campaign is available to supply the dialer settings and script, or when the follow-up safety rules block the call. An enrolled contact uses its campaign context; an unenrolled contact can use the selected client's campaign shell for this explicit follow-up without being enrolled or added to cadence. Use the row checkbox and Call selected to open a campaign-scoped bulk dialer session; contacts without a usable campaign shell or on another campaign are skipped. Mark done opens the manual outcome menu with Completed, Left voicemail, No answer, or Marked done. The completion is recorded for the follow-up type, confirmation stage when applicable, and current meeting slot, so the same contact can need new work after a meeting moves or its required stage changes.

  5. Open the Asked for Info queue

    Select Asked for Info to see every non-archived contact in the selected client whose current status is asked_for_info. The queue is separate from booked-meeting follow-ups and includes contacts without an active campaign, so an information request does not disappear when no dialer enrollment exists.

  6. Review an information request

    Each Asked for Info row shows the contact, company, Asked for Info badge, follow-up date when one is set, last-contacted time, and the active campaign name or No active campaign. The row Call button is available only for a contact enrolled in an active campaign; otherwise it is disabled.

  7. Call one or more Asked for Info contacts

    Use the checkbox on a row or Select all visible, then choose Call selected. The bulk action groups callable contacts by an available active or paused campaign shell and opens the largest group in that campaign's dialer with the Asked for Info status and selected contact IDs. Contacts without a usable campaign shell or on another campaign are reported and skipped. A row Call button opens the same Asked for Info dialer queue for one contact, including an unenrolled contact when a campaign shell is available.

  8. Review completed meeting follow-ups

    Done lists meeting follow-ups completed in the last 14 days, newest first. Rows show the contact, type, outcome, who completed it and when, whether it came via a call or was manual, and any notes. A recent completion for an old slot remains in history, but the contact stays in Pending when a new meeting slot or follow-up type needs work. This is a read-only history in the page UI.

  9. Use the confirmation Slack digest

    Active SalesHive SDRs with a current confirmation milestone due receive one weekday digest at 8:30 AM in their resolved timezone. Each item identifies the 48h or 24h stage. Each item shows the due state, prospect and client, meeting time in both the meeting and SDR timezones, and either a Call to confirm link when an active campaign exists or a note that a manual call is needed. The digest uses the same current meeting-slot completion rule as this page, so finished confirmations are left out of later digests.

  10. 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. This view is separate from the meeting and Asked for Info tabs and is created automatically for missed inbound prospect calls and voicemails, including calls whose number does not match a contact. Call History remains the audit trail.

  11. Review and resolve a callback

    The callback view shows pending, unread, and handled counts. Review the caller, event type, callback time, source number, assignment, client, and snooze deadline. Use Redial in dialer for a matched contact with a campaign, Contact activity for the contact record with callback context, Mark handled when recovered, Snooze to defer it, Mark read to clear unread status, and Reassign when another assigned SDR should take it.

What the buttons do

Pending tab
Shows meeting follow-ups still owed for the selected client, sorted by meeting time soonest first.
Asked for Info tab
Shows current asked_for_info contacts for the selected client, including contacts without active campaign enrollment.
Done tab
Shows completed meeting follow-ups from the last 14 days, newest first, with the outcome and person who completed it.
All / Confirmation / Reschedule / No-show chips
Filter the meeting Pending list by follow-up type. Confirmation includes the current 48h or 24h milestone rows, and each chip shows its count.
Call
Opens the dialer for one contact in meeting-followup scope on a meeting row, or in the Asked for Info queue on an Asked for Info row. An active or paused campaign can supply the settings and script for an explicitly selected contact even when no current enrollment exists; the contact is not enrolled by the call action.
Select all visible
Selects every currently visible meeting follow-up or Asked for Info row for a bulk call.
Call selected
Opens the dialer for selected contacts grouped by an available active or paused campaign shell. Contacts without a usable campaign shell or on another campaign are skipped.
Mark done
Opens the manual meeting follow-up outcome menu.
Completed / Left voicemail / No answer / Marked done
The four outcomes in the meeting follow-up Mark done menu.
Inbound callbacks
Opens the recovery queue for missed inbound prospect calls and voicemails. An unread badge appears when unread callback items exist.
Redial in dialer
Opens a matched callback contact in the dialer using inbound-callback scope.
Mark handled / Snooze / Mark read / Reassign
Resolve, defer, clear unread state, or assign an inbound callback to another assigned SDR.
Contact activity / Call History
Opens the matched contact record or the associated call audit row. Contact activity from an active callback preserves callback context for recovery.
Call to confirm (Slack digest)
Opens the meeting-followup dialer for the current 48h or 24h confirmation milestone when the prospect has an active campaign.
Open SDR Hub (Slack digest)
Opens the full SDR Hub confirmation worklist so an SDR can review and record completion.
Confirmation stage badge
Shows 48h confirmation or 24h confirmation on a pending confirmation row. A separate 48h missed badge marks a two-touch row whose first milestone was not completed before the 24h stage became due.

Common questions

The list is derived live from booked meeting state. A meeting_rescheduling contact needs a Reschedule, a meeting_set contact whose meeting time passed without Meeting Held needs a No-show chase, and a meeting with a current confirmation milestone due needs a Confirmation. Standard accounts use one 24h confirmation; accounts with two-touch enabled use separate 48h and 24h stages. A stored completion suppresses a confirmation only when its stage and captured meeting slot match the current work.
It is a separate outreach follow-up queue for non-archived contacts in the selected client whose current status is asked_for_info. It includes contacts with and without active campaign enrollment, so the request remains visible even when the contact cannot be loaded into the dialer yet.
The contact has no active or paused campaign available to supply the dialer settings and script. The queue keeps the contact visible even without enrollment, and the Call action can open it without enrollment when a campaign shell exists. If no shell is available, create or restore a usable campaign before calling.
Select one or more rows, then choose Call selected. Callable contacts are grouped by an available active or paused campaign shell and the largest group opens in the campaign dialer with Asked for Info scope. An unenrolled contact can be included when a shell exists. Selected contacts without a usable campaign, or on another campaign than the group opened, are skipped and reported.
No. Asked for Info has its own tab and count. The Pending tab and its All, Confirmation, Reschedule, and No-show filters are reserved for meeting follow-up work.
A standard account shows a confirmation at its 24h milestone. An account with two-touch enabled can show a 48h confirmation first and a separate 24h confirmation later, using business-day milestone dates and the available lead time. A 48h milestone is not created when the meeting was booked too late to complete it.
A follow-up is auto-captured when you dial a booked prospect from meeting-followup scope and log a call. You can also click Mark done to record a manual completion, for example after confirming by email. A confirmation completion stores its 48h or 24h stage and the meeting slot for matching against future work.
Active SalesHive SDRs with a current confirmation milestone due receive one weekday digest at 8:30 AM in their resolved timezone. It lists the prospect, client, 48h or 24h due stage, meeting time in the meeting and SDR timezones, and a direct Call to confirm link when an active campaign exists. A completion for the current stage and meeting slot is omitted from later digests, and clients do not receive this internal SDR notification.
Clients can view the worklist for their own account, but Call, Mark done, and delete are staff-only actions. A client who clicks one receives a clear Forbidden message.
The meeting date changes, so a completion logged against the old slot no longer matches. The contact re-enters Pending under Reschedule, or Confirmation if the new time is soon. A completion for another follow-up type also does not clear the new work.
The Done tab shows meeting follow-up completions from the last 14 days, newest first.
When a prospect calls one of the client's campaign numbers and the SDR does not answer, SalesHive creates a Missed callback item. A voicemail upgrades the item 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 normal status rules would exclude it.
Snooze hides a callback until 1 hour, 4 hours, or tomorrow. It returns to Pending when the selected 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 matched callbacks can link to their associated call row.
No. Logging a call on a booked prospect preserves the meeting status against regression. A lower-rank disposition is recorded on the call log while the meeting state remains intact.
The contact is still booked but the meeting time passed without a Meeting Held being logged. Once the meeting is held, the contact leaves the meeting follow-up list.
No. Pending matching requires both the current follow-up type and the current meeting date and time. A prior Confirmation completion cannot clear a Reschedule, and moving the meeting creates fresh work for the new slot.
Standard accounts show one 24h confirmation. Accounts with two-touch enabled show separate 48h and 24h confirmation rows as each milestone becomes due. The current row can include a 48h missed badge when the first stage was skipped before the 24h stage became due.
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.

Book a strategy call

Ready to fill your pipeline?

Choose a 30-minute time and we will map out exactly how SalesHive can book meetings for your team.

Loading available meeting times