INWORLD FIRST-TOKEN FALLBACK PLANNING WORKSHEET
Free resource. Reviewed October 20, 2026. No provider requests or tests performed.
This document does not configure Burki or a provider. Production usage costs extra.

1. READER TASK
Approved answer task: __________________________
Facts owner and last review date: __________________________
Actions excluded: __________________________
Expected fallback behavior when facts are insufficient: __________________

2. CONFIGURATION INVENTORY
API format and current documentation URL: __________________
Primary exact catalog ID: __________________
Fallback exact catalog ID(s), in order: __________________
Account access and request compatibility reviewer: __________________
Chosen first-token deadline and rationale: __________________
Original request/prompt version: __________________
Credential owner and server storage reference (never the secret): __________
Current raw-provider versus native application support: __________________

3. COMPLETE WAIT BUDGET
Primary wait allowance: ____
Replacement first-token allowance: ____
Transport allowance: ____
Speech generation allowance: ____
Caller-channel delivery allowance: ____
Total acceptable wait and who approved it: ____
Keep unavailable measurements blank. A provider timestamp is not heard audio.

4. FICTIONAL FACT FIXTURE
Lark Studio reception: Monday-Friday, 09:00-17:00, closed public holidays.
No appointment inventory is supplied.
Question: Can I visit reception at noon on a public holiday?
Expected meaning: Reception closed; no appointment or exception invented.
Question: Is a member of staff available for a private visit at 18:00?
Expected meaning: Facts insufficient; staff must confirm; no visit arranged.
Do not use real customer data or external actions to fill this worksheet.

5. PROPOSED CASES, NOT RESULTS
Primary within budget: answer supported? replacement unnecessary? __________
Primary misses deadline: attempt distinguishable? replacement correct? ____
Replacement unavailable: approved unavailable response? __________________
Unstated exception: invented availability or callback? ____________________
Fallback more confident: supported by facts? _____________________________
Future tool-enabled scope: independent action outcome/retry review? _______

6. RECEIPT ROW (COPY FOR EACH FUTURE AUTHORIZED ATTEMPT)
Recording/request fixture ID: ____   Prompt version: ____
Exact model and settings: ____   Date/time and geography: ____
Request sent: ____   First text received: ____
First audio generated: ____   First audio heard: ____
Attempt metadata source/file: ____   Final outcome: ____
Returned words: ____   Reviewer rationale: ____
Accepted / failed / unknown: ____   Next correction: ____

7. COST RECORD
Pricing date/account terms: ____
For every attempt: input tokens ____ output tokens ____ cache treatment ____
Attempted-request billing verified from: ____
Recognition ____ synthesis ____ carrier/number ____ platform ____ other ____
Total units and estimate: ____   Unresolved charges: ____
Do not record a failed attempt as free without evidence.

8. DECISION
Configuration-only / simulated / deployed / provider-accepted: ___________
Evidence missing before publication or use: _____________________________
Reviewer and decision date: _____________________________

Primary references, checked October 20, 2026:
https://docs.inworld.ai/router/capabilities/request-level
https://docs.inworld.ai/router/quickstart
https://inworld.ai/models
https://inworld.ai/pricing
Original guide: https://burki.dev/blog/inworld-inference-first-token-fallback