Français · English
Free template · Instagram sales · Coaches and setters
Instagram DM follow-up tracker: free template and daily workflow
An Instagram DM follow-up tracker should tell you which conversation needs attention, who owns the next action and what to do next. Use the free CSV template below to separate unanswered questions, agreed check-ins, booking checks and closed conversations. The worked examples show how to make those decisions before sending another message.
Download the free Instagram DM tracker template
Download either CSV directly, without an account. The blank file contains the column headers. The example file contains six fictional records labelled EXAMPLE-01 to EXAMPLE-06, not real Instagram handles.
Version 1 · October 16, 2026. CSV files contain editable values, not formulas, automatic reminders or an integration. Example timestamps use UTC. Import the file as comma-separated UTF-8 data in your spreadsheet app.
What should an Instagram lead tracker include?
Keep one record per prospect, with enough context to decide the next action. A name and an old date are not sufficient: you need to know who last wrote, whether a booking exists and whether the person asked you to stop.
| Field | What to record and why |
|---|---|
| Lead ID or handle | A consistent identifier so the record links back to the correct conversation. Use a unique identifier within your working list. |
| Stage | The current situation, such as Reply needed, Waiting for agreed date, Booking link sent, Call booked, Closed - declined or Needs review. |
| Last inbound UTC | The timestamp of the latest message from the prospect. Keep it separate from your own most recent message. |
| Last outbound UTC | The timestamp of your latest sent message. A reply you sent is not a fresh inbound interaction. |
| Owner | The person responsible for reviewing and completing the next action. |
| Next action | A concrete task: answer a question, check a calendar or review an agreed check-in. Avoid a vague instruction like “chase”. |
| Review at UTC | When a person should review the record. This is a work reminder, not a scheduled send time. |
| Stop follow-up | Yes when further sales follow-up should stop. It is a manual instruction in this CSV, not an automatic suppression rule. |
| Booking status | Confirmed, Unknown or Not applicable. Sending a link is not proof of a reservation. |
| Context note | A short account of the question, promise or constraint that explains the next action. |
| Checked at UTC | When you last reconciled the record with the actual thread and, where relevant, the calendar. |
Start with simple stages. These labels are our proposed workflow, not EKO’s native stage names and not a universal sales funnel. Keep a small controlled list so that “booked”, “call booked” and “appointment” do not become three labels for the same event.
Why record inbound and outbound messages separately?
If a prospect asked a question at 08:30 and your last message was at 08:00, the immediate task may be answering them. If you wrote at 08:30 after their 08:00 question, you may already have answered. Read the content as well as the timestamps: an acknowledgement or reaction does not necessarily resolve the question.
How should dates and time zones be entered?
The example files use an ISO timestamp such as 2026-10-16T09:00:00.000Z, where Z means UTC. Use one documented convention across your team. When a prospect asks for “Friday morning”, agree which date and time zone that means before recording a precise check-in.
Spreadsheet apps may import these timestamps as text. Preserve the original values, and use your app’s date conversion or import settings before relying on date sorting. Do not mix local-time text and UTC timestamps in the same column.
Six worked examples: who should you reply to or follow up with?
Reference time for these fictional examples: October 16, 2026, at 09:00 UTC. The CSV and the cards below describe the same records. “Review” means inspect and decide, not automatically send.
EXAMPLE-01: the prospect is waiting for your answer
Record: last inbound October 16 at 08:30 UTC; last outbound 08:00 UTC. Stage: Reply needed. Owner: Alex.
Context: the prospect asked which session times are available.
Next action: answer the availability question. Do not send a “still interested?” nudge to someone whose question you have not answered.
EXAMPLE-02: a future check-in was agreed
Record: last inbound October 15 at 12:00 UTC; last outbound 12:10 UTC. Review date: October 20 at 10:00 UTC. Owner: Morgan.
Context: the prospect requested a check-in on October 20.
Next action: keep the agreed review date. On that date, check the current conversation and the applicable sending conditions before deciding how to respond. Silence today does not cancel the agreement to wait.
EXAMPLE-03: a booking link was sent, but the outcome is unknown
Record: stage Booking link sent. Booking status: Unknown. Owner: Alex.
Context: a calendar link was sent on October 15; no reservation has been verified.
Next action: check the calendar or booking system first. A link click, a polite reply and a confirmed appointment are different events. Do not claim the person failed to book when you have not checked.
EXAMPLE-04: the call is already booked
Record: stage Call booked. Booking status: Confirmed. Owner: Morgan. Next review: October 16 at 13:00 UTC.
Context: the reservation has been verified in the calendar.
Next action: prepare the call and use the appropriate appointment process. Stop generic booking nudges. Keep preparation separate from re-opening the sales conversation.
EXAMPLE-05: further sales follow-up was declined
Record: stage Closed - declined. Stop follow-up: Yes. Owner: Alex. No future sales review date.
Context: the prospect explicitly declined further sales follow-up.
Next action: archive the sales follow-up and remove any corresponding reminders or queued outreach in the tools you use. Editing the CSV alone does not cancel an automation elsewhere.
EXAMPLE-06: the tracker may be out of date
Record: stage Needs review. Last checked October 10 at 10:20 UTC. Owner: Morgan.
Context: the record has not been reconciled since October 10, so newer messages or bookings could change the next action.
Next action: reopen the thread, verify the available evidence and update the record. An old row is a reason to investigate, not proof that a prospect has ignored you.
A daily workflow for Instagram DM follow-ups
Work through a short review at a time that fits your activity. The sequence below is an operating method you can adapt, not a measured promise about time saved.
- Reconcile before sorting. Check changed conversations and relevant bookings, update the timestamps and mark when each record was checked.
- Apply stop decisions. Remove declined contacts from sales follow-up queues and check any separate tools that may still have reminders or sends queued.
- Answer what is waiting on you. Review inbound questions and incomplete answers before treating the conversation as a silent lead.
- Honor agreed dates. Keep future check-ins scheduled for review rather than advancing them because the row looks old.
- Verify booking outcomes. Move confirmed appointments into preparation. Investigate unknown outcomes instead of guessing.
- Review the remaining quiet conversations. Decide whether there is a relevant next step, whether the channel permits it and whether to leave the next move to the prospect.
- Record the result. Update the action, owner and next review date. Close the record when there is no further task.
Use two working queues
Reply queue: people waiting for an answer or a promised item from you. Review queue: conversations requiring a decision about timing, booking, context or an appropriate follow-up. Keeping these separate prevents a chronological inbox from becoming your only prioritization rule.
When should you follow up?
Use the conversation and any agreement as your starting point. This template does not prescribe universal day-one, day-three or day-seven messages. A promised check-in, an unanswered practical question and a refusal require different treatment. A date in your tracker never creates permission to send.
Why can you set a reminder but still be unable to send a DM?
A reminder schedules your work; it does not determine message eligibility. This matters when a tool can remind you to revisit a conversation after its API-based sending window has closed.
| Capability | What it means |
|---|---|
| Follow-up reminder | A prompt for a person to review a conversation. No message needs to be sent. |
| Scheduled DM | A prepared message set for later delivery in a supported sending environment. Its own conditions still apply. |
| Automated follow-up | A system sends a message when its triggers and conditions are met. Rules vary with the integration and message type. |
Manychat’s Inbox documentation explicitly says that a reminder can be set more than 24 hours ahead while the chance to engage may be lost. Its Smart Delay documentation also says a delay does not reopen the 24-hour messaging window.
Sources: Manychat Inbox reminders and Smart Delay and message deliverability, reviewed October 16, 2026.
The Human Agent extension described by Manychat is for human support situations that cannot be resolved in the standard window. Do not treat it as authorization for a promotional drip sequence. These are documented conditions of that messaging environment, not a claim that every message sent directly in the Instagram app follows the same technical path.
Source: Manychat’s explanation of the Human Agent window.
Instagram also documents native message scheduling. Therefore, “Instagram cannot schedule messages” would be too broad. Native scheduling, an internal work reminder and a third-party API automation should be checked separately.
Source: Instagram Help Center: schedule a message in a chat.
Can EKO replace parts of your manual Instagram tracker?
EKO is one option for making tracked conversations and follow-up priorities visible inside Instagram Web. Its documentation describes a Chrome extension, pipeline stages and a Radar follow-up board. Optional AI Notes can help recover context. You still review the conversation and send the message yourself.
| Part of the method | What EKO documents, and what to keep checking |
|---|---|
| See prospects by stage | EKO documents a pipeline with stages such as Cold, Warm, Call Booked and Closed. Our template labels are a separate proposed system. |
| Spot conversations to review | The Radar board highlights conversation age. Check the latest messages and any agreed date before acting. |
| Recover the context | AI Notes are a documented feature. Verify a summary against the original exchange, especially promises and objections. |
| Confirm the booking | The documentation reviewed does not establish calendar reconciliation for this workflow. Check the reservation in your booking system. |
| Import this CSV or recreate every field | We have not confirmed CSV import or support for every template field. Do not assume this is an EKO import file. |
| Stop all follow-up | Declined contacts still need to be handled in every tool where work or messages are queued. This page does not establish an automatic cross-tool stop function. |
Source: EKO’s public product presentation and extension listing, checked October 16, 2026. This is a capability comparison, not a claim that we configured the template inside an EKO account.
Explore EKO’s Instagram tracking workflow
EKO’s documented setup is desktop Chrome, with French product and support positioning. For its plan details, AI limits and suitability for English-speaking users, read our EKO Instagram CRM review. This guide focuses on how to organize the work.
How to tell whether the tracker is helping
Review a consistent set of open conversations and look for concrete operational changes. Useful measures include:
- Open records without an owner: tasks that may be left to somebody else.
- Open records without a next action: conversations whose purpose is unclear.
- Overdue review dates: work not yet reviewed, not necessarily messages that should have been sent.
- Unanswered prospect questions: situations where the next move belongs to you.
- Confirmed bookings still receiving booking nudges: records or queues that need correction.
These observations help assess the workflow. They do not prove that a tracker increases conversion or recovers a particular amount of revenue. Keep booked calls, attended calls and paid clients as separate outcomes when you measure sales.
Instagram DM tracking questions
Is this an Instagram message-tracking app?
No. It is a downloadable manual CSV template and an operating guide. It does not monitor an inbox, access another person’s messages or create an Instagram integration.
Can I use it without a paid CRM?
Yes. Open the CSV in your spreadsheet app and maintain it manually. If keeping the records current becomes difficult, compare a conversation-tracking tool against the specific work you want to reduce.
What is the difference between a reply and a follow-up?
A reply answers a message or request waiting on you. A follow-up resumes a conversation after your previous contribution. Review the content before deciding which action the situation requires.
Does a booking-link click mean the call is booked?
No. Confirm the reservation in the calendar or booking system. Until then, the booking outcome remains unknown.
What should happen when a lead says “not now”?
Distinguish a request for a specific later check-in from a refusal of further outreach. Record what was actually agreed. Do not silently convert “not now” into an indefinite follow-up sequence.
Can I import the template into EKO?
CSV import into EKO has not been confirmed in the public documentation we reviewed. The file is for manual tracking and is not presented as an EKO-compatible import format.
Can I set a reminder outside an automated messaging window?
A tool may let you schedule an internal reminder even when a later automated send is not permitted. Check the sending environment separately. A reminder date does not reopen a messaging window.
Method and sources
We designed the field structure and six fictional records to illustrate the decisions in this guide. They are not customer results or an implementation test. Product capabilities and messaging distinctions were checked against official provider material on October 16, 2026.
- EKO official website: pipeline, Radar, AI Notes and manual sending.
- Official EKO Chrome Web Store listing: extension environment and published functionality.
- Manychat Inbox: reminders, ownership and sending conditions.
- Manychat Smart Delay: delays and the messaging window.
- Manychat Human Agent documentation: human support conditions beyond the standard window.
- Instagram Help Center: native message scheduling.
Start with your own records: download the blank tracker, read the six worked examples, or explore EKO if you want to assess an in-browser tracking tool.