Operating model

One onboarding.
A business-aware operator.

CHOP separates business knowledge from conversational behavior. Your team declares the facts and boundaries; the operator uses them consistently and escalates when it reaches a boundary.

Capture the business

The onboarding form collects stable operating information: identity, services, contact channels, commercial behavior and escalation rules. Flexible month-to-month promotions stay out of the permanent baseline.

Create the Business Pack

The onboarding answers are normalized into a structured business context that the Operator can consume. This keeps the runtime generic while each business remains configurable.

Handle customer intent

CHOP interprets the request, checks the declared service and commercial state, and selects the next safe action: answer, collect information, request a manual quote, mark out of scope, or escalate.

Respect transaction truth

CHOP does not turn a request into a confirmed booking, payment, discount, warranty or availability claim unless the connected business system has actually confirmed it.

Hand over with context

When a staff member or manager is needed, CHOP packages the reason, customer request and conversation context so the human can continue instead of restarting the interaction.

The Operator stays generic.
The Business Pack makes it specific.

That distinction is what lets CHOP support multiple local-business categories without hardcoding each company into the Core.