Canned Responses

What it does

Stores the replies your team sends over and over — deposit timing, withdrawal timing, how to send a document — so nobody retypes them. An operator drops one into a chat by typing / in the message box, and Chat Automation can send one on its own when you have set up a rule for it.

Each response has several wordings per language. Legion picks one, and two players asking the same question do not get a byte-identical answer.

A response is only usable once it exists in every language your site serves (set in Web Settings): a site serving Indonesian and English needs those two, and never Thai or Lao. That is deliberate: a player who writes to you in their own language should not be answered in someone else’s.

New Indonesian-language sites start with a ready set of replies in Indonesian and English. Edit, retire or add to them freely. Some start as Draft. A draft with a blank such as {{isi.link_rtp}} needs your own details: your RTP page, promotions, togel prizes, withdrawal time. Replace the blank with your text before you can save it and turn on Live. The site link reply is live from the start: it sends the site the player is chatting on. The other drafts are true only on some sites, such as the bank-transfer deposit form, or state something only your team can know, such as a disruption or a form you cancelled. A live reply is open to every assistant rule with an empty list, so turn one of these on only while no such rule is live, and off again once it stops being true. None of them goes to a player on its own until you set up Chat Automation. From then on a rule sends the replies it names, an assistant rule with an empty list chooses from all your live replies, so edit or retire these first, the assistant sends the Handover reply when it passes a chat to your team, and replies the assistant writes itself take their tone from all your live replies.

Where to find it

Support -> Canned Responses

Common tasks

1. Click New response.
2. Give it a code — this is how you and your rules refer to it. Lowercase, no spaces, for example withdraw_eta.
3. Give it a name and a category, so it is easy to find later.
4. Write a description: when this reply fits. The assistant reads it to choose.
5. Pick its kind, and any record checks it depends on.
6. Write the wording under the en tab. Add a second wording if you would like some variety.
7. Do the same under id, lo and th.
8. Turn on Live, then Save.

The Live switch stays greyed out until every language your site serves has a wording and the description is written, and the page tells you what is still missing.

The description

The single biggest lever on how well the assistant chooses. It never sees your wording when it decides - it reads the description, so say when the reply fits, not what it says.

• Weak: Deposit info.
• Strong: The player says they paid but the balance has not changed, and the record shows the deposit still pending.

A response cannot go live without one; only a Handover response, which the assistant never chooses, may leave it empty.

Kinds

• Answer - an ordinary reply.
• Comfort - sympathy for a player who is venting. Capped per visit in the assistant settings; past the cap no more comfort replies are sent, and venting with nothing new in it may be left unanswered.
• Please wait - asks the player to wait while you check. Capped per visit in the assistant settings. Past the cap a chase moves on to the reason and last-line replies; with a cap above 0, a player asking about another matter still gets one.
• Handover - what the player reads when the assistant hands the chat to your team. It is never offered to the assistant as a choice; it is sent by the handover itself, together with an internal note telling your team why. With no handover response, the handover is only the note.
• Asks for something - asks the player for what a check needs, all in one message.
• Why it takes a while - after the please-wait replies, or at once when the player asks why: the reason, in plain words.
• Last line of a wait - closes a wait. After it no please-wait, reason or comfort reply goes out until a reply states a new status, such as the deposit landing, but for the first line on another matter. It needs a please-wait or reason reply first.

A player who keeps chasing with nothing new is left unanswered once these have gone. The third such chase in a visit is handed to your team, once.

Record checks

A reply such as “your deposit has arrived” is only true if the player’s record shows it. Under Only when the record shows, tick the checks the reply assumes - for example A recent deposit completed. The assistant may send it only when every ticked check holds.

Some checks compare an amount the player typed against the record (The deposit they mention is on record / is not on record). The assistant never repeats the amount; a claim the record does not back sends no reply, and is named in the note your team reads when the chat is handed over.

A QR deposit the player has not paid yet is never A deposit is being processed: tick A QR deposit is waiting to be paid for a reply that tells them to pay the QR before it expires or start a new deposit.

Leave the checks empty for a reply that says nothing about the player’s money.

When the player states an amount, only the deposits or withdrawals that match it count for every check on the reply, ticked or not. A withdrawal of 100,000 paid yesterday says nothing about the 500,000 they ask after, so “your withdrawal was sent” is not sent. A withdrawal may differ from the amount they state by its fee.

Most times per visit

How often the assistant may send this reply in one visit. Empty means once, and 0 means no limit. Once used up, the assistant no longer picks it first in that visit; the last ask before a handover may still use it, but for a chase past the waiting lines. A reply with several wordings uses a different one each time, so a limit above 1 reads best with more than one wording.

A please-wait reply usually has 0 here: Please-wait replies per visit on the assistant page is what limits it.

Asks the player for

Say which amount this reply asks the player for. When another reply needs that amount (it requires a check such as The deposit they mention is on record) and the player has not stated it, this reply goes first, once a visit. A reply cannot ask for what it already assumes.

Record no older than

Limit a reply to a recent deposit or withdrawal: “your deposit landed” with 6 here is not sent about one asked for 7 hours ago. Hours count from when it was asked for, 1 to 72. It needs a record check to act on, and tightens only: the assistant reads the last 72 hours.

Replies in parts

A blank line in a wording splits it into separate messages, each typed in turn, up to 3. If the player writes before the last one, the rest are not sent. A single line break stays inside one message.

Using variables

Type {{player.name}} and Legion fills in the player’s name when it sends. Click any of the chips under the message box to insert one - the list is the complete set, and anything else is refused when you save. In Support Inbox the variables the inbox knows are filled in as the response goes into the reply box; one it cannot fill stays as written, so you see it before you send.

{{coin.name}} is your coin’s name in the language the response is written in, as you set it on Coin Economy.

{{site.domain}} is the address of the site the player is chatting on, without www. or another prefix when you have added that shorter domain too: someone on www.yoursite.com is sent yoursite.com. Until the player’s chat has connected once, a reply that uses it is not sent automatically.

Deliberately not available: balances, amounts, email addresses and phone numbers. A figure quoted in an automated message becomes an argument later, and a canned reply is text you are sending to someone you have not spoken to yet.

The length meter

Under each box is a byte count. It counts bytes, not characters, because Thai and Lao take three bytes per character. A message that looks comfortably short in English can be over the limit in Thai — the meter is there so you find that out while writing rather than when it fails to send.

Retiring a response

Click Retire. If a live rule still points at it, Legion refuses and names the rule — change or switch off that rule first. This is on purpose: silently retiring it would leave the rule looking fine while quietly sending nothing.

Retiring frees the code, so you can reuse it on a new response.