Verification codes

The problem this solves

A caller claiming to be someone should not be able to trigger a refund on that person's order. Verification closes that gap without requiring your team to be on the call.

1. 1
   Request capturedThe caller asks for a refund, booking change or escalation. SIMCOAI captures the detail but actions nothing yet.
2. 2
   Code issuedA verification code is sent to the contact details already on the record — not to details the caller supplies during the call.
3. 3
   Customer confirmsThe customer provides the code. Until they do, the request stays unverified.
4. 4
   Marked verifiedThe workflow record is flagged verified. Your team sees that flag when they review it.
5. 5
   Human decidesA person reviews and decides. Verification never approves anything by itself.

What verification does not do

Verification confirms identity. It does not approve the request.