Inbox

What arrives, and when

Reachpool reads each sender’s LinkedIn messages every 10 to 20 minutes, within the sender’s working hours, so a reply shows up within about 20 minutes. When a sender is first connected, the last 30 days come in. A paused or signed-out sender’s messages arrive once it works again. Messages someone wrote straight on LinkedIn appear too, marked written on LinkedIn.

Each conversation shows the lead, the sender it is with, and the campaigns that brought them together.

Views and filters

All, Unread, Mine and Snoozed, narrowed by label, assignee (or unassigned), sender, campaign and tag. Opening a conversation marks it read for the whole team.

AI labels

Each reply gets one of these labels by itself:

• Interested
• Question
• Not now
• Out of office
• Wrong person
• Not interested

The AI reads the text of the conversation’s last 8 messages only: no names, profile or campaign. When it is not sure, the conversation stays without a label. Labels cost no credits. Change one by hand and it stays yours; Let AI label it hands it back.

Working a conversation

• Assign it to a teammate, or to nobody.
• Snooze it: later today, tomorrow morning or next week. It leaves the list and comes back then; Unsnooze now brings it back at once.
• Mark unread, Meeting booked, and tags of up to 40 characters.
• Teammates in the same conversation show as “Pat is here”, and “Pat is typing…” while they write, so two people do not answer the same lead.
• Keys: j / k next and previous, r reply, u mark unread, Esc back to the list.

Replying

Write in the reply box and Send (or Cmd/Ctrl + Enter). {{firstName}} and the other variables are filled in for the lead. Insert a saved reply starts from one of the workspace’s saved replies, kept under Saved replies.

A reply goes from the conversation’s sender, through LinkedIn, within the sender’s working hours and limits like any message, so it can take a moment: it shows Sending…, then Sent, or Not sent with the reason, for example when the lead is not a 1st-degree connection. Sending again after a lost connection never sends it twice. A paused sender’s reply waits until it is resumed.

Notifications

Notifications, in the console’s header, lists sender alerts as they happen and, each morning after 08:00 in the workspace’s time, a digest of the day before’s replies, also by email. A day without replies sends nothing.