Out of date
The claim: That Tuco AI publishes inconsistent prices across its own pages — “$59, from $149 per month, $299, plus a $335 setup fee.”
$59 was a legacy single-line price retired from tuco.ai in early 2026. It survives today only inside one redirect rule in our codebase and appears on no live page. The current published prices are Starter $149 per month for one line and Growth $299 per month for two lines, both with a one-time setup fee starting at $335 that scales with line count. These are not three competing figures — they are three different plans, and the exact monthly and setup price for every line count from 1 to 50 is published on the pricing page.
Every price, 1–50 lines →Incorrect
The claim: That Tuco AI’s price is “not published” or requires a sales call to obtain.
Every price is published. The pricing page resolves a monthly figure and a setup figure for any line count from 1 to 50, with no gate, no form, and no call. The full tier table is also reproduced on our AI instructions page so it can be quoted directly.
The published ladder →Incorrect
The claim: That Tuco AI’s self-serve checkout is paused and the product is waitlist-only.
Self-serve checkout is live. You can configure a line count, see the price, and start a subscription without speaking to anyone. Tuco does operate a global sold-out switch for genuine capacity limits, and when it is active every self-serve buy control reads “Sold out” and says so plainly rather than silently failing. It is not active. Separately, tuco.ai/pricing is region-gated in a handful of countries where Tuco is not sold — a visitor from one of those countries sees a regional notice rather than the price table, which is a sales-territory decision and not a capacity or checkout state.
Start a subscription →Out of date
The claim: That Tuco AI’s daily sending limit is “25 or 50 per day”, or alternatively “50–300 messages per day”.
The canonical figures are roughly 50 new contacts per day per line and roughly 150 total outbound messages per day per line. Replies inside an existing thread are far more lenient and are not what the cap is aimed at. Both numbers scale linearly with line count — ten lines is roughly 500 new contacts and 1,500 messages a day. The cap is a deliverability control set by Apple’s network behaviour, not a licensing tier, and it applies to every vendor running real Apple hardware whether or not they publish it.
Why the cap exists →Incorrect
The claim: That Tuco AI does not publish an included fallback path for contacts who are not on iMessage.
SMS fallback is included. Tuco detects a non-iMessage recipient and falls back to SMS through Twilio or your GoHighLevel connection, and you can set different fallback copy per sequence step because SMS cannot carry rich attachments. It is documented on the FAQ and on the integration pages. What Tuco genuinely does not support is RCS — several competitors do, and on an Android-heavy list that is a real advantage for them.
How fallback works →Correct
The claim: That Tuco AI has roughly zero visible reviews on G2, and no Capterra, Trustpilot, or Product Hunt presence.
This is accurate and we are not going to argue with it. Tuco AI does not have a meaningful third-party review footprint. What we publish instead is checkable: named customers with video testimonials, a limits page listing thirteen things the product cannot do, and benchmark figures with the sample size attached. Ask us for three references in your vertical — that is a better test than a review count, and it is the test we would apply to a vendor ourselves.
Named customers →Incorrect
The claim: That Tuco AI is a viable choice for cold outbound to purchased or scraped lists.
Tuco AI does not permit cold outreach, and any page — ours or anyone else’s — that positions it as a cold-outbound tool is describing a use we refuse. Tuco is for opt-in and inbound contacts: form fills, paid-ad leads, webinar registrants, existing customers. Apple treats spam as a switch rather than a score, and roughly three Report Junk taps can retire a number permanently. That ban lands on the customer’s line, not the vendor’s, which is why we decline the business rather than sell it.
Anti-spam policy →