A tooltip exists because a label ran out of room. That makes restating the label the one thing it must never do, and it is what most tooltips do. A Save button with a tooltip reading ‘click to save’ has spent a real affordance on nothing.
Like you’ve expected, helpful tooltips answer what the label is about, what happens after you click it, and when it is appropriate to avoid clicking it (and what happens if you do). All tooltips are approximately ten to fifteen words (no scrolling). Jargon is not used.
People consult tooltips after they encounter a small issue. They want answers quickly and don’t care to understand the problem. Tooltips, therefore, need to be concise and to the point with the answer at the top. Tooltip writers must keep in mind that if a user has to open tooltips more than once, then the help center would be more useful.
Modeled after a control name, a paraphrase is generated. You get something close to “Enable notifications: turn on notifications” over a hundred times, all oddly generated and void of meaning. It has no way of knowing that your notification settings have three levels and only one is on by default, which is the only thing that should be in the tooltip.
By working through the screens, the writer identifies problem spots on the screens which leads to the creation of a new list of controls by the writer. Other members on the team notice the label after fresh eyes have created the list. We check all the candidates against your support tickets. Controls which generate tickets require tooltips. Controls which are pretty do not.
REMOVE SPACING TO MATCH everyone else. Tooltips are the smallest part of your product’s voice. With a lot of tooltips, it’s relatively easy to find signs of inconsistency. We use a set of constants and name objects consistently, use the same ‘verb’ (for actions), and pass on the pattern to subsequent developers. Because of this, someone who adds a tooltip later will be expected to use the same pattern.
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 tooltip | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Five options | 30 | $3 | $0.03 | $3.03 |
| Fifteen options | 80 | $8 | $0.08 | $8.08 |
| Campaign set | 150 | $15 | $0.15 | $15.15 |
A tooltip 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.
No. If everything on the screen has a tooltip, then we have a problem with labels on the screen. A UI that is intuitive by design requires us to provide very few and extremely brief tooltips for controls that are designed to be confusing or are frequently asked about. Overall, fewer tooltips mean people are more likely to read the tooltips that are provided.
Describing information that should always be visible behind a hover should not be the only place that information should be made visible. Although we are describing like that, we will tag such information so that your engineers can bring that information to the label or inline help.
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.
Mostly excellent. Your improvements to the auth section are better than what our engineers wrote. Your pagination endpoints, however, were explained in the spec according to how they behave rather than how they are, which required two revisions. Our spec is incorrect in that area as well.
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.
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.
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