Verify confirms that whoever holds a phone or inbox right now could read the code. It doesn't know if that number belongs to an existing customer, a brand-new signup, or someone trying to take over an account. That logic belongs in your own system.
The useful questions are about when to ask. Every login, or only a new device? Before a payout change, a large booking, a password reset? And what an approval opens: a verified flag on the user, a released order, a confirmed appointment written back to the system that holds it.
n-frames builds that layer around Verify: the rules that decide when a code is needed, the write-back that acts on approved results in your user or booking records, and Fraud Guard and country settings tuned to where your customers really are. For flows that ask for a code inside a phone menu or text conversation, see Twilio Studio.