Website Widget
Put a support chat on your own website: every conversation becomes a ticket in your Discord server, answered by your staff and Atlas
The website widget is a chat you add to your own website. A visitor opens it, reads your common questions or starts a conversation, and every conversation becomes a normal ticket in your Discord server. Atlas can answer first from your knowledge base, and staff reply by typing in the ticket channel. The visitor never sees Discord. It is for servers whose customers also reach them on a website, such as a store, a game server's site or a product page, so your team handles website chats and Discord tickets in one place.
The website widget needs a Pro or Enterprise plan on the bot owner's account (the Enterprise trial includes it). Only the bot owner can open its settings page; dashboard staff do not see it. Hiding Powered by TicketCord in the widget needs Enterprise. View pricing
What you need
- Pro or Enterprise on the bot owner's account. Each server has one widget per bot.
- A website you can edit, served over
https://. You paste one line of code into its pages. - A server set up with TicketCord, so new tickets have somewhere to open. Widget tickets use your server's ticket settings, or those of the panel button a visitor's topic points to (see Topics).
- Optional: a knowledge base for Atlas to answer from (AI assistant → Atlas → Sources), and your own server code if you want to sign visitors in.
Set it up
Open the Website widget page
Go to Website widget in your server's settings. Only the bot owner sees this page.
Add your websites
Under Websites, enter each website address, such as https://example.com, click Add, and save. The widget only loads on the websites you list. See Websites.
Copy the install code
The Install code appears on the first card after you save for the first time. Copy it and paste it into every page that should show the widget, just before the end of the page (before </body>). It looks like this:
<script async src="https://ticketcord.com/widget/loader.js" data-widget="wk_..."></script>Turn it on
Switch on Turn on the website widget. You cannot turn it on before at least one website is saved.
Choose the rest
Pick who can use it (Who can use it), add topics and common questions, set the look under Appearance, and decide how Atlas answers. Save after each change.
The install code is not a secret: it only names your widget, and it works only on the websites you list. The Preview card does not show a live preview yet. To try the widget before your website goes live, turn on Allow local testing and open a page on your computer that has the install code.
Change the key or sign everyone out
Open Advanced on the first card:
- Change the widget key makes a new key, so the install code changes. Websites that still use the old code stop showing the widget, and every visitor is signed out. Use it when the widget appears on a site you did not add.
- Sign out all visitors ends every visitor's session; their next visit starts a new one.
In both cases open conversations stay in Discord. Visitors who were not signed in by your website cannot open their earlier conversations in the widget again. Signed-in visitors see theirs again the next time your website signs them in.
Websites
The widget loads only on the websites listed under Websites, up to 20. Browsers refuse to show it anywhere else, so copying your install code to another site does nothing.
| Entry | What it covers |
|---|---|
https://example.com | Exactly https://example.com, not www.example.com |
https://www.example.com | Exactly that address |
https://*.example.com | Every subdomain, such as shop.example.com and www.example.com, but not https://example.com itself. Add both entries to cover both |
https://example.com:8443 | That address on port 8443 only |
Enter only the website address, without a page path. Plain http:// is refused. Allow local testing also loads the widget on http://localhost and http://127.0.0.1, on any port. Turn it off when you are done testing.
Who can use it
Under Who can use it, Show the widget to has three choices:
| Choice | What visitors see |
|---|---|
| Everyone (default) | Every visitor sees the widget and can start a conversation |
| Signed-in visitors only | Only visitors your website signs in with a token see it. Everyone else sees nothing at all, not even the launcher |
| Only when your site opens it | Hidden until your website calls TicketCord('show') (see JavaScript API) |
Signed-in visitors only needs the identity secret, so create it first (below). For a site that gets spam or abuse, it is the strongest protection: only people with an account on your site can write, and the automatic pause never applies to them.
Signing visitors in
Your website can tell the widget who the visitor is, so staff see a Verified by site name and email, the visitor's conversations follow them across devices, and you can limit the widget to signed-in visitors. Your server signs a short token for the signed-in user; your page passes it to the widget.
Get the identity secret
Under Identity secret, click Create secret (or Show secret once it exists). Only the bot owner can see or change it. Keep it on your server, never in your website's code: anyone with it could sign in as any visitor.
Sign a token on your server
Sign a JWT with HS256 and the secret for the user who is signed in on your site. Sign a fresh one when the page loads, so it never expires while the visitor chats.
Pass the token on every page
Call TicketCord('identify', { token }) on every page that loads the widget (see below). A signed-in visitor's session is only used on pages that identify that same visitor.
The token's claims:
| Claim | Required | Rules |
|---|---|---|
sub | Yes | Your own ID for this person, the same every time, 1 to 128 characters. It decides which conversations are theirs |
iat | Yes | When you signed it, in Unix seconds |
exp | Yes | When it expires, in Unix seconds, after iat and at most 24 hours after it |
name | No | Up to 80 characters |
email | No | A valid email address, up to 254 characters |
discord_id | No | The person's Discord user ID. Staff see it as a mention on the opening card |
avatar | No | The avatar hash of that Discord account, as Discord gives it to you with the user (32 characters, with a_ in front for an animated one). The widget then shows the visitor their own picture instead of their initial. Only used together with discord_id; a full image URL is refused |
fields | No | Up to 20 extra details as text, such as { "plan": "Pro" }. Keys start with a letter and use letters, digits and _ (up to 32 characters); values up to 200 characters |
aud | No | If you send it, it must be your widget key (wk_...) |
Leave out a claim you do not have: a claim set to null is refused. A token with any claim over its limit, a wrong signature, another algorithm, or an expired time is refused as a whole, and the widget then hides itself on that page (see Troubleshooting). Up to one minute of clock difference between your server and TicketCord is allowed.
The How to sign visitors in section of the dashboard has the same examples, ready to copy:
Node.js
// npm install jsonwebtoken
import jwt from 'jsonwebtoken'
const now = Math.floor(Date.now() / 1000)
const claims = {
sub: String(user.id), // required, the same for this person every time
iat: now,
exp: now + 3600, // at most 24 hours
}
// Optional: leave out what you do not have (null is refused)
if (user.name) claims.name = user.name
if (user.email) claims.email = user.email
// claims.discord_id = '123456789012345678'
// claims.avatar = user.discordAvatarHash // with discord_id: shows their picture
// claims.fields = { plan: 'Pro' }
const token = jwt.sign(claims, process.env.TICKETCORD_WIDGET_SECRET, { algorithm: 'HS256' })PHP
// composer require firebase/php-jwt
use Firebase\JWT\JWT;
$now = time();
$claims = [
'sub' => (string) $user->id, // required
'iat' => $now,
'exp' => $now + 3600, // at most 24 hours
];
// Optional: leave out what you do not have (null is refused)
if (!empty($user->name)) $claims['name'] = $user->name;
if (!empty($user->email)) $claims['email'] = $user->email;
$token = JWT::encode($claims, getenv('TICKETCORD_WIDGET_SECRET'), 'HS256');Python
# pip install pyjwt
import os, time, jwt
now = int(time.time())
claims = {
"sub": str(user.id), # required
"iat": now,
"exp": now + 3600, # at most 24 hours
}
# Optional: leave out what you do not have (None is refused)
if user.name:
claims["name"] = user.name
if user.email:
claims["email"] = user.email
token = jwt.encode(claims, os.environ["TICKETCORD_WIDGET_SECRET"], algorithm="HS256")Set iat yourself: some libraries do not add it, and a token without it is refused. Then, on your website:
<script>
window.TicketCord = window.TicketCord || function () {
(window.TicketCord.q = window.TicketCord.q || []).push(arguments)
}
TicketCord('identify', { token: '<token from your server>' })
</script>Change secret makes a new secret: tokens signed with the old one stop working at once, so update your server right away.
Details without signing in
Without a token, your page can still pass details with TicketCord('set', { name, email, fields }). They only fill in the form for the visitor, who can change them, and staff see the visitor as Not verified. A Discord ID passed this way is ignored. Use signed tokens for anything you rely on.
JavaScript API
The install code creates window.TicketCord. Calls made before the widget has loaded are kept and run in order once it loads, if you add the short queue snippet shown above before them.
| Call | What it does |
|---|---|
TicketCord('identify', { token }) | Signs the visitor in with a token from your server (Signing visitors in). Call it on every page that loads the widget |
TicketCord('logout') | Signs the visitor out. See the warning below |
TicketCord('set', { name, email, fields }) | Passes unverified details that fill in the form |
TicketCord('open') | Opens the chat panel |
TicketCord('close') | Closes the chat panel |
TicketCord('show') | Shows the widget. Needed with Only when your site opens it; it also undoes hide |
TicketCord('hide') | Hides the launcher and the panel on this page |
TicketCord('on', event, handler) | Runs your function on an event: ready (the widget loaded), open, close, or unread, which receives { count }, the number of unread replies. Up to 20 handlers per event |
Call logout only when the user really signs out of your site. It signs the visitor out of the widget everywhere, on every device and tab, and it also ends the anonymous session on that browser, so the widget starts fresh. Do not call it on page loads for visitors who are not signed in: the widget keeps an anonymous visitor's conversations on its own.
Topics
Topics let visitors pick what their conversation is about, and send it to the right place. Each topic is one of your existing panel buttons or dropdown options that opens a ticket: under Add a topic, choose a button or option. A conversation with that topic opens its ticket like that button or option would: in its category, for its staff roles, with its channel naming, its welcome design and its Atlas settings. You can add up to 20 topics and rename each one under Name visitors see (leave it empty to use the option's own name; an option with no name of its own needs one).
With topics, the visitor must choose one. Without topics, the form has no topic field and tickets use your server's defaults. A topic whose button or option was deleted, or no longer opens a ticket, shows Option deleted on the page and is not offered to visitors.
Common questions
Common questions are short answers visitors can read on the widget's home before they write. Add up to 30, each with a question (up to 120 characters) and an answer (up to 1,500 characters). Answers are plain text; a blank line starts a new paragraph. Visitors can search them, and each answer asks Did this answer your question? The dashboard shows how often visitors answered Helpful and Not helpful. No, talk to us opens the new conversation form with the question already in the message.
Appearance
| Setting | Values | Default |
|---|---|---|
| Use your own accent color | Off, or a color for buttons and the visitor's messages | Off (a neutral color that suits any site) |
| Greeting and Second line | The text at the top of the home screen (up to 60 and 140 characters) | "Hi there." ("Hi" and the name for signed-in visitors) and "How can we help?" |
| Launcher | Icon, or Icon and text with your Launcher text (up to 24 characters) | Icon |
| Position | Bottom right or Bottom left | Bottom right |
| Theme | Match the site, Light or Dark | Match the site |
| Show staff names | On: visitors see the name and avatar of the staff member who replies. Off: every reply shows your Team name and server icon | On |
| Team name | Shown when staff names are off, and as the name automatic answers appear under (up to 40 characters) | Your server's name |
| Show Powered by TicketCord | A small link at the bottom of the widget. Hiding it needs Enterprise | On |
The widget's logo is your server's icon, and its name is your server's name; both update when you save the page. There is no logo upload.
What visitors see
- Launcher. A button in the corner of the page, with a badge for unread replies. A new reply while the panel is closed shows a short preview bubble. While your page's tab is in the background, unread replies show in the tab title as
(1). - Home. Your greeting, whether the team is online, Send us a message, recent conversations, and your common questions. Signed-in visitors are greeted by name.
- New conversation. Name (required), Email (optional), Topic (when you have topics) and the message, up to 2,000 characters. Signed-in visitors see their name and email instead of the two fields. When Atlas can answer, the form says an automatic answer comes first.
- The conversation. The visitor's messages show Sending, Sent, Delivered or Not delivered with Retry. Staff replies show the staff member's name and avatar, or your team name. Automatic answers show under your team name, marked Automatic answer, with That answered it and Talk to a person. Visitors see when staff are typing and when someone joins.
- Files. Visitors can attach a file with the paperclip, or paste a copied picture or file into the message box (a screenshot, for example). Accepted: PNG, JPEG, GIF and WebP pictures, HEIC photos, MP4, MOV and WebM videos, PDFs, Word, Excel and PowerPoint documents (.docx, .xlsx, .pptx, without macros) and plain text files (.txt, .log, .csv, .json, .md), up to 10 MB each and 20 per conversation. Anything else, such as programs, archives and web pages, is refused, and the widget says This file type can't be sent. Files staff send show as downloads, and images from staff show as previews.
- Links. Web links in a message can be clicked on both sides. A link with its own text, written as
[text](address), shows the site it opens beside the text, and hovering any link shows its full address, so a visitor always sees where a link goes before opening it. - Waiting and away. After Talk to a person, the visitor sees You are in the queue. When the team is away under your business hours (Enterprise), the widget shows Away and when you are back, and the conversation still opens: Your message is waiting for the team.
- Closing. The visitor can End conversation from the menu. A closed conversation shows Conversation closed and, when Closing tickets → Ratings is on, How did we do? with 1 to 5 stars, which counts as the ticket's rating. A visitor cannot reopen a closed conversation; they can Start a new one. If staff reopen the ticket, the visitor sees Conversation reopened.
- Menu. Mute sounds (remembered on that browser), Download transcript (the conversation as a text file), Larger window and End conversation.
- Languages. The widget speaks the same 19 languages as the bot and picks the visitor's browser language, then your General → Bot language, then English. Right-to-left languages are laid out right to left.
- Light and dark. With Match the site, the widget follows your website's light or dark look, then the visitor's device. On phones it opens full screen.
The widget lists a visitor's newest 20 conversations. A visitor who is not signed in keeps their conversations on that browser only; clearing the browser's site data or using another device starts over. Signed-in visitors see their conversations on every device.
How staff reply
A new conversation opens a normal ticket: it is numbered, can be claimed, closes with a transcript like any other ticket, and is kept under your retention settings. Staff work it in Discord.
The opening card
Instead of the welcome message, the ticket starts with the Website widget card for staff: the topic as its title (New website conversation without one), the visitor's name and email with Verified by site or Not verified, their Discord account (only when your website verified it), the page they wrote from, their language, and the details your website passed under Details from the site. A line on the card shows Online now while the visitor has the widget open, or Last seen with the time once they leave. The visitor's first message follows as its own message.
The card has your ticket buttons (such as Claim and Close) and Block visitor. Change its text on the Messages page (see Website widget card), or post a welcome design instead under Opening message on the widget page: a topic's own welcome design comes first, then the one you choose there, then the built-in card. It pings the staff roles your server pings on new tickets, except outside business hours, when the ticket gets your off-hours notice instead.
Replying
Staff reply by typing in the ticket channel. The same rule as ModMail decides what reaches the visitor:
- A message from staff (the server owner, an administrator or a member with a staff role) in the open ticket's channel, with text or files, is sent to the visitor. Messages from other members, bots and Discord's own notices are not.
/noteis private: notes never reach the visitor. There is no other way to keep a message in the channel private, so do not type anything there that the visitor should not read.- Mentions reach the visitor as names. Links reach the visitor as you sent them, links to Discord too, so do not paste an address that should stay private, such as a webhook address. A link the visitor sends can be clicked in the channel; a link with its own text shows there as typed, text and address both visible.
- Editing a sent message updates it in the widget. Deleting a message removes it from the visitor's conversation, also one of the visitor's own messages.
- A ✅ reaction marks the newest staff message the visitor has seen; it moves forward as they read. A ❌ reaction from the bot means that message could not be delivered to the visitor.
- Visitor files arrive in the channel as images or files. Staff files up to 25 MB reach the visitor.
- While staff type, the visitor sees that they are typing, and while the visitor types, the bot shows as typing in the channel.
The visitor never sees the channel, the ticket number or staff member IDs. Close the ticket as usual; the visitor sees it closed. When the visitor ends the conversation, the ticket closes with the reason Closed by the visitor; That answered it closes it with Resolved by the visitor. No close message or rating request is sent by DM: the visitor has no Discord account in the ticket.
Block a visitor
Block visitor on the opening card stops a visitor from using the widget, after a confirmation. It is for staff of the server. It blocks the visitor's browser identity, their signed-in account on your site if any, the email address they gave if any, and, for visitors who were not signed in, their network, so other visitors who are not signed in on the same network are blocked too. A blocked visitor no longer sees the widget and gets no more replies. They are not told they are blocked.
Blocked visitors are listed under Blocked visitors on the widget page, newest first, by name and kind (Visitor, Signed-in visitor, Email address, Network) with the date; click Unblock to lift one. A server can block up to 500 visitors.
Automatic answers and tokens
Atlas answers widget conversations from your knowledge base the same way it answers in tickets, under your settings on AI assistant → Atlas → Answer questions in tickets, and hands the conversation to staff when it cannot help or the visitor asks for a person, as on Discord tickets. The answer is posted in the ticket channel for staff too. The widget page has its own switches under Atlas in the widget:
| Setting | What it does | Default |
|---|---|---|
| Let Atlas answer visitors | Off: every conversation waits for your team | On |
| Answer visitors who are not signed in | Off: Atlas only answers visitors your website signs in | On |
| Daily token limit | The most tokens all automatic AI on this widget's conversations may use in a day | 300,000 |
Atlas also stays silent on a topic whose panel option keeps Atlas out, and when your account is out of AI tokens. Silent means staff simply have the ticket: the visitor sees no error, and their message waits for the team.
What it costs. Every automatic AI feature on a widget conversation uses the bot owner's AI tokens, like on any ticket: Atlas answers, the ticket summary card, and priority, duplicate and tone checks. Three daily limits keep that in check, and they reset at midnight UTC:
| Limit | Tokens a day |
|---|---|
| The widget's Daily token limit (you set it) | 300,000 by default. Enter 0 or at least 49,000, up to 100,000,000 |
| Each visitor | 150,000 |
| All visitors who are not signed in, on one network together | 300,000 |
An answer starts only when every limit that applies still has room for it: 49,000 tokens, or 60,000 when the visitor's message has a screenshot (4,800 more for each further image, up to three). Only what the answer really uses is counted afterwards. That is why a limit between 1 and 48,999 cannot be saved: it could never answer. 0 turns off every automatic AI feature on widget conversations, not only Atlas answers. When a limit is used up, these features pause until the next day and conversations wait for your team.
Limits
| What | Limit |
|---|---|
| New conversations | 10 a day per visitor, 10 a day per network for visitors who are not signed in, 500 a day per widget |
| Open conversations per visitor | 3. A new message beyond that is added to the visitor's newest open conversation |
| Messages | 20 a minute and 200 a day per visitor, and the same per network for visitors who are not signed in |
| Message length | 2,000 characters |
| Files from visitors | Pictures (PNG, JPEG, GIF, WebP, HEIC), videos (MP4, MOV, WebM), PDF, Word, Excel and PowerPoint documents without macros, or plain text; 10 MB each; 20 per conversation |
| Files from staff | 25 MB each |
| Websites | 20 |
| Topics | 20 |
| Common questions | 30 (question 120 characters, answer 1,500 characters) |
| Details your website passes | 20 per visitor, 200 characters each |
| Blocked visitors | 500 per server |
| Conversations listed to a visitor | The newest 20 |
Automatic pause
When more than 5 attempts to start a conversation come from one network within 10 minutes, the widget pauses that network: nobody on it can start a new conversation for 1 hour. If it happens again within a day, the pause lasts 24 hours. The pause is per widget and applies only to visitors who are not signed in: everyone behind the same address (a household, an office, a school) shares it, and signed-in visitors are never paused. The visitor sees Chat is paused. and roughly when they can try again when they start a new conversation; conversations they already have keep working. A pause cannot be lifted from the dashboard; it ends by itself. If your site gets abuse, set Show the widget to to Signed-in visitors only.
Privacy and data
What TicketCord keeps about a visitor, for their widget only:
- The name and email address they typed or your website signed (the email address is stored encrypted), and whether your website verified them.
- For signed-in visitors: your
subID, the Discord ID and the details your website signed. - Their language, when they were first and last seen, and the last page they wrote from. Page addresses are kept without the part after
?or#, so sign-in codes in links are never stored. - For visitors who are not signed in, their network as a one-way code, never the address itself, used for limits, the pause and blocks.
- The conversation itself, which is the ticket's content: it follows your server's retention settings like any ticket. In the ticket's transcript, the opening card shows the visitor's email address hidden.
Blocks store one-way codes of what was blocked and the visitor's name as its label, never the email address or the network itself. Sign out all visitors ends every session (see Change the key or sign everyone out). Your website must tell its visitors about the chat in its own privacy policy, like any other tool it uses.
When a bot is disconnected, its widgets, visitors and blocks are deleted. Reconnecting TicketCord after a RestoreCord restore into a new server moves the widget with the same install code. Your data export includes your widget settings and blocks.
If your plan changes
When the bot owner's plan no longer includes the website widget, the widget stops loading on your websites, and its settings page is locked. The settings, visitors and blocks are kept, and the widget comes back with the same install code when you are on Pro or Enterprise again. Tickets already opened stay in Discord. On Pro, Powered by TicketCord always shows, even if it was hidden on Enterprise.
What is not included
- No email after the visitor leaves. Replies reach the visitor only in the widget. A visitor who closes the page sees your reply when they come back to your site on the same browser, or on any device if they are signed in.
- No logo upload. The widget shows your server's icon.
- No reopening by visitors. A closed conversation stays closed for the visitor; they start a new one.
- One widget per server, and no custom CSS.
- No live preview yet on the settings page. Use Allow local testing.
- Signed-in visitors only shows nothing to signed-out visitors: there is no sign-in prompt in the widget.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| The widget does not appear | The widget is off, or the page's address is not in Websites exactly. https://*.example.com does not cover https://example.com, and www.example.com is a different address | Turn it on, and add the exact address of the page (without the path) |
The widget does not appear on localhost | Allow local testing is off | Turn it on while you test |
| The widget does not appear after the key was changed | The page still has the old install code | Copy the new Install code into your pages |
| The widget does not appear on one site only | The site's Content Security Policy blocks it | Allow https://ticketcord.com for scripts, frames and connections (script-src, frame-src and connect-src) |
| The widget does not appear for signed-out visitors | Show the widget to is Signed-in visitors only | Expected. Choose Everyone to show it to all visitors |
| The widget does not appear until a button is clicked | Show the widget to is Only when your site opens it | Call TicketCord('show') where it should appear |
The widget disappears after identify | The token was refused: wrong or old secret, exp more than 24 hours after iat, no iat, an expired token, a claim set to null, or a claim over its limit | Sign with the current identity secret and the claims in Signing visitors in, and sign a fresh token on each page load |
| The widget disappears for one visitor | Staff blocked them, or their network | Unblock them under Blocked visitors if it was a mistake |
| Staff see Not verified | The visitor was not signed in with a token, or your page used set instead of identify | Sign the visitor in with identify |
| A visitor sees Chat is paused. | More than 5 attempts to start a conversation came from their network in 10 minutes | Wait for the pause to end (1 hour, or 24 hours when it happens again within a day). Signed-in visitors are never paused |
| Atlas does not answer | Let Atlas answer visitors is off, the visitor is not signed in and Answer visitors who are not signed in is off, the topic keeps Atlas out, a daily limit is used up, the account is out of AI tokens, or Atlas would not answer the same question in a ticket | Check the Atlas in the widget card, your AI tokens on AI usage, and your knowledge base |
| A staff reply has a ❌ | It could not be delivered to the visitor | Send it again. If it keeps failing, contact support |
| A staff message did not reach the visitor | It was sent by someone without a staff role, or as a bot | Reply as staff (the server owner, an administrator or a staff role) |
Block visitor says the server has blocked the most visitors it can (TC016) | 500 blocks are in place | Unblock some under Blocked visitors |
Block visitor says the ticket came from a widget this server no longer has (TC004) | The widget was moved or removed since the ticket opened | Nothing to block from this ticket |
Block visitor says the visitor could not be blocked (TC000) | A temporary problem | Try again in a minute |
Common questions
Which plans include the website widget?
Pro and Enterprise, on the bot owner's account; the Enterprise trial includes it too. Hiding Powered by TicketCord in the widget needs Enterprise. Automatic answers use the owner's AI tokens.
Do visitors need a Discord account?
No. Visitors chat in the widget on your website and never see Discord. Your staff answer in the ticket channel in your server.
Can visitors see what staff write in the ticket channel?
Yes, every message staff send in the open ticket's channel reaches the visitor, as with ModMail. Use /note for anything private: notes never reach the visitor.
Is the install code a secret?
No. It only names your widget, and the widget loads only on the websites you list. The identity secret is different: keep it on your server and never put it in your website's code.
How much does Atlas cost on the widget?
It uses the bot owner's AI tokens like any ticket. The widget's Daily token limit (300,000 by default) caps all automatic AI on widget conversations each day, each visitor can use up to 150,000 a day, and visitors who are not signed in share 300,000 a day per network. Set the limit to 0 to turn automatic AI off on the widget.
Why did the widget pause a visitor?
More than 5 attempts to start a conversation came from their network within 10 minutes, so nobody on that network can start a new conversation for 1 hour (24 hours when it happens again within a day). Conversations they already have keep working. It only affects visitors who are not signed in, and it ends by itself. Limit the widget to signed-in visitors if your site gets abuse.
Does the visitor get an email when staff reply?
No. Replies reach the visitor only in the widget, the next time they open your site. Signed-in visitors see their conversations on every device.
How do I stop someone from spamming the widget?
Press Block visitor on the opening card of their ticket. For repeated abuse, set Show the widget to to Signed-in visitors only, so only people with an account on your site can write.
How Atlas answers and what it can do
Ask for help setting up your widget
Was this page helpful?
Last updated on