A bug reporting widget that keeps the customer in the conversation
chatwithdev lets visitors report a problem directly on your website. Read and reply in Telegram or the dashboard, turn the conversation into a ticket, and follow up after you have checked the fix on the live site.
Try the same chat you'll add to your site.
We use chatwithdev for our own support. Send a question here and read the reply in the widget. This opens a real conversation with us.
Replies may take a little time. You can leave an email in the chat for follow-up.
Collect the report where the problem happens
Add the chat widget with one embed script. A visitor can describe the problem without finding your issue tracker or creating another account. Your reply appears in the same website chat, so you can ask a follow-up question before deciding what needs work.
For example, “the export button is broken” is a starting point. Ask which report they opened, what date range they selected, and what happened after they clicked. Those answers help you write a ticket that another developer can investigate. See how website messages reach Telegram.
From customer conversation to confirmed ticket
- Read the report and ask for context
Understand the expected result and the actual behavior. A separate visitor thread keeps the exchange together.
- Review the drafted ticket
Create a ticket from the conversation. Review its title, summary, kind, and priority, then confirm it. The original conversation stays attached.
- Prepare and review the change
Handle the ticket yourself, or use Pro to dispatch the confirmed task to a coding agent through GitHub or your own runner. Review the proposed change.
- Deploy, test, and confirm the live fix
Check the customer’s original problem after deployment. Explicitly confirm that the fix is live to notify the visitors linked to the ticket.
“Merged” and “fixed for the customer” are different states
A pull request can merge while a release is still waiting. An issue can close because it is a duplicate or will not be worked on. Neither event proves that the customer can finish the task they reported.
chatwithdev keeps live verification as an explicit step. You decide when the deployed result is ready for the customer. This also gives you room to explain a workaround or ask another question in chat while the ticket is in progress.
Use tickets with or without a coding agent
The core workflow is useful for a solo developer, a founder handling support, or a small SaaS team. Tickets are available on every plan. Pro adds the option to send confirmed work to GitHub or your own runner; you still review the result and check it after deployment.
Bug reporting widget questions
Do customers need a GitHub or Telegram account to report a bug?
No. Customers report problems in the chat widget on your website. Telegram and GitHub are tools on your side of the workflow.
What information should I ask for in a bug report?
Ask what the customer was trying to do, what they expected, what happened instead, and the steps that reproduce it. Ask for the page and browser when relevant. Keep credentials and other sensitive information out of the conversation.
Does the widget automatically capture screenshots or console logs?
This workflow starts with a customer conversation. It does not promise automatic screenshots, session replay, or console-log collection. Ask the visitor for the details you need to investigate.
Does a merged pull request mark the problem as fixed?
No. A merged PR still needs a deployment and a live check. Explicitly confirm that the fix is live before chatwithdev sends a fix notification to linked visitors. Closing an issue alone does not send it either.
Do I need a coding agent to use tickets?
No. Ticketing is included on every plan and you can handle the work yourself. Pro adds coding-agent dispatch through GitHub or your own runner.
How much does it cost?
New projects get 14 days of Pro free, including unlimited messages. Afterwards, the free plan includes 5 customer messages each month. You are only charged if you choose a paid plan. Starter is $15 per month with unlimited messages; Pro is $25 per month and adds coding-agent dispatch. Yearly billing is also available.
Add bug reporting to your site
Copy the embed from your dashboard, choose a Developer or Support greeting, and connect Telegram. Send a test report from the website and reply to it before inviting customers to use it.