Question 1

What is the difference between the iMessage status "sent" and "delivered"

Accepted Answer

"Sent" means Tuco successfully handed your message to iMessage — it does not, by itself, confirm the recipient received or read it. "Delivered" is the separate confirmation that it reached their device. In practice, both usually mean the message went through fine. The only statuses that signal a real problem are Fallback and Failed.

What each status means

Sent — Tuco handed the message to iMessage. Not a delivery or read confirmation.
Delivered — Apple confirmed the message reached the recipient's device.
Read — the recipient opened it (shows only if they have read receipts turned on).
Fallback — the recipient isn't reachable on iMessage, so it should go out over your SMS fallback instead.
Failed — the message couldn't be sent (e.g. a bad number, or a line issue).

Why a message can show "Sent" but not "Delivered"

This is usually not a problem:

iOS message screening (iOS 26+): if the recipient hasn't saved your number, Apple may screen messages from unknown senders and suppress the delivery receipt — so the message shows "Sent" even though it actually reached their inbox.
The recipient has read receipts turned off, or is on Do Not Disturb / a Focus mode.
On older iOS versions (or with screening off), "Delivered" appears much more consistently.

So a "Sent" status is normal and usually fine. You only need to act on Fallback (recipient not on iMessage — set up an SMS fallback) or Failed (a real sendin

Question 2

How to install Tuco AI for iMessage automation inside Go High Level (GHL)

Accepted Answer

How To Integrate or Connect GoHighLevel Integration with Tuco AI - iMessage Automation Software through GHL

Made by Tuco Support with Scribe

Learn how to configure your GoHighLevel integration to streamline your marketing automation using Tuco AI. This guide walks you through the essential steps to connect your API keys and location settings successfully.

Integration Initiation

Select Integrations from the sidebar menu after logging into app.tuco.ai

If you see Lead Connector instead of Go High Level do not worry! Go High Level is a trademark and hence we were requested to use the name "Lead Connector" instead of Go High Level

||| If you see Lead Connector instead of Go High Level do not worry! Go High Level is a trademark and hence we were requested to use the name "Lead Connector" instead of Go High Level

Choose the run mode for Tuco and click Continue.

![](https://colony-r

Question 3

How to uninstall and reinstall Go HIgh Level app for Tuco AI

Accepted Answer

How to Uninstall and ReInstall GoHighLevel with Tuco AI

Made by Tuco Support with Scribe

Learn how to seamlessly remove and re-install your GoHighLevel account to the Tuco AI platform. This guide walks you through the necessary steps to reinstall the integration and configure your API keys for a successful connection.

Uninstall Current App

Navigate to App Marketplace

Select the "Installed Apps" tab

Click the options menu (three dots) for the app

Select "Uninstall"

Confirm uninstallation by clicking "Uninstall"

![](https://colony-

Question 4

How to call using Tuco AI Calling Extension inside of Go High Level using the same iMessage Number

Accepted Answer

How to Install and Use the Tuco Calling Extension inside of Go High Level

Made by Tuco Support with Scribe

Learn how to effectively find, install, and configure the Tuco Calling Chrome extension for your browser. This guide provides step-by-step instructions for managing your account, checking conversations, and adjusting call settings for a seamless communication experience.

||| Gotcha! Make sure to visit chrome://extension and double check it's turned on and all permissions are given

||| Gotcha 2! Old pages will not load you will have to logout, login and do a hard refresh (command + shift + R on mac and Control + Shift + R on windows multiple times) to make sure the extension loads

Extension Installation

Search for the "Tuco Calling" Chrome extension or directly go to https://chromewebstore.google.com/detail/tuco-calling/penfbnaoncbafijgahkldipilkjflgac

![](https://colony-recorder.s3.amazonaws.com/files/2026-07

Question 5

Troubleshoot GoHighLevel → Tuco Message Delivery Issues (Message Not Sent, Follow-Up Skipped, Delayed, Queued)

Accepted Answer

Learn how to troubleshoot message delivery between GoHighLevel and Tuco. This guide explains how to use GoHighLevel Execution Logs and Tuco Activity Logs to determine why a message was sent, skipped, delayed, queued, deduplicated, or rescheduled.

👉 Prefer a plain checklist? See Why didn't my contact get a message?

Common Issues

No phone number, or number in the wrong field

The most common reason a contact isn't messaged is that Tuco has no phone number it can read. Tuco reads the standard phone field. If the real number lives in a custom GHL field (e.g. “Mobile”, “Cell”, “Phone 2”), map that field to phone so Tuco imports it — otherwise the send fails with missing_recipient.

Open the contact in Tuco and confirm a phone number is present.
If it's blank, fix the field mapping and re-sync.

Message Deduped

Tuco prevents accidental duplicate sends.

There are two layers of deduplication:

GoHighLevel may cache identical requests within the same workflow execution.
Tuco deduplicates identical messages sent to the same contact within a 24-hour window.

If you're testing with a single contact:

Change the message (e.g. "Hi" → "Hey").
If sending an attachment, upload a new copy instead of reusing the existing file.

You can upload new attachments at:

https://app.tuco.ai/uploads

Line Offline

Occasionally Apple temporarily marks a Ma

Question 6

My lead/customer doesn't see a contact card (or the "Maybe: [Name]" label)

Accepted Answer

Short version: the "Maybe: [Name]" label is generated by the recipient's device, not by us. It comes from an on-device Apple feature, and the setting that controls it lives on your lead's iPhone or Mac — it ships enabled by default, so if they don't see it, it's worth confirming the toggle on their device.

What we control (and what we don't)

There are two separate mechanisms, and only one of them is on our side:

What we control: we add the contact on the sending line and can enable "Share Name and Photo" (Messages → Settings → General). That sends the recipient a prompt offering our name and photo, and can be set to share automatically with contacts or ask each time. But that produces a save-contact prompt on their end — it does not create the "Maybe:" label.
What the recipient's device controls: the "Maybe: [Name]" label itself. This is generated entirely on the recipient's device.

How the "Maybe:" label actually works

Apple calls this Siri Suggestions (formerly "Suggested Contacts"). When a message arrives from a number that isn't saved in the recipient's contacts, their device checks its own local data — Mail, Messages, Calendar — for anything identifying that number, and shows "Maybe: [Name]" if it finds a match.

All processing happens on-device. Nothing is sent from our side, and there is nothing we can toggle to force it.

Where the setting is on the recipient's device

Siri Suggestions ship enabled by default,

Frequently Read Articles

Browse All Categories