Everyone who gets a message from a sadistic programmer is doing this in a bad mood, so give them the three things they desire: what happened, whether it was their fault, and what key to press next. Most messages provide one of the three along with an apology.
Given unsuccessful designs, we expect you to come up with a list of errors rather than photocopy something. Telling someone what to be specific about means there is something he/she needs to be specific about.
Errors show wording differences in volumetric terms. ‘Something Went Wrong’ creates a ticket. ‘Your card issuer declined this payment, please try another card or call your bank’ creates a retry. The distinction is not in the sentences’ tones. It is if the sentences have actions that can be performed by the reader without the need for external communication.
The following error copy examples are structured to be polite apologies. They say ‘Oops, something went wrong, please try again later’ in English, Spanish, German, French, Mandarin Chinese, Italian, Portuguese, Hindi, and Arabic. They have no ability to speak to your condition states, and for that reason cannot distinguish a rate limit from an expired token. Therefore, for the user, the answer to the issue, which may take a second, or may take a phone call to the bank, is the same.
We request engineering for a copy of the real error states and the ones currently using the generic string. The writer cites the error states and describes all error messages triggered, the state the user was in when the errors happened, and from which state each error message was triggered. Typically, we suggest separating two failure states that share a message.
Incorrect information can show up in unexpected places: pop-up messages, fields that contain validation logic, full page notifications, emails that are sent due to a failed background job. We group those, so that an error related to a failed payment has a matching error message displayed in the application and in the payment receipt email. We also indicate which channel each string belongs to.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical error message | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single screen | 60 | $6 | $0.06 | $6.06 |
| Small set | 150 | $15 | $0.15 | $15.15 |
| Whole flow | 350 | $35 | $0.35 | $35.35 |
An error message is shorter than our 100-word minimum order, so a single one is charged as 100 words ($10.10). Most clients commission these in batches, which uses the minimum properly — ask for however many options you want and we will quote the set.
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
We rely on what is already created and break things in our test accounts to copy the rest. This method will be both time-consuming and incomplete. You will receive the list that we verified and the states that we think exist. This will leave a gap so that it is not assumed, thought of, and guessed.
Yes, and they have their own rules. Validation messages are read before a record is submitted. They should describe the information that will complete the record, rather than explain the information that is missing. We describe them as a separate group and have them phrased positively. They literally describe allowable input.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
They requested access to our staging endpoint with read access and used it too. The auth section of your docs shows us the 409 error we return for duplicate idempotency keys. That error is not documented anywhere in our old docs. Contract documentation has never come back and educated me about my API before.
Our API documentation was written over an uneven four-year span. The author went through every single one and flagged six cases where our error responses were inconsistent with the description and raised them instead of just fixing them on the fly. That was worth the order.
Ordering is clearly very good, and the screenshots are clearly explained. The guide assumes the customer has admin access, which a good number of them do not. We wrote a pre-req box ourselves in ten minutes. Everything else was complete.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees