Give support agents product rules, not a folder of documentation.
Resolve what the product allows, what behaviour exists and which path a request belongs to before using customer-specific data.
Before touching a customer's record, an agent can ask what the product actually allows: whether a subscription in this state can be cancelled, who is recorded as allowed to do it, what has to happen next, and — if it cannot — what can be done from here instead. The answer comes from the code that runs the product, so it does not drift away from the product separately.
Connect the repository behind the product your support team answers for.
Give the support agent your MCP key.
Have it ask what the product allows for this kind of record, in this state, for this action.
Read the conditions it hands back, then act in your own support tools.
There is no support screen and no ticket integration: this is reachable only through MCP, from an agent you connect yourself. GitMir sees no customer, no account and no history — you pass a kind of record and a state, nothing more. Where the product has never written a rule, the answer says exactly that instead of inventing one.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.