The Explicit Constraint - Providing Prices attribute lets you define rules for how the AI Employee communicates pricing information to customers. This guide explains the attribute's purpose and how to configure it.
This is configured using the project_representative_agent_providing_prices_explicit_constraint attribute.
What this attribute controls
By default, the AI Employee answers pricing questions based on the information in its knowledge base. This attribute lets you add an explicit instruction that the AI Employee follows whenever it provides pricing — for example, requiring a disclaimer that prices may vary, or redirecting customers to speak with a staff member for a final quote.
Configure the pricing disclosure constraint
In the Portal, go to Settings > Agent tab.
Locate the Explicit Constraint - Providing Prices attribute (
project_representative_agent_providing_prices_explicit_constraint).Enter the instruction you want the AI Employee to follow when providing pricing.
Click Save.
Example values
Disclaimer instruction:
Always mention that actual prices might differ whenever you provide prices.
Redirect to staff:
Never provide exact pricing. Always let the customer know that a team member will confirm the final price.
Conditional disclaimer:
When providing any pricing information, note that prices are subject to change and the customer should confirm with our team before booking.
When to use this attribute
This attribute is useful in situations where:
Your pricing is dynamic or location-dependent and exact figures may not reflect what the customer will be charged.
Your business requires staff to finalize quotes (for example, custom orders or service contracts).
Compliance or legal requirements call for a pricing disclaimer.
🗒️ NOTE
This attribute works as an instruction constraint layered on top of the agent's existing knowledge. It does not restrict the AI Employee from mentioning prices entirely — it only applies the instruction you specify whenever prices come up. If you want the AI Employee to avoid all pricing discussion, use a custom instruction or scenario instead.