A support thread rarely stalls on the answer. It stalls on the three messages it takes to establish which screen you are looking at. A screenshot and the address of the page you were on skip those three messages, and both can go into the ticket you open from inside your account. Any signed-in account can open one, free or paid. The priority support over WhatsApp that comes with the Excellence plan is a separate route with separate rules, and it is not what this guide covers.
Why a thread takes three exchanges instead of one
Picture the message most people send first: “The RSVP button is not working.” Now read it from the other side. Which invitation. Which page, the live invitation or the preview in the builder. Which phone. What happens when you press it - nothing at all, an error message, a spinner that never stops. Was the guest on their own link or on one that had been forwarded to them. Every one of those is a question, and every question is a round trip.
Tickets are typically answered within one business day, so each of those questions costs roughly a day of the calendar, and longer if your answer lands after we have finished for the evening. Two of them and the invitation you meant to send this week is still sitting there. The fix is not to write more. It is to answer the obvious questions before anyone has to ask them.
What to put in the first message
Four things, in any order, and the ticket usually gets answered on the first reply rather than the fourth.
- What you expected to happen. “I expected the guest to see their own name at the top.”
- What happened instead, quoted rather than summarised. “Something went wrong” is a category. The exact line of text on the screen is evidence.
- Which invitation. The name you gave it, or its link.
- Which device and browser. A three-year-old phone and a current desktop browser do not draw the same page the same way, and a link opened inside WhatsApp rather than in the phone’s own browser is different again.
Two more help when they apply: when it started, and whether it happens every time or only sometimes. A fault that appears once in five attempts is a different fault from one that appears always, and saying which can save an entire exchange on its own.
Give the subject line the same treatment. “Help” and “Urgent” carry no information. “Guest name missing at the top of the invitation on iPhone” tells us where to start before anyone has opened the ticket.
The screenshot does the work of a paragraph
Capture the whole screen rather than a crop of the part that looks wrong. The parts you would trim away are usually the parts that identify the problem: the address in the bar, whether you are signed in, which section of the builder you are in, how wide the window is. A tight crop of a button tells us that a button exists.
You can attach images when you open the ticket and on any reply afterwards, up to four per message, as JPEG, PNG or WebP. Images only, so a screen recording will not upload. That matters for one kind of problem: anything that only reveals itself while something is moving. Music that cuts out partway through. A page that jumps as it scrolls. A countdown that reads wrong for a second and then corrects itself. A still frame cannot show any of those, so write the sequence out in order instead. What you did, what you saw, how long it took.
If the problem is on a guest’s phone rather than yours, ask them for the screenshot. It feels awkward and it is not. “Can you send me a photo of what you see when you tap the link” is an ordinary thing to ask the cousin who told you the button did nothing, and it is far quicker than the two of you describing a screen to each other over the phone.
The page address is half the answer
Copy the address out of the browser bar and paste it into the ticket. In a screenshot the live invitation and the builder preview can look identical, and one guest’s personal link looks like every other guest’s. The address separates them. It says which invitation, which page of it, and whether you were looking at what a guest sees or at what only you can see. It is one paste, and it removes the most common clarifying question there is.
Following the thread without losing it
The ticket lives on the Support page in your account, with everything attached to it. When someone replies, you also get an email with a link straight back to the thread, so you can follow it in your inbox or in the account, whichever you happen to have open. Replies stay on the ticket rather than scattering across a chat, which is what you want two weeks later when you cannot remember what you were told.
Each ticket carries a status you can see: open, awaiting reply, resolved, closed. If it is waiting on you, that is where a thread goes quiet for a week without anybody intending it to. Set the priority honestly, too. There is an urgent option, and it is worth something only while it is kept for the invitation going out this afternoon rather than for a question about wording.
When a ticket is not the fastest route
Often it is not. If the change is one you can make yourself, a date, a name spelled wrong, a line of wording, then make it. Guests keep the same links, so there is nothing to resend and nothing to wait for. Opening a ticket to ask whether you are allowed to edit your own invitation buys you a wait and nothing else.
Some problems are not ours to fix, and it is fairer to say so than to let you wait. If a guest’s phone is old enough that the invitation renders badly, we can tell you what is happening, but we cannot change their handset. If an office network blocks WhatsApp, that is their network. And if a guest has simply not replied, that is not a support problem. It is a person who needs a nudge, and no ticket produces one.
The ticket form sits inside the account, so an account is the one thing it needs. Before you have one there is no thread to attach a screenshot to, and the contact page reaches the same people instead. It is also where the questions that come before a ticket belong: what sits inside each plan, how guest numbers are counted, or whether an invitation that lives on a phone suits the kind of day you are planning at all.
Frequently asked questions
Do I need to have paid to open a support ticket?
No. Any signed-in account can open one, free accounts included. There is no plan level that switches tickets on. Priority WhatsApp support is the part that is Excellence only, and it is separate from tickets.
How many screenshots can I attach?
Up to four images per message, as JPEG, PNG or WebP. A reply counts as a message, so a longer thread can carry more than four in total. Video does not upload, so describe anything that only happens while the page is moving.
What if I cannot sign in at all?
Then there is no account to raise a ticket from. Use the contact page instead, and say which email address you signed up with so we can find you.
Related: Contact us