Skip to content

Sandbox ​

When a customer reports something your WordPress plugin or theme does, or fails to do, Overdesk can start a private test site: a fresh copy of WordPress with your product installed. It tries what the customer describes there before it writes the reply, and the reply says what it checked. Instead of "this should work", the customer reads what happened when it was tried.

You set it up on the Sandbox tab under Settings.

Set it up ​

  1. Open Settings, then Sandbox.
  2. Under Products, add each of your plugins and themes by its WordPress.org slug: the last part of its address on wordpress.org, like foogallery in wordpress.org/plugins/foogallery. You can paste the whole address instead. Overdesk checks the slug with WordPress.org and shows the product's name. Press Add.
  3. Leave Try the customer's issue on a test site before replying ticked. It is on by default.
  4. For a paid version that WordPress.org does not have, press Add your zip file beside its product and choose the zip you give your customers. The test site then installs that zip instead of the WordPress.org download. Remove zip file goes back to the download.

Overdesk uses test sites only once at least one product is on the list, so adding your first product is what turns the feature on. If your workspace follows WordPress.org support forums, those plugins are offered under the form, one click each.

Owners and admins can change the list and the switch. Everyone else in the workspace sees them read-only. A list holds up to 20 products.

When a test site is used ​

  • When the customer reports something the software does or fails to do (an error, a conflict with another plugin or theme, a setting that seems to do nothing, a page that breaks), Overdesk tries it on a test site before writing the reply, including when your knowledge base already describes the problem. The test shows whether it happens on a fresh install with the customer's versions. Unless Overdesk has switched on starting the test site for your workspace, it decides ticket by ticket, so a reply can still come from the knowledge base alone. Billing, licenses, accounts and policies are answered without a test site, and so, as a rule, are questions about how to do something or whether a product can do it, and features only your paid version has: without your own zip file, the test site has the free WordPress.org release.
  • Overdesk switches on one more way of working for a workspace, the way it arms live sending. Your team does not turn it on and it is not in the dashboard. Where it is on, a customer message that reports a problem with one of your products, in the sense above, gets a test site that Overdesk starts itself while the draft is written, and Overdesk tells the drafter to check the reported problem there first, before it reads code, even when your knowledge base describes the problem. Once a test site has been used for a reply, whoever started it, a later message in the same conversation within a day gets no test site for its reply, and neither does any message once the conversation has had 3 test sites in a day, however they ended. There are two exceptions, both only while the conversation has had fewer than 3 test sites in the day. The customer's answer to a reply that was allowed to ask for their Site Health info (see below): within a day of that reply, a message that answers it with a version can still get a test site. And a message that says the advice in an earlier reply did not work, or that the customer had already tried it, gets a new test site, and the drafter is told not to assume the earlier conclusion still holds: it checks again, tests other explanations, and does not repeat the advice the customer says failed. Where it is off, nothing changes.
  • When the drafter starts the test site, it starts with at least one of your products, plus any other WordPress.org plugin or theme the customer mentions, so a conflict can be reproduced. When Overdesk starts it itself, only the product the message is about is installed. A report of a conflict with another plugin or theme is left to the drafter, which is asked to start the site with the plugins or theme the problem involves.
  • It uses the WordPress, PHP and plugin versions the customer gave, including their Site Health info when they paste it into a message: the text WordPress copies from Tools, then Site Health, then Info, then Copy site info to clipboard. Overdesk reads the WordPress and PHP versions, the theme and the active plugins from it, wherever it sits in the message. Pasting it does not push the customer's question out of what Overdesk reads: when Overdesk can tell where the pasted info ends, the customer's own words come first and the pasted info is not used to search your knowledge base. When the drafter starts the site, from a long plugin list it installs the ones that could touch the problem. It is used only when the conversation shows one site: when its messages, attached files or linked pages hold Site Health info for two different sites (an older paste and a newer one, or one your team shared), or any Overdesk cannot read, none of it is used. When they gave none, it uses the versions their site last reported to a connected licence system such as Freemius, or those a page they linked to shows in its code, and otherwise the newest. Where Overdesk starts the test site itself, it picks the versions in this order: the ones the customer wrote in their own words, their pasted Site Health info, the versions their site last reported to a connected licence system, a page they linked, and otherwise the newest. Of the versions in messages, Overdesk takes only the customer's own words, leaving out your teammates' messages and the quoted earlier replies it can recognise. When their plugin version is not on WordPress.org, the newest release is installed and the reply says so. The test site has the newest WordPress release, plus 7.0, 6.9 and 6.8, on PHP 7.4 or 8.0 to 8.5. A PHP version is matched by its first two numbers, so a site on PHP 8.2.29 is tested on PHP 8.2. When the customer is on a version the test site does not have, a close one is used and the reply says which.
  • Where Overdesk starts the test site itself, a reply can ask the customer for one thing: their Site Health info, copied from Tools, then Site Health, then Info, then Copy site info to clipboard. It asks only when the customer reports a problem with one of your products, no WordPress, PHP or product version came from their own words, the subject line, a Site Health paste, a connected licence system or a linked page (a version in the subject or in their messages counts when it is written as WordPress, WP, PHP or a product's name, slug or short brand, such as the first word of its name unless that is a common English word, followed by a dotted version number, with "version" or "v" allowed between; a number with "requires", "requirement", "minimum" or "tested up to" among the four words before the name is a requirement and does not count, and neither does the subject of a forwarded message, in English, German, French, Spanish, Portuguese or Dutch), no Site Health info appears anywhere in the conversation, readable or not, no earlier reply from your team that the customer received mentioned Site Health, system info, system status, debug info or a system report, or asked for a version (a question that mentions a version, a "which" or "what" question in which WordPress, PHP or WP is followed by "version", "are you" or "do you", or a request such as "let me know", "send", "share", "tell", "provide" or "include" before the word version, when it does not ask "if" or "whether" something, as "let me know if the new version fixes it" does not, and it opens a sentence or follows "please", "kindly", "if you could", "could you", "can you" or "would you", with "also" or "just" allowed after them; a request line ending in a colon counts with the list under it), no earlier reply in the conversation was allowed to ask, in any language, unless that draft was discarded or rewritten through an @Overdesk mention, and the checks on the test site did not show the problem. Overdesk tells the drafter to say only what the info shows, the WordPress and PHP versions their site runs with its theme and plugins, never what anyone will do with it, and to give no time or result. When the checks on the test site showed the problem, the reply does not ask, not even in case the fix does not work. The customer's answer is a message sent after both the reply that was allowed to ask and the team's last reply, in which their own words hold Site Health info that Overdesk can read (a forwarded copy counts, a quoted one does not), or a WordPress or PHP version. A version of your product alone is not an answer. Such an answer can get a test site again on those versions, within a day of the ask as the exception to the day rule, or later, still within the limits on test sites a conversation and a workspace have in a day. When the message does not itself report a problem, as with "Here you go:" and the paste, Overdesk ties it back to the product the ask was about. A reply in between such as "I'll get it tonight" does not stop this, and the ask stays open until a draft is written with a test site planned on versions the customer gave, or until an answer is drafted. A draft with a test site on the newest versions, because they gave none, does not close it, so an answer within a day still gets its test site, while the conversation is under its daily limit. Where Overdesk does not start the test site itself, nothing changes.
  • Replies you ask for with Re-draft are written without a test site.

On the test site, Overdesk can load any page as a visitor or logged in as the site's administrator and read the page, its JavaScript errors and its PHP notices, and take a screenshot when how the page looks matters, up to 4 on one reply. It can also run WP-CLI commands and PHP with WordPress loaded, for example to read a setting or create a page that holds a shortcode. A page load has up to 45 seconds and a command or piece of PHP up to 60 seconds, and a page load says how long the check took. The test site cannot request web addresses, its own pages included, so PHP or a command that would is not run. A command or piece of PHP that runs past its minute is a result about that step only: what was run takes longer than that on the test site, with the data it had.

What the reply says ​

  • The reply says something was tested only after a page was loaded, a WP-CLI command was run or PHP was run on the test site and the result was seen. Starting the test site is not a test. It says it plainly, in the customer's terms: the versions, what was done, and what happened.
  • When the test site could not start, stopped, was not available, or started and checked nothing, the reply does not say that anything was tested.
  • A check that did not show the problem is reported as what was checked and what it showed. The reply never says "it works", never blames the customer's own site on the strength of a check, and never says the problem could not be reproduced when the check could not do what the customer did. A check can miss a problem: the test site loads pages but does not click, hover or type.
  • A command or piece of PHP that times what the customer reports, such as a gallery or a shortcode rendering, and runs past its 60 seconds is reported as a measured result: what was run, with how much data, and that it did not finish in that time on the test site. The test site runs PHP more slowly than a normal web server, so the reply does not give that as the time the customer's own site takes, and it is not proof of the cause. Overdesk is told to build test data in a step of its own, apart from the timing, and to leave a setup step that runs out of time out of the reply.
  • A draft that claims a test with no finished test behind it is held for a person, whatever your rules say. See Rules.
  • A draft that was allowed to ask the customer for their Site Health info is held for a person too, whatever your rules say, and no rule can send it. It shows as Overdesk let this reply ask for the customer's Site Health info, so a person checks it first. See Rules.

On Agent drafts, a draft the test site checked is marked Tested. Its page shows "Tested on a test site:" with the WordPress, PHP and product versions and how many checks were run, and, when the customer pasted their Site Health info, what it lists: their WordPress and PHP versions, their theme and how many plugins are active. When Overdesk started the test site itself, the line also says where each version came from, such as the customer's message, their Site Health info, their licence system, a linked page or the newest release. The note on the ticket in your help desk says the same. When the test site did not finish, or started but checked nothing, the page says that nothing was tested.

What the result means ​

Once the draft is written, the reviewer reads the test site's record and records what it showed about the problem the customer reported, for every test site that finished and checked something. On Agent drafts, under the test site line, and in the note on the ticket, Overdesk says so when the result should make you look closer:

  • The test site could not settle this, and what to ask the customer for: their versions, the steps they took, the page where it happens or the error they see.
  • The checks did not test the problem the customer reported.
  • The reply says something the test site did not show, so check it before sending.

The reviewer counts a check only when it is the kind of thing the customer did: loading a page does not check a click, so one page load says nothing about a problem the customer saw when they clicked.

When the reply tells the customer something the record does not show, such as that the problem was reproduced when the checks did not test it, the draft waits for a person. A test site that did not finish, or started and checked nothing, gets no result.

Two starter rules read the test site's result: Test site could not finish and Approved answers the test site checked. Both start off. A draft Overdesk tried a test site on waits for a person for now, so the second sends nothing even when it is on. See Rules.

What a test site can reach, and what it keeps ​

  • Each test site is a separate machine, started for one draft and deleted once that draft is written. None is shared between drafts or between workspaces.
  • A test site cannot reach the internet or any other part of Overdesk. Overdesk downloads your products from WordPress.org itself, or uses your zip file, and copies them in.
  • Overdesk copies nothing from your help desk into a test site. What the model types there, such as a shortcode from the ticket, goes in with names and contact details replaced, as in everything else it sees. See How customer data is handled.
  • A draft uses its test site for up to 4 minutes. A workspace can run 2 test sites at once and 200 a day. Past either limit, the reply is written without one.
  • Reading your code never uses up a reply's checks: after the code is read, the test site keeps room of its own for a start and a few checks.
  • The record of each run, what was tried and what the test site showed, is kept for 180 days. See Data retention.
  • Your zip files are kept until you remove them or delete the workspace, and only your own test sites install them.

The model's work with the test site runs on your Anthropic key like the rest of the draft, so a tested draft uses more tokens than one written from the knowledge base alone. The test site itself costs you nothing.

Your own zip file ​

A zip file can be added to any product on the list, and it replaces that product's WordPress.org download on every test site. Overdesk checks it when you add it:

  • It must hold one folder, the plugin's or theme's own, with everything inside it, and be no larger than 64 MB. A zip made on a Mac is fine: the extra folder macOS adds is left out.
  • A plugin needs a PHP file at the top of that folder with a Plugin Name line and a Version line, as WordPress itself expects. A theme needs a style.css with a Theme Name line and a Version line.
  • Links to other files, and paths that lead outside the folder, are refused.
  • Plugins named on its Requires Plugins line are installed first, from WordPress.org.

The list shows the folder name, the version and the size of each zip. The test site always installs the zip, whatever version the customer mentioned, and the reply says which version it used.

If the setting cannot be read ​

If Overdesk fails to read the switch or your product list while writing a draft, it writes that draft without a test site.