Craft CMS setup guide

• Telegram. A Telegram account, and a group for your team with Topics turned on. You can make the group during setup.
• A Craft site, on Craft CMS 5 or later, with a place you develop and deploy from, as you already work.
• A payment card, for the seven-day free trial. Nothing is charged during the trial.
• About ten minutes.

1. Go to humanreply.app/start and choose Other.
2. Type your site's address, the one your visitors use.
3. Press Start setup. Setup opens in your browser, and everything in it is saved as you go.

1. Create your bot. Open BotFather in Telegram from the setup page (the first message is typed for you), choose a name, and paste the token BotFather gives you.
2. Add it to your group. Add the bot to your team's group as an admin, and turn on Topics. The page checks as you go.
3. Send a test lead. Write a message on the setup page and answer it from your phone, to see the whole loop once.
4. Set your hours. Business hours, auto-away, and the ways a visitor can ask for a reply when nobody is free.
5. Make your account. Your email and the six-digit code we send to it, then the plan: seven days free, then $12 a month, or $120 a year. You add your card on Stripe; nothing is charged during the trial, and the plan starts by itself when the trial ends unless you cancel before then.

The last setup page shows a line for your site. Your site key is the part of it after data-site=, like rl_xxxxxxxx: it is all the plugin needs.

1. Where you develop your site, open the control panel, go to Plugin Store, search for Human Reply Live Chat and press Install. Or, from your project's folder:

   composer require human-reply/craft-live-chat
   php craft plugin/install human-reply-live-chat

2. Go to Settings › Plugins › Human Reply Live Chat, paste your site key into Site key and press Save.
3. Deploy as you always do. The plugin and its key travel with your project config.
4. Open your site once. The setup page turns to "You're live."

The chat is on every page your site renders, just before </body>. The control panel and previews never show it.

The plugin in Craft's Plugin Store. Its code is on GitHub.

Most production sites don't allow admin changes, so the plugin's settings can't be edited there. Set the key where you develop and deploy it, or keep it in each environment's .env instead:

1. In Site key, type $HUMAN_REPLY_SITE_KEY and save.
2. In the .env of every environment that should show the chat, add:

   HUMAN_REPLY_SITE_KEY=rl_xxxxxxxx

An environment without it shows no chat, and the field says so. A config/human-reply-live-chat.php returning ['siteKey' => 'rl_xxxxxxxx'] works too, and wins over the field.

Or paste the line

Without the plugin, the line from the setup page works too. Paste it into the layout every page uses, like templates/_layout.twig, just before </body>, then deploy.

<script src="https://humanreply.app/embed.js" data-site="rl_xxxxxxxx" defer></script>

The line from the setup page. Yours carries your site's own key in place of rl_xxxxxxxx.

Sign in at humanreply.app and open your dashboard. Under Customize:

• Design: your logo and team name, the colour, light or dark, the font and size, the launcher's label.
• Position: bottom left or bottom right, the space from the edges, and the stack order if something on your site covers the bubble.
• Language: the bubble's language, your greetings, and any of its words.
• Behavior: the ways to reply you offer, and what visitors see about your team.

Changes are saved as you make them and reach your site at once. There is nothing to change in Craft, and nothing to deploy.

• Every conversation opens as its own topic in your Telegram group, with a card that says who is writing: the page, where they came from, how many times they have visited, their language and device.
• Tap Claim, or just reply. Your answer shows on your site in seconds. Photos and files work both ways.
• React 👀 to a message to show the visitor it has been seen.
• Won or Lost closes the conversation and keeps it as a record.
• In the Desk topic, tap I'm available or I'm away. When nobody is free, the chat says so and asks the visitor where the reply should go.
• The dashboard shows today's chats, every transcript, and analytics: conversations, first-reply time and ratings, by page and by person.

Settings › Plan & billing shows when the trial ends and what comes next. Manage billing opens Stripe, where you can change the card, see invoices, switch between monthly and yearly, or cancel. If the plan ends, the chat leaves your site until you start it again; your settings, your team and your conversations are kept.

1. Where you develop your site, go to Settings › Plugins, open the menu beside Human Reply Live Chat and choose Uninstall. If you installed it with Composer, also run composer remove human-reply/craft-live-chat. If you pasted the line instead, delete it from your layout.
2. Deploy. The chat leaves your site with that version.

Removing the plugin doesn't end your plan: cancel it under Settings › Plan & billing. To delete your Human Reply account and its conversations, write to hello@send.humanreply.app.

• The setup page keeps listening. It listens for your published site. Your local site shows the chat but doesn't count: deploy, then open your site's own address.
• The field says "isn't set to a site key on this server". It holds $HUMAN_REPLY_SITE_KEY and this environment's .env doesn't. Add the line to that .env.
• There is no Settings page for the plugin in production. Admin changes are off there, as they should be. Set the key where you develop and deploy it, or use .env.
• Settings › Connection says "Not on your site yet." The site isn't deployed with the plugin and its key yet, or nobody has opened it since. The row shows the line again, with your site key in it.
• Anything else: hello@send.humanreply.app. A person answers.