Plan allowances are now Starter 10, Growth 100 and Scale 1,000 analyses a month.<\/p>","0.1.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3712933,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3712933,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3712933,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3712933,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0","0.1.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3713567,"resolution":"1","location":"assets","locale":"","width":1286,"height":1887},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3712933,"resolution":"2","location":"assets","locale":"","width":1286,"height":1567},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3712933,"resolution":"3","location":"assets","locale":"","width":1286,"height":1089},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3712933,"resolution":"4","location":"assets","locale":"","width":1286,"height":408}},"screenshots":{"1":"Setup: what leaves your store and where it goes, the agreement, domain verification and your plan.","2":"Rules: the rules you write, each with the offer a shopper sees when it matches.","3":"History: the pass over reviews your store already had, and re-judging them.","4":"Requests: the messages shoppers have sent through an offer."}},"plugin_section":[],"plugin_tags":[2368,5431,1519,282702,286],"plugin_category":[45,53],"plugin_contributors":[282703],"plugin_business_model":[],"class_list":["post-375524","plugin","type-plugin","status-publish","hentry","plugin_tags-customer-service","plugin_tags-product-reviews","plugin_tags-reviews","plugin_tags-service-recovery","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-ratings-and-reviews","plugin_contributors-redphoenixteamou","plugin_committers-redphoenixteamou"],"banners":{"banner":"https:\/\/ps.w.org\/postlude\/assets\/banner-772x250.png?rev=3712933","banner_2x":"https:\/\/ps.w.org\/postlude\/assets\/banner-1544x500.png?rev=3712933","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/postlude\/assets\/icon-128x128.png?rev=3712933","icon_2x":"https:\/\/ps.w.org\/postlude\/assets\/icon-256x256.png?rev=3712933","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/postlude\/assets\/screenshot-1.png?rev=3713567","caption":"Setup: what leaves your store and where it goes, the agreement, domain verification and your plan."},{"src":"https:\/\/ps.w.org\/postlude\/assets\/screenshot-2.png?rev=3712933","caption":"Rules: the rules you write, each with the offer a shopper sees when it matches."},{"src":"https:\/\/ps.w.org\/postlude\/assets\/screenshot-3.png?rev=3712933","caption":"History: the pass over reviews your store already had, and re-judging them."},{"src":"https:\/\/ps.w.org\/postlude\/assets\/screenshot-4.png?rev=3712933","caption":"Requests: the messages shoppers have sent through an offer."}],"raw_content":"\n
Postlude \u2014 Review Recovery for WooCommerce.<\/p>\n\n
A shopper who has just written \"it arrived damaged\" has told the store about a\nproblem and, usually, nobody has asked them about it. Postlude reads what the\nreview says against rules the store writes itself, and where a review\ndescribes a problem one of those rules looks for, it shows that shopper a short\nnote beside their review offering to put them in touch with the store. The\nshopper writes a message; the store gets an email and a screen listing every\nrequest that came in.<\/p>\n\n
Postlude ships no rules. Each rule is a short name, which only the store sees,\nand a description of what the reviewer says, such as \"The reviewer says the\ncard arrived creased or in worse condition than listed\". A store can hold up to\n16 rules. For each rule the store writes the offer the shopper sees, the\nbutton's label, and whether the button opens a request form (with the store's\nown instructions at the top of it) or goes to a web or email address. An offer\nis a remedy, never an incentive, and it may never be conditional on removing,\nchanging or withholding a review.<\/p>\n\n
That is the whole of it. Postlude is a service-recovery tool, not a review\ntool.<\/p>\n\n
Postlude never edits, hides, filters, delays, intercepts or deletes a review,\nand it never asks a shopper to change or withdraw one. The Frequently Asked\nQuestions below say exactly what it does write.<\/p>\n\n
Nothing here promises anything about your ratings. What it offers is a way to\nhear from an unhappy customer while there is still something you can do for\nthem.<\/p>\n\n
Postlude is an interface to an external service, and it cannot work without\none. This section describes that service in full.<\/p>\n\n
Installing and activating the plugin contacts no external server at all. No\nregistration, no telemetry, no update check, no remote fonts or assets \u2014 the\nadmin screens and the storefront make no outbound request whatsoever while the\nplugin is installed and not yet enabled.<\/p>\n\n
The first request Postlude ever makes is the registration below, and it is made\nby your own press of the \"Accept the agreement and enable Postlude\" button on\nthe Setup tab (WooCommerce \u2192 Postlude, which opens Setup until Postlude is\nswitched on), after you have read the disclosures printed above that button.\nUntil you press it, nothing about your store or your shoppers has left the\nsite.<\/p>\n\n
That tab asks for a business name and a contact email, and pressing the\nbutton records your acceptance of the Terms of Use published at\nhttps:\/\/postlude.red-phoenix.team\/terms and of the data processing agreement\npublished at https:\/\/postlude.red-phoenix.team\/dpa, together with the version\ndate of each. The record is kept in your own site's database. Have those two details to hand\nbefore you enable, and read the agreement and the screen's disclosures before\nyou press it. When a new version of the agreement is published, the Setup\ntab asks you to accept it; your earlier acceptance is kept.<\/p>\n\n
Review text is sent to the Postlude analysis service at https:\/\/postlude.red-phoenix.team.\nThe service acts as a processor on your instructions. It reads the review text\nand answers with which of the rules you have switched on the text matches, and\nhow confident it is. It returns no prose. The only wording of yours that\nreaches the underlying model is the description of each of your rules, sent\nwith the review text as the question that rule asks. The rule's name is not\nsent to the model. There is no other way to send the model a question, an\ninstruction or a prompt through this plugin.<\/p>\n\n
The service is operated by Red Phoenix Team O\u00dc, the makers of this plugin.\nBehind it, the text is scored by a third-party model vendor, typesafe.ai, in the\nUnited States. The current list of sub-processors is the one in the data\nprocessing agreement at https:\/\/postlude.red-phoenix.team\/dpa.<\/p>\n\n
Postlude processes the review text in the European Union, and passes it to the\nmodel vendor that scores it, typesafe.ai, in the United States, which acts as\na sub-processor. So the text leaves the EU. This is the same statement the Setup\ntab makes inside your admin, and it is the statement to reconcile with your\nown privacy policy and your own transfer arrangements.<\/p>\n\n
Postlude makes five kinds of request, and no others.<\/p>\n\n
1. Registering your store \u2014 first when you press Enable.<\/strong>\nCarries your store's domain, the business name and contact email you type into\nthe enable form, a plan field that always reads 2. Analysing one review \u2014 when a review is analysed.<\/strong>\nCarries the review text, scrubbed and truncated as described below; a reference\nto the review inside your own store of the form 3. Analysing your existing reviews in batches \u2014 beginning when you press Enable.<\/strong>\nThe same per-review content as above, sent for several reviews at a time, over\nthe approved product reviews your store already had. This pass is started by the\nsame press of Enable that registers the store \u2014 it is not a separate decision\nyou make later \u2014 and it then works through your back catalogue in the\nbackground, over as many requests as the backlog takes. It is the largest amount\nof review text Postlude ever sends, so it is worth reading the two sections\nbelow before you enable.<\/p>\n\n That first pass sends only reviews Postlude has not analysed yet. Afterwards,\nthe History tab (WooCommerce \u2192 Postlude, then History) offers two ways to run\nit again. \"Analyse reviews not yet analysed\" does the same: reviews already analysed are skipped, are not\ncharged again, and keep their verdicts. \"Re-judge all reviews\" sends every\napproved review again, analysed or not, to be judged under the rules and match\nbreadths set now; the screen states how many reviews that is, and each review\nsent uses one analysis from your store's monthly allowance, including\nreviews already analysed. A re-judge replaces the earlier verdicts, stops a\nrule you have since switched off from tagging the review, and leaves a tag you\nmarked as wrong marked. A re-judge that stops and is started again begins from\nthe first review and is charged again for every review it sends. Because a\nre-judged review is stamped with the time it was re-judged, the dashboard's\nfigures for a period count the reviews re-judged in it, including ones first\nanalysed in an earlier period.<\/p>\n\n 4. Sending your rules \u2014 when you save them, and before analysing when needed.<\/strong>\nCarries the name and description of every rule you have written, switched on\nor off, and an internal id for each. It carries no offer text, button label,\nlink address or form instructions, nothing about any shopper and no review\ntext. It is sent after you save your rules whenever the set has changed since\nit was last sent, and again before an analysis if the last send failed; while\nit fails, no review is analysed. The service stores the names and descriptions\nfor your store, deletes a rule when a saved set leaves it out, and deletes all\nof them when your store's registration is deleted. When a review is analysed\nagainst a rule, the service sends that rule's description to the model vendor\nwith the review text; the rule's name is never sent to the model vendor. Do not\nput personal data, such as a customer's name, email address or order number,\nin a rule's name or description.<\/p>\n\n After you edit a rule's description, reviews it judged under the earlier\nwording keep their verdicts and are marked on the reviews screen as judged\nunder earlier wording, with a link to \"Re-judge all reviews\", which is charged\nas described above. Renaming a rule marks nothing.<\/p>\n\n 5. Reporting a wrong tag \u2014 when you press \"Wrong tag\".<\/strong>\nCarries the rule the tag belongs to and the model version that answered, and\nnothing about the review or the reviewer.<\/p>\n\n No reviewer name, display name or author identifier. No reviewer email address.\nNo reviewer IP address. No WordPress user id, customer id or account\nidentifier. No order data of any kind \u2014 no order id, line items, SKUs, prices,\ntotals, purchase dates, shipping or billing details. No star rating or numeric\nevaluation of the review. The service rejects a request carrying any of these\noutright, by key name, rather than accepting it and discarding the value.<\/p>\n\n The message a shopper types into the request form, together with the name and\nany order reference they give, is not<\/strong> sent to the analysis service. It is\nstored in your own WordPress database and emailed to you.<\/p>\n\n Before the text is sent, Postlude tries to remove email addresses, phone\nnumbers, order numbers and IP addresses from it. This is best effort and it is\nnot a guarantee. The known gaps:<\/p>\n\n At most 1,000 characters of the scrubbed text are sent. That is a ceiling on\nwhat leaves, not a window onto the start of the review: scrubbing runs first and\nshortens the text as it replaces things, so wording past the shopper's 1,000th\ncharacter can still be inside what is sent.<\/p>\n\n The accurate summary is \"only review text, with obvious identifiers removed\".\nIt is not \"no personal data is transferred\", and Postlude does not claim that.<\/p>\n\n The service counts how many analyses your store has used against its allowance.\nThose counters are held against a site key issued to your store, and the key\nresolves back to your store, so they are pseudonymous rather than anonymous.\nThey carry no review text and no shopper details.<\/p>\n\n Analysis draws on one monthly allowance per store, set by the store's plan:<\/p>\n\n Every store starts on Starter. The allowance is shown on the Setup tab\n(WooCommerce \u2192 Postlude, then Setup) and renews at 00:00 UTC on the 1st of\neach month.<\/p>\n\n New reviews, the pass over your existing reviews, every later run of it and\nevery re-judge all draw on that same allowance, so a history run can use the\nwhole month's allowance.<\/p>\n\n When it is used up, Postlude stops analysing new reviews until the allowance\nrenews, and it stops quietly: a shopper is shown no offer and the review is\nstored with no analysis, so the reviews screen shows it as \"Not analysed\"\nrather than as a review in which nothing was found. A history run that\nreaches it stops too, and the History tab reports it as a completed run rather\nthan an error; it does not resume by itself, and you can run it again once the\nallowance renews on the 1st.<\/p>\n\n No review is changed either way.<\/p>\n\n Prices are in euros and exclude VAT, which is added at checkout. Starter is free and needs no payment. Growth (\u20ac5 a month)\nand Scale (\u20ac20 a month) are bought on Stripe's hosted payment page, through\nStripe Managed Payments; Link, by Stripe, is the merchant of record for the\nsale.<\/p>\n\n The Setup tab shows a link to that page for each paid plan and, on a paid\nplan, a \"Manage subscription\" link to Link. The service supplies these links\nin its registration responses and the plugin stores them in the\n postlude_billing option. The upgrade links are Stripe Payment Links\n(buy.stripe.com) carrying your store's site id, so the service knows which\nstore paid. Showing them makes no request; only clicking one takes your own\nbrowser to Stripe or Link. The plugin never contacts Stripe or Link and never\nsends them anything about your store or your shoppers. Your payment details go\nto Stripe, not to your store and not to Postlude. Stripe's terms and privacy\npolicy: https:\/\/stripe.com\/legal, https:\/\/stripe.com\/privacy. Link's:\nhttps:\/\/link.com\/terms, https:\/\/link.com\/privacy.<\/p>\n\n Stripe tells the Postlude service when a payment is confirmed, and the service\nmoves your store to the new plan. Your store learns of the change the next\ntime it reads its registration from the service; the \"Check plan status\"\nbutton on the Setup tab does that on demand.<\/p>\n\n Plans are sold under the Terms of Use at\nhttps:\/\/postlude.red-phoenix.team\/terms.<\/p>\n\n Terms of use: https:\/\/postlude.red-phoenix.team\/terms\nPrivacy policy: https:\/\/postlude.red-phoenix.team\/privacy\nData processing agreement: https:\/\/postlude.red-phoenix.team\/dpa<\/p>\n\n The notice beside the request form reads: \"The store may use an automated\nservice to read review text. Your name, email address and order details are not\nsent with it, and email addresses, phone numbers and order numbers found in the\ntext are removed first; anything else you write in the review is sent as you\nwrote it.\"<\/p>\n\n\n No. It cannot. Postlude does not write to reviews, does not moderate them and\ndoes not delay them. Your store publishes reviews exactly as it did before.\nPostlude's whole function is to give a shopper who reported a problem a way to\nreach you about it.<\/p>\n\n Postlude never edits, hides, filters, delays, intercepts or deletes a review,\nand it never asks a shopper to change or withdraw one. It has no ability to do\nany of those things: there is no code path in this plugin that writes a\nreview's text, its author, its status or its publication. The review the shopper\nwrote is published exactly as your store would have published it without this\nplugin, and it stays that way. What Postlude does write is its own bookkeeping\nagainst a review \u2014 hidden metadata recording that a review is waiting to be\nanalysed or was covered by the history pass, and holding the one-time link it\nissues to the shopper, in hashed form, with its expiry and whether it has been\nused. None of it is visible to a reader of the review, and none of it changes a\nword of what was written. Postlude adds a conversation beside the review; it does not touch the\nreview itself.<\/p><\/dd>\n No. With the plugin installed and not enabled, no admin page and no storefront\npage makes any outbound request. The first request is the registration you\ntrigger by pressing Enable.<\/p><\/dd>\n The review text is not persisted and not logged by the analysis service. It is\nprocessed in the European Union and scored by a sub-processor in the United\nStates, as described under External services.<\/p><\/dd>\n Only through your rules. Each rule's description is sent to the Postlude\nservice and, with the review text, to the model vendor, as the question that\nrule asks of a review. Nothing else of yours reaches the model: not the rule's\nname, not the offer text, the button label, the link address or the form\ninstructions, and there is no field for any other question, instruction or\nprompt. Write descriptions about what the reviewer says, and keep personal\ndata out of them.<\/p><\/dd>\n No. A fresh install has no rules, and Postlude analyses no review until you\nhave written and switched on at least one. A store can hold up to 16 rules on\nevery plan.<\/p><\/dd>\n Reviews already judged under the earlier wording keep their verdicts, and each\nof those tags on the reviews screen is marked \"judged under earlier wording\",\nwith a link to re-judge. Re-judging is the only way to refresh them, and each\nreview re-judged uses one analysis from your store's monthly allowance. Renaming a rule or changing its offer marks nothing. A deleted\nrule's tags stay and read \"Deleted rule\".<\/p><\/dd>\n Yes. Without WooCommerce active, Postlude does nothing at all, and activating it\nwithout WooCommerce quietly deactivates it again rather than leaving a broken\nplugin behind.<\/p><\/dd>\n Nothing is shown to the shopper and nothing is recorded. A timeout or a failure\ncosts that one review its offer; it never blocks a page, and it never changes\nwhat the shopper sees of their own review.<\/p><\/dd>\n Deleting Postlude from the Plugins screen removes everything it stored on your\nsite: its settings, rules and plan details, its two database tables (review\nverdicts and shopper requests), the markers it keeps on reviews, and any jobs\nit still had queued. The service is not contacted when you uninstall; it keeps\nits own records as its Privacy Policy and Data Processing Agreement describe.<\/p><\/dd>\n\n<\/dl>\n\n\nstarter<\/code> (the service, not\nthe plugin, decides your plan), the word woocommerce<\/code> as the platform, your site's language and the plugin's version.\nThis is what lets the service issue your store a site key and prove the domain\nis yours. It carries nothing about any shopper and no review text. The same\nrequest is sent again on the two other buttons that need it: \"Check verification\nagain\", which re-reads whether your domain has been verified, and \"Replace the\nsite key\", which issues your store a new key and stops the old one working. It\nis also sent, with your existing key, when you accept a new version of the\nagreement; that re-reads the registration and issues no new key.<\/p>\n\nwp-comment-123<\/code>; the ids of\nthe rules you have switched on; and the product title where the review has a\nproduct. The request also has a language field and a submitted-at field, and\nPostlude leaves both of them empty.<\/p>\n\nWhat is never sent<\/h4>\n\n
What is removed from the review text first, and what is not<\/h4>\n\n
\n
Usage counters<\/h4>\n\n
\n
Plans and payment<\/h4>\n\n
The service's terms and privacy policy<\/h4>\n\n
What shoppers are told<\/h4>\n\n
\n
\/.well-known\/postlude-verification<\/code> over https at the root of your domain, which the plugin serves automatically. If the Setup tab still shows the domain as unverified, make sure the site answers over https at the domain root and press \"Check verification again\".<\/li>\n\n
Does Postlude stop bad reviews being published?<\/h3><\/dt>\n
What does Postlude add to my store?<\/h3><\/dt>\n
\n
Does anything leave my store before I switch Postlude on?<\/h3><\/dt>\n
Is the review text stored by the service?<\/h3><\/dt>\n
Can I send my own instructions or prompts to the model?<\/h3><\/dt>\n
Does Postlude come with rules?<\/h3><\/dt>\n
What happens when I change a rule's description?<\/h3><\/dt>\n
Does it need WooCommerce?<\/h3><\/dt>\n
What happens if the service is unreachable?<\/h3><\/dt>\n
What does uninstalling remove?<\/h3><\/dt>\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n