# Reg without FTD, and payment

Instead of “no deposit — lost”, a separate pool: Registered / No FTD. These people already have high intent, and the manager's job is to find out exactly where each of them stopped.

**What you leave with:** A Reg without FTD pool in the CRM, each person's reason for stopping, a five-touch sequence and a ready payment FAQ.

## 01. Registered / No FTD is a critical segment

A person who got through registration has already done more than any new lead. If they made no deposit, the reason is nearly always specific — and it can be found.

**Instead of**

- “No deposit — lost”
- The same “So, did you deposit?” to everyone

**A separate pool**

- A stage of its own in the CRM: Registered / No FTD
- These users already have high intent
- The reason they stopped has to be found

## 02. Why people stop: eleven reasons

You cannot treat every reason with the same “So, did you deposit?”. First find out which one this person has, then solve that one.

| Reason | Where to start |
| --- | --- |
| The payment method is unavailable | Offer a method that is really available in their GEO |
| The payment was declined | Go through the error step by step; if that does not solve it, pass it to support |
| Did not understand the process | A step-by-step instruction or a short screen recording |
| Does not know what amount to choose | Explain: do not use the whole balance at once, and start with small actions |
| Doubts the product | A demo, the FAQ, the next Live |
| Doubts the person | Real reviews and cases, a live voice instead of a template |
| Got distracted | A short reminder with a specific next step |
| Wants to watch a bit longer | Bring them back to the content: a Live or a breakdown of their question |
| Has no money right now | Do not push: record the next action and a date |
| A technical issue | Collect the details and pass them to support |
| Expected a different product | Explain honestly what the product gives and what it does not |

## 03. Follow-up from Reg to FTD: five touches

Each touch does its own job: find out whether it worked, find where they stopped, remove the specific barrier, bring them back to the content, and show what opens after the FTD.

1. **Touch 1** — “Did you manage to register?”
2. **Touch 2** — “Where did you stop?”
3. **Touch 3** — Solve the specific barrier.
4. **Touch 4** — Bring them back to the content: “There's a Live on exactly this today”.
5. **Touch 5** — Show the value: “After the FTD you'll get X, Y and Z”.

Adapt how often you get in touch to the GEO, the source and how the user responds.

**01. Touch 1**

> **Manager:** Hi! Did you manage to register?

> **User:** Yes, the account's there

**02. Touch 2**

> **Manager:** Great. Where did you stop?

> **User:** Tried to top up, the card didn't go through

**03. Touch 3**

> **Manager:** Got it. For your country another method usually works better — here's a two-minute instruction. If there's an error again, send me a screenshot.

_The next day_

**04. Touch 4**

> **Manager:** At 19:00 today there's a Live on exactly the first steps after registration — you can ask your question on air.

_Two days later_

**05. Touch 5**

> **Manager:** After the FTD you'll get the VIP breakdowns, the beginners' course and personal support. If any payment questions are left, I'm here.

## 04. Payment is a bottleneck of its own

A bad situation: the user is ready for the FTD, but the manager does not know how to help. That is why the payment FAQ is prepared in advance — around five questions.

- [ ] Which methods are really available
- [ ] Which method people use most
- [ ] Where errors happen
- [ ] What the steps are for each method
- [ ] Where support escalation is needed

---

[Back to the programme](https://gamechange.partners/en/academy/conversion/)
