Nectarblocks now has a full support ticket portal built into the app. You can open a ticket, read the whole back-and-forth with our team, reply with a screenshot attached, and see each ticket’s status, all from your account instead of your inbox. It is live now for anyone signed in to their Nectarblocks account, and there is nothing to install.
Opening a ticket was always the simple part. The conversation that followed lived in email, a thread in your inbox a tab away from the app you were working in.
Now that thread lives in the app too: the ticket, its history, and your replies in one place. Email still arrives, the same conversation in a second window, so you can pick it up wherever you happen to be.
See every ticket and its history in one place
The support area opens as a list of your tickets. Across the top are four filters, All, Open, Awaiting reply, and Resolved, each with a live count; a search box matches on a subject or a ticket number; and the rows line up under Ticket, Subject, and Last activity columns, the way a table would.
Open a ticket and the list does not disappear. It folds into a left rail beside the conversation, so the thread you are reading and the rest of your history stay on screen together. The open ticket lives in the URL /support/tickets/${id}, so a deep link or a refresh reopens the same one.
Reply, attach a file, and resolve it without leaving the app
A ticket opens into the conversation itself: your messages and our team’s replies as bubbles, each with an avatar, an author, and a time, split by a divider when the day changes. Under the thread sits a reply box with a rich editor and a paperclip for attachments. Files upload the moment you pick them, so nothing waits for the send.
A reply here is a real ticket comment, the same one our team works from, and it still reaches you by email. Answer that email and it continues this same conversation. The app and your inbox are two windows onto one thread.
When your issue is handled, Mark as resolved closes it out, and a later reply reopens it. The one exception is a fully closed ticket: it cannot take new replies, so the app points you to open a new one and reference the old number.
Open a new ticket with the right details up front
The New Support Ticket form asks for what actually helps us answer fast. You pick a Category, give a Version and a Subject, and write the details in the same editor the reply box uses. A Website Details section takes your site URL and hosting provider, and two sections stay collapsed unless you need them, WordPress Access and FTP Access, for the times an issue needs someone to log in or dig at the file level. Most tickets never open them, which is the point.
A sidebar card shows whether support is covered. With Nectarblocks that means an active subscription: billing and account questions are always open to anyone, and technical topics need coverage, which the support policy spells out and an active subscription provides. Submit, and you land inside the new conversation rather than back at the list.
What else changed
A few smaller touches. The avatar on your own messages is the one from your account button in the navbar, so “you” in the thread looks like you everywhere else. Attachments are handled without storing anything: each file goes straight to the helpdesk and its token travels with the message.
Where to find it
There is nothing to update. The portal is part of the app, so it is already there the next time you sign in and open Support.
The next time a Nectarblocks site misbehaves, the fix starts the same way it always did: open a ticket. What changed is everything after. Instead of hunting your inbox for the last reply, you open the app, see the whole thread, and answer in the same box you filed from. Email still works. It is just no longer the only place the conversation exists.