To answer support tickets from code without a developer, put the ticket's question to Claude with the Everyone profile, then read the status of the answer before you write to the customer. A Verified answer can be repeated. Backend only, Not found and Inconclusive each call for a different move, and not all of them end with a developer.
This walk-through is for support leads and agents, with a section for customer success. It follows one ticket from the moment it lands to the reply. The tool is DeployIt, an MCP server that answers questions about your product from your repositories; the method holds for any ticket whose answer is a rule written in the code.
The ticket: “my IBAN is valid and your form refuses it”
An invented ticket, to carry the method. A customer writes on a Tuesday morning: sign-up stops at the payment step with “Invalid IBAN”. They have checked the number three times, and they attach a screenshot.
The agent knows two things. The message is real, and the help article on payments does not mention it. The usual sequel is a message to a developer and a holding reply to the customer. Here is the other route.
How do you answer support tickets from code, step by step?
1. Turn the ticket into a question about the product
The code holds the rule, not this customer's account. So ask what the product does, in plain words, the way you would ask a colleague: when does the sign-up form show this message?
Leave the customer's name and IBAN out of the question. The answer does not depend on them, and every question is logged under your name in your company's log.
2. Ask Claude
Why do some customers get “Invalid IBAN” when they sign up?
The form rejects an IBAN from a country that isn't accepted for direct debit.
It shows the same message when the check digits are wrong, so the customer can't tell which of the two is blocking them.
Behind the question, DeployIt investigates in the code before it answers. A first investigation takes 20 to 60 seconds. The same question, asked again in the same words and without context, comes back at once as long as the code has not changed.
3. Read the status before the answer
Every answer about the code carries a status, and the status tells you whether you can repeat it. This one is Verified: the rule was confirmed in the code. The line beside it says what was consulted, and that no line of code was shown.
That is the Everyone profile at work. The answer is prose: a filter removes the code, the file paths and the names of team members it recognises. No filter is infallible, and a leak test tells your administrators what still gets through.
4. Reply, then pass on what you learned
One more question settles which of the two causes applies: “Which countries does the sign-up form accept for direct debit?” In this example it also comes back Verified, and the country code at the start of the customer's IBAN is not on the list. The reply, as an example:
Our form shows “Invalid IBAN” in two cases: when the check digits do not match, and when the IBAN's country is not one we accept for direct debit. Yours is the second case: its country is not on our list, which is…
The ticket closes without a developer. One thing remains. A single message covers two causes, and the customer cannot tell them apart: that is a finding for the product team, sent with the answer and its status.
What do you do with each status?
The IBAN ticket landed on the comfortable case. The three other statuses turn up too, and the reply changes each time. All four are defined in Reading an answer.
Verified: repeat it. Confirmed in the code. Say it to the customer in your own words. It is the only status that counts as a fact.
Backend only: don't send the customer looking for a button. The product can do it, but no screen leads there. Example: “Can a customer change the IBAN used for their direct debit?” comes back Backend only. The agent does not write “go to your settings”: they write that the change cannot be made from the interface, and ask internally whether someone can make it for the customer.
Not found: say “we don't believe so”, not “no”. The investigation searched without finding: the feature is most likely absent from the product, and that is not proof. Example: “Can the first invoice be paid by card instead of direct debit?” comes back Not found. Tell the customer the product does not appear to offer it; if they show you a screen that says otherwise, escalate.
Inconclusive: don't repeat it as a fact. The investigation didn't get there. Ask again “in depth” if your profile allows it. If it still does not conclude, escalate the question with its status: the developer knows what has already been asked.
A refusal is a fifth case, and it is not a status. The topic is one your company has put off-limits, or a question cap is reached: DeployIt says so plainly to Claude, which passes it on to you.
Which tickets still go to a developer?
Fewer, and better framed. Three kinds remain.
A bug. The answer is Verified and the behaviour is wrong: the code does what the answer says, and it should not. The escalation fits in one sentence, with the answer attached.
One customer's data. The code holds the rule. What is stored for this account is not in the repository: it is in your back office, or with whoever can look there.
A decision. An exception, a refund, a date. No reading of the code contains them.
A fourth kind looks like a developer question and often is not: “did this change recently?” Ask Claude what changed. DeployIt lists what landed on the tracked branch over the period you choose (1 to 90 days, 14 by default), grouped into deliveries, with no person's name. The method is in what changed in the product this week, and the sorting of what reaches developers in how to reduce developer interruptions from support.
Customer success: which questions does a CSM settle from the code before a renewal call?
A renewal call goes wrong on a detail nobody checked. A customer success manager with the Everyone profile checks it the day before, and reads the statuses the same way. Four example questions:
- “What happens to a discount code at renewal?” In the example shown on our home page, the answer is Verified: the code applies to the first subscription period only, the plan price comes back at renewal, and nothing tells the customer before the charge. Better said on the call than found on the invoice.
- “What happens when a payment fails twice?”
- “What limits does our Standard plan put on exports?”
- “What changed in billing since our last call?”
The rule for the call is the rule for the ticket. Verified goes in as a fact; Backend only, as “the product can do it, but not from the interface”; Not found, as “I don't believe so, I will confirm”. An Inconclusive answer stays out of the call until someone has settled it.
Sales teams ask the same questions one step earlier, before a promise: see sales questions answered from the code.
What DeployIt does here
DeployIt is an MCP server. Your company gets one link, https://mcp.deployit.ai/<company>/<code>; each person adds it to Claude (on the web, on the desktop or in Claude Code) and signs up with a name and an email, which is not verified; their questions are logged under that name. Everyone starts with the Everyone profile: questions about the product, answered from the code; a filter removes the code, the file paths and the names of team members it recognises from the answers, without proving their absence, and a leak test tells you what still gets through. An administrator gives the Developers profile (excerpts) or the Leadership profile (developer statistics) to whoever needs it. Repositories are connected from GitHub or GitLab; DeployIt makes no commit, branch or pull request, and only adds one webhook per repository.
The full description, profile by profile, is in DeployIt: ask your code and follow each developer's work from Claude.
Next step: take a ticket you closed last week with a developer's help. Add the demo address below to your Claude connectors to see what an answer and its status look like, then connect one repository, add your company link to Claude in three steps and ask that ticket's question.
Price. Free plan: 15 questions a week for the whole company. A 30-day trial, no card. Plans from €290 a month excluding tax for up to 25 tracked developers: see pricing.
Ask your code from Claude
30-day trial, no card. Or try the demo first: add https://mcp.deployit.ai/demo to your Claude connectors.
Frequently asked questions
Can a support agent answer a ticket from the code without reading code?
Yes. With the Everyone profile of DeployIt, the agent asks the question in Claude in plain language and gets an answer in prose, drawn from the code. A filter removes the code, the file paths and the names of team members it recognises. No filter is infallible, which is why a leak test tells administrators what still gets through.
What do the statuses Verified, Backend only, Not found and Inconclusive mean?
Verified: confirmed in the code, you can repeat it. Backend only: the product can do it, but no screen leads there. Not found: searched for without being found, most likely absent from the product, which is not proof. Inconclusive: the investigation did not get there, so do not repeat it as a fact.
When should a support ticket still be escalated to a developer?
When the answer is still Inconclusive after a second attempt, when a Not found contradicts what the customer shows you, or when the ticket describes a bug or asks for a decision. The code says what the product does. It does not say what is stored in one customer account, nor what your company will decide.
How long does it take to get an answer from the code?
A first investigation takes 20 to 60 seconds. The same question, asked again in the same words and without context, comes back at once as long as the code has not changed. The wait is limited to one minute: past that, the investigation carries on in the background and you ask the same question again a little later.
How many questions can a support team ask?
On the free plan, the whole company has 15 questions about the code a week, and an answer already known does not count. On a plan, questions are included within a fair-use limit shown in your workspace. The Everyone profile is capped by default at 40 questions per person per month, a setting an administrator can change.
Continue reading
Does our product support this? Pre-sales technical questions, answered from the code
For salespeople, pre-sales and sales leaders: before saying yes to a prospect, ask Claude what the product really does, and let the status of the answer set what you may promise.
How to ask questions about your codebase in Claude before you ask an engineer
For support and product teams: most of the questions you send a developer have their answer in the code. How to ask Claude instead, and how to tell which ones still need a person.
How do you reduce developer interruptions from support?
For support leads, and the CTO whose developers they message: the questions that escalate fall into four cases. Documentation fixes one; for the one that comes back after every release, support asks Claude what the code does.