Disconnect Calls After Forwarding to External Number

I find this question surprising. 
Calls should be disconnected once they’ve been transferred to an external number - regardless if automatic call recording is enabled or not.

Are you saying you have recordings in your call log, after 1 external caller has been transferred to another external destination?

Example scenario:
A - external caller
B - user on RC
C - external destination

A calls B  (call recorded)
B transfers A to C (this part shouldn’t be recorded. are you saying it is?)

Basically yes. Customer calls into our RC line, chooses extension 201 (or any extension as they all forward to 201). ALL calls for extension 201 get forwarded to an external number. The entire call to the external number has been recorded in RC. 

So not only are we being charged extra to forward calls (which is ridiculous to me), we are then using up minutes because it’s not disconnecting. 

Ideally I just want all calls to our main/toll-free number to forward to a local number with a different provider. But that seems impossible...

I was able to reproduce this on my end and did some digging. I couldn’t find an RC article talking about the billing side of call forwarding, but I did find a verizon article(They are RC partners btw):
“..you'll be billed for all forwarded calls according to your plan. You'll be billed just like you would if you answered the call...”
I am thinking this could be an industry standard - maybe somebody from RC can confirm. 

I would rephrase your question like this:
“How are incoming calls to a Toll-Free number which are then forwarded to an external number billed?”
If we go back to our example:
A calls B(toll-free)
B forwards A to C
Which party is getting charged for the call? It seems like it’s B. 

Why would it keep recording? Isn’t there a requirement to explain the call is recorded once the transfer is complete? How is Ring Central in compliance with that in these cases? 

Sorry to bump an old thread but it seems the OPs question was never answered and the issue persists. 
I too would like to disconnect the call at the point of transfer. 

Thanks,
Brian

So every phone system I have ever administered for the past 30 years has worked this way.  When a caller dials a number you own the carrier hands the cal off to RingCentral’s carrier which passes the call to your specific tenant. once your tenant receives the call you now have call control.  Whether you transfer or forward that call to an external number your Ring Central system still has the call flowing through it.  A call is passing through you for the entire call.  In the past, Old Avaya on-prem system with Lumen as our carrier, the only way to keep a caller from passing through my Avaya was to go onto the Lumen portal and forward the call at the carrier level.  This action is handled at the carrier level so the caller is never presented or answered by the Avaya system. The caller never flows through the Avaya so there is no call control at our end.  I have not seen a method of accessing Ring Centrals carrier to place the forward rule at the carrier level.  I will defer to any RingCentral moderator to weigh in on the carrier level forwarding feature.

This may not help with the cost of double legging a call but I hope it explains the process in which calls are routed.