Belongivity  |  FGFunnels Training
Module 4: Conversations and Follow-Up
Prepared by Emile  ·  May 2026

Dr. Tonya,

The contacts who feel most cared for are the ones whose consultant never lost the thread. This module is about how to make sure you never do.

By the end, you will know how to use the Conversations Hub once Gmail is connected, how to read a thread and identify who needs a reply, how to reply from inside the platform instead of from Gmail, and how to build a daily rhythm that keeps the whole system current without taking more than a few minutes each morning.


1. How the Hub Works Right Now

Before Gmail is connected

The Conversations Hub is live in your account now. At this stage it will show messages sent from inside the platform - automated emails from your workflows, for example. It may look quiet. That is expected. The hub is waiting for activity to populate it.

The Gmail connection is the next piece of infrastructure to set up. Once it is in place, the hub becomes the central view for all communication with your contacts.

What changes when Gmail is connected

Once your Gmail is wired to FGFunnels, every email you send or receive from a contact appears in their thread automatically. You do not configure anything per contact. It works in the background across all your conversations.

The result is a single chronological record of everything between you and a given person. Your sent emails, their replies, messages from inside the platform - all in one place, in order. Before you respond to anyone, you can see exactly what was last said and when. That is the view that makes follow-up clean.


2. Reading a Thread

How to open one

In the left menu, click "Conversations." The left side of the screen shows your active conversation list. Click any contact name to open their thread on the right.

You can also reach a thread directly from a contact record. Open the contact, look for the conversation icon or Messages tab on their page, and click it. This takes you straight to your thread with that one person.

What you are looking at

The thread reads top to bottom, oldest message at the top, newest at the bottom. Each entry shows the message, the channel it came through, and the date. Your outgoing messages and their incoming messages are visually distinct so you can follow the back-and-forth.

What to look for

Find the most recent message. Who sent it? If the last message in the thread is from the contact and you have not replied, that thread is waiting on you. If the date on their message is more than a day or two old, it has been waiting long enough.

📷 Screenshot: Conversations Hub with an open thread Click "Conversations" in the left menu. Open a contact thread. Capture the full view showing the conversation list on the left and the message thread on the right.

3. Replying from the Hub

How to reply

At the bottom of the thread panel, there is a compose area. Type your message there and send. The reply goes to the contact and is recorded in the thread immediately.

Why to reply here and not from Gmail

This is important. When you reply to someone from Gmail directly, that message does not appear in the FGFunnels thread. The record breaks. From that point on, the thread is incomplete - and the next time you open it before a call or meeting, you are working from a partial picture.

Replying from inside the platform is what keeps the history whole. This will feel like a change from your current routine. It becomes automatic quickly, and the payoff is that you always have the full picture before any conversation.

One place to read. One place to reply. That discipline is the whole thing. The moment you start mixing it with direct Gmail replies, the thread breaks and the system loses its value.
📷 Screenshot: Reply compose area In an open thread, capture the compose area at the bottom of the thread panel. Show the text input field and the send button.

4. The Daily Follow-Up Routine

The problem this solves

You are running three kinds of work across many relationships at different stages. The thing that erodes trust fastest is not bad intentions. It is losing track. A reply that comes three weeks late. A contact you meant to check in with after their event. A proposal sitting unanswered because you forgot to follow up.

The system you have built is designed to prevent all of that. But only if you check it. Here is the routine that makes it work.

The morning check - three minutes

Step 1  —  Conversations Hub Open the hub. Scan for any thread where the last message is from the contact and has been sitting for more than a day. Those are today's replies. Handle them before anything else.

Step 2  —  Pipeline Board Open Opportunities. Scan for any card that has not moved in longer than the stage should take. A contact sitting in Discovery Call Booked for two weeks without a completed call needs a follow-up or a decision. Move the card or make contact - do not let it sit.

Step 3  —  Contacts Sort by Last Contact Date. Anyone you have not touched in a while - check their Next Action field. If there is a next step listed and today is close to the right time, do it or schedule it. If the Next Action field is blank, add one now.

That is the whole routine. Hub, pipeline, contacts. Three steps, three minutes. Nothing falls through a crack.

📷 Screenshot: Contacts sorted by Last Contact Date In the Contacts view, sort the list by "Last Contact Date" to show the contacts you have not been in touch with recently at the top. Capture the sorted list.

You Are Ready

That is the core training. You know how to navigate the platform, manage your contacts with precision, keep your pipelines current, and run the daily rhythm that holds it all together.

The best next step is to use it. Log in tomorrow morning and run the daily routine for the first time. The first morning will take longer. The second will be faster. By the end of the first week it will feel like second nature.

When questions come up - and they will - write them down as you go. We will address them as the next phase of the work unfolds.

Emile

← Module 3: Working the Pipeline ↩ All Modules