Transcripts

When a ticket closes, your bot always attaches the conversation as a TXT file, in your ticket log and in the direct message to the member. The Transcripts tab adds a private web page of the conversation, with a link posted alongside the TXT file. You can also show those pages on your own web address instead of ours.

Transcript links are the HTML transcripts add-on, added from your bot's page under Add-ons and setup. Without it, tickets close with the TXT file only and this tab offers the add-on. If the add-on ends, links stop opening; links that have not yet expired open again if you add it back.

Changes on this tab do not restart your bot. They apply from the next ticket that closes.

Post a transcript link when a ticket closes

Tick this box to turn transcript links on, then press Save changes.

  • On: when a ticket closes, the bot saves a web page of the conversation and adds its link to the Ticket closed card in your ticket log and to the direct message the member gets. The TXT file is still attached as well.
  • Off: tickets close with the TXT file only. Turning links off also stops old links opening: anyone who follows a link sent earlier sees a "Transcript not found" page. If you turn links back on, links that have not yet expired open again.

A ticket still closes normally, with just its TXT file, if a transcript page cannot be saved, for example because it is too large or your bot's transcript storage is full.

Transcript pages are stored with your bot's other data, and are deleted with it if your plan ends. See Overview.

Links are kept for

Each transcript page is kept for 30 days after its ticket closes, or a year with the Transcripts kept for a year add-on, which needs HTML transcripts. After that, the page is deleted and its link stops working.

A change applies to tickets that close afterwards. Links already sent keep the period they were created with. While the HTML transcripts add-on is off, no transcript page opens, and new pages are kept for 30 days.

Your links look like

Shows the start of your links. Each link ends with a long random code that is different for every ticket, for example:

https://transcripts.dionmevans.me/<your bot's code>/<ticket code>

Once your own domain is live, new links look like https://transcripts.yourserver.com/<ticket code> instead.

Anyone who has a link can read that conversation, without signing in. That is why the bot only sends it to your ticket log and to the member who opened the ticket. Treat links like the conversation itself and do not post them publicly.

Use your own domain

You can have transcript pages shown on an address you own, such as transcripts.yourserver.com. This is an optional add-on for the one-time setup fee shown on the Transcripts page. It needs the HTML transcripts add-on, because an own domain shows HTML transcript pages; add that first from the Overview tab. If the page says Own domains are not on sale yet, it cannot be bought at the moment.

What you can use

  • A subdomain of a domain you own, such as transcripts.yourserver.com. A bare domain such as yourserver.com is refused, so your main website is not affected.
  • A name that no other bot uses and that our servers do not already use.

Step 1: Pay for the setup

  1. Type your subdomain in Your domain.
  2. If you have them, enter a Promo code or Gift card, or tick Use my account credit.
  3. Tick the box to agree to the rent-a-bot terms.
  4. Press Set up my domain.

Codes and credit are applied first. If they cover the whole fee, the setup is paid straight away. Otherwise you pay the rest by card through Square, and the page shows Waiting for payment with a Pay £X by card button until Square confirms it. Setup starts once it is paid. While you wait, you can press Cancel this request if you change your mind.

Step 2: Add the DNS record

Once the setup is paid, the page shows one record to add where you manage DNS for your domain, for example at your domain registrar or at Cloudflare:

SettingValue
TypeCNAME
Nameyour subdomain, for example transcripts.yourserver.com
Targettranscripts.dionmevans.me
ProxyOff (DNS only, the grey cloud on Cloudflare)

Keep the proxy off. If your subdomain points anywhere other than our server, including through a proxy, or has a separate IPv6 (AAAA) record pointing elsewhere, the setup cannot finish.

Step 3: Wait for it to go live

We check your domain automatically and the page shows where it has got to:

StatusWhat it means
Waiting for DNSPaid. We are waiting for your subdomain to point at us. DNS changes can take a while to spread, and we keep checking.
Setting upYour subdomain points at us, and we are getting a security certificate for it.
Needs attentionSomething went wrong, for example we could not get a certificate, or the name is already used on our servers. The page explains what happened.
LiveNew transcript links use your domain. We also email you when this happens.

Links sent before your domain went live keep working on our address until they expire.

Check again

If the status is Needs attention, fix what the message describes, usually the CNAME record or the proxy setting, then press Check again. Your domain goes back to Waiting for DNS and we try again from the start.

Changing the name before it is live

Typed it wrong? Until your domain is Live, you can change it for free. Type the correct subdomain under Typed it wrong? Change it for free until it is live and press Save domain. We then check the new name from Waiting for DNS, so remember to add the DNS record for the new name.

Removing your domain

Once your domain is Live, you can press Remove my domain. Then:

  • new transcript links go back to our address;
  • links that were sent on your domain stop opening;
  • links sent on our address keep working until they expire;
  • we take your domain off our server and delete its certificate.

Removing your domain uses up the setup you paid for. To use a domain again, including the same one, you pay for a new setup. To switch straight to a different domain, you also have to remove the live one first.

You can then delete the CNAME record from your DNS.