Recovery point objective is a business decision wearing a technical costume. It gets set once during onboarding, usually to the platform default, and then never revisited — because the number on the screen is a frequency, and a frequency does not obviously map to anything a client would care about.
It maps to something very specific: the amount of their work that ceases to exist.
The arithmetic
Take a two-hundred-seat tenant with ordinary mail volume. Work out what an eight-hour recovery window represents in the units the client thinks in.
Halving the window halves the loss. It does not remove it.
This is the part that gets glossed over in vendor material, where a shorter interval is presented as though it approached zero risk. It does not. It approaches half.
Which makes the right cadence a per-client judgement rather than a platform default. A client whose data changes slowly is correctly served by a daily backup, and anything more is spend without benefit. A client processing transactions all afternoon is badly served by it, because the recovery is nearly as expensive as the incident.
The defaults on this platform are three backups a day for Microsoft 365 and one a day for identity, both configurable to six. The platform supports intervals down to five minutes; that is a capability statement, not a description of what is running.
Multiply their seat count by their realistic hourly message rate by your configured window. Put that number in front of them. It is a far more productive conversation than "we back up three times a day".
Recovery point is not recovery time
They get conflated constantly. Recovery point is how much you lose; recovery time is how long you are down. A platform can be excellent at one and poor at the other, and they are traded against each other in real deployments.
The reason to separate them explicitly is that clients care about them differently. Losing four hours of email is a productivity problem. Being unable to restore for two days is an existence problem. Only one of those is fixed by backing up more often.