Guides
There is a lot written about care and almost nothing about the small mechanical problem underneath it: how somebody asks for something, and how that request reaches a person who can do it. That gap is what we know about, so it is what we write about.
These are meant to be useful whether or not you ever use our product, and they are free to quote, link and print. Where we are not the right people to ask, each one says so and says who is.
-
When asking stops
Requests get quieter long before anyone notices, and it reads as good news. What makes asking expensive, and what brings it back.
-
Suggesting a button
Most refusals are of the terms, not the help. What is usually being refused, and what can be offered instead.
-
Wording a button
Why “Assistance required” goes unpressed and “Come and chat” does not, and how to write the four or five that earn their place.
-
Deciding who goes
When three people could answer, often none does — and sometimes all three do. What actually fixes it.
-
Notification reliability
Nine reasons a phone stays silent, in the order they are likely, and what to test before anyone depends on it.
-
Low vision and tremor
The measurements we hold ourselves to, published in full, and why the usual accessibility minimums are far too small here.
More will follow. If there is something you keep having to explain to people and cannot find a decent page to send them, write to hello@gobuttons.app — that is a better guide topic than anything we would come up with unprompted.