Outreach Follow-Up Tracker: Due Dates and Private Handoffs

Use the Social Media Outreach Results Tracker to review supplied schedules locally. It does not send messages, synchronize inboxes, or create calendar appointments.

Give the due queue one precise operating question

Start the morning review with a specific question: which contacted records in this selected campaign and first-contact cohort are explicitly open and scheduled for review by the declared cutoff? That question is narrower than every unfinished relationship in the business. The tracker uses your own dates and states to answer it, leaving richer project tasks and appointment details in their existing systems. A date in Next follow-up can mean checking an agreement, reviewing new information, or deciding that no further action is appropriate. It does not mean another message should be sent, and the tool cannot determine whether a particular contact expects further communication.

Choose the Platform context that describes the supplied ledger, an Account label for the review, Cohort start and Cohort end for first-contact eligibility, and As of date for the snapshot. The same queue rules apply across Instagram, TikTok, YouTube, Facebook, LinkedIn, Threads, X, Snapchat, and Reddit contexts. Those choices do not assert that every platform offers the same messaging route or that SMTasker supports an inbox action for each one. The tracker does not inspect platform availability at all. Its calendar is built from the records you provide, so the human reviewer must retain the relationship context outside the calculation.

The cohort boundary is particularly important for daily operations. A contact approached before the selected interval may have an old scheduled date and still be absent from this queue. That absence is correct for the selected report, not proof that the contact has no outstanding work. If your agenda needs a broader first-contact period, choose it explicitly and analyze again. Do not move First contact merely to pull a familiar person into today’s result. The scope counts distinguish eligible, uncontacted, and outside-cohort records so the reviewer can understand the difference between the saved inventory and the selected working agenda.

Prepare a day-only calendar without inventing activity

The tracker accepts calendar dates such as 2026-11-10, not meeting times or time zones. At that cutoff, a November 10 follow-up is due today and a November 8 follow-up is two calendar days overdue. Weekends and holidays count because the calculation is a difference between calendar days, not a business-day service agreement. Decide the appropriate review date yourself when a contact asks for a later check. A Friday task does not automatically move to Monday, and a date entered before Last touch does not automatically move forward. The tool flags the ordering so you can interpret the actual task rather than silently changing it.

Keep completed activity separate from planned activity. First contact, Last touch, Reply date, Lead recorded on, and Booking recorded on must not be later than As of date. Next follow-up can be later because it describes a future plan. If a call was confirmed November 9 for November 24, the booking observation belongs to November 9; the appointment itself remains in the real scheduling system. This distinction permits an honest current snapshot without pretending the future meeting has already occurred. The ledger does not provide a meeting-calendar integration, reminders, time-slot management, or a record of whether the eventual appointment was attended.

Do not use As of date as a historical rewind control. A current record containing a November 9 reply is incompatible with a November 5 snapshot, and validation should reject that contradiction. To reproduce an earlier review, open the deliberately saved earlier project or reconstruct it from trustworthy historical evidence. The current status and latest touch cannot reveal every previous state on their own. Save dated project versions privately when historical comparison matters, and label the review cutoff clearly. A useful calendar handoff states what the ledger knew at the cutoff rather than claiming to recover a complete event history from one current row.

Set up the twelve-record handoff example

Use a fictional campaign called November handoff, with Cohort start November 1, Cohort end November 7, and As of date November 10, 2026. Records due-01 through due-08 have first-contact dates inside that interval. Add due-12 as another eligible contact, due-09 as an uncontacted prospect, due-10 as an October 30 first contact, and due-11 as a November 3 contact assigned to a different campaign called Separate work. Select November handoff in Campaign filter. There are twelve saved records, eleven selected records, and nine eligible records. This guide’s fixture is intentionally different from the six-record built-in example.

Give due-01 a neutral reply and November 8 follow-up; due-02 tracked no reply and November 10; due-03 a negative reply and November 9; and due-04 a positive reply, recorded booking, and November 10. Keep those four records open. Set due-05 to paused with November 7, and due-06 to closed with November 6. Keep due-07 open with unknown reply, unknown Last touch, and a future November 11 schedule. Leave due-08 open but unscheduled. Finally, keep due-12 open with November 8 follow-up and November 9 Last touch. Only dates for actual completed activity need to be on or before the cutoff.

For the excluded records, give uncontacted due-09 a November 9 schedule, outside-cohort due-10 a November 1 schedule, and other-campaign due-11 a November 8 schedule. None belongs to the current due rows. The first is counted as uncontacted scheduling in the selected scope; the second remains outside the first-contact cohort; the third fails the campaign selection. This deliberately mixed inventory tests whether a handoff respects eligibility instead of copying every old date from the saved table. Keep all aliases fictional when reproducing it. A scheduling demonstration needs representative states and dates, not real contact names, private message text, or a copy of an actual customer list.

Read the ordered agenda and its outcome flags

The example produces five due records: due-01, due-12, due-03, due-02, and due-04, in that order. November 8 comes first, with the exact references breaking the same-date tie; November 9 follows, then November 10. There are three overdue tasks and two due today. The two November 8 rows are each two calendar days late, the November 9 row is one day late, and the November 10 rows are zero days late. This ordering is deterministic, not a priority score. It does not know whether a booked preparation task is more urgent than checking a neutral response or reconciling an apparently stale schedule.

Due-03 remains present despite its negative reply because it is explicitly open and scheduled. It receives a follow-up-on-negative review flag. Due-04 remains present despite the recorded booking and receives follow-up-on-booking. These flags prevent an outcome from being mistaken for an automatic state change. A negative contact might need a promised administrative closure; a booking might need preparation. Alternatively, either schedule may be inappropriate and should be removed or the record closed. Decide from the underlying agreement. The calculator deliberately does not infer consent, suitability, or a next message from the combination of a status and an overdue date.

Due-12 is flagged because its November 8 schedule precedes its November 9 Last touch. Review whether the newer activity already completed the task, created a different task, or left the original one outstanding. Due-07 has a last-touch-unknown flag even though its future follow-up is not due yet. That missing value is not zero days since activity. These four eligible contacts generate four flag occurrences in this particular fixture, but other records can carry several flags each. Keep flagged-contact counts separate from occurrences so a single complicated relationship is not reported as several different contacts with issues.

Close or pause work without creating duplicate contacts

After reviewing a due record, choose the state that represents the remaining work. Closed means it should not join the open queue; paused means it is intentionally not active; open leaves a scheduled eligible record available when its date arrives. These labels do not change themselves when a reply becomes negative or a booking becomes yes. An open record with no Next follow-up is also not due, even if the relationship feels important. Use that distinction carefully: unscheduled is not the same as completed. Keep wider project accountability in the operating system that holds owners and detailed tasks, since this ledger does not add those fields.

A completed follow-up updates the existing reference rather than creating another contact. Maintain one exact reference across the whole project and one primary campaign assignment. References are case-sensitive after trimming and NFC normalization, so standardize aliases before team entry instead of relying on the tool to match people. Touch count describes the number of interactions you have actually recorded; Last touch describes the latest known activity date. Neither changes the contacted denominator when a person receives another follow-up. If you cannot establish the count or latest date, retain unknown rather than inserting a convenient value to make the record appear complete.

A contact can return to open work after being paused if that accurately reflects a new agreed task, but the current row is still a snapshot rather than a full audit trail. Save a dated project before meaningful revisions when the prior review must remain reproducible. Reassigning a primary campaign similarly changes later grouped reports and does not preserve the earlier grouping automatically. Keep commitments, reasons for state changes, and task owners in separate authorized documentation. The ledger’s value is a compact, checkable current agenda, not an imitation of a CRM history assembled by duplicating one person under several slightly different aliases.

Keep reply coverage beside the calendar workload

The due queue and the reply rates answer different questions. A scheduled record can have a positive, neutral, negative, none, or unknown reply status and still be due when its state and eligibility permit. Conversely, a replied contact may be closed or unscheduled and absent from the agenda. In the twelve-record example, set due-06 and due-08 positive, due-05 none, and due-07 and due-12 unknown. Together with the four earlier statuses, the nine eligible records contain seven known reply statuses, five replies, and three positive replies. The calendar’s five due tasks therefore must not be used as the reply-rate denominator.

Reply rate is five among seven known statuses, approximately 71.43 percent. Positive reply rate is three among seven, approximately 42.86 percent, while positive share is three among the five replied records, or 60 percent. Reply coverage is seven among nine eligible contacts, approximately 77.78 percent. None contributes to known status; unknown does not. This distinction gives the handoff two useful pieces of information: what checked records say and how much of the eligible group has actually been checked. If every reply status were unknown, the rate would be unavailable, not zero, even though the queue could still contain valid scheduled review tasks.

Lead and booking coverage should be read independently when those outcomes matter to the recipient. A booking observed without a recorded lead can be valid but flagged for review; it does not require inventing an earlier qualification event. Likewise, calendar lateness does not prove commercial loss, poor prospect fit, or an ineffective campaign. The tool makes no causal claim that additional touches produce more replies or bookings. Use the results to allocate evidence checks and task review, not to prescribe a target number of approaches. A clear handoff can say that two statuses remain unknown and three tasks are overdue without asserting why either condition exists.

Choose the handoff file by recipient need

For a manager who needs workload counts, choose Summary only before analyzing. The resulting copied text, review CSV, PDF, and report attachments exclude contact references, raw records, and row-level activity dates, statuses, or touch data. Aggregate due counts and counts by date remain useful for staffing a review session. Account and campaign labels also remain, so summary is not anonymization. A label naming an unreleased client initiative can reveal confidential work without a single contact alias. Prepare neutral but meaningful labels and inspect the report before sharing it. Local browser processing does not determine who can read the file after it leaves your computer.

For the person responsible for this selected agenda, Include contact references adds only current eligible contact, due, and flag rows. In the fixture, due-09, due-10, and due-11 must remain absent from report row detail because they are uncontacted, outside the cohort, and outside the campaign respectively. That restriction also applies to report CSV and JSON attachments. A long PDF may display a limited, explicitly described set of due or contact rows; complete chosen-scope rows remain in its report attachments. Review the selected scope, counts, and display note together rather than treating a short visible list as either the full project or the full attachment inventory.

Save project has a different purpose and a broader privacy footprint. It always includes every saved record, including the three excluded aliases in this fixture, plus the settings required to reopen the project. Do not send that JSON as a restricted handoff just because the report uses Summary only or a narrow campaign selection. Keep it privately for Open project, and use the scoped review outputs for distribution. Report CSV and JSON are not lossless project backups or input templates. The full saved-record table also remains unfiltered for editing, so capturing the editor is not a substitute for exporting the intended privacy-controlled report.

Finish the daily review with an explicit owner decision

A practical daily pass starts by validating the intended cutoff and scope, then running Analyze outreach. Read overdue and due-today counts, inspect outcome and date-order flags, and consult the source context before deciding any next action. Work through the chosen records with the responsible people in your normal operating process. After changes to dates, states, statuses, filters, or report detail, analyze again because prior results are invalidated. The tracker does not preserve an old report as a reliable current agenda after edits. Resolve a pending entry or pasted CSV first so the calculation represents saved records rather than an unfinished draft waiting in the editor.

For bulk preparation, follow the exact thirteen-column CSV template rather than a platform export or a previously downloaded review. Paste CSV requires Replace records to commit the text; Open CSV validates a file and replaces the saved records after any necessary unsaved-work confirmation. Replacement is not a merge of new follow-ups into old contacts. Keep a private project save before a deliberate replacement, and preserve the current dataset when validation fails. There is no autosave or account-backed storage. These simple habits make a handoff reproducible without promising that a copied summary can be reopened as the original complete, editable record.

The account routine that surrounds the review can remain a separate SMTasker workflow. The product supports nine social platforms through connected Android devices and a Windows or Mac client, with optional Skye setup assistance and permission-controlled MCP access for compatible assistants. Those capabilities should not be described as importing this ledger, matching contact identities, synchronizing outcomes, or sending from its due queue. Manual record review still needs an owner who understands the relationship. Close the handoff with a specific decision about evidence, state, or schedule, then use the appropriate supported account controls only for work that has independently been defined and approved.

Questions about Outreach Follow-Up Tracker

Continue with another outreach guide

Review your supplied contact records in the Social Media Outreach Results Tracker, or choose another guide below. Find more practical resources in all free tools.