Yes, and you’ll get 7k sats (hopefully) cause it’ll cost you at least 3k to open the channel
But that will leave you with a very small channel.
You need to go bigger, otherwise you’ll barely have any inbound and outbound liquidity
Discussion
These are the two channels I have. They’re +100k channels. That gives me some wiggle room. 
So I can send another larger transaction after the initial 10k sats?
Here’s how it works. Let’s say you send 10k sats as your initial transaction, that will open a channel. The channel will have 7k sats in it once they take the 3k sats to open it. Phoenix will give you a small bump in inbound liquidity. So your channel may be able to accept something like 2k or 3k more sats.
If you now send another 10k sats, you’ll first fill the existing channel and Phoenix will open another channel with the remaining sats.
You’ll end up will one full channel (no more inbound liquidity) and another channel with maybe 5k sats in it.
What you need is to avoid the need to keep opening channels because that’s a waste of your sats.
I would do it this way. Let’s say you want to have 100k inbound liquidity.
Send 200k sats yo Phoenix as your initial transaction. That will open a much a bigger channel with 197k sats. Then from Phoenix send 97k sats back to a different wallet.
You’ll have an open channel in Phoenix with 100k sats and around 100k sats of inbound liquidity.
Does this make sense?
Yes , yes it does
As you fill your inbound liquidity over time, you’ll need to send sats out of Phoenix to leave room for more incoming transactions.
Lightning is tricky this way. We don’t see these things wil WoS or Alby because they manage these issues.
But Phoenix is much closer to how an actual Lightning node works. It forces you to manage your own liquidity.
I like it. Always learning.
Ok, so I have to take the difference into consideration for spill over in sats. Noted🫡