Copy pack
Build from the verified source Master Prompt and Build Contract for this voice receptionist. Preserve the no-screen call flow, transcript states, admin-only booking behavior, and staff handoff boundaries.
Master Prompt Build Contract
Master Prompt
# Master Build Prompt: DentalVoice Receptionist
Build DentalVoice Receptionist as a voice-only AI receptionist starter for a dental clinic. The actual product is phone-call based, but the starter preview should use a product-native voice call console so builders can see and test the call behavior: scenario rail, transcript turns, extracted appointment fields, outcome state, staff handoff, and a small call log. Do not build a public website, patient portal, clinic dashboard, CRM, payment screen, or medical advice app.
Product purpose:
- Answer simple clinic/admin questions inside a phone-call flow.
- Collect appointment requests with name, phone, new/returning patient status, reason for visit, preferred time, and insurance basics when safe.
- Handle unavailable times by offering alternatives or staff callback.
- Hand off to staff when the caller asks clinical, urgent, payment, complaint, uncertain, or insurance-guarantee questions.
- Keep all demo callers, phone numbers, insurance names, and appointments clearly labeled as placeholder call data.
UI style and color tokens:
- Overall tone: calm clinical operations, concise, reassuring, not marketing.
- Background: #F1F8F6.
- Primary deep green: #123B3A.
- Soft panel green: #EAF7F2.
- Surface white: #FBFEFC.
- Warm handoff accent: #F67452.
- Border: #C7DDD8.
- Text: #0D1F1F and muted #526966.
- Use the existing app sans font. Letter spacing stays normal. Buttons use compact familiar icons from lucide.
Required layout:
- Open with the DentalVoice call console as the main product surface, not a decorative scene beside it.
- Header strip: DV mark, "Voice call console", current status pill, and controls for Play next turn, Confirm appointment, Send to staff, and Reset call.
- Left rail: clickable call scenario buttons for New patient booking, Reschedule, Pain or urgent call, Insurance question, and After-hours callback.
- Center: transcript timeline with receptionist/caller/system turns. The transcript is the primary voice-product artifact.
- Right panel: extracted appointment fields, outcome card, validation/error copy, and call log.
- Copy rail outside the preview may expose only Master Prompt and Build Contract.
Required interactions:
- Selecting a scenario changes transcript, extracted fields, status, outcome, and call log.
- Play next turn advances the transcript one turn and reveals fields only after the relevant caller turn.
- Confirm appointment only succeeds for bookable scenarios after required turns are captured; otherwise it shows a clear validation state.
- Pain/urgent, insurance-uncertain, payment, complaint, and clinical questions must route to staff instead of confirming an appointment.
- Send to staff changes status to Needs staff handoff, adds a system transcript note, and writes to the call log.
- Reset call returns to the New patient booking placeholder call.
Required states:
- Listening.
- Collecting fields.
- Ready to confirm.
- Appointment confirmed.
- Needs staff handoff.
- After-hours voicemail.
- Validation error when confirm is attempted too early or on a handoff-only scenario.
Demo data shape:
- scenarioId
- transcriptTurns: role, text, summary
- callerName
- phone
- patientType
- reason
- preferredTime
- insuranceNote
- urgency
- outcome
- callLog
Non-goals:
- No visual app screen for patients, no clinic dashboard, no CRM, no marketing site, and no portal.
- No medical diagnosis, treatment advice, clinical recommendation, prescription guidance, or emergency triage.
- No payment collection, checkout, Stripe, billing workflow, insurance guarantee, EHR/EMR integration, production phone integration, PHI readiness, HIPAA/compliance claim, or fake proof that real calls were handled.
- No fabricated clinic metrics, testimonials, real patient data, real appointment confirmation, or real insurance verification.
Acceptance criteria:
- A tester can open the starter, choose a call scenario, play transcript turns, see extracted appointment fields update, confirm a safe appointment request, route unsafe/uncertain calls to staff, and reset the demo.
- The preview clearly says placeholder call data only.
- Every clickable control visibly changes state, data, transcript, validation, or outcome.
- The Master Prompt and Build Contract preserve the voice-only product scope while allowing the call console as the QA/demo surface. 