What a reply can and cannot be
There is no guaranteed response time. The inbox is read by a person, not by a status board with a clock. A clear report is more likely to be understood than a long one that never says what broke. Silence is not a confirmation that a feature will be built, and a polite reply is not a contract to implement a change by a date. The terms explain that the tool is free and may change or be discontinued. A conversation about a bug does not create a service-level agreement.
Some messages cannot be answered by looking in a database, because the relevant database does not exist. The grid is saved only in your browser. Exports are generated on your device. If the mail says "please send me the inventory I made on the library computer," there is nothing to send. The practical help is to explain how local storage works and to point you to the privacy page. That feels like a refusal. It is a description of where the bytes are.
Tabley also cannot see your screen while you type. A sentence such as "the color is wrong" needs the color you expected, the color you got, and whether the low-contrast warning was showing. A sentence such as "export failed" needs the format you chose and whether the rest of the page still responded. The sections below are a support article for writing that kind of mail the first time, so you do not lose an evening to a second round of questions.
Report a bug so it can be reproduced
A bug is a behavior that contradicts the product: a button that does nothing, an export that will not download, a paste that lands in the wrong place, a header mode that does not match its label, a language that shows the wrong direction, or a help page that describes a control the screen does not have. A wish for formulas is not a bug. A wish for more than 12 columns is not a bug. Those are requests, and they belong in the feature section further down, with an honest understanding that the grid limit is deliberate.
Start the report with one sentence that names the failure. "PNG export does nothing after I click, in Firefox on a laptop" is a start. "Tabley is broken" is not. Then give the steps in order, from a state a stranger can reach. Say whether you began from a blank grid or from a named template, such as the gradebook or the weekly schedule. Say what you clicked, what you typed, and what you expected to see instead. If the problem appears only after paste or only after import of a CSV, say that, because those paths are different from typing.
Include the browser and the kind of device. "Chrome on Android" and "Safari on a desktop" are different debugging worlds. Include the interface language you had selected, especially if you were using Arabic, because the layout is right to left and a screenshot from a left-to-right assumption can mislead both of us. Mention the approximate grid size if you were near 40 rows or 12 columns. Limits are a common source of "the button ignored me," and it helps to know whether you had already reached the ceiling.
Say what you already tried. A reload, a second browser, a smaller grid, and a different export format are useful facts. "JPEG works, PDF does not" narrows the problem more than a list of adjectives. If the page showed a failure note, quote it. The export path can surface a short error when a file cannot be prepared, and the exact words matter.
What to attach, and what to leave out
A screenshot helps when the issue is visual: contrast, borders, a stripe that seems to cover the header, alignment, or a caption that collides with the grid. Capture the table and the control you used, not only the finished cells. Crop out unrelated browser tabs if they contain other people's information. If you annotate the image, use a plain circle, not a rewrite of the text that hides the original bug.
Do not attach a real class list, a patient roster, a full customer file, or passwords. The editor never needed those to demonstrate a layout bug. Replace names with "Student A" or rebuild the smallest grid that still fails. If the bug is "paste destroys characters in our actual CSV," you can often reduce the file to two rows that contain the odd character, such as a quote or a line break, and send that toy file. A minimal CSV is a better attachment than a live export of everyone in the building.
If you cannot reproduce the problem without the real text, say so, and describe the shape instead: how many rows, which column has commas, whether cells contain line breaks from Shift+Enter, whether you used mono type, whether a fill was set on the whole column. Those details are often enough. You can also offer to try a specific test and report back. That is slower, and it is safer than mailing sensitive cells to an inbox that exists to fix software.
Mention whether the draft is still in the browser. If you can still undo, note whether undo restores the previous state. If local storage seems empty after a crash, say whether you had exported anything. Do not send the only copy of an important file as an attachment and then delete your local one while you wait. The inbox is not a backup, and a reply might not arrive the same day.
Editorial corrections
The help center is part of the product. A wrong description is a defect even if the button itself works. If a page tells you that a control behaves one way and the screen does another, write with the page name and the sentence. "On the features page, the paragraph about header modes says both headers color the corner, but I am seeing something else" gives an editor a place to stand. "Your docs are confusing" does not.
Corrections are welcome for typos, for steps that are out of order, for template descriptions that do not match the sample columns, and for translations of meaning when an English page and another language seem to promise different tools. Tabley publishes help in English, French, Spanish, Portuguese, German, Norwegian, Arabic, and Japanese. If you read more than one, you are in a good position to notice a drift. Quote both sentences. A correction does not need a screenshot unless the issue is the site chrome rather than the prose.
Also write when a page is technically accurate and still misleading. For example, a new user might think Excel export means a macro-enabled workbook, when the format is Excel (.xls) as a data table, not a programming environment. If a sentence pushed you toward that mistake, say which sentence. The fix is often a clearer clause, not a new feature. The tips and templates pages are especially worth correcting, because people follow them while they work and a bad example becomes a bad table.
Do not send a rewrite of an entire page as a demand. A suggested paragraph is useful. A claim that the help must rank for a particular advertising goal is not something the editor will chase. The standard is whether a careful reader can operate the tool without surprises.
Feature requests that can be evaluated
A feature request should name the job, not only the button. "Add formulas" is a direction that would turn the product into a spreadsheet, which the about page says it refuses to be. "I want the total row of invoice lines to show a sum I typed by hand, and I wish the caption could include the currency symbol more visibly" is a request about presentation that fits the tool. You may still be told no. You will at least have been understood.
Include who hits the limit. A teacher who needs a thirteenth column for a term's quizzes is a different story from a request for unlimited columns "because databases have them." The ceiling of 40 rows and 12 columns is part of keeping tables printable. A request to raise it should explain the reader who would still succeed with a wider grid on paper or on a phone. If the honest answer is that the data belongs in a workbook, the request can say that too. You might be asking for a better handoff, such as clearer CSV import notes, rather than a bigger grid.
Useful requests often look small from the outside. Examples that fit the current design include a clearer empty state, a template whose sample text is a better teaching tool, a border weight that is easier to see in print, or a note in the interface when paste is clipped because the grid cannot grow past the maximum. When you write, say whether you have a workaround today. Workarounds teach the publisher how people actually finish the job.
Requests that fight the privacy design need a stronger reason. "Please store my tables in an account" changes the product from a local editor into a host of other people's content. That is not a skin change. If you ask for it, acknowledge the privacy consequences you are willing to accept. Requests for live co-editing raise the same class of issue. They are not forbidden topics. They are topics that contradict the current refusal, so they should be framed as a reconsideration, not as a bug.
Before you write, check the likely causes
Many letters are solved by a limit or a habit rather than by a patch. If add-row or add-column seems dead, count the grid. At 40 rows or 12 columns the control cannot add another. If a row will not disappear, you may be on the last remaining row. The grid does not collapse to zero. If paste looks short, you may have started the paste in a cell too far to the right, so the block had no room before the last column. Select the top-left cell of the destination and try again.
If colors look faint, read the low-contrast warning and try a darker text color or a different fill. Header fill and header text are separate from body fill and body text. A stripe color is separate again. Painting "all cells" does not replace the header's own colors. That surprise is common and it is described in the features guide. Checking it saves a mail.
If the draft vanished, ask whether the browser, the profile, or the device changed. Local storage does not follow you. Private windows may drop it. A cleared cache drops it. An export you already downloaded may still be in your downloads folder even when the editor looks new. Search for that file before you assume the work is gone.
If the contact button does nothing, the usual cause is the missing mail handler described at the top of this page. The form is not a chat widget. It will not show a green "sent" banner after a server accepts the text, because no server accepts the text. Either your mail app opens or you need to write hello@tabley.online manually.
Privacy of the message you send
Email you send can be read by the person who handles the inbox and may be kept long enough to fix the issue and to see whether it comes back. Do not expect the message to be anonymous. Your address is on it so a reply can exist. The table editor does not attach your grid automatically. Anything sensitive in the mail is there because it was typed or attached.
Please omit government identifiers, payment card numbers, and health details even if they appear in a table you were building. A bug in border weight does not need them. If a privacy question is about a hypothetical roster, describe it as a hypothetical. The privacy page already covers local storage, on-device export, the absence of an account, and the possibility that a future Google AdSense script could set cookies. The ads.txt publisher id is ca-pub-9824879170988442. You do not need to repeat that id in ordinary bug mail unless your question is specifically about advertising.
If you are writing on behalf of a school, a clinic, or a company and you need a formal statement, say that in the first line and name the question precisely. The honest answer may be "the product does not offer that contract or that certification." Getting that answer quickly is better than a vague exchange. Tabley will not invent a street address or a registration number to satisfy a form. If a procurement form requires those fields, this tool is probably the wrong category of vendor, and the about page explains the category it does occupy.
A simple structure you can copy
You can paste this shape into the message field and fill it in. It is a guide, not a form the site validates.
What happened, in one sentence.
What you expected instead.
Browser, device, and interface language.
Template or blank grid, and approximate rows and columns.
Steps, in order.
Whether export, paste, import, print, or ordinary typing was involved.
What you already tried.
Whether a screenshot is attached, and confirmation that real people's private data is not in it.
That structure is enough for a bug. For a feature, replace the steps with the job you are trying to finish and who reads the finished table. For a correction, replace them with the page, the sentence, and the wording you think would not mislead. For a privacy question, name the data you care about, such as cell text, cookies, or email, so the reply does not wander.
Then send it to hello@tabley.online, either through the button that opens your email app or from your own mailbox. Keep your own copy. If you write again about the same issue, quote your earlier description so the thread can be matched by content rather than by a ticket number that was never issued. That is the whole of the support system, and it is enough when the letter carries the facts the product can actually use.