# Algomo vs Open.cx

Open.cx, branded Open and formerly OpenCX, is an AI customer support platform for chat, email, voice and outbound, built by OpenChat, Inc. Algomo is an AI agent for your website that reads the live page every time a visitor asks. If you are comparing Algomo as an Open.cx alternative, this page looks at who connects the AI to your systems and how current its answers are.

TL;DR: Teams stall on an AI agent over the integration work and over answers that go out of date, and Open.cx has your team build an action for each API and re-crawls your site weekly by default, while Algomo connects itself to what your pages already call and reads each page live.

Open.cx and Algomo overlap more than most pairs of AI agents. Both can be run from a coding assistant, and both can act on a visitor's page. The differences sit in the integration, the freshness of answers and the bill.

## Algomo vs Open.cx at a glance

|  | Algomo | Open.cx |
| --- | --- | --- |
| Main job | An AI agent for your website, with an inbox your team takes over from, for support and inbound sales. | An AI support platform across chat, email, voice, WhatsApp and outbound, with its own helpdesk or on top of yours. |
| Owner | Algomo | OpenChat, Inc., independent, backed by Y Combinator and X by Unifonic. |
| Who does the integration | Algomo's AI, from the requests your pages already send. | Your team builds an HTTP action per endpoint, or imports an OpenAPI spec. |
| Where the answers come from | The live page and the live data behind it. | Crawled pages and synced sources, re-crawled every 7 days by default. |
| Published pricing | Free plan, then one monthly amount from $50 to $4,300. | 75¢ to 90¢ per resolved ticket, set by volume, plus carrier costs at cost. No free plan. |
| Channels | Chat on your website, with a follow-up email. | Chat, email, voice, WhatsApp, SMS, Slack, Teams and social, plus outbound sequences. |
| Biggest limitation | Does not answer phone calls or incoming email. | Between crawls, the agent answers from the last copy of your site. |

## What part of Open.cx do you need?

TL;DR: Open.cx for a support team that wants one AI across phone, email, messaging and outbound campaigns, and Algomo for website questions that depend on live prices, stock, bookings or a visitor's own account.

Open.cx sells six agents on one platform: inbound support, outbound, a copilot for your team, QA, customer insight and an app builder. Most buyers need one or two of them. Match your case:

- Your customers phone, email and message on WhatsApp as much as they use your website: Open.cx. - You run outbound sequences by phone, SMS or email: Open.cx. - Your visitors ask on the site about things that change during the day: Algomo. - Nobody on your team has time to describe each API to the AI: Algomo.

The two risks come first below. Building, acting on the page, guarantees, channels, handover and the bill follow.

## Who connects the AI to your systems?

TL;DR: On Open.cx your team creates an action for each API, with its endpoint, parameters, headers and a test, while Algomo discovers the requests your pages already make and turns them into tools, with a first version answering the same day.

An agent that can look up an order or move a booking needs a connection to the system that holds it. Writing and maintaining those connections is where an AI project usually spends its first months.

## Open.cx actions

Open.cx calls them AI Actions. In the dashboard, someone on your team creates each one: a name and description the AI reads, the method, the endpoint URL, a body schema, headers and parameters, which customer segments may use it and on which channels. A test button checks the HTTP call.

[Open.cx's own article](https://docs.open.cx/actions/build-an-action) warns that a passing test proves the call works, not that the AI will pick it. Where you have an OpenAPI spec, actions can be generated from it and kept in sync from your build pipeline. MCP servers can also be added as actions.

## Algomo integrations

Algomo starts from your website's address. It records the requests your pages send for stock, an order or a booking search, and each one becomes a tool the agent can call. Algomo's AI deployment engineer handles the discovery, the wiring and the upkeep. Your first version answers the same day.

Your team does not write descriptions, schemas or headers for these, because your site already makes the calls. Systems only staff can reach, such as a CRM, use a connector, from the Business plan. If a redesign breaks a connection, Algomo flags it so the mapping can be rebuilt.

[The demo library](/demos) shows it on large brands' own systems, with no project on their side. [The Blinds 2go demo](/demos/blinds2go) prices three made-to-measure windows in one card through the site's price engine. [The Nike demo](/demos/nike) reads a live price and UK 9.5 stock. [The IKEA demo](/demos/ikea) checks stock at IKEA Bristol.

Tools Algomo created for one workspace from requests its pages already make. Each one can be switched off.

## Getting the AI connected

|  | Algomo | Open.cx |
| --- | --- | --- |
| Finding the systems behind your site | ✓ Algomo's AI, from your pages' requests | Your team lists them |
| Describing each call to the AI | ✓ Built by Algomo's AI | Your team writes the name, description, schema and headers |
| From an OpenAPI spec | Not needed | ✓ Generated and kept in sync |
| First version answering | ✓ The same day | After sources are crawled and actions built |
| A system behind a staff login | A connector, from the Business plan | An action with stored secrets |

Our take: count the APIs your agent would need on day one, and ask each vendor who writes each one up and how long that takes.

## Can it repeat something your site stopped saying last week?

TL;DR: Open.cx re-crawls a website source every 7 days by default, with daily crawls on request, while Algomo reads the live page for every question and makes your next month free if a reviewed agent contradicts your site.

Pages change between crawls. A delivery date slips, a fee is removed, a promotion ends early. Until the next crawl, an agent that answers from a copy keeps quoting the old version.

## Open.cx knowledge

Open.cx learns your website with a crawler. Your team adds the start URL, include and exclude paths, a page limit and a crawl interval. The default interval is 168 hours, which is 7 days, and it cannot be set lower. The Open.cx team can switch on daily crawls on request, and a source can also be left manual.

Open.cx's Add Website form, with Schedule set to Weekly and no page limit. From the docs article "Connect a website".

Other content comes in by sync, from Zendesk, Intercom, Front, Notion, Confluence, Shopify, SharePoint and others, or from a help center you write inside Open.cx. Account data comes live through the actions your team built.

## Algomo agentic search

Algomo does not keep a copy of your site to answer from. It knows where your pages are, opens the one that answers the question while the visitor waits, and reads what it says now. Remove a fee at four, and the answer at 4:01 no longer mentions it. There is no crawl interval to set.

Stock, orders and bookings work the same way. They are read at the moment of the question, through the same request your page would make.

Algomo reviews an agent before it goes live. If a reviewed agent contradicts your website, your next month is free, under the terms on [the guarantee page](/resources/guarantee).

## Where each answer comes from

|  | Algomo | Open.cx |
| --- | --- | --- |
| Your public pages | ✓ Opened live, per question | ✓ A crawled copy |
| How often pages are re-read | ✓ Every question | Every 7 days by default, daily on request |
| Help centre and docs tools | ✓ Read live as pages of your site | ✓ Synced from Zendesk, Intercom, Notion and more |
| Account and order data | ✓ Your pages' own requests | ✓ Actions your team built |
| A written promise on accuracy | ✓ Next month free | Not on the pricing page |

Our take: edit one line on a page the agent uses, ask both agents about it the same afternoon, and keep the one that gives the new wording.

## What happened when we asked Open.cx's AI on live sites?

TL;DR: On 21 and 22 November 2026 we asked Open.cx's AI 291 questions on 25 live websites that run its widget. 185 answers were correct, and 8 sites gave a wrong answer that a second visitor heard too. The 8 sites belong to 6 companies: three are Sunday Natural shops on one Open.cx account, and two are Fury Water Adventures sites.

On 21 November we tried 32 websites that Open.cx names as customers or that load its widget. Most of the named customers show no Open.cx widget on their public site. 13 sites had a working widget, and 12 of them answered a visitor with no account. The 13th passed both of our questions to its staff. Each question came from a line the site prints, and each answer was checked against the site's own pages. 74 of the 114 answers were plainly correct. The rest were hedges, hand-offs to staff, requests for a name, fares read from a live booking system, points where a site contradicts itself, slips a second visitor did not hear, and the 3 confirmed findings. A finding is confirmed when a fresh visitor with no cookies hears the same wrong answer and no other page on the site supports it. Where a chat asked for an email before it would start, we gave a test address of ours.

The 3 findings that day come from Indie Campers and from Sunday Natural's shops in Spain and Poland, which run on one Open.cx account. We also checked 18 Open.cx customers for its AI working inside another company's chat window. Two had it, More.com and Foodics. Of the 70 questions we asked there, 56 answers were correct and none was a confirmed wrong answer.

On 22 November we tried 62 more websites. Open.cx says on its own site that FareHarbor, the tour booking platform, runs on Open, and FareHarbor offers the agent to some of its tour operators as FareHarbor Agent. 12 of the new sites answered: 8 FareHarbor operators and 4 more Sunday Natural shops. We asked 177 questions there, and 111 answers were plainly correct. 5 more sites gave a confirmed wrong answer: Sunday Natural's UK shop, Fury Water Adventures in Key West and in St. Augustine, PacWhale Eco-Adventures and Futurismo.

Of the 8 sites with a confirmed wrong answer, 4 are FareHarbor operators that run Open.cx, 3 are Sunday Natural shops on the one account, and 1 is Indie Campers. Fury's Key West agent said its Greene Street rental shop is open until 6 p.m., where the site prints 9:00am-5:00pm. Futurismo's agent said there is no discount for a second tour, where every page carries the line "Mix & Save: Enjoy a 10% Discount on your Second Tour".

## PacWhale Eco-Adventures: a buy-one-get-one-free whale watch

On 22 November 2026, the chat was open on the Māʻalaea whale-watch sail page of pacwhale.com. We asked: "Is the whale watch sail from Maalaea buy one get one free right now?"

Recorded on 22 November 2026 on PacWhale's Māʻalaea whale-watch sail page, as a new visitor. The boxed fare label says Buy One Get One Free Through 12/20/26. The assistant said the offer is 15% off, not buy one get one free. Told the website says buy one get one free through 12/20/26, it corrected itself and said it had confused the general whale-watch discount with this offer.

PacWhale's assistant said: "No, the current offer for whale watch tours is 15% off, not buy one, get one free." A fresh visitor heard: "The current pricing information lists whale watch tours at 15% off, not buy one, get one free." Asked about the Lāhainā sail, it gave the same answer.

The fare box on the page says "BUY ONE GET ONE FREE THROUGH 12/20/26", and the buy-one-get-one-free listing shows the same sail. On the 70 pages we read, "15% OFF" appears only as an online special on other tours. PacWhale is one of the FareHarbor operators, and its site loads the Open.cx widget under its own account.

## Indie Campers: how many European countries a campervan may enter

On 21 November 2026, the chat was open on indiecampers.com. We asked: "In how many European countries am I allowed to drive the campervan?"

Recorded on 21 November 2026 as a new visitor. The chat only loads on the indiecampers.com home page, so the clip shows the boxed list of 32 countries on the help article, asks on the home page, and returns to the list. Indie Campers Support said 36 countries, adding Monaco, San Marino, Vatican City and Liechtenstein. Told the website says 32, it kept its answer and said the four are not in the website's list.

Open.cx's AI said: "For a campervan picked up in Europe, you can drive in 36 countries: 32 specifically listed in the Rental Agreement, plus Monaco, San Marino, Vatican City and Liechtenstein." A fresh visitor was first asked what kind of vehicle it was. After the reply "An Indie Campers vehicle, picked up in Lisbon.", it said: "You can drive the campervan in 36 European countries: 32 listed countries, plus Monaco, San Marino, Vatican City and Liechtenstein."

The help article "Prohibited uses: Where am I allowed to travel?" says: "You can drive in these 32 European countries", and lists them. Clause 15.3 of the Rental Agreement for Europe lists the same 32, and clause 15.3.1 says that driving in other countries "constitutes a violation of this Rental Agreement". None of the 220 help articles mentions Monaco, San Marino or Vatican City. The site loads the Open.cx widget, and its settings name the account "Indie Campers Support".

The chat on indiecampers.com telling a fresh visitor with a van from Lisbon that it can be driven in 36 European countries, 21 November 2026.

## Sunday Natural Spain: when shipping becomes free

On 21 November 2026, the chat was open on the shipping page of sunday-natural.es. We asked, in Spanish, from what order value shipping to mainland Spain is free: "¿A partir de qué importe es gratis el envío a España peninsular?"

Recorded on 21 November 2026 on Sunday Natural's Spanish shipping page, as a new visitor. The page shows the boxed España peninsular row: 3,90 €, free from 99,00 €. Sunday Support said there is no minimum order for free shipping. Told the website says free from 99,00 €, it apologised for the confusion and kept its answer: DHL to mainland Spain costs 3,90 € and no free-shipping threshold is listed.

The first visitor was told: "El envío a España peninsular cuesta 3,90 € con DHL y no es gratuito a partir de ningún importe" (shipping to mainland Spain costs 3,90 € with DHL and is not free from any amount). A fresh visitor heard: "Para la España peninsular no hay un importe mínimo para obtener el envío gratuito" (for mainland Spain there is no minimum amount for free shipping).

The table on the same page has a column headed "ENVÍO GRATIS EN PEDIDOS DESDE*" (free shipping on orders from). Its España peninsular (DHL) row reads 3,90 € and 99,00 €. Open.cx publishes a Sunday Natural customer story.

The chat on sunday-natural.es telling a fresh visitor that mainland Spain has no free-shipping threshold, 21 November 2026.

## Sunday Natural Poland: the same agent, the same question

The company's Polish shop runs the same Open.cx agent. On 21 November 2026, on the shipping page of sunday.pl, we asked from what order value shipping is free: "Od jakiej kwoty zamówienia wysyłka jest darmowa?"

Recorded on 21 November 2026 on Sunday Natural's Polish shipping page, as a new visitor. The page shows the boxed InPost Kurier row: 14.90 PLN, free from 390 PLN. Sunday Support said free from 99 €, with 1,90 € below that. Told the website says 390 PLN, it corrected itself to 390 zł.

The agent said InPost delivery in Poland is free "przy zamówieniach od 99 €" (on orders from 99 €) and costs 1,90 € below that. A fresh visitor heard: "Wysyłka do Polski przez InPost jest bezpłatna przy zamówieniu od 99 €. Poniżej tej kwoty kosztuje 1,90 €." (Shipping to Poland by InPost is free on orders from 99 €. Below that amount it costs 1,90 €.)

The page prices in złoty and prints no euro threshold. Its InPost Kurier row reads 14.90 PLN, and the column headed "DARMOWA WYSYŁKA OD KWOTY ZAMÓWIENIA*" (free shipping from order value) reads 390 PLN.

The chat on sunday.pl telling a fresh visitor that InPost shipping is free from 99 € and costs 1,90 € below that, 21 November 2026.

## Sunday Natural UK: euro prices on a shop that charges in pounds

On 22 November 2026, on the shipping page of sunday-natural.co.uk, we asked: "How much is delivery to the UK, and from what order value is it free?"

Recorded on 22 November 2026 on Sunday Natural's UK shipping page, as a new visitor. The boxed Great Britain row reads £4.90, free from £79. Sunday Support said €7.90, free from €99.00. Told the website says £4.90 and free from £79, it corrected itself to those figures.

Sunday Support said: "For delivery to Great Britain, shipping costs €7.90 with Royal Mail and usually takes 3–4 working days. Delivery is free on orders of €99.00 or more", and linked the German shop's English shipping page. A fresh visitor heard "the listed standard rate is €7.90, with free delivery on orders of €99 or more", and a third visitor heard the same figures.

The table on the UK shipping page reads "Great Britain (Royal Mail) | £4.90 | 3 - 4 | £79" under "Free Shipping on Orders From*". The UK shop prices in pounds only. The €7.90 and €99 row is on the English page of sunday.de, for orders placed on the EU shops.

We keep the full record behind every answer above: the transcript, a capture of the page at the time, the screenshots and the time stamps. If you work at Open.cx or at a site named here and want that record, write to support@algomo.com.

## How do you build and change the agent?

TL;DR: Both can be built from a coding assistant over MCP, and Open.cx adds an assistant called Companion inside its dashboard, while Algomo stages every change for you to preview on your own site before it ships.

Your agent changes every week. The question is who makes the change, from where, and what they see before customers do.

## Open.cx MCP and Companion

Open.cx has [an MCP server](https://docs.open.cx/mcp/introduction) for Claude Code, Cursor, VS Code, Windsurf, Zed and Claude Desktop. MCP is the open protocol that lets an assistant work another product. From there you can edit training scenarios, crawl websites and configure actions. Inside the dashboard, Companion does the same in plain language and can build a workflow or a mini app.

## Algomo AI-first platform

Algomo is built and changed over MCP from Claude Code, Codex, Cursor, ChatGPT or the Claude app. You say what the agent should do, and the assistant writes the configuration and its tools.

Each change is staged. You preview it on your own site, read the difference, then put it live, and Algomo keeps the history. If returns move from 14 to 30 days, one sentence makes the change, and you read it before a visitor sees it.

An Algomo agent: the model, its instructions in priority order, the tools it may use and a test chat.

Our take: ask each vendor to make a real change from your own coding assistant during the demo, and look at what you can review before it goes live.

## What can each AI do on the visitor's page?

TL;DR: Open.cx's Companion mode can click, type and choose on the page once the visitor allows each step, while Algomo works inside the visitor's own browser session and completes the steps where they can watch.

Doing beats describing. A visitor who asks how to apply a discount would rather see it applied. Both products can act on the page, so test how each one does it.

## Open.cx Companion mode

Open.cx's widget has [a Companion mode](https://docs.open.cx/widget/companion-mode) with three settings you switch on: it sees the page, points at a control, and acts on the page. With acting on, it can click, type or choose a value. Before each step the visitor sees the control and the proposed value and chooses Allow or No. It never touches password fields or file pickers.

## Algomo co-navigation

Algomo runs in the visitor's browser, on your page, inside the session the browser already holds, with their prices, region and basket. It can filter a list, apply a code, add an item to the basket, open the right page beside the chat, check the visitor's own order or book a slot, and the visitor sees every step.

It knows the page the visitor is on and what they viewed this visit. Because it works as that visitor, it sees only what they may see, and it does only what you gave it a tool for.

Our take: ask both agents to finish one real task on your site, and count the clicks the visitor still makes.

## What can run during the chat, and after it?

TL;DR: Open.cx runs workflows, outbound sequences and over 50 playbooks from a visual builder, while Algomo runs any function you describe, during or after the chat, from a two-factor code to a research memo.

Some steps happen outside the reply. Confirm identity before showing an account. Alert a manager. Send a summary when the visitor leaves.

## Open.cx workflows

[Open.cx's pricing page](https://www.open.cx/pricing) lists a visual workflow builder, actions on any API and more than 50 pre-built playbooks. Its outbound engine runs sequences by WhatsApp, phone, SMS and email, and its App Builder adds features you describe to Companion.

## Algomo workflows and widgets

Each Algomo agent has a workflow engine behind it. During a chat it can send a two-factor code before it shows account details, apply routing rules or alert a person in Slack. After the chat it can email a summary, or research the visitor's company in the background and send your team a memo.

Describe a small app to your coding assistant, such as a quote calculator or a booking panel, and Algomo builds it as a widget the visitor uses in the chat.

An Algomo workflow: a visitor on the pricing page is looked up by email and offered a demo.

Our take: name one task that happens by hand after a chat today, and ask each vendor to run it with nobody watching.

## What does each vendor guarantee?

TL;DR: Open.cx refunds every dollar of spend, up to $2 million, if you are not satisfied in your first 120 days, while Algomo gives your next month free if a reviewed agent contradicts your website.

The two guarantees cover different risks. One covers your first months of spend. The other covers whether the answers are true, for as long as you run the agent.

## Open.cx's refund guarantee

Open.cx says you apply once in 30 seconds and are covered from the day your subscription goes live. If you are not fully satisfied within 120 days, it refunds every dollar of Open spend, up to $2 million, with no metrics to hit.

## Algomo's accuracy guarantee

Algomo reviews an agent before it goes live. If that agent ever contradicts your website, the next month is free. It has no end date.

Our take: read both sets of terms, and decide which risk worries your team more.

## Where does each AI answer your customers?

TL;DR: Open.cx answers on chat, email, voice, WhatsApp, SMS, Slack, Teams and social, and runs outbound, while Algomo answers in chat on your website with a follow-up email.

Look at where last month's questions arrived. If most came by phone or email, a website agent reaches only part of them.

## Open.cx channels

Open.cx runs one agent across chat, email, voice with local numbers in over 100 countries, WhatsApp, SMS, Slack, Teams and social. It works on top of Zendesk, Intercom, Freshdesk, Salesforce, HubSpot or Front, or as its own helpdesk with inbox, macros and SLAs. Trunkrs, a delivery company Open.cx features among its customer stories, runs the Open widget on its site.

The Trunkrs chat open at its greeting, introducing Fred, its AI assistant, with name, email, Trunkrs number and postcode fields and Powered by Open at the bottom. Open.cx lists Trunkrs among its customer stories. From trunkrs.nl.

## Algomo channels

Algomo answers in chat on your website and can send a follow-up email to a visitor who left. It does not answer phone calls or incoming email.

Our take: if phone, email or WhatsApp carry most of your volume, choose Open.cx for those channels.

## What happens when the AI hands over to a person?

TL;DR: Open.cx hands over when it cannot resolve an issue, when the customer asks, or on topics you forbid it, while Algomo alerts the right person by email and Slack and they join the live chat with the transcript.

Some topics should never stay with an AI: a chargeback, a legal threat, a request to delete an account. What matters is how cleanly they reach a person.

## Open.cx handoff

Open.cx transfers a conversation to a person when the AI decides it cannot resolve it, or when the customer asks. You can list prohibited topics, such as refunds or legal action, and every matching conversation goes straight to your team. A handed-over ticket is not billed.

Open.cx's prohibited topics, Legal action, Account deletion, Chargebacks and Refunds, which the AI hands to a person. From the docs article "Handoff Topics".

## Algomo handoff

Algomo hands over on rules you set: by topic, by page, or when the visitor asks. The right person gets an email and a Slack message and steps into the chat on your site with the whole transcript. With a connector, Algomo can open the ticket in your helpdesk instead.

Our take: ask for a person on each, and check what your colleague sees before they reply.

## What does the first week look like?

TL;DR: Open.cx starts with a rate agreed in writing and a named solutions engineer, while Algomo's free plan puts a working agent on your own site the same day with no card.

Your team wants to hear the agent answer your own questions before a contract. How quickly you get there depends on who does the setup.

## Setting up Open.cx

[Open.cx's quickstart](https://docs.open.cx/quickstart) puts an agent on a site in under 10 minutes: join an organisation, train it on a knowledge source, embed the widget. The pricing page includes a named solutions engineer, an AI trainer and white-glove onboarding, and the final rate is agreed in writing before you go live.

## Setting up and testing Algomo

Algomo's free plan is self-serve with no card. You give it your address, it finds the systems your pages call, and the first version answers the same day. You can preview it on your live site from the browser extension before adding any code, from a test allowance kept apart from live use.

Once live, every answer records the tools it called, with inputs, outputs, time and cost.

A conversation in Algomo, with the tools the agent called, the visitor's record and the reply box your team takes over from.

Our take: ask each vendor what will be answering on your own site by the end of the first day, and with whose work.

## What does each vendor store that could reach your customers' accounts?

TL;DR: Open.cx is ISO 27001 certified with a SOC 2 Type II report and stores the secrets your actions use, while Algomo's agent runs from the visitor's browser and keeps no token for anything your site already does.

An agent that reads orders needs access to the order system. Your security team will ask what the vendor keeps to get it.

## Open.cx security

Open.cx says it is ISO 27001 certified, has a SOC 2 Type II report and is aligned with GDPR, with hosting in Frankfurt. Its AI providers process some data outside the EU under its DPA. Action credentials live as global variables or named secrets, and the widget can pass a signed-in visitor's own token.

## Algomo security

Algomo is secure by design. When it reads stock, a price or the visitor's own order, the request leaves the visitor's browser exactly as your page sends it. For that, Algomo receives and stores no token or credential.

A system only staff can reach needs a connector, and Algomo stores that login encrypted with AES-256-GCM, revocable at any time. Algomo holds Cyber Essentials for the whole organisation, works to UK and EU GDPR, hosts its application, database and files in the EU, and offers a data processing agreement on every plan. [Algomo's compliance page](/trust) has the detail.

Algomo connectors for staff-only systems. Each stored login is encrypted and can be revoked.

Our take: ask each vendor which stored secret could open a customer's account, and how you revoke it.

## How much does Open.cx cost compared with Algomo?

TL;DR: At 1,000 AI resolutions a month Open.cx comes to $750 to $900 plus carrier costs, while 1,000 helped conversations on Algomo fit the $200 plan.

A per-resolution bill rises with every month your agent does well. Your finance team will want to see it at today's volume and at twice that.

## How Open.cx bills

Open.cx charges 75¢ to 90¢ per resolved ticket, with the exact rate set by your monthly volume and agreed in writing before you go live. Above 100,000 resolutions a month it quotes a custom rate. There are no seat, message, setup or monthly fees.

Open.cx's price of 75¢ to 90¢ per resolution, set by monthly volume and locked in writing before go-live. From Open.cx's pricing page.

A resolved ticket is one Open.cx closes without a teammate, where the customer confirms the outcome or does not reopen it. A ticket handed to a person is not billed. Phone, WhatsApp and email send costs pass through at cost, which Open.cx says usually comes to under 10¢ per resolution.

## How Algomo bills

Algomo's free plan has 100 credits a month, about twenty helped conversations, with no card. Paid plans are one monthly amount you choose: $50 for 2,000 credits, $200 for 8,000, $600 for 25,000, up to $4,300 for 200,000. [Algomo's pricing page](/pricing) has the full ladder.

A conversation that helped someone costs 5 credits, plus 5 for each further ten replies. Spam and dead ends cost nothing. Unused credits roll over, and the agent pauses when they run out, so the bill stays at the amount you chose.

Here is the sum. At 1,000 resolutions a month, 75¢ to 90¢ each comes to $750 to $900, plus carrier costs. At 5,000, it comes to $3,750 to $4,500.

On Algomo, 1,000 helped conversations use 5,000 credits, which the $200 plan covers, and 5,000 use 25,000 credits, which is the $600 plan. Open.cx's figure also covers phone, email and messaging. Algomo's covers the agent on your website and its inbox.

## What moves each bill

|  | Algomo | Open.cx |
| --- | --- | --- |
| One more AI resolution | ✓ 5 credits from your plan | 75¢ to 90¢ |
| A conversation handed to a person | ✓ No separate charge | ✓ Not billed |
| Phone and messaging send costs | None | Passed through at cost |
| A month busier than planned | ✓ The agent pauses at your amount | Billed per extra resolution |
| Starting free | ✓ Free plan, no card | No free plan |

Our take: ask Open.cx for your rate in writing at your volume, multiply by last month's resolutions, and compare it with Algomo's plan for the same count.

## What to ask any vendor selling you an AI agent

TL;DR: Five questions, each with a check you can run during the demo.

- Who describes each of our APIs to the AI? Ask to watch one being connected. - When was our pricing page last read? Ask for the timestamp. - If we change a line now, when does the agent say the new one? Change it and ask. - Can the agent finish a task on our page for the visitor? Ask it to. - Can it run a step our site cannot, such as a two-factor check? Ask to see it.

Run each check on your own site, not on a demo the vendor set up.

## Which one fits your team?

### Choose Open.cx if

- Your customers phone, email and message on WhatsApp as much as they use your website.
- You run outbound campaigns by phone, SMS or email and want the same AI behind them.
- Your procurement needs ISO 27001 or a SOC 2 Type II report from the vendor today.

### Don't choose Open.cx if

- Your pages change more often than a weekly crawl.
- Nobody on your team has time to write up each API as an action.
- You want a monthly amount set in advance instead of a charge per resolution.
- You want to start on your own site today, on a free plan.

## Conclusion

TL;DR: Choose Open.cx for one AI across phone, email, messaging and outbound, and choose Algomo when your customers ask on your website and you want the connections built for you and each answer read live.

On the integration, Open.cx gives your team a form for each action or an OpenAPI import. Algomo uses the requests your site already makes, with a first version the same day.

On freshness, Open.cx answers from a crawl that repeats weekly by default. Algomo reads the live page and backs it with a free month. [The comparison hub](/compare) sets other AI agents side by side.

## Questions buyers ask about Algomo and Open.cx

### Is Algomo a good Open.cx alternative?

Yes, when your customers ask on your website about things that change. Algomo connects itself to your site's own requests, reads each page live and bills one monthly amount. If most of your volume comes by phone, email or WhatsApp, Open.cx covers those channels.

### How much does Open.cx cost?

[Open.cx's pricing page](https://www.open.cx/pricing) lists 75¢ to 90¢ per resolved ticket, with the rate set by monthly volume and agreed in writing before go-live. Handed-over tickets are free, carrier costs pass through at cost, and above 100,000 resolutions a month the rate is quoted.

### Who owns Open.cx?

Open.cx is run by OpenChat, Inc., an independent company founded in 2023. It raised $7 million in a round led by Y Combinator and X by Unifonic. No sale or merger has been announced.

### Is Open the same as OpenCX?

Yes. The product now carries the name Open on open.cx, and its documentation and widget packages still use the OpenCX name.

### How often does Open.cx re-read my website?

Every 7 days by default. [Open.cx's docs](https://docs.open.cx/) set 168 hours as the shortest interval you can choose, with daily crawls switched on by the Open.cx team on request.

### Does Open.cx answer phone calls?

Yes. Open.cx runs voice agents on local numbers in over 100 countries, and outbound calls. Algomo does not answer phone calls.

### What do 10,000 AI resolutions a month cost on each?

On Open.cx, 10,000 at 75¢ to 90¢ come to $7,500 to $9,000, plus carrier costs. On Algomo, 10,000 helped conversations use 50,000 credits, which the $1,400 plan with 60,000 covers.

## Where these facts come from

All the information on this page was available in November 2026. The sources are:

- [Open.cx's pricing page](https://www.open.cx/pricing): the rate, what a resolved ticket is, fees, carrier costs, the platform list and the refund guarantee. - [Open.cx's home page](https://www.open.cx/): the six agents, channels, customer stories, security claims and the guarantee terms. - [Open.cx's funding announcement](https://www.open.cx/news/announcing-our-new-funding-round): the $7 million round. - [Open.cx's company summary](https://www.open.cx/llms.txt): OpenChat, Inc. and the founding year. - [Open.cx's docs](https://docs.open.cx/): [the website crawler article](https://docs.open.cx/knowledge/sources/website/connect), [the build an action article](https://docs.open.cx/actions/build-an-action), [the MCP article](https://docs.open.cx/mcp/introduction), [the Companion article](https://docs.open.cx/companion/introduction), [the Companion mode article](https://docs.open.cx/widget/companion-mode) and [the handoff topics article](https://docs.open.cx/handoff/topics). - [Open.cx's customer stories](https://www.open.cx/customer-stories), and [the Trunkrs website](https://trunkrs.nl/) for the chat on its home page. - [Algomo's pricing page](/pricing), [Algomo's compliance page](/trust) and [the guarantee page](/resources/guarantee). - [The demo library](/demos), for [the Blinds 2go demo](/demos/blinds2go), [the Nike demo](/demos/nike) and [the IKEA demo](/demos/ikea).
