Turn a call transcript into structured CRM notes, not a wall of text

Here are my raw notes or transcript from a call with Tomas Reyes at Halifax Freight Systems: Tomas said their current dispatch process takes 3 hours a day of manual work, mentioned they're also looking at a competitor, said he'd need to check with his boss on budget, no firm next date set

Convert this into structured CRM notes using these exact fields, in this exact order — leave a field explicitly marked "not discussed" rather than guessing or leaving it blank, since a blank field looks like an oversight while "not discussed" is an honest, useful signal to whoever reads this next:

- CALL SUMMARY — two to three sentences, what actually happened on the call, not what was hoped to happen
- PAIN OR USE CASE — their stated problem, in their own words wherever possible, not a paraphrase that sounds more like a product pitch than what they actually said
- METRICS — any number, quota, or measurable outcome they mentioned, quoted directly if possible
- ECONOMIC BUYER — a named person, or "not yet identified" if nobody specific was named
- DECISION CRITERIA — what they said they'll evaluate options against, or "not discussed" if this never came up
- DECISION PROCESS OR TIMELINE — the actual steps and dates mentioned, or "not discussed" if none were given
- COMPETITION — named alternatives they mentioned, or "none mentioned" if the call gave no signal either way
- RISKS OR OPEN QUESTIONS — anything unresolved, concerning, or contradictory from the call that the next person reading this should know about before acting on the deal
- NEXT STEP — the specific committed action and date, exactly as agreed on the call — never write a next step that sounds resolved if it wasn't actually confirmed before the call ended

RULES
Do not infer a field from vague or adjacent language if it wasn't actually said directly — a prospect saying "we're pretty deliberate about these decisions" is not the same as stating an actual decision process, and writing it into the DECISION PROCESS field as if it were specific detail manufactures a false sense of qualification for whoever reads this next. Keep each field to one or two lines maximum; if a field needs more than that to capture what happened, that's usually a sign the raw notes need a follow-up call to actually clarify it, not a longer CRM note. Flag explicitly if NEXT STEP wasn't actually confirmed on the call, rather than writing one that reads as settled — a next step invented to make the notes look complete is worse for pipeline hygiene than an honestly blank one, because nobody will think to double-check something that already looks resolved.

OUTPUT FORMAT
The nine fields, in the order given, ready to paste directly into a CRM opportunity record.