Proof hub / Tutorial sample

Explain a callback handoff flow to a non-technical operator.

Goal: when a buyer submits a demo, quote, or missed-call form, the business should know who asked for help, whether consent exists, what system owns the record, and what has to happen next.

1. Map the handoff

Start with one form, one lead owner, one CRM record, and one callback rule. The flow is: form submit, consent check, CRM upsert, owner alert, callback queue, run log.

2. Define the payload

{
  "event_id": "lead_20260522_001",
  "source": "pricing_page",
  "name": "Sample Buyer",
  "phone": "+15551234567",
  "consent_to_call": true,
  "requested_time": "next_business_hour",
  "service_interest": "after-hours support"
}

3. Set acceptance checks

  • No callback is queued when `consent_to_call` is false.
  • Duplicate `event_id` values update the same lead instead of creating repeats.
  • The owner alert includes source, service interest, and callback status.
  • The run log stores success, skipped, and failed states with timestamps.

4. Explain it to the operator

"A new lead comes in, the system checks whether we are allowed to call, updates the CRM, tells the owner, and adds the lead to a callback queue. If consent is missing or a duplicate appears, it logs the reason instead of guessing."