Read and respond in the smart inbox
Keep replies from connected mailboxes together and answer from the original sender.
On this page
Use Inbox as your daily conversation queue
Inbox brings replies from connected mailboxes into one place. You can read and respond there without moving between every individual mailbox. Before answering, read the thread and identify the sender mailbox and original outreach context. A reply may be a question, interest, an automatic response or a request to stop. The classification helps you find relevant messages, but the person’s actual words should determine your response.
Assign someone to review new replies regularly when a campaign is active. The guides do not describe a complete assignment or ticket-status workflow, so agree ownership in your team process rather than assuming an automatic owner will be chosen.
Read the thread and send an answer
Open Inbox
Select Inbox from the sidebar in the intended organization. Browse replies gathered from the connected mailboxes.
Expected result: The relevant incoming conversations are available in one view.
Open the conversation
Read the original message and the incoming response. Inspect the classification, including any opt-out detection.
Expected result: You can identify what the recipient is asking and which mailbox owns the thread.
Write a direct answer
Type your response in the conversation. Answer the question asked and avoid repeating the original pitch when the recipient has moved the discussion forward.
Expected result: The draft addresses the actual reply and has the intended next step.
Send from the existing conversation
Send your response in Inbox. The documented behavior uses the same inbox as the original conversation.
Expected result: The thread shows your response from the original sending mailbox.
Continue from that thread
Return to the same conversation when the recipient responds again. Check the recent messages before another teammate replies.
Expected result: The exchange remains together, with no unnecessary new outreach thread.
Example replies by intent
| Item | How to use it |
|---|---|
| A request for details | Answer the specific question and offer a relevant resource if it exists. |
| An interested reply | Clarify the next practical step without treating interest as a confirmed sale. |
| A request to stop | Respect it and review its classification and follow-up outcome. |
| An automatic response | Read the context; the guides do not specify every automatic-response rule. |
| A mistaken contact | Acknowledge the mismatch and correct the audience preparation process. |
Example answer to a real question
Example recipient question: What would the review cover?
Example answer:
It covers how work moves between people, what information is missing at each handoff and how follow-ups are tracked. If useful, I can send the checklist before we discuss anything further.Use this wording only if it accurately describes your service and the checklist exists. A useful answer narrows the next step; it does not add unapproved promises, invented pricing or a claim that the recipient has already agreed.
If a reply is missing
Compare the original mailbox with Inbox and confirm the correct organization and sender account. For custom mailboxes, IMAP provides reading access; a working SMTP connection alone does not prove replies can be read. Record when the reply arrived and the relevant conversation reference. The supplied guides do not promise a synchronization interval, so do not infer a failure from an undocumented delay alone.