Telegram · Ringover · Odoo

A sales secretary that waits for your ok.

Hermes reads your mail and Quicktalk / Ringover calls, posts a card on Telegram, and writes to Odoo only when you reply ok. A Docker appliance, on your side.

Karukera QuickTalk Automation card — open source MIT.
Open sourceMIT0 stars0 forks

github.com/cryptulien/quicktalk-automation

Open source. The bot runs on your VPS. Your keys stay yours.

The call happened. The CRM is still empty.

Someone called back about a quote. The thread is in the inbox, the transcript is in Ringover, and nobody opened Odoo. The kit holds those three pieces, shows them to you, and writes nothing on its own.

How it works

How it works: IMAP and QuickTalk into Hermes, Telegram card, human ok, then Odoo.

Two phases. Not one more.

  1. 1

    You clone the repo

    START-HERE.md first.

  2. 2

    An AI installs the VPS

    It reads FOR-AI.md then pack/deploy/SKILL.md. Docker, Telegram token, one LLM key. No Odoo here.

  3. 3

    You talk to the bot

    The onboard wizard asks one question at a time, probes, and writes tenant.yaml only at the end.

  4. 4

    Cards start arriving

    ok / ignore / a tweak. The mail draft is a note. Odoo sends nothing.

The kit, today

MIT license. Hermes appliance + Docker ingest. Odoo, Ringover, IMAP configured in Telegram. 42 files.

Open sourceMIT0 stars0 forks

github.com/cryptulien/quicktalk-automation

Before you clone.

Do I need to code?
Not for daily use. Install is Docker + install.sh, then the bot. An AI can follow pack/deploy/SKILL.md.
Is this hosted at Karukera?
No. The kit runs on your VPS. Karukera never sees your mail or your calls.
Does Odoo send the mail by itself?
No. The draft is a note on the lead. Never an outgoing mail.
What do I need?
A VPS, a Telegram bot, an LLM key, Odoo, a Ringover key, and IMAP (app password).

Put the bot on a VPS you control.

MIT license. One clone. One Telegram. Nothing in Odoo before your ok.

Open sourceMIT0 stars0 forks

github.com/cryptulien/quicktalk-automation