TikTok Outreach Tracking: From Shortlist to Reply

Prepare your own creator ledger in the Social Media Outreach Results Tracker. TikTok is a reporting context for supplied records, not an account connection or an imported inbox.

Decide when a shortlisted creator becomes a contact

A stationery studio finds creators who demonstrate journal layouts and wants to offer a small paper-testing collaboration. Its researcher saves twelve promising profiles, but the partnership owner has approached only five. Reporting five replies against twelve sourced profiles would mix two different jobs. Discovery establishes possible fit; contact establishes an opportunity to respond. Keep that distinction even when both activities happen on the same afternoon. In this tracker, a supplied First contact date determines contacted-cohort eligibility. A profile you watched, followed, or placed on a shortlist does not acquire that date merely because someone plans to approach its owner later.

Choose an observable first-contact rule before collecting results. For the stationery team, it is the date an authorized operator actually makes the collaboration approach through the available route. A draft proposal is not enough, and an unsuccessful attempt that never establishes the intended contact should not quietly become a completed approach. TikTok messaging access depends on account circumstances and settings; the ledger does not test that access. When the actual contact occurs through another agreed channel, document that route in the team’s separate evidence and describe TikTok as the sourcing context rather than claiming the platform delivered every interaction.

An uncontacted candidate can still have a saved reference and a planned Next follow-up date, but that schedule does not put the candidate into the due queue. The tool counts uncontacted scheduled records separately so an unfinished sourcing task cannot inflate an outreach workload. Keep research reminders in the appropriate planning system when they require richer detail than this ledger provides. The useful question here is narrower: among creators actually approached within the chosen dates, what reply status is known, what outcomes have been recorded, and which explicitly open records have a scheduled review due by the cutoff?

Give each creator one stable project reference

Use neutral internal aliases such as paper-01 rather than copying a display name into every report. A display name may change or resemble another creator’s name, while a stable internal alias lets the team maintain one record. References are trimmed, normalized to Unicode NFC, and compared case-sensitively across the entire project. Consequently, paper-01 and Paper-01 remain different strings; they are not automatically recognized as the same person. Agree on one spelling before entry. The tracker rejects an exact duplicate, but it cannot discover that two different aliases, usernames, or external addresses belong to the same creator.

Assign the creator one primary Campaign, such as Paper trial, even if the conversation later includes an event invitation. Creating a second record in Event invitations would duplicate the contact rather than extend the original history. Edit the existing entry when your reporting convention calls for a campaign reassignment, recognizing that reassignment changes subsequent grouped results. Campaign labels themselves are grouped after trimming, NFC normalization, and lowercasing; their display spelling is not an identity check. Keep any richer multi-project relationship map outside this deliberately compact ledger instead of manufacturing several independent contacted people from one continuing partnership discussion.

Repeated approaches update Last touch and Touch count on that same reference. If paper-02 receives an initial approach and one later clarification, a count of two describes touches, not two contacts or two opportunities to reply. Leave Touch count unknown if the source record is incomplete rather than reconstructing a plausible number from memory. Likewise, a known First contact date does not require you to invent Last touch. A missing last-touch value creates a review flag for an eligible record. That flag helps the owner reconcile the history without converting uncertainty into a false activity date or a zero-touch claim.

Work through the paper-testing cohort

Consider six fictional records in Paper trial, reviewed as of 2026-11-10 with Cohort start 2026-11-01 and Cohort end 2026-11-06. The first five creators were contacted on November 1, 2, 3, 5, and 6 respectively. Their reply statuses are positive, positive, neutral, none, and unknown. The sixth creator remains on the shortlist without First contact. This example is separate from Load example, which supplies a different teaching dataset. Enter these six records manually or prepare them using the tracker’s exact CSV template structure if you want to reproduce this guide’s arithmetic with fictional information only.

The five contacted creators are eligible, and four have known reply status. Three have replied, so Reply rate is three divided by four, or 75 percent. The two positive replies give a Positive reply rate of two divided by four, or 50 percent. Positive share instead uses replied contacts: two divided by three, approximately 66.67 percent. Reply coverage is four divided by five, or 80 percent. State all four quantities together. Saying that 75 percent of the shortlist replied would be inaccurate, as would calling the 50 percent positive reply rate the share of replies that were positive.

Suppose the first two creators meet the studio’s stated partnership-fit rule, two others are recorded as not qualified, and the fifth has unknown lead status. Leads are then two among four known lead statuses, or 50 percent, with 80 percent lead coverage. One booking is recorded among four known booking statuses, giving 25 percent and the same coverage. These observations do not prove that the outreach produced those outcomes. For a concrete queue, schedule the third creator for November 9 and the fourth for November 10, leave both open, and leave the others unscheduled. Two eligible records are due: one overdue and one due today.

Read observation age before comparing creator batches

At the November 10 cutoff, the paper-testing contacts have had between four and nine calendar days since first contact. That range matters when a researcher compares their current replies with another batch approached yesterday. Both batches might have accurate statuses and still offer very different opportunities to answer. Cohort start and Cohort end select first-contact dates inclusively; they do not give every eligible creator an equal observation window. Read the reported minimum and maximum ages alongside the rates, then decide whether the cohorts are mature enough for the practical comparison you intend to make with the partnership owner.

A rolling review can keep one entry cohort and advance As of date while recording newly observed outcomes. That approach can show how the declared snapshot changes, but the current project is not an event-history database. Moving As of date backward does not recover the status that existed earlier. A reply or booking recorded after that earlier cutoff makes the edited snapshot invalid until you open an appropriate saved historical version or accurately prepare the earlier record yourself. Preserve dated project files when historical reproducibility matters. Do not erase a real later outcome merely to make today’s project appear compatible with an older reporting date.

All dates are day-only business-calendar values rather than timestamps. A contact on November 6 is four calendar days old on November 10 regardless of the hour someone worked or the device’s local time zone. The tool does not measure working hours, response latency within a day, or a survival curve for unanswered outreach. If the studio needs a median response time, it must use evidence and analysis designed for that question. This ledger instead gives a straightforward age range and a cutoff, making it possible to describe incomplete observation honestly without pretending that an attractive rate has already stabilized.

Classify the response without upgrading discovery signals

The studio defines positive as a creator expressing interest in reviewing the actual collaboration brief, neutral as a substantive answer without that interest, and negative as a decline. Those definitions belong to this review, not to a universal TikTok standard. A creator liking the studio’s latest video or following the account does not automatically satisfy them. A message request, an available contact button, and an accepted interaction route are also not equivalent to a written answer. Record the reply observation that the team can substantiate, and use Reply date for the date of that answer rather than the day a researcher happened to notice an unrelated signal.

None means the owner has tracked the contact and recorded no reply yet. Unknown means the tracking cannot currently establish the reply status. Perhaps an agency colleague holds the conversation record and has not supplied an update. These are different conditions: none belongs in the known-status denominator, while unknown does not. If that colleague later confirms no answer, changing unknown to none can reduce the displayed reply rate without any new rejection. Explain the coverage change before treating the percentage movement as a change in creator interest. Better recordkeeping can change a ratio even when the underlying conversation has not changed.

Lead and Booking status ask separate questions. A positive response to seeing the brief might still fail the studio’s availability or production requirements, while a booking may arrive through an independently managed process. Use Lead recorded on and Booking recorded on when recording yes outcomes; do not put the future filming session date into Booking recorded on. A booking confirmed November 8 for a November 21 conversation belongs to November 8 in this snapshot. The tracker can flag a lead without a reply or a booking without a lead for review, but those combinations are not automatically forbidden or proof of faulty tracking.

Schedule a brief review rather than an automatic chase

A useful next action might be checking whether a creator requested a sample specification, not sending another pitch. Next follow-up therefore represents a date for human review. An eligible row appears in the queue only when Record state is open, a schedule is present, and that date is on or before As of date. Paused and closed records stay out even if their dates are old. Future schedules remain saved but are not due yet. The tracker neither contacts the creator nor adds a calendar event, so assign the actual work and any notification through the team’s existing manual operating process.

Suppose paper-03 has a November 9 schedule at the November 10 cutoff. Days late is one calendar day; it does not imply one missed business day or a recommended urgency. A blank Last touch produces an unavailable time-since-touch value, not zero days. If a newer touch has already happened after the scheduled date, the tool flags that ordering for review without moving the appointment itself. The owner can decide whether the old schedule still describes an unfinished task, needs a later date, or should be cleared. Read the source context before treating the oldest queue entry as the next message to deliver.

A negative reply or recorded booking does not automatically remove an explicitly open scheduled record. A declined sample offer might still need an agreed administrative closure, and a booked discussion may need a practical preparation check. Both situations receive review flags when the relevant schedule remains open. Those flags ask for judgment, not more outreach. If there is no remaining task, close the record or remove the schedule deliberately. If the relationship needs a pause, use paused instead. This explicit state decision prevents the team from mistaking a mechanically generated reminder list for permission to continue a conversation.

Share creator progress without sharing the shortlist

The studio’s client wants totals, not aliases that could reveal unreleased creator negotiations. Choose Summary only under Report detail before analyzing the handoff. That report omits contact references, raw records, and row-level activity details from copied text, review CSV, and the PDF report and its report attachments. It still contains account and campaign labels, which may identify the collaboration even without names. Use an appropriately neutral Account label and Campaign when preparing a broadly shared summary. Summary is a restricted reporting mode, not a certification that every remaining label or aggregate is anonymous in a small creator community.

Include contact references is appropriate only when the recipient needs the eligible ledger detail. Its report rows are restricted to the current Campaign filter and first-contact cohort; the uncontacted sixth shortlist entry is not included, and neither are outside-cohort contacts or another campaign’s aliases. This restriction also governs report attachments. Do not infer the same protection for Save project: that separate editable JSON contains every saved record, including the shortlist and excluded campaigns. Store the full project with the authorized record owner, and send the filtered report rather than the project when the recipient’s role is limited to the selected collaboration review.

The saved-record table remains an editing inventory even while a report filter is active. Seeing an unrelated creator there does not mean that creator belongs in the filtered report; conversely, hiding a report row is not deletion from the saved project. Check both intended scope and output type before delivery. The report CSV and JSON attachments are review formats, not input templates or lossless project backups. For a later editing session, retain Save project privately and use Open project. Because this tool has no autosave or persistent account history, a deliberate saved version is the practical way to preserve the studio’s exact supplied snapshot.

Turn the review into a specific partnership decision

For the paper trial, the first decision is to reconcile the fifth creator’s unknown status with the colleague who owns that conversation. The second is to review the two due tasks against the actual brief and current relationship. Neither decision requires declaring the campaign a winner. The small example has incomplete coverage, unequal ages, and user-defined qualification, so a single reply percentage cannot establish which creator category will work best next month. Write the operational conclusion separately: the missing evidence owner, the brief detail that needs checking, and the date for another comparable cohort review. Keep the ledger focused on observations it actually holds.

When adding a new batch, preserve the first-contact rule and the meaning of positive so comparisons remain interpretable. Changing the offer from a sample discussion to a paid production agreement changes the decision being requested, even if the campaign label stays familiar. Record that distinction in your working documentation rather than expecting a platform selector to normalize it. The tracker has one selected platform context for the project, not a per-record channel attribution engine. Use separate, clearly labeled project versions when another sourcing context would make the combined review ambiguous, and maintain identity decisions in the authorized records outside this tool.

For the surrounding account routine, SMTasker offers a nine-platform workspace with a Windows or Mac client and connected Android devices. Its built-in Skye assistant and permission-controlled MCP access can help prepare supported workspace operations, with human review where configured. That is separate from this manual creator ledger: neither feature should be treated as importing these contact records, matching creator identities, synchronizing replies, or executing the due queue. Explore the supported account workflow only after deciding what the partnership team actually needs. The useful bridge is an approved operating plan with clear ownership, not a claim that the tracker runs creator relationship management automatically.

Questions about TikTok Outreach Tracking

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.