The current Smart ACR documentation is confusing because the introductory description does not accurately reflect how the feature actually behaves.

The article begins by stating:

"Smart ACR determines when to play a recording announcement based on the area code and number dialed."

Based on that wording, many administrators will assume Smart ACR is primarily a notification or announcement feature.

However, later in the same article, the documentation states:

"Calls to locations where one-party notification is required: Smart ACR will automatically record these calls."

and

"Calls to locations where two-party notification is required: These calls will not be recorded automatically..."

Those statements show that Smart ACR is doing much more than determining when to play an announcement. It is actively determining whether Automatic Call Recording will occur at all.

I raised a support case after observing behavior that did not match my initial understanding of the feature. Through both testing and discussions with support, it was confirmed that Smart ACR controls recording behavior based on the destination's consent requirements.

What makes this especially confusing is that the opening description focuses on announcements when, in practice:

Calls to one-party consent jurisdictions are automatically recorded.
Calls to two-party consent jurisdictions are not automatically recorded.

This means Smart ACR is primarily making recording decisions, not simply announcement decisions.

Suggestion: Update the introductory description to clearly state that Smart ACR determines whether Automatic Call Recording can be initiated based on RingCentral's consent-law classification of the destination being called.

Something like:

"Smart ACR determines whether Automatic Call Recording can be started based on the consent requirements associated with the destination number and manages recording notifications accordingly."