Troubleshooting

Why is an AI chatbot creating duplicate support tickets?

A single event or conversation can be processed more than once when delivery is retried, or when two tools are configured for the same handoff. Check delivery records and ticket creation records before changing the workflow.

What matters for your decision

Separate duplicate-delivery defense from duplicate-trigger cleanup. Keep one workflow owner and a stable handoff identifier so delivery confirmation does not cause another ticket.

Diagnose before changing settings

  1. Compare timestamps and a stable handoff or delivery identifier across source event, integration and created tickets.
  2. Make repeat delivery a no-op after one successful create; separately disable any second workflow firing for the same handoff.
  3. Test synthetic repeated delivery and an out-of-order event in staging, then verify exactly one downstream ticket.

Go deeper

Sources

Related questions

Your business. Your shortlist.

Find your best-fit AI support software.

Start with your website. Answer a few focused questions, then get a personalized PDF with fit, trade-offs, alternatives and a pilot plan.

Name, email and business domain are required for the PDF, not to start.

AI Support Software

Your personalized recommendation

By DocsBot · Research → short interview → your PDF.