xAutoDM LogoxAutoDM
    DocsReply Tracker
    Convert to calls · 7 min read

    The Reply Tracker

    Sending is the easy half. The Reply Tracker is where replies get answered, tagged, and turned into booked calls — a lightweight CRM that only ever shows conversations you started.

    What it shows

    The Reply Tracker is the inbox for a connected account, filtered down to what matters for outreach. By default it hides everything except conversations XAutoDM started, so your personal DMs and group chats stay out of the way.

    Running several accounts? Use the account switcher at the top. Each account has its own inbox and its own pipeline — they are never mixed together.

    The four pipeline stages

    New

    Where every fresh reply lands. Anything you have not triaged yet sits here — treat it as your daily to-do list.

    Interested

    They replied positively but have not committed. These are the conversations worth a considered follow-up.

    Booked

    A call is on the calendar. This is the number the whole system exists to move, and it feeds your analytics.

    Not interested

    A clear no. Marking this also adds them to your Do-Not-Contact list so no future campaign reaches them again.

    Not interested does real work
    It is not just a label. Marking someone Not interested adds them to your Do-Not-Contact list, so every future campaign — including Live triggers — skips them automatically. Use it rather than just deleting the thread.

    Notes

    Each conversation takes a private note. Use it for the thing you will not remember in a week: their timezone, the objection they raised, the date they asked you to circle back. Notes are yours alone and are never sent to the lead.

    Why the inbox is cached

    Every read from X costs a call, so XAutoDM stores your conversation list and serves it from there. Opening the Reply Tracker is free no matter how often you do it.

    Loading the list

    Served from the cache. Free, and noticeably faster than a live fetch.

    Refresh, or opening a thread

    Pulls fresh from X. This is the one that costs, so hit Refresh when you expect new replies rather than on a loop.

    The timestamp next to Refresh tells you how stale the list is. If a reply you know exists is missing, that is the button.

    A workflow that keeps up

    1

    Refresh once, then work the New filter

    Start each session with one Refresh, then filter to New. Everything else is already triaged.

    2

    Reply inline, then set a stage immediately

    Answer in the thread and tag it in the same breath. An untagged reply is one you will read twice.

    3

    Note the reason on anything not booked

    Especially the objections. Three notes saying the same thing is a signal your opening message needs rewriting.

    4

    Mark Booked the moment it is on the calendar

    This is what feeds calls booked in your analytics. Skip it and your reporting undercounts the only metric that pays.

    Follow-ups stop on their own

    You never need to pause a sequence by hand because someone answered. The send engine checks for a reply before every follow-up, and a reply halts the rest of that lead's sequence immediately. Nobody gets a "just bumping this" after they already responded.

    Turn replies into booked calls

    Every conversation your campaigns start lands in one place, ready to answer.