A call that's clearly a service request can be turned into a scheduled job in a few taps from the call detail page.
The Convert action
Open the call (AI-handled at /voice/[id] or human-handled at /calls/[id]). Above the transcript:
- Convert to job — opens a new-job draft with the call's caller info, address, and intent pre-filled.
You're then dropped into the regular New Job flow, where you can:
- Adjust the customer match (if the AI mis-identified the caller as an existing customer).
- Pick a property if the customer has multiple.
- Set the schedule + tech.
- Save.
The created job is linked back to the call — both pages show the relationship.
When to convert (and when not to)
| Convert | Don't convert |
|---|---|
| Caller asked for a tune-up, install, or service visit | Billing question (use Send SMS / Call back) |
| AI captured enough detail to build a job (problem, address, urgency) | Vendor or business message (use Add to followups) |
| You want the call to become billable work | Spam or wrong-number |
What pre-fills
When you tap Convert, Run a Call pulls:
| Field | Source |
|---|---|
| Caller name + phone | Customer record. |
| Address | If the caller stated it on the call. |
| Intent / problem description | Job notes. |
| Urgency | From the AI's classification → job priority. |
You can override any of these in the new-job form before saving.
What doesn't pre-fill
| Field | Why |
|---|---|
| Line items | You add these from the pricebook when the tech goes on-site. |
| Tech assignment | Left blank; dispatcher slots it. |
| Specific schedule time | Left blank; you pick. |
After the conversion
The job lands on the dispatch board. The call's transcript stays attached to the job, so the assigned tech can read what the customer originally said.