The agent decides what's sent
You see the reply in full and who it would go to. Approve it and it goes; reject it and it is saved as a draft.
Customer Support
Sorted. Drafted. Routed. You hit send.
Lodol triages the queue, drafts replies in your tone and sends bugs to engineering with the details attached, across Zendesk, Intercom, Gmail, Slack and Linear. No fee per resolution, and nothing has to reach a customer before a person approves it.
Free to start, no credit card. No per-resolution fees, and every plan has unlimited seats.
This morning’s queue
- BillingReply drafted in your tone. Waiting for you to approve it.The workflow
- Bug · urgent
Linear ticket opened at high priority, link posted back in the thread.The workflow - How-to
Answer drafted from the Notion page “Resetting two-factor”, posted with the link once approved.The workflow - IdeaForwarded to #ideas with who posted it and a link back.The workflow
- Feature requestLogged in Notion as “SSO with Okta”, with who asked and why.The workflow
- RefundHanded to a person with a holding reply. Refunds always go to a human.The workflow
6 sorted · 1 waiting for you · nothing sent that a person didn't approve
Fits your help desk
Keep your help desk. Lodol works the ticket.
No new inbox for your team to learn and nothing to migrate. Lodol works between the help desk, your docs, the CRM, billing and engineering, and leaves every reply with a person.
Questions arrive
From the support inbox, the help desk or the community, read and sorted.
Context gets pulled
Who they are, what they pay for and what they ordered, added to the ticket.
Replies get drafted
Answers drafted from your own docs, in your tone, for a person to approve.
Bugs reach engineering
A ticket with the details and the customer's own words, linked back.
The team hears first
Urgent tickets and big accounts flagged where your team already talks.
940 apps and 11,056 actions in all, and a workflow can call any other tool’s API directly, so nothing has to move for Lodol to fit in.
Explore all integrationsReady to run
Start from one that already works.
Built and tested by our team for the work around every ticket. Open one, connect your apps, and it runs.
HourlyReview and send replies to support enquiries
Writes a reply to each new support email, asks you to approve it, and sends it or leaves it as a draft.
Nothing reaches a customer until you approve it. What it can't answer becomes a holding reply, not an invented one.
Open this workflowOn new messageTurn Slack support requests into Linear tickets
When someone asks for help in your Slack channel, opens a Linear ticket with a written summary and replies in the thread with the link.
A close call is left alone, and the reporter's own words go on the ticket so the summary can be checked.
Open this workflowOn new messageAnswer Slack questions from your Notion wiki
Searches Notion when a question is posted in Slack and drafts an answer from the pages it found, with links.
Answers only from the pages it found, with links. If they don't cover the question, it says so.
Open this workflowOn new emailSmart email draft generator
When a new email arrives, Claude writes the reply you would have written and leaves it in your Gmail drafts for you to send.
Leaves a bracketed placeholder where it needs a fact, rather than inventing a price, a date or a promise.
Open this workflow
On new messageTelegram support bot that hands over to a person
Answers support messages in Telegram from your own material, and hands anything it cannot answer to a person instead of guessing.
Refunds, billing, complaints and personal data always go to a person. Handing over is the rule.
Open this workflowOn new emailTurn emailed feature requests into Notion tasks
Reads new Gmail email for feature requests and logs the ones it finds in Notion as tasks, with a summary of who asked and why.
Logs each request in the customer's own words, with who asked and why.
Open this workflowCompared
Lodol or a support AI agent?
Intercom Fin, Zendesk AI agents and eesel AI answer customers for you, and they are good at it. Lodol can answer them too, and runs the work around every ticket. Here is how they compare on what a support team weighs.
| What a team asks |  Lodol | Intercom Fin | Zendesk AI agents | eesel AI |
|---|---|---|---|---|
| Chats with customers on your site or by phone | Yes. Your own support agent, answering your site's Intercom or Crisp chat | Yes. Chat, email, voice, WhatsApp, SMS and social | Yes. Messaging, email and voice | Partly. Website chat and messaging apps |
| Works with the help desk you already run | Yes. Zendesk, Intercom, Front, Zoho Desk, HubSpot, Salesforce and more | Yes. Intercom, Zendesk, Salesforce, HubSpot, Freshdesk, Front and more | Partly. Zendesk; other platforms through sales | Yes. Zendesk, Freshdesk, Intercom, Help Scout, Front and more |
| How you pay | Yes. Free, or from $18 a month, by runs. Nothing per resolution or seat | $0.99 per outcome; $49 a month minimum on another help desk | Per automated resolution ($1.50–$2.00 listed), plus seats | Usage-based: per ticket it works, or credit plans |
| A person approves replies before they send | Yes. Any step waits for a person; every run traced | Yes. Loops in a teammate to review | Partly. Drafted replies with its Copilot add-on | Yes. Draft mode, or approval per action |
| Acts beyond the help deskLinear or Jira, the CRM, billing, Slack. | Yes. 940 apps, including Linear, Jira, HubSpot, Stripe and Slack | Partly. Inside conversations, through connectors | Partly. Action flows from Zendesk to other systems | Yes. Actions across connected apps |
| Testing and support analytics | Yes. Test runs before going live; reports from your help desk data | Yes. Simulations, regression tests and insights | Yes. Reporting and analytics on its AI agents | Yes. Simulations on past tickets, and reports |
| Runs on your own AI model | Yes. Your Anthropic, OpenAI or Gemini key | No. Intercom's own models | No. Zendesk's own models | Not stated |
| Try it without a sales call | Yes. Free plan, no card | Partly. Trial on Intercom; sales for other help desks | Yes. 14-day trial, no card | Yes. Free usage to start |
If you want one ready-made AI agent that answers customers across chat, email and the phone, Fin is built for that, and Lodol can run beside it. If you want your own support agent on your site's chat, and the triage, drafts, escalations and updates around every ticket handled, with a person approving what goes out and no fee per resolution, that is Lodol.
From each company’s own website, checked October 2026. Products change; if something here has, tell us and we will correct it.
The cost
A fee per resolution grows with every ticket.
AI support agents are mostly billed per conversation they resolve, so the bill climbs with your volume and with their own success. Lodol is priced by runs, so a resolved ticket costs nothing extra, and your model provider bills the drafts at cents a ticket. Slide to your numbers.
2,000
50%
Per resolution: $990 a month. Lodol: $54 a month.
Fin at $0.99 per resolution$990/mo
1,000 resolutions; the bill grows with each oneLodol drafting every ticket$54/mo
Builder with 2,500 runs, $18, plus about $36 of tokens at 1.8¢ a ticket$936 a month less, and it doesn’t climb as the AI resolves more. Each reply still waits for a person.
Not the same job: a resolution answers the customer with no agent time, and a Lodol draft waits for an agent to approve it. Fin’s price is its published rate on another help desk ($0.99 per outcome, a $49 monthly minimum including 50), as listed in October 2026. Lodol assumes about 6,000 tokens read and 600 written per draft, at Anthropic’s list price for Sonnet 5.5 ($2 and $10 per million), billed to your own key, and a run for every ticket on the smallest plan that covers them. Help-desk seats are left out of both.
In control
Nothing reaches a customer until a person says so.
A reply can wait for an agent to read it, a refund for a lead to decide. Every run leaves a record of what happened and why.
See exactly what happened
Every run is traced step by step, so when a customer says they never heard back, you can see what was drafted, who approved it and when it went.
Questions support teams ask first
It can. Lodol has no chat widget of its own, but a support agent you build can answer the chat on your website through Intercom or Crisp, from your own docs, and hand anything it can't answer to a person. It also works around the ticket: drafting replies for a person to approve, sorting the queue, escalating bugs and adding context.
Zendesk, Intercom, Front, Zoho Desk, Crisp, Freshservice, ServiceNow and Jira Service Management, plus Gmail, Outlook, Slack, Discord, Telegram and WhatsApp. If yours has an API, a workflow can call it directly.
No. Free includes 200 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes. A workflow that drafts replies uses a run per ticket at most, whether or not the ticket is resolved. AI steps run on your own model key, so drafting a reply typically costs a cent or two in tokens, billed by your provider.
Credentials are encrypted in transit and at rest. Roles decide who can run, edit and manage each workflow, every run is recorded step by step, and AI steps run on your own model key, under your provider's terms.
No. Ask Claude or ChatGPT for the workflow in plain words and it builds it in Lodol, or build it step by step in the visual editor. Every template on this page can be opened, connected and run as it is.
Start with the support inbox.
Open the reply workflow, point it at your support mail and approve the first drafts yourself. Free to start, no credit card.
Free plan, no credit card · Credentials encrypted in transit and at rest · Security and trust