Conversations
iMessages
iMessages show iMessage and SMS activity inside your conversations.
Use iMessages to review outgoing messages, incoming replies, delivery activity, message history, campaign context, and follow-up activity from iMessage-based campaigns.
Unlike Email and LinkedIn, iMessage conversations should be viewed inside 1eyeᴬᴵ. This is where your team can review the message history, reply context, campaign connection, target contact, company, persona, ICP, and conversation intent.
What iMessages are for
iMessages help your team answer:
Use iMessages to:
Review outgoing iMessages
Review SMS fallback messages when iMessage is not available
Review incoming replies
Track reads when available
Understand which campaign generated the message
Review conversation intent
Follow up on interested contacts
Investigate failed or not delivered messages
Understand the full message thread in context
Review direct-message activity inside 1eyeᴬᴵ
Where iMessages appear
iMessages appear inside Conversations.
You can review them from:
Conversations → Overview
Conversations → iMessages
Conversations → Conversation Intent
A specific conversation detail view
Use iMessages when you want to focus only on iMessage and SMS activity.
Use Overview when you want to review all channels together.
Viewing iMessages in 1eyeᴬᴵ
iMessage and SMS conversations should be viewed inside 1eyeᴬᴵ.
Unlike connected Gmail mailboxes or connected LinkedIn accounts, iMessage line activity is managed in 1eyeᴬᴵ. Your team should use 1eyeᴬᴵ to review the message thread, understand the campaign context, and handle follow-up.
Use 1eyeᴬᴵ to view:
Outgoing iMessages
SMS fallback messages
Incoming replies
Read status when available
Not delivered messages
Campaign context
Target contact context
Company context
ICP match
Persona match
Conversation intent
This keeps iMessage activity tied to your GTM workflow instead of splitting context across tools.
iMessage and SMS delivery
1eyeᴬᴵ sends through an iMessage-enabled line.
If the target contact has an iMessage-compatible device, such as an iPhone with iMessage enabled, the message can be delivered as an iMessage.
If the target contact does not have an iMessage-compatible device, or iMessage is not available for that phone number, the message may be delivered as SMS.
This means your team can still reach contacts who do not use iMessage, as long as the contact has a usable phone number and the line can deliver the message.
Delivery type may depend on:
The target contact’s device
Whether iMessage is enabled for the phone number
Carrier and phone number support
Message availability
Delivery conditions at the time of send
What an iMessage conversation includes
An iMessage conversation may include:
Target contact
Contact phone number
iMessage line
Line type
Message body
Incoming or outgoing direction
Read activity when available
Delivery status when available
Campaign name
Company context
ICP match
Persona match
Intent status
Intent score
Intent reason
Message timestamp
This gives your team enough context to review and follow up directly from 1eyeᴬᴵ.
Incoming and outgoing messages
iMessage conversations can include incoming and outgoing messages.
Direction | What it means |
|---|---|
Outgoing | Your team or campaign sent an iMessage or SMS fallback message. |
Incoming | The target contact replied by iMessage or SMS. |
Outgoing messages help you understand what was sent.
Incoming messages help you understand what the contact said and whether follow-up is needed.
Outgoing iMessages
Outgoing iMessages are messages sent from a connected iMessage-enabled line.
Outgoing messages may include:
iMessage line
Target contact
Contact phone number
Message body
Sent timestamp
Campaign context
Read activity when available
Delivery status when available
Use outgoing messages to confirm what was sent to the target contact.
SMS fallback messages
If iMessage is not available for the target contact, the message may be sent as SMS.
SMS fallback may happen when:
The target contact does not use an iPhone
The target contact has iMessage disabled
The phone number is not registered with iMessage
iMessage delivery is unavailable at the time of send
The device or carrier falls back to SMS
SMS fallback still appears inside 1eyeᴬᴵ conversation history when available.
Incoming replies
Incoming replies are messages received from target contacts.
Incoming replies are important because they can create Conversation Intent.
Incoming replies may be classified as:
Positive
Neutral
Negative
The reply may also include an intent reason such as:
Meeting
Pricing
Info
Later
Referral
Competitor
Budget
No Need
Wrong Persona
Requested Remove
Use incoming replies to decide the next action.
Message body
The message body shows what was sent or received.
Use the message body to review:
What your team sent
What the contact replied
Whether the message was personalized
Whether the reply needs action
Whether the contact asked for something specific
Whether the contact should be excluded or followed up with
Always read the message body before taking important action.
Read tracking
iMessages may show read activity when available.
Read tracking helps you understand whether a target contact read the message.
When available, 1eyeᴬᴵ may show:
Whether the message was read
When the message was read
Which contact read it
Use read activity as an engagement signal.
Do not treat reads as a reply or buying intent by themselves.
When reads may not appear
Read tracking may not always be available.
Read activity can be affected by:
Recipient device settings
iMessage read receipt settings
SMS fallback
Carrier behavior
Device behavior
Delivery limitations
Tracking availability
If a message shows no read activity, it does not always mean the contact never saw it.
Replies are stronger than reads.
Delivery status
iMessages may show delivery status when available.
Common statuses may include:
Status | What it means |
|---|---|
Sent | The message was sent. |
Read | The message was read when read tracking is available. |
Replied | The contact replied. |
Not Delivered | The message could not be delivered. |
Draft | The message was drafted but not sent. |
Discarded | The message was discarded. |
Use delivery status to understand what happened to the message.
Sent
Sent means the message was sent from a connected iMessage-enabled line.
A sent message may later show read activity, replies, or not delivered status depending on what happens next.
Read
Read means the message was read when tracking is available.
Read is an engagement signal, but not the same as a reply.
Use read activity to prioritize follow-up when combined with ICP, persona, and campaign context.
Replied
Replied means the target contact responded.
Replies are stronger than reads.
A reply may trigger Conversation Intent classification.
Draft
Draft means the message was created but not sent.
Drafts may need review, editing, approval, or manual sending.
Discarded
Discarded means the message was prepared but not used.
Review discarded messages if you need to understand why messages were not sent.
Not Delivered
Not Delivered means the iMessage or SMS could not be delivered.
Not delivered may happen because of:
Invalid phone number
Unreachable number
Carrier issue
iMessage delivery issue
Line issue
Channel limit
Contact data issue
Message restriction
Review Not Delivered messages to clean up contact data and fix campaign issues.
iMessages and Conversation Intent
iMessage and SMS replies can create Conversation Intent.
When a target contact replies, 1eyeᴬᴵ may classify the conversation by:
Intent status
Intent reason
Intent score
Example:
This helps your team decide what to do next.
Positive iMessage replies
Positive iMessage replies show interest or willingness to continue.
Examples:
Recommended action:
Reply quickly
Answer the request directly
Move the conversation forward
Update contact status if needed
Stop unnecessary automated follow-ups
Neutral iMessage replies
Neutral iMessage replies are unclear or weak.
Examples:
Recommended action:
Read the full thread
Review contact and company context
Decide whether follow-up is useful
Ask a simple clarifying question if appropriate
Negative iMessage replies
Negative iMessage replies show disinterest, disqualification, or a request to stop outreach.
Examples:
Recommended action:
Stop outreach where needed
Mark the contact as Excluded if appropriate
Respect opt-out requests
Use the feedback to improve targeting
iMessages and campaigns
iMessages often come from campaign workflows.
A campaign may send:
Intro iMessage
Follow-up iMessage
Final iMessage
Persona-specific iMessage
ICP-specific iMessage
SMS fallback when iMessage is not available
When reviewing an iMessage conversation, check the campaign context so you understand why the message was sent.
iMessages and workflows
iMessage activity is often tied to workflow nodes.
An iMessage workflow node may send:
iMessage when available
SMS fallback when iMessage is not available
iMessage can also be part of a multi-channel workflow with Email and LinkedIn.
Example:
Use Console to inspect whether an iMessage node executed, is pending, or failed.
iMessages and target contacts
iMessages are tied to target contacts when available.
Review the contact context before replying:
Contact name
Title
Persona
Phone number
Company
Contact status
Conversation history
This helps make the reply more relevant.
iMessages and target companies
iMessage conversations also include company context when available.
Review the company before replying:
Company name
Website
ICP match
Industry
Company status
Campaign
Other contacts at the company
In B2B, the company context matters as much as the person.
iMessages and ICP match
If the company matches an ICP, the reply may be more important.
For example:
Use ICP context to decide how quickly to respond and how much effort to invest.
iMessages and persona match
If the contact matches a persona, the reply may be more important.
For example:
Use persona context to tailor the response.
A founder, RevOps leader, IT leader, and finance leader may need different follow-up.
iMessage limits
iMessage activity is subject to line limits and 1eyeᴬᴵ workflow limits.
Limits may include:
New conversations per day
Plan-level iMessage line limits
Campaign workflow timing
User or workspace schedule when available
If iMessages are not sending, check line limits and campaign execution in Console.
New conversations per day
An iMessage line may show a daily new conversation limit.
Example:
This helps control how many new iMessage or SMS conversations can be started from the line each day.
Use this limit carefully. Do not treat it as a target to max out every day.
Search iMessages
Use search to find specific iMessage conversations.
You can search for:
Contact name
Company name
Campaign name
Keyword from a message
Intent reason
Phone number
Examples:
Search is useful when you know which message or contact you want to review.
Filter iMessages
iMessages can be filtered.
Common filters may include:
Channel
Direction
Intent Status
Intent Reason
Intent Score
Status
Record Status
Campaign
Company
Updated Date
Use filters to narrow the message list.
Filter by channel
Use channel filters when reviewing iMessage inside broader Conversations.
Select:
This shows iMessage and SMS activity and hides Email or LinkedIn activity.
Filter by direction
Use direction to focus on incoming or outgoing message activity.
Direction | Use it for |
|---|---|
Incoming | Reviewing replies from contacts. |
Outgoing | Reviewing sent iMessages or SMS fallback messages. |
Incoming is usually where follow-up work starts.
Filter by intent status
Use intent status to review replies by outcome.
Common values:
Positive
Neutral
Negative
Start with Positive when following up.
Review Negative for opt-outs, wrong-person replies, and disqualifications.
Filter by intent reason
Use intent reason to group replies by follow-up type.
Examples:
Meeting
Pricing
Info
Later
Referral
Competitor
Budget
No Need
Wrong Persona
Requested Remove
This helps your team handle similar conversations together.
Filter by status
Use status to review delivery or message state.
Examples may include:
Sent
Read
Replied
Draft
Discarded
Not Delivered
This is useful for both follow-up and troubleshooting.
Filter by campaign
Use campaign filters to review iMessage activity from a specific campaign.
This helps answer:
Which iMessage replies came from this campaign?
Which messages were read?
Which messages were not delivered?
Which contacts need follow-up?
Which campaign generated positive replies?
Filter by company
Use company filters to review iMessage activity for one target company.
This is useful when several contacts from the same company are in campaigns.
Filter by updated date
Use updated date to find recent iMessage conversations.
This helps you review:
New replies today
Recently read messages
Recently updated message threads
Activity from a campaign launch window
Recommended workflow: review iMessage replies
Use this workflow daily.
Open Conversations
Go to iMessages
Filter by Incoming if needed
Start with Positive intent
Review Meeting and Info replies first
Open each conversation
Read the full thread
Review company and persona context
Reply or route the conversation
Stop automated follow-ups where needed
Recommended workflow: review read activity
Use this workflow when a contact has read but not replied.
Open Conversations
Go to iMessages
Find the message conversation
Review read status when available
Check company and persona fit
Decide whether a follow-up is warranted
Avoid overreacting to reads alone
Reads can indicate engagement, but replies are stronger.
Recommended workflow: reply to an iMessage
Use this workflow when responding to a target contact.
Open the iMessage conversation
Read the latest reply
Review intent status, reason, and score
Review the target contact
Review the company and ICP
Review the campaign context
Keep the reply concise
Answer the contact directly
Move the conversation to the next step
Send the reply from 1eyeᴬᴵ
Recommended workflow: review not delivered iMessages
Use this workflow when iMessages or SMS fallback messages are not delivered.
Open Conversations
Select Not Delivered if applicable
Filter by iMessage if needed
Open the message or contact
Review the contact phone number
Check iMessage line status
Check campaign context
Check daily conversation limits
Open Console for execution details
Fix the issue before continuing
Recommended workflow: handle opt-outs
Use this workflow when someone asks not to be contacted.
Open the conversation
Confirm the request
Do not continue iMessage or SMS outreach
Mark the contact as Excluded
Stop campaign outreach to that contact
Review whether the company should also be excluded
Keep the record clean for future campaigns
Best practices
Review iMessages inside 1eyeᴬᴵ
iMessage and SMS conversation history should be managed in 1eyeᴬᴵ.Start with incoming replies
Replies are more important than sent messages or reads.Prioritize positive intent
Meeting, info, referral, and pricing replies should be handled quickly.Keep messages short
iMessage and SMS are direct channels. Keep replies concise.Read the full thread
Do not reply based only on a preview.Use company and persona context
A better reply reflects who the contact is and why they were targeted.Treat reads as directional
Reads are useful, but not perfect.Understand SMS fallback
If iMessage is not available, the message may be sent as SMS.Respect daily limits
Do not max out daily new conversation limits just because they are available.Respect opt-outs immediately
Requested remove should stop outreach.Review not delivered messages regularly
Delivery issues usually point to phone data, line, channel, or workflow issues.Use 1eyeᴬᴵ for GTM context
1eyeᴬᴵ connects the iMessage thread to campaign, company, ICP, persona, signals, and intent.Use replies to improve campaigns
Replies tell you which ICPs, personas, messages, and workflows are working.
Troubleshooting
I do not see an iMessage I expected
Check:
Filters are not hiding it
You are in the correct workspace
You are viewing iMessages or All Conversations
The message had time to process
The campaign is selected correctly
The contact phone number is correct
The iMessage line is connected
An iMessage reply is not showing
Check:
The iMessage line is connected
The reply went to the connected line
The message had time to sync
Filters are not hiding incoming messages
The conversation is tied to the correct contact or campaign
The contact phone number matches the target contact record
I do not see the iMessage in an external inbox
iMessage and SMS activity should be viewed inside 1eyeᴬᴵ.
Use 1eyeᴬᴵ to review message history, campaign context, replies, status, and intent.
Message was sent as SMS instead of iMessage
This can happen when iMessage is not available for the target contact.
Common reasons include:
The target contact does not use an iPhone
The target contact has iMessage disabled
The phone number is not registered with iMessage
iMessage delivery is unavailable at the time of send
The device or carrier falls back to SMS
The message can still be delivered as SMS when available.
Read status is not showing
Read tracking may be blocked or unavailable.
Common reasons include:
Recipient read receipts are off
Recipient device settings
SMS fallback
Carrier behavior
Delivery limitations
Tracking availability
Read count looks different than expected
Read data may depend on device and delivery behavior.
Use read data as directional context, not absolute proof of interest.
Message was not delivered
Check:
Contact phone number
iMessage line connection
Campaign status
Daily conversation limits
Contact status
Exclusions
Delivery failure details when available
iMessage intent looks wrong
Read the full thread.
Intent can be harder to classify when replies are short, vague, sarcastic, incomplete, or missing context.
A contact replied “stop” or “remove me”
Stop outreach and mark the contact as Excluded.
Do not continue campaign messages to that contact.
iMessage line disconnected
Check the iMessage channel setup.
A line may become unavailable because of:
Line status issue
Workspace plan limit
Channel disabled
Provisioning issue
Admin or support action
If the line is not connected, it cannot be used in campaigns.
FAQ
What are iMessages?
iMessages are iMessage and SMS conversation activity from connected iMessage-enabled lines.
What activity is included?
iMessages may include outgoing iMessages, SMS fallback messages, incoming replies, read activity when available, and delivery status when available.
Can I view iMessages outside 1eyeᴬᴵ?
iMessage and SMS activity should be viewed inside 1eyeᴬᴵ.
Why use 1eyeᴬᴵ to view iMessages?
1eyeᴬᴵ adds campaign context, target contact, company, ICP, persona, signals, workflow history, message status, and conversation intent.
Can I send iMessages from 1eyeᴬᴵ?
Yes, when iMessage is enabled, an iMessage line is connected, the target contact has a phone number, and the campaign workflow includes an iMessage node.
What happens if the contact does not have an iPhone?
If the target contact does not have an iMessage-compatible device, the message may be sent as SMS.
What happens if iMessage is disabled for the contact?
If iMessage is not available for that phone number, the message may be sent as SMS.
Can iMessage replies create Conversation Intent?
Yes. iMessage and SMS replies can be classified by intent status, reason, and score when available.
What should I do with positive iMessage replies?
Review quickly, reply with context, and move the conversation forward.
What should I do with negative iMessage replies?
Respect the response, stop outreach where needed, and exclude the contact when appropriate.
What should I do with not delivered iMessages?
Review contact phone data, iMessage line status, campaign setup, and Console execution details.
Can one iMessage conversation have multiple messages?
Yes. A conversation can include multiple outgoing messages and incoming replies.
Can one conversation include other channels?
In the broader Conversations view, one conversation can include activity across email, LinkedIn, iMessage, and SMS fallback when available.
Do iMessage limits apply?
Yes. iMessage activity is subject to line, plan, schedule, and workflow limits.
Are reads always available?
No. Read tracking depends on device settings, delivery type, and availability.
Are replies stronger than reads?
Yes. Replies are usually much stronger than reads.
Next step
Next, go to Tasks to learn how to manage follow-ups, approvals, and action items from campaigns and conversations.