BURKI NATIVE CALLBACK CONFIRMATION WORKSHEET
Prepared October 14, 2026. Free manual worksheet, not a call or automation.
Original guide: https://burki.dev/blog/burki-callback-request-confirmation

PURPOSE
Separate caller-supplied digits, a proposed number, native confirmation and staff
follow-up. Record callback requests saves a request only. It does not call, send
a message or schedule a callback. No paid call or real request was created for
this resource. Keep expected behavior separate from actual observed evidence.

1. SETUP AND SCOPE
Review owner and date:
Organization and assistant ID:
Standalone standard / standalone GPT Live / unsupported workflow or builder:
Actual publication state/version:
Applicable transcript-retention policy permitted and verified by:
Voice, language, provider and funding prerequisites:
Actual route: text review / browser / telephone / none:
Staff owner and actual approved follow-up process:
Any independently accepted delivery action:

Current Actions control: Record callback requests.
Supports standalone standard and GPT Live with transcript retention permitted.
Workflows/builder unsupported. Confirmation recognizes explicit English
affirmations after native number readback. Do not invent a generic retention
toggle or treat audio-recording consent as transcript-retention permission.

Intentionally enable/save only in an authorized setup. For existing assistants,
read Publish -> Published version first. Unpublished needs reviewed saved settings
and appropriate authorized checks before Publish assistant. Published saved edits
remain drafts until Publish saved changes; telephone calls use the published
version. Legacy live settings means saving currently changes connected calls.
Provider/Knowledge/calendar dependencies remain live. Publishing does not verify
a phone route or follow-up result.

2. ADAPTABLE INSTRUCTIONS
Help callers using approved public business facts. Collect a callback number only
for the approved caller-requested staff follow-up. Use the native collection
action with complete caller-supplied digits and country context. Ask only for
missing/corrected details. Let native readback finish, then wait for explicit
confirmation. A corrected number requires a fresh native proposal/readback and
confirmation. Do not infer confirmation from yes elsewhere or from a model flag.
Do not say a call/message was sent or a response time accepted without an actual
confirming result. Explain the actual staff process and incomplete confirmation.

Approved business facts and real follow-up process, before use:


3. STATE REVIEW
Partial: missing/invalid/corrected number; no confirmed value established.
Proposed: complete structurally valid number normalized internationally;
native readback and confirmation still needed.
Confirmed: current revision completed uninterrupted native readback and received
the immediately following qualifying English caller affirmation.

Number validity is not subscriber identity, ownership, consent to marketing or
reachability. A confirmed request is not a completed callback or delivered message.

Event/check record (fill actual values only through an approved private process):
Caller-supplied country context:
Current proposal/revision:
Native readback completed without interruption:
Immediately following caller response:
Correction/interruption/unrelated response:
New proposal/readback required:
Actual saved callback status:
Confirmed value, if authorized to retain here:
Evidence and review time:

Do not paste real private numbers into a publicly shared copy of this worksheet.
Store actual identifiers only where approved. No retention-forever promise.

4. SYMBOLIC WORKED EXAMPLE
[original number] and [corrected number] are placeholders, not dialable values.
Do not paste them into the number action or claim they passed its parser.

Caller supplies [original number] and country context.
Native action begins proposed-number readback.
Caller interrupts and corrects the last digits.
Expected: old proposal cannot be confirmed; collect corrected/missing details.
Caller supplies [corrected number].
Native action proposes and completes uninterrupted readback of corrected value.
Immediately following caller turn: "Yes."
Expected: current corrected revision can become confirmed.
Alternative response: "Can you call tomorrow?"
Expected: no confirmation of the earlier number; fresh readback/affirmation needed.

Example is an expected-state plan. No actual call, playback or saved result exists
from this worksheet.

5. CALL REVIEW AND STAFF OUTCOME
In Calls, open the relevant review. When a native result is available, Callback
request shows Caller confirmed [number] or Incomplete - no confirmed callback
number. The UI states that no callback or message has been sent.

Actual call ID and assistant/publication:
Actual callback section/status seen:
Latest correction agrees with saved result:
Missing/processing/retention uncertainty:
Native confirmation evidence:

Separate staff record:
Assigned owner:
Actual delivery receipt, if applicable:
Actual follow-up attempt and evidence:
Actual answered/resolved outcome:
Unknowns:

An absent callback section does not establish success or explain the cause.
Do not choose a number from a transcript and call it natively confirmed.

6. EXPECTED VERSUS OBSERVED CASES
No tests were run for this guide. Write expectations before any separately
authorized test, using safe approved details/routes. Do not call unrelated people.

National digits, missing country:
Expected: ask country, do not guess.
Observed/evidence:

Interrupted readback:
Expected: no confirmation from interrupted proposal; fresh process as needed.
Observed/evidence:

Corrected final digits:
Expected: new current value gets its own readback and confirmation.
Observed/evidence:

Yes answers another question:
Expected: no retroactive number approval.
Observed/evidence:

Completed current readback followed immediately by explicit English yes:
Expected: native confirmation may be recorded for current revision only.
Observed/evidence:

Ambiguous or non-English response:
Expected: no unsupported English-recognizer confirmation claim.
Observed/evidence:

Retention blocks data:
Expected: respect policy, inspect blocker; do not use recording consent as fix.
Observed/evidence:

Saved confirmed request:
Expected: staff process still separate; no dispatched callback claim.
Observed/evidence:

7. COSTS AND NEXT ACTION
Free resource does not mean free voice/model/platform/carrier usage or future
callbacks. Check actual account allowance, provider prerequisites and
https://burki.dev/pricing. No paid test is needed merely to prepare this document.
Source/deployment/text review does not replace caller-heard or provider evidence.

Blockers:
Review decision:
Approved next action and owner:
Verified outcomes:
Unknown outcomes: