Batch creation, export, and retry are unavailable in the reviewed implementation. Existing schema or job-read operations do not establish a working batch runner.
Prepare the batch
Define the recipient source and authority to contact each recipient. Record the intended agent, branch, version, caller number, recipient time zone, and relevant context. Keep credential values and unrelated personal data out of batch input. Plan maximum concurrency, cancellation, retry rules, and how an uncertain provider outcome is reconciled. A repeat must not silently place a second call. Review call consent and capacity planning.Verify the released runner
Begin with a small controlled recipient set. Confirm admission, scheduling, per-call identity, result persistence, cancellation behavior, and safe export. Measure actual provider outcomes rather than treating a job identifier as a completed batch. Add an executable submission example only when the runtime and provider path are released. Preserve current availability as the boundary for integration planning.Frequently asked questions
Can I rely on a submit-job schema today?
Can I rely on a submit-job schema today?
No. The current creation path is unavailable. Schema parity is separate from provider and runner execution.