Sales training content governance: protecting price and promises

Short answer

Price and promise statements in a training scenario go straight into real conversations: whatever the employee learns as the "right answer" in practice, they say to customers. So these statements should be managed as approved content, not ordinary text. Four rules are enough: sensitive statements are kept in a separate list, each has an owner and a date, changes happen only with approval, and profiles, standards and the knowledge base are updated from the same source.

This article sets out six types of sensitive statement, a simple approval flow, a change log and typical mistakes. The aim is not bureaucracy — it is to stop practice teaching employees the wrong words for real customers.

Why price and promises are managed separately

Much of a practice scenario — the customer's behaviour, tone, the form of the objection — can be approximate, and that is fine. But figures and promises must be exact. If an old price, a discount that no longer exists or an unsupported result promise is marked as a "good answer" in practice, the employee makes it a habit. On a real call it then causes complaints, returns or legal risk.

How wrong promises are detected in real conversations is a separate topic: unverified promises in sales calls. In training the aim is to close off their source.

Six types of sensitive statement

1. 1PriceList price, bundle price, the price of add-on services.
2. 2Discounts and termsDiscount limits, campaign terms, payment options, instalments.
3. 3TimescalesDelivery, installation, response time, service levels.
4. 4Warranty and returnsWarranty period, exceptions, return policy.
5. 5Result claimsLines such as "your sales will grow" or "your costs will fall" — usually forbidden, or only with evidence.
6. 6Regulated claimsFinancial, insurance, medical or legal statements — subject to sector rules.

Four rules

• One source: sensitive statements live in one document — a separate section of the knowledge base. Profiles and standards refer to it rather than repeating the figure.
• An owner: each type has an owner — sales or finance for price, product or legal for warranty.
• A date: the date each statement took effect and was last checked.
• Approval: a change does not reach profiles and standards without the owner's approval.

What one line of the list looks like

The line below is illustrative. The same fields are filled in for each statement in the list:

• Statement: "Installation is free".
• Type: terms. Owner: head of sales.
• Condition and exception: within the city only, for the standard model; drilling through walls is charged extra.
• Date it took effect and date last checked.
• Profiles that refer to it: "price objection", "budget falls short".
• Forbidden variant: "everything is free" — without stating the exception.

A simple approval flow

1. 1Change proposalSomeone — the profile owner, sales or marketing — proposes a change: what, why, from when.
2. 2Owner approvalThe owner of that type approves or amends it.
3. 3Sector checkIn regulated sectors, compliance or legal checks the wording.
4. 4UpdateThe knowledge base is updated, then the profiles and standards that refer to it.
5. 5AnnouncementA short message to the team: what changed and from when.

A change log

One line per change is enough: date, statement, old and new value, who approved it, which profiles were updated. The log answers two questions. First, "why did an employee quote the old price last month?" — perhaps practice still used the old value then. Second, "who approved this statement?" — in a dispute, the answer is clear. Overall versioning ties in with the knowledge base and scenario updates.

Using it in evaluation

The sensitive-statement list should also feed into the evaluation standard. If an employee states an old price, an unauthorised discount or a forbidden result promise in practice, the report should flag it as a weak answer. Otherwise the employee can earn a "good" score with a wrong promise. The same applies to "better answer" examples — their figures must match the list too; this risk is explained in hallucination in simulation.

Illustrative example: the end of a campaign

This is not a real customer case. A furniture company runs a 15% summer discount, and it is written into the good-conversation standard of the "price objection" profile. The campaign ends on 1 September, but the profile is not updated. Two weeks later a customer complains that a seller promised them the campaign discount. The investigation shows the discount was typed by hand into two places in the profile, and the knowledge base had no end date for the campaign. The fix: the discount is kept in the knowledge base with a date, the profile refers to it, and a change log is started.

Common mistakes

• Writing a figure separately into several profiles.
• Not recording a campaign's end date.
• Not assigning an owner to sensitive statements.
• Changing regulated wording without compliance.
• Not flagging forbidden promises in the evaluation standard.
• Not telling the team about a change.

Regulated sectors

In sectors such as banking, insurance, healthcare, education and investment, sales statements may be restricted by consumer protection and sector rules: result guarantees, risk disclosures, mandatory information. In these sectors, prepare the sensitive-statement list with compliance and include mandatory disclosures in the practice standard. This article is not legal advice; check the specific requirements with a lawyer.

Limitations

An approval flow lowers the chance of a wrong statement entering practice, but does not fully stop the AI customer or evaluator from using a wrong figure on their own in a conversation — so spot-checks remain necessary. An overly heavy process slows updates; in a small team a simple two-person flow is enough.

In Vexvon AI Training

In Vexvon AI Training the profile's sales notes and good call script are written and edited by the company itself — that is where sensitive statements live. The product knowledge criterion checks for accurate information and no invented facts. Each evaluation keeps the rubric version it used; a change log for profile content is the company's own process.

Next step

Find every price, discount and warranty statement in your profiles and gather them into one list — with an owner and a date. For when to update scenarios see the update signals; more articles are in rollout and reliability. To build it together, contact us.