Flagship workflow demonstration
A complete synthetic lead-response journey
Follow one synthetic service inquiry from extraction and reply preparation through owner approval, assignment, activity recording, and a callback reminder.
1. Original inquiry
Hi, this is Jordan Lee. The upstairs AC at 42 Harbor View Drive stopped cooling this afternoon. You can reach me at 555-010-0198. Could someone come tomorrow morning and let me know the diagnostic-call price?
2. Details extracted
- Name: Jordan Lee
- Phone: 555-010-0198
- Email: Not provided
- Service: Residential AC diagnostic
- Location: 42 Harbor View Drive
- Urgency: Service requested for tomorrow morning
- Requested Time: Tomorrow morning
Still needed
- email address
- equipment make and model
- property access details
Confidence: 93%
3. First reply prepared
Hi Jordan — thanks for contacting us about the upstairs AC at 42 Harbor View Drive. We have your request for tomorrow morning. Before we confirm a time, could you share the equipment make and model and any access instructions? We will confirm the diagnostic-call price with the appointment.
4. Owner edit recorded
Approved With Edit
Added the approved $129 diagnostic price and clarified that the arrival window is confirmed before booking.
Approved text
Hi Jordan — thanks for contacting us about the upstairs AC at 42 Harbor View Drive. We have your request for tomorrow morning. Before we confirm a time, could you share the equipment make and model and any access instructions? Our diagnostic call is $129, and we will confirm the arrival window before booking.
5. Lead assigned
Synthetic dispatch queue
Residential HVAC request with a requested service window
Person still needed: Confirm availability and arrival window
6. Activity recorded
Status: Awaiting scheduling confirmation
- Inquiry received
- Fields extracted and validated
- Draft reviewed and edited
- Lead assigned to dispatch
7. Callback kept visible
Check for missing equipment and access details
Due: Next business day at 9:00 AM
8. Weak inquiry stops safely
Need service soon. Call me.
Manual review: No name, location, service type, or usable contact details
Technical evidence
- Report schema version:
1 - Journey identifier:
synthetic-lead-journey-001 - Input SHA-256:
b80c81a65d0b31aac695775826df445af550fac061b9ea4fd011555f3bc496ef - Internal synthetic record:
DEMO-LEAD-001 - Inspect the generated JSON report
What this demonstration does not prove
- Every person, address, phone number, price, and system record in this walkthrough is synthetic.
- The walkthrough demonstrates the proposed data and approval contract; it does not send email, update a live CRM, or create a real calendar event.
- A production build requires customer-approved reply rules, prices, integrations, test cases, permissions, and fallback procedures.
- The separate 100-scenario benchmark measures classification and review routing only.