There is no ticket robot, no chatbot and no help centre that loops you back to this page.
Best for anything that is broken. Open TabsPack, go to Support, and write. It attaches five lines saying which browser and version you are on, which is usually the thing we would have had to ask for.
You see the whole message before it goes, and you can switch the diagnostics off. Nothing about your tabs is in it, ever.
support@palworks.ai for anything at all: a question, a feature you want, a file that would not import, or a licensing question for your organisation.
If it is a file that would not import, attaching it helps enormously. Have a look at it first, since it contains the addresses of the tabs it holds.
Best for anything you would like other people to be able to find and add to: a bug, a format TabsPack should read, a browser behaving strangely.
Open an issue. There are templates for a bug, a feature and an import format that did not work.
Please do not open a public issue. Write to security@palworks.ai and give us a chance to fix it first. Full details are on the security page.
A file would not import. TabsPack works out what a file is by reading it, not by its name, and it says what it found. If it refused, the report usually names the reason on the line it happened. Send us that line and the file if you can.
Firefox says the add-on "appears to be corrupt". It is not. Release Firefox
refuses to install any extension that Mozilla has not signed, and reports it with that unhelpful
sentence. Until the listing is live, use about:debugging and Load Temporary Add-on, or
Firefox Developer Edition. The FAQ has the steps.
Add you to a mailing list, pass it to anybody, or keep it for any purpose other than answering you. There is no marketing automation here to put you into. The privacy policy describes exactly what happens to a support message.
TabsPack