How To Complain Card
The complaints route in three plain steps, plus the quarterly ledger of every complaint received and what each one changed.
The complaints route in three plain steps, plus the quarterly ledger of every complaint received and what each one changed.
Search blocks by description or jump to a page.
The source for every Ecommerce block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
How to Complain Card publishes the complaints route in three numbered steps then backs it with a quarterly ledger. The steps card runs say the word (reply with "complaint" and it skips the rota to the founder the same day), one business day (a signed reply, never a template), and it goes in the ledger. Below, the ledger lists each complaint received against the exact change it caused, and a closing line gives the real count: three across 2,841 orders for the quarter.
Steps and ledger are two arrays, the step number derived from index and zero-padded. The ledger is the honest weight of the block, it turns a published process into an audited one, since a complaint with no recorded change is just a form that goes nowhere.
Reach for this block low on the contact page or a policy page, where a reader who is already unhappy can find the route without hunting. The ledger has to be real and kept current or it does the opposite of what it promises.
A natural flow around it on an Ecommerce Pro page:
Before
After
One strong use is the three step route with a live ledger. Other complaint variants:
Tip: the ledger is what makes the first two steps believable; publish the steps without it and you are asking to be taken on faith.