The work your company repeats every day, handled by Velros AI instead of people Get a free assessment →

Plugins & Themes

Install and bug questions, license checks, refunds, feature requests, and reviews stay scattered across channels, and Velros AI gathers them so support and sales stop stepping on each other.

Get an assessment
Channels unified Refund & license approval Bug repro captured

Plugins & Themes

  • Channels unified
  • Refund & license approval
  • Bug repro captured

The channels stay. Only the work a person confirms is separated out.

Channels unified · Refund & license approval · Bug repro captured

What a person confirms runs on a single thread.

Rather than adding another screen, we sort the work arriving on the channels you use and separate out only the decisions a person should see.

The same channels

Nothing new to install. Velros AI runs over the email, store inbox, GitHub issues, and Discord you already use, and we build the screens, approval queue, and reports you need and keep improving them as you operate.

These inquiries, handled like this.

The requests that arrive at Plugins & Themes every day, kept on one screen along with what to confirm and what to improve next.

The order a person kept by hand, moved over as it was.

  1. Sort Requests scattered across email, your Shopify store, and GitHub issues get auto-sorted into install, bug, license, refund, or review.
  2. Check It cross-checks the order number against payment and license records, and pins bugs to the exact WordPress/PHP version and repro steps.
  3. Draft A workaround note or a refund yes/no reply is drafted to match the customer's tone before you ever type.
  4. Approve Refunds, license re-issues, and roadmap changes come up as an approval card so you just click to send.

What you can see

It keeps the original messages, logs, staff edits, and approval-hold reasons that come in from email, your store inbox, GitHub issues, and Discord, so you have the evidence for the next release.

What stops

Refunds, license and pricing changes, roadmap commitments, and bulk sends go out only after you or your team lead reviews them.

Someone who knows the industry sets the rules with you.

A Velros operations designer and a working expert turn your standards for install and bug support, licensing, refunds, and feature requests into real operating procedures.

The Velros operations design team

Industries rule design and weekly improvement

Get an assessment

It keeps improving

Staff edits and the reasons work was held get gathered into next week's operating rule.

A person's time

Less repeat checking, and more of the day on the decisions and the growth that matter.

In depth

While install tickets pile up, the developer can't ship the next release

Sell one plugin or theme and the questions never stop. It won't install, it conflicts with another plugin, the license key won't activate, they want a refund. Most of it is already in the docs or fixed by a single reinstall. But while you're stuck answering the same things, the bug fixes and the next version keep slipping. The only things a human really has to judge are whether to refund, whether to free up another license, and whether a request belongs on the roadmap.

From the moment a ticket lands to when it's closed

  1. Pulls scattered channels into one place

    Email, your store inboxes (Shopify App Store, WordPress.org), and GitHub issues get collected into one line and grouped by the same version and the same symptom.

  2. Turns repeat questions into drafts

    Install order, deactivating a conflicting plugin, clearing the cache, reactivating a license. Answers already in your docs come back as a reply draft and a bug-repro checklist tailored to that user's setup.

  3. Sends judgment calls to an approval card

    Refunds, extra licenses, and "please add this to the next version" go up as an approval card for a human to confirm. Nothing goes out until you send it.

What a human confirms

Refunds
Charge reversals and refunds are approved by a person after the amount and reason are checked. Your marketplace policy and the digital-goods return terms are shown side by side.
License exceptions
Site-count overages, key reissues, and extra dev seats aren't granted automatically. A person confirms them.
Roadmap decisions
Whether a feature request lands in the next version or becomes a paid add-on is product direction, so a person decides. The draft only ever replies "under review."

Deadlines and duties you can't miss

No automatic right of return on digital goods
There is no federal cooling-off period for online digital purchases, so refunds run on the policy you published and your marketplace's rules. State the terms before purchase and apply them consistently.
Honor the stated policy (FTC)
The FTC treats your published refund, license, and pricing terms as promises you must keep. Drafts always answer from the policy you've actually posted, never an off-the-cuff exception.
Email and customer data
Support and marketing email must carry a working opt-out and honor it (CAN-SPAM). Buyer emails and payment data are used only for the purpose they were given for, and not passed to third parties.

FTC Act, 15 U.S.C. §45, and the CAN-SPAM Act of 2003 · your marketplace refund policy (Shopify App Store / WordPress.org)

Common questions

Does it send replies on its own?
No. Even for repeat questions it only prepares a draft; nothing goes out until a person checks it. Refunds and licenses always pass through an approval card.
Does it read GitHub issues too?
Yes. Email, store inboxes, and GitHub issues are collected in one place and grouped by the same version and symptom. It also drafts a bug-repro checklist.
Will it set my refund rules for me?
No. It uses the policy you set as the basis, verbatim. Velros shows that policy next to the required disclosures, and a person makes the call.

We'll find what to cut first in Plugins & Themes, together.

Where the inquiries land, the order your staff check them in, and the rules a person applies last, laid out as one day of work.

Talk about our industry

What comes in

Messaging, phone, search and email, in one place

What gets checked

What your staff decide, and what a person decides

What improves

Fewer repeat inquiries and fewer dropped follow-ups, every week