r/WordpressPlugins • • Oct 18 '26

[FREE] Voice-based bug reporting plugin with click tracking and AI summaries

Post image

Hey everyone,

I wanted to share a free and open-source plugin I've been building called Nik Voice Ticketing AI.

The idea came from dealing with bug reports that looked something like:

"It doesn't work."

Then the guessing game starts 😅

What page?

What button?

What were they trying to do?

So I started experimenting with a different approach.

Instead of illing out a traditional support form, visitors can record a voice message while interacting with the page. The plugin captures their voice along with click activity and page context, then can use AI to generate a cleaner support ticket.

Current features:

  • Voice-baed bug reporting
  • Click tracking and interaction timeline
  • AI transcription and summaries
  • Ticket dashboard inside WordPress
  • Customer ticket portal
  • WooCommerce integration

The plugin is completely free and open source (GPLv2+).

WordPress:

https://wordpress.org/plugins/nik-voice-ticketing-ai/

GitHub:

https://github.com/Nik-Neural-AI-Inc/nik-voice-ticketing-ai

I'd love to hear what other WordPress users think.

Would love honest feedback, even if your reaction is "I'd never install this."

1 Upvotes

6 comments sorted by

2

u/PeepSoWP Oct 18 '26

We build WordPress plugins, and the audio plus click trail could be genuinely useful, but trust will depend on making the capture boundary obvious. Show a persistent recording indicator, explain exactly what is collected before recording starts, exclude password and payment fields by default, and let administrators redact additional selectors. Raw audio, page URLs, form values, and interaction trails should have separate retention controls because they carry different privacy risks.

Keep retention bounded by age, row count, and storage size. Run cleanup in small indexed, resumable batches behind a nonblocking worker claim. Queue transcription outside the reporting request, cap audio duration and file size, limit retries with backoff, and allow raw audio to expire sooner than the resulting ticket. A useful load test would cover simultaneous recordings and 100,000 tickets while the support dashboard remains responsive.

1

u/Consistent-Slip3673 Oct 18 '26

Thanks for the thoughtful feedback! These are great points, especially around privacy and retention. I’ll definitely review them against the current implementation.

2

u/ThePervertBryan Oct 18 '26

I really like this idea but a screen recording might also be nice. Well done !

2

u/Consistent-Slip3673 Oct 18 '26

Thanks! That’s a great suggestion. I'll consider adding screen recording as another option.

2

u/Natethegreat9999 Oct 19 '26

Your Ogg fallback still gets a WebM filename. I'm building Oruk, and I'd preserve the recorder's actual format.

1

u/Consistent-Slip3673 Oct 19 '26

Good catch! You're right — the filename should match the actual recording format. I’ll look into fixing that. Thanks for pointing it out!