FreeOpen sourceCRM and retention

second deposit: why FTDs skip the second deposit

The back office shows the second deposit rate but not the reason. The skill finds it in your exports: which first-session scenario loses players, how much Sum Dep that costs per month and which fresh FTDs you can still win back.

What it does

1

Finds the reason

Every FTD without a second deposit gets one of 12 reasons: from a cashier decline and a rejected withdrawal to a bonus with heavy wagering.

2

Counts what you miss

How many second deposits are short of the norm of similar players and how much Sum Dep that costs per month.

3

Gives a list for today

Fresh FTDs from the last 72 hours: reason, state, when to message and what to offer. One file per action for your CRM.

4

Knows the country

Legal payout deadlines, banned payment methods and deposit limits, from official sources only.

Example: a report from your exports

For each reason you see how many FTDs it loses, how far their second deposit falls below the norm and what to do. On top, the total: missed Sum Dep per month as a range, from the second deposits alone to the Sum Dep of returning players.

  • 24 metrics with definitions: second deposit within 24 hours, 72 hours, 7 and 30 days, cashier approval, withdrawals, bonuses
  • Where you lose: payment methods, countries and traffic sources where the gap is larger than chance
  • A 20% control group: after 7 days you see how much more often messaged players come back
  • Self-excluded players and players with limits stay out of both the numbers and the list
second deposit report from exports

A report on the demo data from the repository. The data is made up.

Install

Option 1. Let Claude install it

Open Claude Code and paste this text:

Prompt for Claude Code
Install the second-deposit skill from https://github.com/igamingsychov/second-deposit-igaming :
1. Clone the repository into ~/.claude/skills/second-deposit. If that folder already exists, ask me what to do.
2. Check that python3 is available.
3. Tell me when you are done and what to type to test it.

Option 2. One terminal command

Puts the skill where Claude Code looks for it:

Terminal
git clone https://github.com/igamingsychov/second-deposit-igaming.git ~/.claude/skills/second-deposit
You need Claude Code and python3. No third-party libraries or internet are needed for the calculation. To test it, type show the second-deposit skill demo in a new session and Claude will build a report on made-up data.

How to use it

Example requests

  • break down the second deposit from the exports in ~/Downloads/exports
  • why do FTDs not come back? the files are in the data folder
  • build the FTD list for today from the fresh export
  • schedule a daily second-deposit run at 9:00

What to export

At minimum: deposits for 60-120 days with every attempt, successful, declined and abandoned. Withdrawals, bonuses, bets and player data add reasons. Before the calculation the skill tells you how many of the 12 reasons your files can cover.

The repository has a sample workbook with instructions and SQL queries for your analyst.

Your data stays with you

Scripts do the math on your computer. Claude sees column names, formats and totals, but not rows with players: player lists are written to files.

License

MIT license: use it and adapt it. Author: Yevhen Sychov.