Live demo
BeginnerTry it: callback rule check lab
This is the working lab from our tutorial on writing a callback rule for payment, bank-change and code requests. Each row is one request that reached staff at the invented Ombervale Association of School Facility Managers by phone call, voice message or video call, and that seemed to come from a leader or a known contact. Choose what was asked and what staff did, and the page applies the rule.
Invented organization and requests for practice. This is a teaching example, not a case study. The lab checks only the choices made on this page. It places no call, calls no AI tool, and sends and stores nothing.
Pick a case
What each field means
| Field | Choices |
|---|---|
| Channel | Phone call, Voice message or Video call: how the request arrived |
| Ask | Payment, Bank change (a payee's bank details), Code or password, or Other |
| Callback | On file: hung up and called a number already on file. Their number: called the number the caller gave, or replied in the same thread. Not done. |
| Second approver | Yes or No: a second person approved before money or bank details moved |
| Moved | Yes or No: the caller switched to a new number, app or chat, or blamed a bad connection and moved to text |
| Pressure | None, Urgent, or Secret or skip approval |
Every field can be left blank so you can see what the rule does with a gap. A blank is never read as "No" or "None."
Requests in this case
| Row | Channel | Ask | Callback | Second approver | Moved | Pressure |
|---|
Rules, in order (first match wins)
- R1, STOP: a sign-in code or password is asked for. Never give it out, even after a callback.
- R2, STOP: a payment or bank change, and the callback went to the caller's own number or the same thread.
- R3, STOP: a payment or bank change, and the caller asked for secrecy or to skip approval.
- R4, VERIFY: a field is blank or not one of the listed values.
- R5, VERIFY: a payment or bank change, and no callback was made.
- R6, VERIFY: a payment or bank change with no second approver.
- R7, VERIFY: another kind of request, no callback on a number on file, and the caller moved channels or pushed for speed or secrecy.
- R8, PASS: everything else. The rule checks the process, not the person.
Teaching choices: the rule order, the split between STOP and VERIFY, the second approver, and extending "never share codes" to phone and video calls. The FTC and FBI guidance the tutorial cites names written channels for codes and does not say two people must approve.
Result
| Row | What happened | Channel | Ask | Callback | Second approver | Moved | Pressure | Verdict | Rule ID | Also matched | Message |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Pick a case. | |||||||||||
Not checked yet.
Plain-text record (select and copy it by hand)
Nothing checked yet.
This is a teaching tool. A PASS means the steps on this page were followed for one request. It is not proof of who was on the line, not legal advice, and not a replacement for your own approval policy.