# Companion video: From enquiry to consultation

**Manuscript:** [Turn an enquiry into a tracked lead and a booked consultation](../appmint-turn-an-enquiry-into-a-project.md). **Fixture:** Cedar & Form, production organisation `learnmu4zs1td`, Jordan Morgan. **Existing media:** real browser stills and evidence ledger under `../assets/appmint-crm/`. No new video clips were recorded for this conversion.

## Story and pacing

Maya arrives through a referral; Daniel arrives through a booking. The episode shows both routes converging on one sales pipeline without creating duplicate people or pretending that a booking automatically becomes a project.

Suggested chapters: “Capture the opportunity” (7–9 minutes), “Build a bookable service” (5–6), “Book and confirm” (5–6), “Bring bookings into sales” (5–7). The Markdown is the detailed reference; do not film a slow scroll through it. Open on the two bookings and the final pipeline, then explain why there are separate records.

Opening narration: “An enquiry has a value, an appointment has a time, and the next person needs the context. We’ll put all three in the right place, then follow a second customer whose journey starts with a booking.”

## Fixture continuity

| Record | Capture value |
| --- | --- |
| Pipeline | Cedar & Form — Design Enquiries |
| Maya | maya.bennett@example.com, +12025550147, Referral,4800 |
| Daniel | d.reyes@example.com, +12025550148, Website,12500 after import review |
| Definition | design-consultation-review; Service; Active |
| Service | Design consultation;30min;0price;0break |
| Schedule | Mon–Fri09:00–17:00America/Chicago;Spots1 |
| Maya booking | 21Sep2026 10:00–10:30;reference151dce44;finalConfirmed |
| Daniel booking | Same day11:00–11:30;finalNew |
| Final lead stages | MayaContacted;DanielNew |

For new footage use future dates and record the new references. If reusing the existing fixture, search before adding records. Never film a second creation as though it were a first-run empty state. Lead, customer and reservation IDs serve different purposes.

## Shot list

| Scene | Still | Action to record | Narration focus |
| --- | --- | --- | --- |
| Outcome | 20,27 | Show two bookings, then pipeline | Appointment status and sales stage are separate |
| Navigate | 01 | CRM chevron → Leads; identify Pipeline and Lead Manager | Board versus record-finding view |
| Pipeline | 02 | Name, description, template, colour, Create | Seven stages, each with a business meaning |
| Maya enquiry | 03 | Enter name/email/phone/source/value | Potential engagement, not revenue |
| Find saved lead | 04,05 | Inspect board count, Lead Manager email search | Search before creating another record |
| Repair assignment | 06,07 | Explicit Pipeline then Stage; Update; reload | Visible default text is not enough; verify saved assignment |
| Context | 08 | Pipeline card → Activity → Note → Add Activity; wait; reopen | Context a colleague can use |
| Empty booking | 09 | Reservations → New Reservation | Definition is the prerequisite |
| Definition identity | 10 | Name,Type,Status,Title | Identifier versus service label |
| Service | 11 | Expand Services → Add item → duration/price/break | Duration and turnaround |
| Availability | 12,30 | Expand weekday choices; show timezone/hours/spots | Business timezone and capacity |
| Readback | 13 | Save, reload and reopen definition | Avoid duplicate creation after a stale list |
| Slot selection | 14 | Future weekday →10:00 | Read timezone with the time |
| Customer | 15 | Enter Maya and special requests | Lead is not automatically the same customer record |
| Review | 16 | Pause on date/time/customer →Confirm | One deliberate submission |
| Saved result | 17,18 | New card →CHANGE STATUS Confirmed →reload | Creation confirmation versus business confirmation |
| Capacity | 19 | Start another booking, same day |10:00 gone,11:00 available |
| Daniel | 20 | Book and reload11:00 | Booking-first entry route |
| Duplicate check | 21 | Search Daniel email in Lead Manager; clear search | No reliance on a checkbox alone |
| Import | 22,23 | Import Leads →From Reservations →Daniel only →Import(1) | Exclude existing leads was insufficient |
| Complete opportunity | 24,25,26 | Inspect defaults, Edit pipeline/stage/source/value/notes, reload | Import does not carry all sales context |
| Progress | 27,29 | Change Maya stage; read it back; inspect History | Verify actual card and keep a working activity note |

## Graphics and close-ups

Use a simple record map: **Lead = opportunity**, **Reservation = appointment**, **Customer = identity**. Animate an arrow labelled **manual import and review** from reservation to lead; do not imply automatic synchronisation. A second small graphic can show `work days + hours + timezone + duration + spots → offered slots`.

For field-heavy screens, keep the section title and at least one navigation landmark visible while zooming. Avoid cropping out the date or timezone on booking shots. Use the same callout number for the field being discussed across a scene, not random arrows that obscure text.

## Product issues to preserve accurately

- Global lead creation left Maya under default/unknown assignment. Edit fixed pipeline/stage; a full reload was needed to see it consistently on the board.
- Creation dropped title/notes. Edit notes persisted. Title Homeowner appears on Lead Manager but not consistently in the form or pipeline overview.
- The pipeline drawer's activity label is singular **Activity**; Lead Manager has a different detail component. Do not intercut them as a single screen.
- Activity write is asynchronous; closing/reopening too early can show the old snapshot. Record the actual wait and successful readback.
- The imported Daniel record started with Other,0value,DefaultPipeline/Unknown and no booking notes. Show review and completion.
- Existing Maya appeared in the importer despite Exclude existing leads. Select Daniel by email/name, not Select all.
- Maya's reservation persisted despite automatic SMS failures. No successful email/SMS delivery was demonstrated. Do not cut to an unrelated confirmation message.
- An automated drag intended Daniel but actually moved Maya. The final screenshot reports MayaContacted/DanielNew. Re-record a clearly targeted human stage change for the video; do not describe that screenshot as DanielContacted.
- Stage History was empty after the persisted move. Do not narrate a history entry or audit trail that is not visible.

## Remaining advanced scenes

No agreement was sent, no owner assignment was completed, no lead was marked won/converted and no project was generated. These belong in the relevant later courses. Research/enrichment controls were not exercised; no enrichment accuracy claim belongs in this episode.

Customer records for both booking emails appeared in Customers & Benefits after the bookings. Their list display used email addresses rather than a friendly full name. Capture that distinction if adding a customer-identity explanation.

Deliver source footage, edited chapters, captions, transcript, timestamps and an asset ledger. Keep screenshots in the course package; update manuscript and video together if a product fix changes any recovery step.