Canadian live chat software with a practical AI support path.

Website first

We optimize around the conversations that happen on your own site: product questions, lead capture, account help, and pre-sale confidence.

Human handoff

AI should reduce repeat work without trapping visitors. Conversations can move from automation to a real teammate with useful context attached.

Operating history

Richscripts has shipped and maintained web software for more than two decades, which matters when teams choose a support vendor.

Hit heavy, stay small

We value focused teams that can move quickly, communicate clearly, and keep product decisions close to the work.

Ambition by the boatload

We like building products that last, not just launching them. That means aiming for quality, stability, and real customer usefulness.

Open communication

Transparent conversations make product work easier, faster, and far more durable over time.

Autonomy and attitude

We favor self-starters who take pride in details and stay accountable to the experience customers actually have.

Support and win

When our customers and teammates are equipped to succeed, the product gets stronger too.

Teamwork makes the work better

We combine product expertise, support knowledge, and implementation experience to build software that earns its keep.

Long horizons

We ship improvements steadily rather than rewriting the product every few years. Customers who installed a snippet a decade ago still have a working widget.

Configuration, branding and transcripts survive plan changes, because losing them is the sort of surprise that makes software untrustworthy.

Website first

The product is built for teams supporting customers on their own website, not for running a contact centre. That focus is why the setup is a snippet rather than a project.

When something belongs in a CRM or a helpdesk, we would rather connect to it than reimplement it badly.

Small on purpose

A small team cannot build everything, so it has to choose. We choose the things a support team touches every day: the console, the widget, the transcript, the answer.

It also means the person reading your bug report is usually close to the person who can fix it.

Talk to us

The chat button on this page reaches the same console our customers use, with the same transcript history and the same handoff behaviour.

Email works too, and is the better channel for anything with an attachment or an account detail.

What helps us help you

The site the widget is installed on, what you expected to happen, and what happened instead. A URL is worth several paragraphs.

If the widget is not appearing, the browser console message is usually the whole diagnosis.

Self-service first

Our guides library covers setup, operations and measurement in detail, and it is written for people running chat rather than for buyers.

If a guide is wrong or missing something, telling us is genuinely useful.

Not a suite

MyLiveChat is not a marketing automation platform or a full CRM, and we do not pretend the chat widget should become one.

Teams that need those run them alongside, and connect chat to them.

Not an authentication channel

A public chat widget is open to anyone who can load your page. It is not a place to verify identity or hand out account secrets, and we say so in our own guides.

Sensitive workflows belong behind your login, with chat pointing at them.

Not a replacement for good content

If a question arrives fifty times a week, the win is a better page, not a faster answer.

The product is at its best when it tells you which page to fix.