Booking Confirmation Voice Pack: Success, Reschedule, Cancel

Problem It Solves

In store booking workflows, the hard part is not drafting one line, but turning confirmed facts into reusable spoken notifications: which store or service the guest should hear, how success, reschedule, and cancellation should be phrased, and how names, places, and services are pronounced. It must not invent times, prices, or discounts, and it must avoid voice mismatch, wrong readings, unauthorized cloning, or repeated billing.

How It Works

The skill first produces a free visible slot table before any paid synthesis. It defaults to ten slots: success, reschedule, cancellation, reminder, late arrival, no-show, waitlist, arrival, deposit, closing. Each slot records a short spoken sentence derived from confirmed facts and whether to use a catalog voice or a cloned voice. Cloning and narration are separate paid stages, each requiring a six-field confirmation card covering action, credits, charge count, client_request_id, stopped state, and low-balance handling. All remote Beatra calls go through the bundled scripts/mcp_client.py, such as beatra.assets.upload, beatra.voices.clone, beatra.speech.synthesize, and beatra.tasks.get, rather than passing local paths directly into synthesis. Text is split into short sentences, kept under 50,000 characters per submission, and audio checks the actual MIME, duration, size, and billing.net_charged_credits.

Boundaries and Caveats

It fits booking confirmation voice lines, not IVR tree menus, dated in-store promotion broadcasts, or general narration. Receiving a file is not consent; if a name exists but the pronunciation table is empty, stop and collect the reading. Before cloning, confirm an authorized sample, and do not retry paid requests because an update check failed.