When it acts
- When it detects an error in your API
- When someone on your team decides to from the inbox
Connect GitHub and answer "is this a bug on your side?"
When Intake sees that a problem needs someone technical, it creates a GitHub issue with the conversation history, the account’s plan and the steps it has already tried.
What it solves
"Is this a bug on your side?", answered with facts
When a customer reports something odd, a clear answer usually takes hours: someone has to check whether it’s already reported, already fixed and in which release. The agent checks issues and releases before replying, so the first answer already says whether it’s a known bug and when the fix is due.
What it solves
Engineering stops being the middleman
Most of what support sends to engineering is about checking something, not fixing it: seeing whether the customer’s error matches an open one. The agent does that. What reaches a developer is what needs a developer, and it arrives with the version, the error message and the related issue.
What it solves
The update arrives when it’s fixed
Few things annoy a customer more than finding out on their own that their bug was fixed three weeks ago. With GitHub connected, the agent knows when the issue linked to that conversation is closed and can tell whoever reported it, without anyone having to remember.
What it does
What the connection gives the agent and what it does with it
What counts in an integration is what it lets the agent do. This is the data GitHub brings and what the agent does with it on its own.
What it can do
- Create a GitHub issue
- Link the conversation to an existing issue
- Notify you when the issue is closed
How GitHub helps the AI agent
Three concrete things that change your team’s day.
Issues with the full picture
Developers see in GitHub which user has the problem and what Intake tried, with no back-and-forth.
Priorities backed by data
Intake counts repeated complaints so you know which bug affects the most customers.
The customer hears about the fix
When the issue is resolved, Intake can let the customer know in the same support conversation.
How it works
Three steps, and only the first needs a GitHub admin. You can change the rest later without reconnecting anything.
Authorize the connection
Open the integrations panel, pick GitHub and authorize access with the account your team already uses. You need admin rights in GitHub, so if you don’t have them, this is the only step you’ll have to ask someone for.
Choose what the agent sees
Select the channels, events and account fields it can access. Anything you don’t select stays hidden from it, and you can change it anytime without reconnecting.
The agent answers with that data
From the first conversation, the agent checks that data before replying, resolves what it can close on its own and hands the rest to a person, with the case already prepared.
Frequently asked questions
How long does it take to connect GitHub?
A few minutes. You authorize access and choose what it can see; nothing needs rewriting and no development work is needed to start.
Can I revoke access later?
Yes, from either side: by revoking the connection in Intake or removing the permission in GitHub. The agent stops reading that data right away and keeps answering with everything else.
Does using GitHub cost extra?
No. Every integration is included in the plan, from €49 a month. There are no add-ons to buy and no per-call charges.
What happens if GitHub stops responding?
The agent answers with what it does have and, if the question depended on that data, hands the conversation to a person and explains why. It never makes up data it couldn’t look up.
Are issues created automatically?
You decide. Intake can create them automatically for certain API errors, or wait for someone on the support team to click a button.
Does the customer hear about status changes?
Yes. Intake keeps the conversation open and can notify the customer when the issue moves to "Done".
