Standing service store-wismo-reply-drafts-retested-monthly · revised 12 October 2026
Standing service
Re-test your "where is my order" reply drafts every month and after any carrier change
Each month we re-run your 30-case test on your reply drafts against current order fields and carrier wording, list any template that no longer fills correctly, and propose fixes for your approval.
This starts a conversation by email. Nothing is charged, and nothing is checked, until we have agreed scope and terms with you in writing.
The responsibility you hand over
Reply templates break quietly when a carrier renames a status, a tracking field moves or a new carrier is added. The first sign is a customer told the wrong thing. A monthly re-run of a fixed test shows what changed before a customer does.
Who it’s for: Owner whose "where is my order" templates are already built and who wants to know when a carrier or store change breaks them.
Usually starts when: A carrier changed its status wording or you changed how tracking is stored, and a template quoted the wrong thing.
The result: Every month you receive the re-run results of your 30-case test and a list of templates that no longer fill correctly. A change your named person plants in a copy of your carrier wording in the first month is caught.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target for delivering each report is agreed in writing before it starts, set to what a service at this stage can keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock and runs on the schedule we agree.
What must remain true
- Every template fills correctly from current field names and carrier wording, or is listed as failing
- The 30-case test still routes every trap case to a person
What we watch
- The carrier wording you send
- Field names and order fields you tell us about
- The 30-case test file
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A carrier changes how it words a status. | We re-run the test, list the templates that no longer fill correctly and propose fixes. |
| You change how tracking is stored. | We re-run the test and list affected templates. |
| A trap case no longer goes to a person. | We list it first and propose a fix to the pre-send check. |
| You have no templates yet. | We point you to the one-off job that writes them. Linked job: Where-is-my-order reply drafts |
We do on our own
- Re-run the test
- List failing templates
- Propose fixes
We ask you first
- Any change to a template or the pre-send check
- Any new delivery state
- Anything that needs live access
We escalate to you when
- A trap case reaches a draft instead of a person
- A carrier drops tracking events you rely on
- The test file no longer represents your orders
How you know it held. Each month the results list all 30 cases with pass or fail and the date of the carrier wording used, and you can re-run the test with the steps we hand over.
How we keep it true
This service is never finished. Each period's report shows whether the thing it checks stayed true, and it continues until you end it.
Draft "where is my order" replies from order facts, with a check that stops stale ones Job Optional
Eight templates (four replies, four hand-over notes), filled from named order and tracking fields, with a rule that sends any draft whose value differs from the live order to a person.
Bought separately, each time it is needed; not part of the monthly fee
The one-off job that writes the templates, the pre-send check and the test.
What is included, and what is not
- Monthly re-run results
- List of failing templates
- Proposed fixes
- Updated test file when you approve
Included
- Your set of templates and the 30-case test file from the one-off job
- A monthly re-run against current field names and the carrier wording you send
- A list of templates that fail or changed since last month
- Proposed template fixes for your approval
- An extra re-run after a carrier or tracking change you tell us about
Not included
- Sending any reply
- Connecting to your store or carrier
- Refunds or reshipping decisions
- Customer data
- New templates for new states (see the one-off job)
- Out-of-hours cover or a guaranteed response time
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
In the first month your named person plants a change in a copy of your carrier wording (for example "Out for delivery" renamed) without telling us where, and the note lists every template it breaks.
Evidence: The change you planted and the note side by side.
Each month all 30 cases are listed as pass or fail, and every trap case goes to a person.
Evidence: The monthly results table.
Each month templates that failed or changed since last month are listed.
Evidence: The comparison with last month.
Sign-off. You read each report and tell us whether the rules and thresholds still suit you. A period counts as delivered when you have the report.
If it fails. If we cannot complete a period because an input is missing or has changed shape, we say so, explain what we need and do not guess. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- Templates and the 30-case test exist (from the one-off job or your own)
- You send current carrier event wording and field names each month, or when they change
- A named person approves template changes
- Test cases stay anonymised
We stop and tell you if
- The test file is lost and cannot be rebuilt
- Carrier wording is never available to us
- The plan is to send replies automatically
What could go wrong
The service reads what you send and reports. Nothing in your store or helpdesk is changed by us, so there is nothing to undo. Ending it leaves your systems as they are, and you keep every report we sent.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A carrier changes wording between monthly runs. | You tell us when you notice a change and we re-run at once; the monthly run is the backstop. |
| A clean re-run is read as proof that replies are right. | The note says it re-runs a fixed test and does not promise what any reply says. |
A separate automated reviewer checks the work and the test results before hand-over. Your named person approves every template change. No human supervisor from us is included unless your agreement names one, and at launch the work is largely automated.
Stays with a person
- You approve every template change
- You send every reply
Access we would need
- Carrier wording and field names that you send
Questions
Does it send my replies?
No. It re-tests the templates. A person sends every reply.
What if my carrier changes its wording?
Tell us, and we re-run the test at once.
Does a clean report mean nothing is wrong?
No. It means nothing was found in the inputs you sent, by the checks listed here. It is not assurance, and it does not replace your own checking.
Also part of
Send an enquiry
Send us
- Which carriers you use
- How tracking is stored on orders
- Any recent change to either
- No customer data
Later, once you agree
- The templates and test file through an agreed secure route
- Current carrier wording each month
- The name of the person who approves template changes
You keep your store, your helpdesk and every login. We work on the files you send through a secure route agreed after you say yes, and hand back files and a report. We never ask for store or helpdesk logins, and nothing goes live until your named person applies it.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “store-wismo-reply-drafts-retested-monthly” as the subject.