Where they live

These are two JSON documents in your own vault. The analyzer reads them at runtime, so a change applies to the next call scored — existing analyses are not re-scored.

call-intelligence/config/scorecard-templates.json
call-intelligence/config/objection-taxonomy.json

They are created for you the first time you open the page or create a call agent, with four scorecard templates and fourteen objection tags to start from.

Editing

Use Edit on either card. Ambrose validates before saving: every id must be unique, every template needs a name and at least one question. A malformed config silently ruins a week of scoring, so a bad edit is rejected rather than stored.

The version you replace is kept beside it, so an edit that turns out wrong can be undone.

Your edits are yours. Once you change a document, it is your agency's own copy — platform updates never overwrite it.

Choosing a scorecard

The analyzer picks the template matching the call type — Medicare closing, appointment setting, ACA enrolment, or a general methodology scorecard otherwise. Add your own template for a call type you run that is not covered.

Proposed tags

When the analyzer hears an objection that fits nothing in your taxonomy, it proposes a tag rather than forcing a wrong one. Approving it adds it to the taxonomy and re-tags the affected calls.