Provide 24/7 affordable customer service with AI-powered chat.
Connect to learn more

Block an IP Address (Olark Classic)

**NOTE: This help article was written for our Olark Classic chat console. Some things may not apply, may have moved, or may look different. For up to date chat console documentation, click here.

Sometimes it’s useful to be able to block a certain visitor. Whether it's your development team and colleagues that have no need to chat with you or a persistent troll distracting your support team, we have you covered.

This guide will show you how to use a visitor's IP address to hide the chat box from the blocked visitor.  

Create an automation rule

  1. Navigate to your Automation page.
  2. Click New Rule and name your new rule.
  3. As your WHEN condition choose Agents are either available or unavailable to chat.
  4. Choose Visitor's IP from the pulldown menu in the IF section and enter the IP address. You can add as many IP addresses to this Automation Rule as you need.
  5. As the THEN action select once per page load.
  6. Choose Hide the Olark chat box from the pulldown menu in the Actions section.
  7. Click Save Rule.

Your rule when finished should look something like this:

Automation troll block rule

Please note that IP addresses can only be revealed by clicking on Reveal IP address in the Additional Info section of your chat console. You’ll only be able to obtain a visitor’s IP address while they are chatting with you and not after the conversation.

reveal-ip

Full information on how and why we manage IP addresses the way we do is available here.

Please provide the domain name where your Olark live chat is installed.
Include the relevant transcript URL, if possible. You can send us the specific URL from your Transcripts page.
If you see specific error messages, banners, warnings, notices, etc., please let us know here.
Max file size 10MB.
Uploading...
fileuploaded.jpg
Upload failed. Max size for files is 10 MB.
Thank you! Your submission has been received and you'll hear from us shortly!
Oops! Something went wrong while submitting the form.