Map CRM fields for call summaries

A sales lead, support issue, booking request, emergency service call, and billing question usually need different fields. Do not force one universal form onto every call.

Keep the natural-language summary for context, then write key fields like service type, urgency, location, email, preferred time, and next action into structured destinations.

Decide whether calls should match existing contacts by phone, email, account name, or another identifier before creating a new record.

If a required field is missing or the CRM rejects an update, preserve the summary and alert the owner so follow-up does not disappear.